Download PDF - IBM Redbooks

Example 8-31 shows the results of a -DB2 display thread command, indicating that a trusted
connection is established.
Example 8-31 Displaying a trusted connection
SERVER RA * 220 T73DIA001 SAPINST DISTSERV 0098 757
V485-TRUSTED CONTEXT=DB0TTRUSTSAP,
SYSTEM AUTHID=SAPINST,
ROLE=SAPR3
V437-WORKSTATION=*, USERID=SAPSYS,
APPLICATION NAME=SAPMSSY2
V442-CRTKN=9.12.5.63.50866.110811214831
V445-G90C053F.C6B2.110811214831=757 ACCESSING DATA FOR
::9.12.5.63
SERVER RA * 74 T73BTC012 SAPINST DISTSERV 0098 1025
V485-TRUSTED CONTEXT=DB0TTRUSTSAP,
SYSTEM AUTHID=SAPINST,
ROLE=SAPR3
V437-WORKSTATION=SAP_COLLECTOR_PERF, USERID=DDIC,
APPLICATION NAME=SWNC_TCOLL_STARTER
V442-CRTKN=192.10.10.1.58954.110812120216
V445-C00A0A01.E64A.110812120216=1025 ACCESSING DATA FOR
::192.10.10.1
DB2 10 supports only trusted connections from specific predefined TCP/IP addresses of the
application servers.
Tip: Before using trusted connection, check whether another user ID or group has
authority for system administrative privileges by using the following SQL statement:
SELECT * from SYSIBM.SYSUSERAUTH;
If the SAPR3 group or user SAPINST has SYSADM authority, revoke the administrative
authority before using a trusted context and connection:
REVOKE SYSADM FROM SAPR3;
For verification of trusted connections, we redefine the trusted context DB0TTRUSTSAP by
using the same SQL statement in Example 8-30 on page 135 and delete one of the attributes,
such as the IP address 9.12.5.63.
136 Running SAP Solutions with IBM DB2 10 for z/OS on the IBM zEnterprise System