This article describes a software update that lets the Microsoft Service for Distributed Relational Database Architecture (DRDA) activate permissions that are associated with an application role that's defined in a SQL Server database.
Software update informationA supported feature that changes the product's default behavior is now available from Microsoft Support. However, this feature is intended to change only the behavior that this article describes. Apply it only to systems that specifically require it.
This update is included in Cumulative Update 1 for Host Integration Server 2013.
After you apply the update, the Microsoft Service for DRDA is updated to support calling SQL Server system stored procedures, such as sp_setapprole. To call a SQL Server system stored procedure, such as sp_setapprole, you have to use a COBOL program on an IBM mainframe that uses static SQL to call the remote SQL Server system by using a CALL statement with parameters. The following example contains COBOL code that shows how to call the sp_setapprole stored procedure by passing two required parameters:
01 PASSWD1 PIC X(9).
MOVE 'approle1' TO ROLENAM1.
MOVE 'Password1' TO PASSWD1.
Frequently, access to data in a SQL Server databases is enabled based on application roles. By calling the sp_setapprole stored procedure through the Microsoft Service for DRDA, you let customers who use application roles manage access to SQL Server databases when they are being integrated with IBM DB2 databases.
Article ID: 2920658 - Last Review: 1 Apr 2014 - Revision: 1