SAR File Creation

This topic provides the information required for SAR file creation with respect to IBD. For more detailed information on SAR File creation, refer to the IBM manual for z/OS Connect EE.

Steps for SAR file creation in z/OS Connect EE with respect to IBD:
  1. Start the IBM® Explorer for z/OS.
  2. Open the z/OS Connect Enterprise Edition perspective.
  3. Navigate to FileNew.
  4. Select the z/OSConnect EE Service Project wizard.



  5. The z/OSConnect EE Service Project window will appear.
  6. From the Project type drop-down field, select CICSCOMMAREA Service / CICSCHANNEL Service as an interface between z/OS Connect and IBD.
    Note:
    This information should be provided during SAR file creation.


  7. Click Finish.
  8. The z/OS Connect EE Service Project Editor dialog opens.
  9. Add the program name (e.g., CLAIMCI0) to the Program input area, as shown.

  10. Click the Configuration tab at the bottom of the screen.
  11. The Service Project Editor:  Configuration window will appear.
  12. Add the Connection reference, e.g.:  zconipic.

    Here, connection reference (zconipic) is the ID used in the server.xml on the host side and the transaction ZSMI is a mirror transaction configured on the host side. ZSMI is a replica of the CSMI transaction, which CICS provides. We have to make a change in ZSMI to support IBD programs. TWASIZE should be defined as 1024.

    Figure 1. ZSMI Transaction definition
    ZSMI Transaction definition

    Figure 2. SERVER.XML at the host side configured liberty server
    SERVER.XML at the host side configured liberty server

    The user must define the new TCPIP Service in the CICS region, the bridge between the host liberty server and the CICS region.
    Along with the TCPIPS port in CICS, the z/OS Connect client workspace communicated with the z/OS Connect Liberty server through one port. This port should also be defined in SERVER.XML with the following annotation.



  13. Click the Definition tab at the bottom of the screen.
  14. Click Create Service Interface…
  15. Enter the Service interface name and click OK.

  16. Now, the user has created a new service interface file.
  17. In the Service Interface editor, click Import COBOL or PLI data Structures into the service interface.





    Note:
    • Copybook is the data structure supported on the host side. z/OS connect supports a copybook structure to transfer and retrieve the data to and from the mainframe.
    • Since EGL-generated COBOL uses String datatype as a pointer, z/OS connect will not support such datatype. Hence, the string data type is ignored inside the EGL program while using z/OS connect.
  18. Right-click on CICSClaimsService in the Project Explorer view.
  19. Navigate to z/OS Connect EEàExport z/OS Connect EE Service Archive.