none
Can i expect samples for "Service for DRDA" in HIS 2013 SDK? RRS feed

  • Question

  • Hi,

    I get the information of releasing HIS 2013 SDK samples from link "http://social.technet.microsoft.com/Forums/lync/en-US/c465da10-8999-41ca-b1af-e61a80c51437/sdk-samples-in-his-2013?forum=biztalkhis" .

    Can i expect samples for "Service for DRDA" in HIS 2013 SDK?

    Actually i can see "Service for DRDA" object and its counters in Perfmon. But unable to produce instances in it.

    Friday, October 25, 2013 9:59 AM

Answers

  • The HIS 2013 SDK does not include a Service for DRDA sample. You can refer to the HIS 2013 Online documentation for information regarding the DRDA Service. For example, the following may be useful:

    http://msdn.microsoft.com/en-us/library/dn150134(v=bts.80).aspx

    http://msdn.microsoft.com/en-us/library/dn130703(v=bts.80).aspx

    http://msdn.microsoft.com/en-us/library/dn149048(v=bts.80).aspx

    http://msdn.microsoft.com/en-us/library/dn192296(v=bts.80).aspx

    http://msdn.microsoft.com/en-us/library/dn150200(v=bts.80).aspx

    Thanks...


    Stephen Jackson - MSFT

    • Marked as answer by swetha0318 Thursday, October 31, 2013 6:04 AM
    Friday, October 25, 2013 3:30 PM
  • As an FYI, the Microsoft Service for DRDA (Data Service) lets you connect IBM DB2 client programs to Microsoft SQL Server® databases. The Data Service takes advantage of Microsoft SQL Server connectivity services, Microsoft ADO.NET Framework, and Distributed Database Architecture (DRDA). The Data Service converts DRDA protocol code points and data formats to Microsoft ADO.NET Data Provider for SQL Server commands and data types. The DB2 client program can execute dynamic SQL statements, bind and execute static SQL packages, and call stored procedures. The Data Service converts and maps DB2 static SQL packages and statements into SQL Server stored procedures, enabling interoperability between DRDA-enabled application requesters and remote SQL Server databases.

    You need 'proper' rights on the host to modify SYSIBM tables (LOCATIONS, IPNAMES, IPLIST, USERNAMES) in order to 'route' the calls from DB2 z/OS to SQL. Once it's all set up, a simple test is from QMF to do a "select * from NWIND.DBO.CUSTOMERS" (or some other database/table). The LOCATIONS table contains the name of the SQL Database, a 'linkname', port used by SQL Server for DRDAAS. The other 3 tables contain IP Address, user names. IPLIST is used for fault tolerant failover.

    If you have further questions on this, please let me know. It's not exactly easy to setup, as part of this can involve (in migration scenario's) doing a bind copy package from DB2 z/OS to SQL Server (which creates stored procedures from the packages). Then your program on the host could make a call to the stored procedures in SQL, and should behave as if talking to DB2 z/OS at a remote location.

    Thanks,

    Charlie


    Charles Ezzell

    Tuesday, October 29, 2013 3:19 PM

All replies

  • The HIS 2013 SDK does not include a Service for DRDA sample. You can refer to the HIS 2013 Online documentation for information regarding the DRDA Service. For example, the following may be useful:

    http://msdn.microsoft.com/en-us/library/dn150134(v=bts.80).aspx

    http://msdn.microsoft.com/en-us/library/dn130703(v=bts.80).aspx

    http://msdn.microsoft.com/en-us/library/dn149048(v=bts.80).aspx

    http://msdn.microsoft.com/en-us/library/dn192296(v=bts.80).aspx

    http://msdn.microsoft.com/en-us/library/dn150200(v=bts.80).aspx

    Thanks...


    Stephen Jackson - MSFT

    • Marked as answer by swetha0318 Thursday, October 31, 2013 6:04 AM
    Friday, October 25, 2013 3:30 PM
  • Hi, 

    What kind of sample are you looking about ?

    Best Regards,



    Steve Melan - BCEE My Blog : http://stevemelan.wordpress.com

    Friday, October 25, 2013 5:57 PM
  • As an FYI, the Microsoft Service for DRDA (Data Service) lets you connect IBM DB2 client programs to Microsoft SQL Server® databases. The Data Service takes advantage of Microsoft SQL Server connectivity services, Microsoft ADO.NET Framework, and Distributed Database Architecture (DRDA). The Data Service converts DRDA protocol code points and data formats to Microsoft ADO.NET Data Provider for SQL Server commands and data types. The DB2 client program can execute dynamic SQL statements, bind and execute static SQL packages, and call stored procedures. The Data Service converts and maps DB2 static SQL packages and statements into SQL Server stored procedures, enabling interoperability between DRDA-enabled application requesters and remote SQL Server databases.

    You need 'proper' rights on the host to modify SYSIBM tables (LOCATIONS, IPNAMES, IPLIST, USERNAMES) in order to 'route' the calls from DB2 z/OS to SQL. Once it's all set up, a simple test is from QMF to do a "select * from NWIND.DBO.CUSTOMERS" (or some other database/table). The LOCATIONS table contains the name of the SQL Database, a 'linkname', port used by SQL Server for DRDAAS. The other 3 tables contain IP Address, user names. IPLIST is used for fault tolerant failover.

    If you have further questions on this, please let me know. It's not exactly easy to setup, as part of this can involve (in migration scenario's) doing a bind copy package from DB2 z/OS to SQL Server (which creates stored procedures from the packages). Then your program on the host could make a call to the stored procedures in SQL, and should behave as if talking to DB2 z/OS at a remote location.

    Thanks,

    Charlie


    Charles Ezzell

    Tuesday, October 29, 2013 3:19 PM
  • The information is useful.

    Thanks,

    ~Sweta

    Thursday, October 31, 2013 6:05 AM