Goal

To ensure that your client application can access the correct transactions on the mainframe.

Method

Using MCS, you can configure an installation of Runtime Service for CICS to access a specific host, and assign tasks to run on that host. There are two ways to make sure the client can find the correct installation of Runtime Service for CICS: one is to configure your task for failover and load balancing (or, use this feature and specify a single run-time service), and the other is to manually edit the client configuration file. In either case, unless you're running your client application on the same computer where you've installed Runtime Service for CICS, you'll also run the Synapta client installer to make sure the client application has the resources it needs.

To make tasks available for your applications, you use these components:

Before You Start

This How-To assumes that you have created a task in Task Builder for CICS and have access to an MCS server, which has a Synapta Services Builder manager installed. We recommend first using the How to Create a Task documentation. If you are using TCP/IP, you must have already installed the TCP/IP connectivity module on the host before you can run your tasks.

Steps

Following are the main steps you need to complete for this How-To. You can either publish your tasks to MCS and then do only the first four steps below, or you can skip publishing your tasks to MCS (you won't be able to use the failover and load balancing feature, or generate EJBs) and then do only steps 1, 2, 3, and 5 below.

  1. Start Runtime Service for CICS, and add it to MCS.

  2. Configure a host connection and map your task to it.

  3. Configure the client environment.

  4. Associate your task with a runtime server.

    -Or-

  5. Manually configure the client to use a runtime server.

  Attachmate