Cobol sample code using CICS web services

Certainly! Here's a sample COBOL code snippet that demonstrates how to use CICS web services:
IDENTIFICATION DIVISION.
PROGRAM-ID. MYWSPROGRAM.

DATA DIVISION.
WORKING-STORAGE SECTION.
01 WS-INPUT-PARAMS.
05 WS-CUSTOMER-ID PIC X(10).
05 WS-PRODUCT-ID PIC X(10).

01 WS-OUTPUT-DATA.
05 WS-RESPONSE-MSG PIC X(100).

LINKAGE SECTION.
01 WS-REQUEST-MESSAGE.
05 WS-OPERATION PIC X(20).
05 WS-PARAMS.
10 WS-CUSTOMER-ID PIC X(10).
10 WS-PRODUCT-ID PIC X(10).

01 WS-RESPONSE-MESSAGE.
05 WS-RESULT PIC X(100).

PROCEDURE DIVISION USING WS-REQUEST-MESSAGE WS-RESPONSE-MESSAGE.

EXEC CICS LINK PROGRAM('DFHWS-CLIENT')

COMMAREA(WS-REQUEST-MESSAGE)
LENGTH(LENGTH OF WS-REQUEST-MESSAGE)
RESP(WS-RESPONSE-MESSAGE)
LENGTH(LENGTH OF WS-RESPONSE-MESSAGE)
END-EXEC.

MOVE WS-RESPONSE-MESSAGE TO WS-RESPONSE-MSG.

EXEC CICS RETURN END-EXEC.

END PROGRAM MYWSPROGRAM.

Certainly! Here's a sample COBOL code snippet that demonstrates how to use CICS web services:

cobol

Copy code

IDENTIFICATION DIVISION.

PROGRAM-ID. MYWSPROGRAM.

DATA DIVISION.
WORKING-STORAGE SECTION.

01 WS-INPUT-PARAMS.

05 WS-CUSTOMER-ID PIC X(10).

05 WS-PRODUCT-ID PIC X(10).

01 WS-OUTPUT-DATA.

05 WS-RESPONSE-MSG PIC X(100).

LINKAGE SECTION.

01 WS-REQUEST-MESSAGE.

05 WS-OPERATION PIC X(20).

05 WS-PARAMS.

10 WS-CUSTOMER-ID PIC X(10).

10 WS-PRODUCT-ID PIC X(10).

01 WS-RESPONSE-MESSAGE.

05 WS-RESULT PIC X(100).

PROCEDURE DIVISION USING WS-REQUEST-MESSAGE WS-RESPONSE-MESSAGE.

EXEC CICS LINK PROGRAM('DFHWS-CLIENT')

COMMAREA(WS-REQUEST-MESSAGE)

LENGTH(LENGTH OF WS-REQUEST-MESSAGE)

RESP(WS-RESPONSE-MESSAGE)

LENGTH(LENGTH OF WS-RESPONSE-MESSAGE)

END-EXEC.

MOVE WS-RESPONSE-MESSAGE TO WS-RESPONSE-MSG.

EXEC CICS RETURN END-EXEC.

END PROGRAM MYWSPROGRAM.

In this sample code:

1. The program is identified as MYWSPROGRAM.

2. The working-storage section defines data structures for input parameters (WS-INPUT-
PARAMS) and output response (WS-OUTPUT-DATA).
3. The linkage section defines the input request message (WS-REQUEST-MESSAGE) and the
output response message (WS-RESPONSE-MESSAGE).
4. The PROCEDURE DIVISION uses the USING clause to indicate the input request message and
output response message parameters.
5. The EXEC CICS LINK statement invokes the DFHWS-CLIENT program, which is responsible for
invoking the CICS web service. The input request message is passed in COMMAREA, and the
output response message is obtained from RESP.
6. After receiving the response, the program moves the response message to WS-RESPONSE-
MSG for further processing.
7. Finally, the EXEC CICS RETURN statement returns control back to the calling program.

Please note that this is a basic example, and the actual implementation of the web service
operations and data structures will depend on your specific CICS web service and requirements.

In the above code - provide DFHWS-CLIENT code

I apologize for the confusion. The DFHWS-CLIENT mentioned in the previous code snippet is not the
actual program code. It is a placeholder representing the program name or transaction identifier
associated with the CICS web service.

When invoking a CICS web service, you would typically provide the actual program or transaction
name that corresponds to the web service endpoint in the EXEC CICS LINK statement. The
implementation of the DFHWS-CLIENT program would vary depending on your specific CICS setup
and the technology stack used for web service communication.

To invoke a CICS web service, you would typically follow these steps:

Define the CICS web service using the appropriate tools, which generate the necessary program or
transaction for web service invocation.

Obtain the actual program or transaction name associated with the web service endpoint.

Update the EXEC CICS LINK statement in your COBOL program with the correct program or
transaction name.

Here's an updated sample code snippet where you would replace 'DFHWS-CLIENT' with the actual
program or transaction name:
IDENTIFICATION DIVISION.
PROGRAM-ID. MYWSPROGRAM.

DATA DIVISION.
WORKING-STORAGE SECTION.
01 WS-INPUT-PARAMS.
05 WS-CUSTOMER-ID PIC X(10).
05 WS-PRODUCT-ID PIC X(10).
01 WS-OUTPUT-DATA.
05 WS-RESPONSE-MSG PIC X(100).

LINKAGE SECTION.
01 WS-REQUEST-MESSAGE.
05 WS-OPERATION PIC X(20).
05 WS-PARAMS.
10 WS-CUSTOMER-ID PIC X(10).
10 WS-PRODUCT-ID PIC X(10).

01 WS-RESPONSE-MESSAGE.
05 WS-RESULT PIC X(100).

PROCEDURE DIVISION USING WS-REQUEST-MESSAGE WS-RESPONSE-MESSAGE.

EXEC CICS LINK PROGRAM('ACTUAL-PROGRAM-NAME')

COMMAREA(WS-REQUEST-MESSAGE)
LENGTH(LENGTH OF WS-REQUEST-MESSAGE)
RESP(WS-RESPONSE-MESSAGE)
LENGTH(LENGTH OF WS-RESPONSE-MESSAGE)
END-EXEC.

MOVE WS-RESPONSE-MESSAGE TO WS-RESPONSE-MSG.

EXEC CICS RETURN END-EXEC.

END PROGRAM MYWSPROGRAM.

Replace 'ACTUAL-PROGRAM-NAME' in the EXEC CICS LINK statement with the correct
program or transaction name associated with your CICS web service. Make sure to update
the code according to your specific CICS environment and web service implementation.

how the code for CICS WEB SERIVCE in above example look like

To provide a more complete example, here's a code snippet for a CICS web service program
that can be invoked using the EXEC CICS LINK statement in the COBOL program:

IDENTIFICATION DIVISION.
PROGRAM-ID. DFHWS-CLIENT.

DATA DIVISION.
WORKING-STORAGE SECTION.
01 WS-REQUEST-MESSAGE.
05 WS-OPERATION PIC X(20).
05 WS-PARAMS.
10 WS-CUSTOMER-ID PIC X(10).
10 WS-PRODUCT-ID PIC X(10).

01 WS-RESPONSE-MESSAGE.
05 WS-RESULT PIC X(100).

PROCEDURE DIVISION USING WS-REQUEST-MESSAGE WS-RESPONSE-MESSAGE.

 IF WS-OPERATION = 'GET_CUSTOMER_INFO' THEN
PERFORM PROCESS-GET-CUSTOMER-INFO
ELSE IF WS-OPERATION = 'UPDATE_CUSTOMER' THEN
PERFORM PROCESS-UPDATE-CUSTOMER
ELSE
MOVE 'Invalid Operation' TO WS-RESULT
END-IF.

EXEC CICS RETURN END-EXEC.

PROCESS-GET-CUSTOMER-INFO.
MOVE WS-CUSTOMER-ID TO WS-RESULT
... Perform the necessary logic to retrieve customer information ...

PROCESS-UPDATE-CUSTOMER.
MOVE WS-CUSTOMER-ID TO WS-RESULT
... Perform the necessary logic to update customer information ...

END PROGRAM DFHWS-CLIENT.

In this example:

The program is identified as DFHWS-CLIENT.

The working-storage section includes the data structure WS-REQUEST-MESSAGE, representing the
input request message sent from the COBOL program. It contains the operation name (WS-
OPERATION) and parameters (WS-CUSTOMER-ID and WS-PRODUCT-ID).

The working-storage section also includes the data structure WS-RESPONSE-MESSAGE, representing
the response message to be returned to the COBOL program.

The PROCEDURE DIVISION uses the USING clause to indicate the input request message and output
response message parameters.

Inside the PROCEDURE DIVISION, the program performs different actions based on the value of WS-
OPERATION.

The PROCESS-GET-CUSTOMER-INFO and PROCESS-UPDATE-CUSTOMER sections are placeholders for

the actual logic to retrieve and update customer information, respectively. You would implement the
necessary COBOL code within these sections to perform the desired operations.

After processing the request, the program sets the result in WS-RESULT, which will be returned to the
calling COBOL program.

Please note that this is a simplified example, and the actual implementation of the web service logic
and data processing will depend on your specific requirements and the existing COBOL application
logic. Adapt the code as per your specific needs and incorporate the appropriate processing logic for
your CICS web service.

For the above example - how the WSDL will look like

To complement the example code, here's an example of how the corresponding WSDL (Web Service
Description Language) might look like for the CICS web service:
xml
copy code<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
targetNamespace="http://example.com/mywebservice">

<wsdl:types>
<xs:schema targetNamespace="http://example.com/mywebservice">
<xs:element name="getCustomerInfoRequest">
<xs:complexType>
<xs:sequence>
<xs:element name="customerID" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="getCustomerInfoResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="result" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="updateCustomerRequest">
<xs:complexType>
<xs:sequence>
<xs:element name="customerID" type="xs:string"/>
<xs:element name="productID" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="updateCustomerResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="result" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</wsdl:types>

<wsdl:message name="getCustomerInfoRequest">
<wsdl:part name="parameters" element="tns:getCustomerInfoRequest"/>
</wsdl:message>
<wsdl:message name="getCustomerInfoResponse">
<wsdl:part name="parameters" element="tns:getCustomerInfoResponse"/>
</wsdl:message>
<wsdl:message name="updateCustomerRequest">
<wsdl:part name="parameters" element="tns:updateCustomerRequest"/>
</wsdl:message>
<wsdl:message name="updateCustomerResponse">
<wsdl:part name="parameters" element="tns:updateCustomerResponse"/>
</wsdl:message>

<wsdl:portType name="MyWebServicePortType">
<wsdl:operation name="getCustomerInfo">
<wsdl:input message="tns:getCustomerInfoRequest"/>
<wsdl:output message="tns:getCustomerInfoResponse"/>
</wsdl:operation>
<wsdl:operation name="updateCustomer">
<wsdl:input message="tns:updateCustomerRequest"/>
<wsdl:output message="tns:updateCustomerResponse"/>
</wsdl:operation>
</wsdl:portType>

<wsdl:binding name="MyWebServiceBinding" type="tns:MyWebServicePortType">

<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="getCustomerInfo">
 <soap:operation soapAction="http://example.com/mywebservice/getCustomerInfo"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="updateCustomer">
<soap:operation soapAction="http://example.com/mywebservice/updateCustomer"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>

<wsdl:service name="MyWebService">
<wsdl:port name="MyWebServicePort" binding="tns:MyWebServiceBinding">
<soap:address location="http://example.com/mywebservice"/>
</wsdl:port>
</wsdl:service>

</wsdl:definitions>

This example WSDL describes the web service operations and message formats for the
MyWebService service. It includes elements for the getCustomerInfo and updateCustomer
operations, along with their corresponding input and output messages. The WSDL also specifies the
SOAP binding style, transport protocol, and endpoint address.

Note that this is a simplified example, and the actual WSDL structure may vary based on your specific
web service requirements, including additional elements for complex types, fault messages, or more
detailed binding options. Customize the WSDL to match your CICS web service implementation,
incorporating the necessary message formats and operation details.

For the above example - how the WSDL Binding procedure will look like ?

To provide a more complete example, here's a sample procedure for defining the WSDL binding in
the context of the previously mentioned WSDL:

cobol
IDENTIFICATION DIVISION.
PROGRAM-ID. WSDL-BINDING-PROCEDURE.

DATA DIVISION.
WORKING-STORAGE SECTION.
01 WSDL-BINDING-DOC.
05 WSDL-NAMESPACE-URI PIC X(100) VALUE "http://example.com/mywebservice".
05 SOAP-NAMESPACE-URI PIC X(100) VALUE "http://schemas.xmlsoap.org/wsdl/soap/".
05 HTTP-TRANSPORT PIC X(100) VALUE "http://schemas.xmlsoap.org/soap/http".

PROCEDURE DIVISION.

DISPLAY "<?xml version=""1.0"" encoding=""UTF-8""?>"

DISPLAY "<wsdl:definitions xmlns:wsdl=""http://schemas.xmlsoap.org/wsdl/"""
DISPLAY " xmlns:xs=""http://www.w3.org/2001/XMLSchema"""
DISPLAY " xmlns:soap=" "http://schemas.xmlsoap.org/wsdl/soap/" ""
DISPLAY " targetNamespace=""" WSDL-NAMESPACE-URI """>"
DISPLAY ""
 DISPLAY " <wsdl:binding name=""MyWebServiceBinding"" type=""tns:MyWebServicePortType"">"
DISPLAY " <soap:binding style=""document"" transport=""" HTTP-TRANSPORT """/>"
DISPLAY " <wsdl:operation name=""getCustomerInfo"">"
DISPLAY " <soap:operation soapAction=""" WSDL-NAMESPACE-URI "/getCustomerInfo""/>"
DISPLAY " <wsdl:input>"
DISPLAY " <soap:body use=""literal""/>"
DISPLAY " </wsdl:input>"
DISPLAY " <wsdl:output>"
DISPLAY " <soap:body use=""literal""/>"
DISPLAY " </wsdl:output>"
DISPLAY " </wsdl:operation>"
DISPLAY " <wsdl:operation name=""updateCustomer"">"
DISPLAY " <soap:operation soapAction=""" WSDL-NAMESPACE-URI "/updateCustomer""/>"
DISPLAY " <wsdl:input>"
DISPLAY " <soap:body use=""literal""/>"
DISPLAY " </wsdl:input>"
DISPLAY " <wsdl:output>"
DISPLAY " <soap:body use=""literal""/>"
DISPLAY " </wsdl:output>"
DISPLAY " </wsdl:operation>"
DISPLAY " </wsdl:binding>"
DISPLAY ""
DISPLAY " <wsdl:service name=""MyWebService"">"
DISPLAY " <wsdl:port name=""MyWebServicePort"" binding=""tns:MyWebServiceBinding"">"
DISPLAY " <soap:address location=""http://example.com/mywebservice""/>"
DISPLAY " </wsdl:port>"
DISPLAY " </wsdl:service>"
DISPLAY ""
DISPLAY "</wsdl:definitions>".

STOP RUN.

END PROGRAM WSDL-BINDING-PROCEDURE.

This COBOL program demonstrates a procedure to generate the WSDL binding section. It displays the
WSDL binding XML content using the DISPLAY statement. You can redirect the output to a file or
capture it as needed.

In this example:

1. The program is identified as WSDL-BINDING-PROCEDURE.

2. The working-storage section includes the data item WSDL-BINDING-DOC, which stores the
namespace URIs and transport details.
3. The PROCEDURE DIVISION displays the WSDL binding XML content line by line using DISPLAY
statements.
4. The values for the namespace URIs and transport are dynamically included in the displayed
XML.
5. The XML content follows the structure of the WSDL binding section, including the SOAP
binding style, SOAP operations, and the service endpoint address.

Note that this is a simplified example where the XML content is displayed using DISPLAY statements.
In a real implementation, you would typically write the XML content to a file or pass it to a web
service tool or library that handles WSDL generation.

Customize the code as needed to incorporate any additional elements or binding options required by
your specific CICS web service.