Skip to main content

Native CICS region to MS SQL Server

  • February 21, 2025
  • 1 reply
  • 2 views
Bruce Cheatwood

I am new to Enterprise Server and am currently working on configuring the environment for an upcoming mainframe migration project.  Currently I am looking to set up my native COBOL CICS region to be able to interact with a MS SQL Server database.  I believe that I need to create an XA resource but I am not sure.  Is this the right direction and if so can someone point me to documentation for how to create the resource?  Thanks for the help.



------------------------------
Bruce Cheatwood
BWXT
Lynchburg VA US
------------------------------

    1 reply

    D
    • David SandsRocketeer
    • Rocketeer
    • February 28, 2025

    I am new to Enterprise Server and am currently working on configuring the environment for an upcoming mainframe migration project.  Currently I am looking to set up my native COBOL CICS region to be able to interact with a MS SQL Server database.  I believe that I need to create an XA resource but I am not sure.  Is this the right direction and if so can someone point me to documentation for how to create the resource?  Thanks for the help.



    ------------------------------
    Bruce Cheatwood
    BWXT
    Lynchburg VA US
    ------------------------------

    Hi Bruce,

    Your correct. You need to use a XA Switch module. For SQL Server you can use ODBC or the MSSQL switch if you want 2 phase commit.

    This docs link cover the XA in general:

    https://docs.rocketsoftware.com/bundle/enterprisedeveloper_dg2_100_html/page/BKCACACONFU020.html

    and this covers what you need to know for building the switches:

    https://docs.rocketsoftware.com/bundle/enterprisedeveloper_dg2_100_html/page/GUID-F6E07E71-C0AB-4DB8-8884-42ED7B57E067.html

    Regards
    David



    ------------------------------
    David Sands
    Principal Support Engineer
    Rocket Forum Shared Account
    ------------------------------

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement