Version 9.5 SP1
 —  Common Integration Scenarios  —

Calling COBOL on z/OS IMS BMP (Batch) from Integration Server

This document covers the following topics:


Introduction

graphics/cob2is-zos-ims-bmp.png

This scenario makes the following important assumptions:

Top of page

1: Extract the Interface of a COBOL Server

Follow the instructions for extracting COBOL, see Using the IDL Extractor for COBOL - Overview and choose Scenario I: Create New IDL and SVM if this is your first extraction. This process creates the following EntireX metafiles:

Top of page

1a: (Optional) Test the Extraction Results

Optionally, you can test the results of the extraction operation, using the EntireX IDL Tester.

  1. For the EntireX RPC Connection and the EntireX Direct RPC Connection method (not possible for other connection methods), test the COBOL Server backend using Test Software AG IDL from the Workbench:

    graphics/common_test-idlTester.png

    Note that the Broker and Server parameters contain the explicit route to call the server program, and you can optionally ping the connection from this client. See EntireX IDL Tester in the EntireX Workbench documentation.

  2. Check the IS log, the EntireX Adapter log, or the RPC logs. Applies to all connection methods.

Top of page

2: Generate the Connection and Application Services in Integration Server

Select the IDL file, and from the context menu choose Generate webMethods Connection from IDL file.... From the wizard, select an Integration Server instance and select the connection type.

graphics/common_generate-connectionType.png

Then select the namespace where you want to write the services to, and specify the connection properties.

graphics/common_generate-defineAdapterServices.png

Choose Finish. The connection service will be automatically enabled in the Integration Server.

Top of page

3: Test the Call from Integration Server to COBOL

From the Service Development perspective, refresh the package where the connection service was written, select the Adapter service, and use the service test to Run Service:

graphics/common_test-calc.png

This invokes the adapter service through the connection service.

In case of error or unexpected results, use the IDL Tester as described under Step 1a above.

Top of page