There are different styles (interface types) for calling a COBOL server.

	Extract the interface of the COBOL server program. See Using the IDL Extractor for COBOL - Overview.
	Generate REST resources, connection and adapter services in Integration Server.
	Execute the call from the REST client to the COBOL server program.

To determine the appropriate scenario

1. First it is important to know the interface type of your COBOL server. Analyzing the technique used to access the interface with COBOL and CICS statements is the safest way to determine this. The following interface types are available and are described in the IDL Extractor for COBOL documentation:

   • CICS with DFHCOMMAREA Calling Convention

   • CICS with Channel Container Calling Convention

   • CICS with DFHCOMMAREA Large Buffer Interface

   There is no clear and easy indication how to identify the interface type of a CICS COBOL server without COBOL and CICS knowledge. Below are some criteria that might help to determine the interface type. If you are unsure, consult a CICS COBOL specialist.

   • The payload size of the CICS COBOL server is greater than 32 KB:

     • In this case it is not a DFHCOMMAREA interface, because the DFHCOMMAREA is limited to 32 KB.

     • It could be a large buffer or channel container interface, which are only limited by the storage (memory) available to them.

   • The CICS COBOL server is located in a remote CICS region:

     • In this case it is not a large buffer interface, because large buffer programs must reside on the same CICS region as the caller, that is, the RPC Server for CICS.

     • It could be a DFHCOMMAREA or channel container interface, which can reside in a remote CICS region.

   Note:
   The most used interface type is the DFHCOMMAREA interface. Large buffer and channel container interfaces are used much less frequently.

2. Second, for the DFHCOMMAREA interface only, you need to decide for the zero footprint or the RPC Server for CICS approach. Here are some guidelines:

   Use the zero footprint approach if:

   • you are already using and familiar with ECI

   • you do not want to install any additional resources in your CICS environment

   Use the RPC Server for CICS if:

   • you are already using (or planning on using) EntireX Broker for extended messaging

When you are sure which interface type and approach you are using, continue with the appropriate scenario:

• Channel Container (zero footprint using CICS IPIC)

• Channel Container (minimal footprint using CICS Socket Listener)

• Channel Container

• DFHCOMMAREA (zero footprint using CICS IPIC)

• DFHCOMMAREA (zero footprint using CICS ECI)

• DFHCOMMAREA (using RPC Server for CICS)

• Large Buffer

• Large Buffer (minimal footprint using CICS Socket Listener)