Creating the BMS map set JCL IBM-CICS

Traditionally, JCL is used to compile and install the physical and symbolic description maps for use within CICS transactions. Another useful feature of the BMS Editor is functionality to generate JCL for a BMS map set that was created and saved into an existing z/OS project. The JCL is generated and written to an existing PDS on the z/OS.

We used the following process to generate the JCL for one of our map sets.

1. Establish a connection to the host

A z/OS project must be created, which is a PC-based representation of artifacts, PDSs, and data set members that also exist on the host. Any objects that are created or edited in the z/OS project are also created on the MVS™ host in real time. This makes development of projects for z/OS almost seamless as there is no need to worry about uploading or creating objects on the host as WD/z does this for you.

Before a z/OS project can be created, a connection to the host system needs to be established.

  1. In the Remote Systems view, expand New Connection → z/OS.
    A window appears, where the connection information is entered. This is shown in Figure. We called our Connection REDSC66. The host name is wtsc66.itso.ibm.com.
  2. Click Next. We kept all the defaults
  3. Figure : Defining a Remote Connection

    Figure : Defining a Remote Connection

  4. Click Finish. If the create of the Connection is successful, the Remote Systems view will report this, and there is an explorer view of the host that you can expand to show the file repositories that you want to view in the z/OS environment. This is seen in Figure.

Figure: A successful connection and Explorer view of the host file groups

Figure: A successful connection and Explorer view of the host file groups

2. Filtering and data set mapping tasks

Now that there is a connection to a host z/OS system, there are a couple of set up tasks to complete. These tasks ensure that the workstation view of the host and the file transfer to and from the host are customized to accommodate local naming conventions and workstation file extensions.

We customize the Remote Systems view of the host file subsystems through the filtering function in WD/z, and ensure that there are mapping rules in place to accommodate the differences in the naming of PDS members and Windows-based filenames.

Filtering the Explorer View of the host connection

The z/OS file systems contain hundreds of data sets and even more members, which you do not necessarily need to display. The tooling allows you to filter the data set and job names, just as you would by using the asterisk on the PDF Dslist function or the prefix command in SDSF on the host system.

As an example, in this book we are interested in the data sets associated with our CICS application CICSWSAP and in the jobs associated with our CICS region SCSCPJA6. The method to filter just these files is as follows:

  1. If not already connected, right-click the connection name in the Remote Systems Explorer view.
  2. Click Connect.
  3. To filter the JES job output to include the jobs associated with our CICS region, right-click JES → New → New JES Job Filter, as seen in Figure.
  4. Figure: Creating a filter for JES jobs

    Creating a filter for JES jobs

  5. Create the filter by entering strings and * for wildcards, as shown in Figure
  6. Figure : JES Job Filter

    JES Job Filter

  7. Enter a filter name, which will appear in the Explorer tree under the JES category, and then click Finish. The expanded view of your selected job has the same effect of sub-command ‘?’ in SDSF option ST, and you can view each of the outputs and perform the same sorts of functions as you would with the SDSF sub-commands.
  8. Similarly, for data set names, right-click MVS Files → New → Filter, and enter a filter string for the data sets that you want to be displayed in the expanded view of this Explorer tree. The result is shown in Figure.

Figure:A filtered data set view for our project

A filtered data set view for our project

z/OS File System Mapping

As part of the default z/OS perspective, there is a view on the work space called z/OS File System Mapping that provides a list of mapping criteria for the lowest level qualifier of a PDS and the workstation file extension. If there is a mapping defined, you can see the workstation file extensions in the Remote Systems view of the members in a PDS.

Use the following steps to add a map definition:

  1. Open the z/OS File System Mapping view.
    Use Window → Show View → z/OS File System Mapping if the view is not already on the work space.
  2. Choose the host name in the System pull-down field.
  3. Right-click the view, and select Add Data Set Mapping as seen in Figure.
  4. Figure: Adding a mapping rule between a PDS member and workstation filename

    Adding a mapping rule between a PDS member and workstation filename

  5. Enter the low-level qualifier of the PDS and the workstation file extension that it is to be mapped to, as in Figure 5-22. In this example we want to map any members in PDS called *.*.BMSMAPS to be given a file extension of .bms on the workstation view.
  6. Figure: Specifying the mapping rule

    Figure: Specifying the mapping rule

  7. Click OK, and the mapping criterion should now appear in the view.

3. Create a z/OS Project for the map set

To generate JCL for our BMS and work with a host z/OS system, including the utilization of the Editors in WD/z to edit existing BMS map sets, JCL, and other files, we need to create a z/OS Project and associate the map sets to that project.

Use the following steps to create an z/OS Project.

  1. Create a connection to the host, as in the previous section.
  2. Select File → New → Project.
  3. In the New Project panel, expand the z/OS view, and choose z/OS Project as in Figure.
  4. Figure :Creating a z/OS Project

    Figure :Creating a z/OS Project

  5. Click Next and enter a project name.
  6. Check the box to also create an MVS subproject as in Figure.
  7. Figure: Creating a subproject

    Figure: Creating a subproject

  8. Click Finish, and enter a subproject name.
  9. Click Next, and take all of the defaults, for now.

The new project should appear in the z/OS Projects view with the associated subproject and host name. This is seen in Figure.

Figure : z/OS Project Explorer view of z/OS project and subproject

Figure : z/OS Project Explorer view of z/OS project and subproject

4. Import map sets into the z/OS Project

You may already have several map sets created in your traditional CICS environment that you want to edit or copy. The BMS Editor provides a modern tooling technique to simplify this process. The BMS Editor can be used on existing map sets on a host system by importing them into a z/OS subproject, or map sets created locally can be copied into the z/OS Project from a local, eneral project type on the work space.

The effect of copying artifacts from a local project into a z/OS Project is that these are also created in the PDS on the host. In our demonstration, we will now allocate a PDS for the z/OS Project to hold our maps and map sets.

  1. Right-click the z/OS subproject name in the z/OS Projects Explorer view.
  2. Select New → Allocate PDS.
  3. This is shown in Figure.

    Figure: Allocating a PDS on the z/OS host

    Figure: Allocating a PDS on the z/OS host

  4. Provide a name for the PDS that conforms to your local naming conventions. The BMS Editor in WD/z only recognizes members of the PDS with a file extension of .bms, so check that there is a z/OS File System Mapping rule in effect for the name you give to the PDS. Alternately, you can create a mapping rule.
  5. Fill in the characteristics of the data set, or take the defaults, and then select Finish. If filtered, the name of the new PDS is displayed in the Remote Systems view, and it also appears in the z/OS Projects view in the sub-project.

5. Create the JCL for the map set

Use the following procedure to create the JCL for assembly of a map set:

  1. Right-click the .bms map set file in the z/OS Project folder.
  2. Select Properties.
  3. In the JCL Job Card and Data Set dialog, specify an existing data set to contain the generated JCL.
  4. In the BMS Settings dialog, click the step name, and then choose Edit step to customize the step name for your site. This is shown in Figure.
  5. Figure : Customizing map set properties

    Figure : Customizing map set properties

    This brings up an Options view where the destination libraries and procedure name can be edited according to your site specifications.

  6. Click OK when finished.
  7. Right-click the .bms set file name again.
  8. Select Generate JCL → For Assemble or Generate JCL → For Assemble Link.
  9. In the input dialog, specify the target JCL data set name and the member name. You can also choose to set a different job name.
  10. Click OK to complete the generation process.

6. Submit the JCL and test in CICS

Now we are ready to submit the JCL using the following steps.

  1. Right-click the generated JCL member in the data set in the Remote Systems view.
  2. Select Submit.
    Note: If the member name already exists, you are prompted to overwrite the member. If the target PDS does not exists, an error message is displayed.
  3. Use JES to view the output of the job.
  4. You can find the output in the library that was specified in the BMS Settings dialog.
  5. This map can now be tested in the CICS region with a CECI Send Map command.

Face Book Twitter Google Plus Instagram Youtube Linkedin Myspace Pinterest Soundcloud Wikipedia

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM-CICS Topics