Enhanced Monitoring Support in DB2 10 for z/os

Transcription

1 Enhanced Monitoring Support in DB2 10 for z/os March 8, 2012 Mark Rader, IBM

2 Agenda Click to edit Master title style 2 Enhancements for problem determination and performance monitoring Monitoring information for static and dynamic SQL Introduction of STMT_ID Modified and new trace records System level monitoring enhancements Connections Threads Idle thread timeout

3 3 Enhanced Problem Determination and Performance Monitoring Support

4 Challenges Click to edit Master title style Prior to DB2 10 for z/os - 4 Support for problem determination and performance monitoring at a statement level is insufficient for both dynamic and static SQL. Statements that perform poorly are difficult to identify Statements that are the source of deadlocks, timeouts or unavailable resources are difficult to identify Performance goals cannot be set at the statement or application level. Statement information is insufficient in DB2 messages and traces. Identifying the specific SQL statement involved in a problem can be expensive The process to narrow down the application in question can be time-consuming. User, application developer, DBA or system administrator action may be required

5 Solutions Click to edit Master title style 5 In DB2 10 for z/os Enhanced problem determination and performance monitoring: Enables rapid problem diagnosis and resolution Messages and traces are captured with statement level information for both dynamic and static statements Provides complete statistics and performance metrics at the statement level for both dynamic and static statements Supports performance monitoring tools System-wide statement level detail is available in real time for tooling

6 Topics Click to edit Master title style Enhanced problem determination and performance monitoring support 6 Statement identifier (STMT_ID) support Trace enhancements Message enhancements

7 Statement Identifier Support Statement ID for static SQL statements 7 Statement ID is a unique value used to identify the specific statement across the DB2 system STMT_ID column is introduced in SYSIBM.SYSPACKSTMT table STMT_ID column is created in DB2 10 CM, as ADD COLUMN, with type INT. Column is ALTERed to BIGINT in the beginning of ENFM process Population of column values begins in ENFM REORG phase for the existing pre-db2 10 packages

8 Statement Identifier Support Statement ID for static SQL statements, continued 8 For pre-db2 10 packages, a REBIND is needed for those users who want to utilize enhanced messages and traces that provide statement ID information. For packages created in DB2 10 NFM, STMT_ID column is populated once the package is bound successfully. Once the package is bound or rebound, SYSIBM.SYSPACKSMT is in sync with the DB2 Directory in SPT01.

9 Statement Identifier Support Statement ID for dynamic SQL statements 9 Statement ID generated for dynamic statements prior to DB2 10 In DB2 10, statement ID is externalized in traces and messages Statement ID is a unique value within each DB2 subsystem Statement ID is only generated for dynamic statements that qualify to be inserted into the dynamic statement cache. Excludes dynamic DDL statements and dynamic LOCK TABLE statements In DB2 10, a predefined statement ID of 1 is reserved for dynamic DDL statements and LOCK TABLE statements

10 Trace Enhancements Click to edit Master title style 10 MONITOR CLASS 29 The new MONITOR CLASS 29 is introduced to facilitate collection of statement level statistics for both static and dynamic statements at the system level IFCIDs 316, 318, 401 and 400 are part of MONITOR CLASS 29 IFCID 316 existed prior to DB2 10 and provides statement detail information for dynamic statements To collect IFCID 316 trace record, IFCID 318 needs to be enabled. IFCID 318 is a switch, not an external record IFCID 401, new in DB2 10, provides statement detail information for static statements To collect IFCID 401 trace record, IFCID 400 need to be enabled. IFCID 400 is a switch, not an external record

11 Trace Enhancements Click to edit Master title style MONITOR CLASS 29, continued 11 IFCID 316 Has IFI READS capability, as in DB2 9 In DB2 10, IFCID 316 enhanced to have an event based trigger When a statement is evicted from the dynamic statement cache, an IFCID 316 record is written describing the single statement and the final cached statement level statistics for the statement

12 Trace Enhancements Click to edit Master title style MONITOR CLASS 29, continued 12 IFCID 401 Has IFI READS capability When an IFI READS request is received, all the static statements in the EDM pool will have their statement level detail externalized Each IFCID 401 record can contain up to 5,000 statements Multiple IFCID 401 records can be returned on a IFI READS request IFCID 401 has an event based trigger When a statement is evicted from the EDM pool, an IFCID 401 record is written describing the single statement and the final cached statement level statistics for the statement Statements returned via IFCID 401 READS can be filtered using WQAL fields

13 Trace Enhancements Click to edit Master title style Other IFCID enhancements 13 IFCID 58 (end SQL) Enhanced to return statement type, statement ID and statement level performance metrics New section of statement type, statement ID and statement statistics details provided at the end of statement execution IFCIDs 63 and 350 (SQL statement), 124 (SQL statement record), 172 (deadlock), 196 (timeout), and 337 (lock escalation) Enhanced to return statement type and statement ID IFCID 65 (open cursor) Enhanced to trace cursor attribute on the implicit commit request IFCID 66 (close cursor) Enhanced to trace implicit close statement

14 Message Enhancements THREAD-INFO token 14 Many messages enhanced to include THREAD-INFO token THREAD-INFO token enhanced to include statement type, statement ID, and role name information Above applies to message IDs: DSNL030I DSNV436I DSNL027I DSNI031I DSNT318I DSNT375I DSNT376I DSNT377I DSNT378I

15 Message Enhancements Example of DSNT375I message 15 DSNT375I > PLAN=DSNTEP3 WITH 915 CORRELATION-ID=RUNTEP1B CONNECTION-ID=BATCH LUW-ID=USIBMSY.SYEC1DB2.C6C38C788498=7 THREAD- INFO=ADMF001:*:*:*:DYNAMIC:7:AVERYLONGROLENAMEROLE1 IS DEADLOCKED WITH PLAN=DSNTEP3 WITH CORRELATION-ID=RUNTEP1A CONNECTION-ID=BATCH LUW-ID=USIBMSY.SYEC1DB2.C6C38C76D2CD=5 THREAD-INFO=ADMF001:*:*:*:DYNAMIC:5:* ON MEMBER VA1B

16 Message Enhancements Example of DSNT375I message, continued For Thread 1 THREAD-INFO= ADMF001:*:*:*:DYNAMIC:7:AVERYLONGROLENAMEROLE1 The statement involved in this Deadlock situation in Thread 1 is a dynamic statement with statement ID 7 Thread 1 is running under a role name called AVERYLONGROLENAMEROLE1 For Thread 2 THREAD-INFO=ADMF001:*:*:*:DYNAMIC:5:* The statement involved in this Deadlock situation in Thread 2 is a dynamic statement with statement ID 5 Note: When the information is not available, an asterisk (*) is displayed in the THREAD-INFO token 16

17 Message Enhancements Example of DSNT375I message, continued 17 Since both statements in the example are dynamic statements, query against SYSIBM.DSN_STATEMENT_CACHE_TABLE using the provided statement IDs in the message to find out more about these statements Before querying the DSN_STATEMENT_CACHE_TABLE Execute EXPLAIN STMTCACHE STMTID :SID; command to externalize this statement from the dynamic statement cache Each row in the table contains information about a statement in the cache as well as the statistics that reflect the execution of the statement

18 Message Enhancements Click to edit Master title style 18 Example of DSNT375I message, continued A sample query SELECT PROGRAM_NAME, COLLID, STMT_TEXT FROM SYSIBM.DSN_STATEMENT_CACHE_TABLE WHERE STMT_ID=7; If the statements involved are static statements, query SYSIBM.SYSPACKSTMT using the provided statement ID A sample query SELECT NAME, COLLID, CONTOKEN, STATEMENT FROM SYSIBM.SYSPACKSTMT WHERE STMT_ID=7; When IFCID 172 is active, an IFCID 172 record should also be written including statement type and statement ID when a deadlock occurs

19 19 System Level Monitoring Enhancements including PM28500 function

20 Challenges Click to edit Master title style Prior to DB2 10 for z/os - 20 DB2 provides three parameters in DSNZPARM to manage these aspects of distributed resources: MAXDBAT maximum number of concurrently active DBATs DB2 9 and prior: up to 1,999 can be specified DB2 10: up to 19,999 can be specified CONDBAT maximum number of concurrent inbound connections Up to 150,000 can be specified IDTHTOIN Idle Thread Time Out Interval number of seconds that an active server thread is allowed to remain idle These values apply to any threads or connections in the subsystem All threads or connections are treated with equal importance

21 Impact to Customers Click to edit Master title style Prior to DB2 10 for z/os 21 A single subsystem value means resources cannot be allocated by business area or priority Vice President s request for connection or thread is equal to summer intern s request Numerous low priority threads can reduce access for high priority threads Customers may be forced to use other means to prioritize thread and connection requests E.g. DB2 Connect Server Gateways Single idle thread timeout value may not reflect behavior of all application threads

22 Solutions Click to edit Master title style 22 In DB2 10 for z/os Profile table support for monitoring active threads, connections and idle thread timeouts provides control with greater granularity Remote connections and remote threads that access DB2 10 for z/os through TCP/IP Customers can monitor resources and behaviors according to business priorities DBAs have greater flexibility and control in managing distributed resources for particular business clients, applications or users Profile support removes a dependency on DB2 Connect Gateway configuration This function requires DB2 10 for z/os NFM

23 Topics Click to edit Master title style System level monitoring enhancements 23 Implementation steps Defining profiles Specifying monitoring functions and message level Monitoring functions: results Possible scenarios

24 Implementation Steps To monitor system level activities: 24 Create profile tables and indexes See Appendix for DDL of four tables and three indexes required User only manages two tables, DB2 handles the others Define profile(s) to specify what resources to monitor Eight exclusive filtering categories Define monitoring function(s) and message level Load or reload profile tables START PROFILE command Optional: Stop monitoring STOP PROFILE command

25 Profile and Attribute tables: simplified example 25 SYSIBM.DSN_PROFILE_TABLE ROLE AUTHID LOCATION PRDID COLLID PKGNAME PROFILEID PROFILE_ ENABLED Tom 20 Y JCC Y TEST.SVL.IBM.COM 22 Y SYSIBM.DSN_PROFILE_ATTRIBUTES ProfileID Keywords Attribute1 Attribute2 Attribute3 Attribute Timestamp 20 MONITOR THREADS EXCEPTION MONITOR IDLE THREADS WARNING MONITOR CONNECTIONS EXCEPTION MONITOR THREADS EXCEPTION

26 Defining Profiles Click to edit Master title style Specify the resources to monitor 26 Insert row(s) in the DSN_PROFILE_TABLE A row in this profile table defines one filtering scope for connections or threads subject to monitoring There are twelve supported filtering criteria used to identify the threads or connections to monitor. These criteria are determined by the contents of one or two columns in the profile table. There are eight exclusive categories to specify monitoring These categories are indicated by color in the following slides Update existing rows in the DSN_PROFILE_TABLE to change monitoring targets

27 Defining Profiles Click to edit Master title style 27 Filtering criteria Client IP address or client domain name 1. Client IP address or domain name (defined in LOCATION column) Client Product ID 2. Client Product ID (defined in PRDID column) Role name, Authorization ID 3. Role name + Authorization ID (defined in ROLE and AUTHID columns) 4. Role name (defined in ROLE column) 5. Authorization ID (defined in AUTHID column) Collection ID, Package name 6. Collection ID + Package name (defined in COLLID and PKGNAME columns) 7. Collection ID (defined in COLLID column) 8. Package name (defined in PKGNAME column)

28 Defining Profiles Click to edit Master title style Filtering criteria, added via APAR PM Location name or Location alias 9. Server location name or server location alias that Client tries to connect to (defined in LOCATION column) Client Application Name 10. End Client Application name (defined in CLIENT_APPLNAME column) Client User ID 11. End Client User ID (defined in CLIENT_USERID column) Client Workstation Name 12. End Client workstation name (defined in CLIENT_WRKSTNNAME column)

29 Defining Profiles Column details Click to edit Master title style 29 LOCATION column accepts three formats IP address : IPv4 dotted-decimal (e.g ) or IPv6 colon-hex format (e.g. 2001:DB8::8:800:200C:417A) Domain name, such as TEST.US.IBM.COM Location name string: 1-16 byte string, such as STLEC1B Support for location name added via PM28500 GROUP_MEMBER applies to members of a data sharing group Blank: valid profile row applies to any member of the data sharing group Non-blank: Value represents member name and valid row applies only to that member of the data sharing group

30 Defining Profiles Click to edit Master title style Default filter support, via APAR PM A single byte asterisk * placed in any of the filtering columns in DSN_PROFILE_TABLE defines a default filter scope Default filter scope matches all threads or connections that are not matched by other profile table rows

31 Defining Profiles Click to edit Master title style Multiple qualified profile rows may match a thread or connection 31 If multiple filtering criteria are specified from the same category in different profile rows, DB2 uses one profile row based on precedence rule within the category. For example: ROLE takes precedence over AUTHID COLLID takes precedence over PKGNAME The more completely defined profile row is used. For example: One profile row specifies ROLE and AUTHID, and both match Another profile row specifies ROLE and matches DB2 uses the profile row that specifies both ROLE and AUTHID

32 Defining Profiles Click to edit Master title style Multiple qualified profile rows may match a thread or connection 32 If multiple filtering criteria are specified from different categories in different profile rows, DB2 uses all profile rows that are qualified and match to the thread or connection. For example: One profile row specifies AUTHID and matches the thread or connection Another profile row specifies PRDID and matches the thread or connection DB2 applies both profile rows to monitor the thread or connection

33 Specifying Monitoring Functions Insert or update rows in DSN_PROFILE_ATTRIBUTES 33 PROFILEID identifies filtering criteria for threads or connections KEYWORD column identifies monitoring function MONITOR CONNECTIONS - Subject to filtering on IP address or domain name only MONITOR THREADS MONITOR IDLE THREADS ATTRIBUTE1 specify WARNING or EXCEPTION and message level DIAGLEVEL1 DSNT771I message issued with minimal information (default) DIAGLEVEL2 DSNT772I message issued with detailed information

34 Specifying Monitoring Functions Insert or update rows in DSN_PROFILE_ATTRIBUTES 34 ATTRIBUTE2 specify threshold (zero or positive value) For MONITOR CONNECTIONS - Number of total connections for this profile Cannot exceed CONDBAT value in DSNZPARM For MONITOR THREADS Number of active threads for this profile Cannot exceed MAXDBAT value in DSNZPARM For MONITOR IDLE THREADS Seconds thread can remain idle Overrides IDTHTOIN value in DSNZPARM for threads monitored by this profile

35 Specifying Message Levels DIAGLEVEL1 or DIAGLEVEL2 DIAGLEVEL1 DSNT771I message at most once every 5 minutes for any profile threshold exceeded. DSNT771I csect-name A MONITOR PROFILE condition-type CONDITION OCCURRED numberof-time TIME(S). Minimum console activity and limited message information Refer to statistics trace records for accumulated occurrences of specific profile threshold exceeded under a specific profile ID. DIAGLEVEL2 DSNT772I message at most once every 5 minutes for each unique occurrence of the profile threshold exceeded in a specific profile ID DSNT772I csect-name A MONITOR PROFILE condition-type CONDITION OCCURRED numberof-time TIME(S) IN PROFILE ID=profile-id WITH PROFILE FILTERING SCOPE=filtering-scope WITH REASON=reason Statistics class 4 IFCID 402 record written at statistics interval 35

36 Monitoring Functions: Results MONITOR CONNECTIONS 36 Remember: only if filtering on IP address or domain name If threshold in ATTRIBUTE2 exceeded, and: WARNING specified in ATTRIBUTE1 Connection request accepted Console message issued (DSNT771I or DSNT772I) EXCEPTION specified in ATTRIBUTE1 Connection request rejected Console message issued (DSNT771I or DSNT772I)

37 Monitoring Functions: Results MONITOR THREADS 37 If threshold in ATTRIBUTE2 exceeded, and: WARNING specified in ATTRIBUTE1 Thread continues, DSNT771I or DSNT772I issued EXCEPTION specified in ATTRIBUTE1 Console message issued (DSNT771I or DSNT772I) If IP address or domain name filtering, thread suspended until next DBAT is available and the number of monitored threads is under the ATTRIBUTE2 threshold Number of threads suspended: up to the value of (CONDBAT threshold) If any other filtering criteria used, thread suspended until next DBAT is available and the number of monitored threads is under the ATTRIBUTE2 threshold Number of threads suspended: up to value in ATTRIBUTE2 If number of suspended threads exceeds value in ATTRIBUTE2, DB2 fails the next connection request and returns SQLCODE

38 Monitoring Functions: Results MONITOR IDLE THREADS 38 If threshold in ATTRIBUTE2 exceeded, and: WARNING specified in ATTRIBUTE1 Thread continues to stay idle Console message issued (DSNT771I or DSNT772I) EXCEPTION specified in ATTRIBUTE1 Thread subject to cancellation Console message issued (DSNT771I or DSNT772I)

39 Monitoring Click Functions: to edit Master Results title style - Example ROLE DB2DEV AUTHID Tom LOCATION TEST.SVL.IBM.COM PRDID COLLID 39 SYSIBM.DSN_PROFILE_TABLE PKGNAME PROFILEID 1 2 PROFILE_ ENABLED Y Y JCC Y ProfileID Keyword MONITOR THREADS MONITOR CONNECTIONS MONITOR IDLE THREADS Attribute1 EXCEPTION_DIAG LEVEL2 WARNING EXCEPTION_DIAG LEVEL1 SYSIBM.DSN_PROFILE_ATTRIBUTES Attribute Timestamp 10 active threads Queue , *Reject 21 st Issue DSNT772I Above 50 connections, continue to accept connections Issue DSNT771I After 300 seconds, cancel idle thread Issue DSNT771I * If monitoring for PROFILEID 1 were based on IP Address or Domain Name, then do not reject 21 st, but queue until reach CONDBAT

40 Load or Reload Profile Table START PROFILE Command 40 START PROFILE command is a member specific command, not a group wide command. In data sharing START PROFILE needs to be issued for each member that is target for system level monitoring. Once START PROFILE is issued, DB2 starts to monitor the next thread or connection that matches profiles in effect Valid rows with Y in PROFILE_ENABLED column are in effect First START PROFILE command loads profile table and begins monitoring Subsequent START PROFILE command reloads profile table Profile actions and thresholds can be dynamically updated and refreshed without issuing STOP PROFILE

41 Profile Monitoring Operations Click to edit Master title style 41 Use history tables to know what profiles and profile monitoring functions are in effect (accepted or rejected) SYSIBM.DSN_PROFILE_HISTORY SYSIBM.DSN_PROFILE_ATTRIBUTES_HISTORY IFCID 402 trace record Statistics Class 4 record When a profile warning or exception occurs, an IFCID 402 trace record is written at a statistical interval which is defined in the STATIME ZPARM Each statistics trace record written can contain up to 500 unique profiles Multiple trace records can be written if there are more than 500 unique profiles whose profile thresholds are exceeded in a given STATIME interval

42 42 Questions?

43 43 Examples

44 Unqualified Rows in DSN_PROFILE_TABLE ROLE Profiles 11 and 15 invalid different filtering categories in same AUTHIDrow LOCATION PRDID COLLID PKGNAME PROFILEID DB2DEV Tom 10 PROFILE_ ENABLED Y 44 DB2DEV SQL Y Tom 12 Y JCC Y TEST.SVL. IBM.COM 14 Y TEST.SVL. IBM.COM COLL1 15 Y SYSIBM.DSN_PROFILE_HISTORY for rows 11, 15 include text REJECTED and the reason for rejection in the STATUS column

45 Validating Profile Rows Sample rows in DSN_PROFILE_HISTORY 45 PROFILEID : STATUS (DSN_PROFILE_HISTORY) 10 : ACCEPTED : : REJECTED - INVALID SCOPE SPECIFIED. FOR SYSTEM LEVEL MONITORING, ONLY IP ADDR, PRDID, ROLE AND/OR AUTHID, COLLECTION ID AND/OR PACKAGE NAME CAN BE SPECIFIED ACCEPTED 13 : ACCEPTED : : ACCEPTED - DOMAIN NAME IS RESOLVED INTO IP ADDRESS ::FFFF: REJECTED - INVALID SCOPE SPECIFIED. FOR SYSTEM LEVEL MONITORING, ONLY IP ADDR, PRDID, ROLE AND/OR AUTHID, COLLECTION ID AND/OR PACKAGE NAME CAN BE SPECIFIED

46 Multiple Profiles Example 1 Multiple profiles that filter on different categories can apply Multiple profiles that filter on one category most specific applies If Tom uses ROLE DB2DEV, PROFILEID 10 applies 46 ROLE AUTHID LOCATION PRDID COLLID PKGNAME PROFILEID PROFILE_ ENABLED DB2DEV Tom 10 Y Tom 12 Y JCC Y TEST.SVL. IBM.COM 14 Y

47 Multiple Profiles Example 2 47 SYSIBM.DSN_PROFILE_TABLE ROLE AUTHID LOCATION PRDID COLLID PKGNAME PROFILEID PROFILE_ ENABLED Tom 20 Y JCC Y TEST.SVL.IBM.COM 22 Y SYSIBM.DSN_PROFILE_ATTRIBUTES ProfileID Keywords Attribute1 Attribute2 Attribute3 Attribute Timestamp 20 MONITOR THREADS EXCEPTION MONITOR IDLE THREADS WARNING MONITOR CONNECTIONS EXCEPTION MONITOR THREADS EXCEPTION 20 * * If 22 MONITOR CONNECTIONS row deleted, then queue requests over 21 up to CONDBAT

48 Multiple Profiles Example 2 Details 48 SYSIBM.DSN_PROFILE_TABLE PROFILEID 20 row defines a profile that matches all the threads that are run by user Tom. PROFILEID 21 row defines a profile that matches all the threads that are using client driver level JCC PROFILEID 22 row defines a profile that matches all the threads and connections that are connecting from Domain Name TEST.SVL.IBM.COM SYSIBM.DSN_PROFILE_ATTRIBUTES All threads that are executed under user Tom connecting from domain name TEST.SVL.IBM.COM using client driver level JCC03570 are monitored by the profiles identified by PROFILEID 20, 21, and 22. PROFILEID 20, 21, and 22 are all active and qualified profiles from different filtering categories that may match the current thread execution environment, therefore all three profiles are applied.

49 Multiple Profiles Example 2 Results 49 If Tom attempts to execute more than 10 concurrent threads, DB2 suspends up to 10 more requests based on PROFILEID 20 with EXCEPTION NOT by PROFILEID 22 because PROFILEID 20 has a lower threshold value in the MONITOR THREADS keyword. The 21st concurrent connection from AUTHID Tom receives If a thread stays idle for more than 3 minutes, DB2 issues a DSNT771I console message and lets the thread continue to stay idle based on PROFILEID 21 with a WARNING action defined. All connections from domain name TEST.SVL.IBM.COM are monitored by the rows identified by PROFILEID 22 as the connection is subject to the filtering on IP Address/Domain Name only. When the number of connections exceeds 45, DB2 rejects any subsequent connection request, since PROFILEID 22 has an EXCEPTION action defined. The lower green star signifies that the total number of threads from this ip address/domain name are limited to 20, plus 25 connections (see 45 in row immediately above); the 46th concurrent connection is rejected. Since Tom is limited to 10 active threads, what is the meaning of PROFILEID 22 with MONITOR THREADS keyword? Other users, other than Tom, can have active threads, up to a total of 20. So, if Tom already has 10 active threads (limited by PROFILEID 20), Lisa can have another 10 active threads from the same IP address/domain name. Between Tom and Lisa (and any others from this IP address) there can be 20 active threads and 25 suspended requests (inactive connections). Note that if the third row of the attribute table (PROFILEID 22, MONITOR CONNECTIONS) were not present, then the fourth row (PROFILEID 22, MONITOR THREADS) allows inactive connections up to the number in CONDBAT, because the filtering category is IP address/domain name..

50 50 Appendix

51 DDL of SYSIBM.DSN_PROFILE_TABLE 51 CREATE TABLE SYSIBM.DSN_PROFILE_TABLE ( "AUTHID" VARCHAR(128),"PLANNAME" VARCHAR(24),"COLLID" VARCHAR(128),"PKGNAME" VARCHAR(128),"LOCATION" VARCHAR(254) -- this change is done via APAR PM28500,"PROFILEID" INTEGER NOT NULL PRIMARY KEY GENERATED BY DEFAULT AS IDENTITY,"PROFILE_TIMESTAMP" TIMESTAMP NOT NULL WITH DEFAULT,"PROFILE_ENABLED" CHAR(1) NOT NULL DEFAULT 'Y',"GROUP_MEMBER" VARCHAR(24),"REMARKS" VARCHAR(762),"ROLE" VARCHAR(128),"PRDID" CHAR(8),"CLIENT_APPLNAME" VARCHAR(255) -- this change is done via APAR PM28500,"CLIENT_USERID" VARCHAR(255) -- this change is done via APAR PM28500,"CLIENT_WRKSTNNAME" VARCHAR(255) -- this change is done via APAR PM28500 ) IN DSNOPTDB.DSNOPTTS CCSID UNICODE;

52 DDL of SYSIBM.DSN_PROFILE_HISTORY 52 CREATE TABLE SYSIBM.DSN_PROFILE_HISTORY ( "AUTHID" VARCHAR(128),"PLANNAME" VARCHAR(24),"COLLID" VARCHAR(128),"PKGNAME" VARCHAR(128),"LOCATION" VARCHAR(254) -- this change is done via APAR PM28500,"PROFILEID" INTEGER NOT NULL,"PROFILE_TIMESTAMP" TIMESTAMP NOT NULL,"PROFILE_ENABLED" CHAR(1) NOT NULL,"GROUP_MEMBER" VARCHAR(24),"STATUS" VARCHAR(254),"ROLE" VARCHAR(128),"PRDID" CHAR(8),"CLIENT_APPLNAME" VARCHAR(255) -- this change is done via APAR PM28500,"CLIENT_USERID" VARCHAR(255) -- this change is done via APAR PM28500,"CLIENT_WRKSTNNAME" VARCHAR(255) -- this change is done via APAR PM28500 ) IN DSNOPTDB.DSNOPTTS CCSID UNICODE;

53 DDL of SYSIBM.DSN_PROFILE_ATTRIBUTES 53 CREATE TABLE SYSIBM.DSN_PROFILE_ATTRIBUTES ( "PROFILEID" INTEGER NOT NULL REFERENCES SYSIBM.DSN_PROFILE_TABLE ON DELETE CASCADE,"KEYWORDS" VARCHAR(128) NOT NULL,"ATTRIBUTE1" VARCHAR(1024),"ATTRIBUTE2" INTEGER,"ATTRIBUTE3" FLOAT,"ATTRIBUTE_TIMESTAMP" TIMESTAMP NOT NULL WITH DEFAULT,"REMARKS" VARCHAR(762) ) IN DSNOPTDB.DSNOPTTS CCSID UNICODE;

54 DDL of DSN_PROFILE_ATTRIBUTES_HISTORY 54 CREATE TABLE SYSIBM.DSN_PROFILE_ATTRIBUTES_HISTORY ( "PROFILEID" INTEGER NOT NULL,"KEYWORDS" VARCHAR(128) NOT NULL,"ATTRIBUTE1" VARCHAR(1024),"ATTRIBUTE2" INTEGER,"ATTRIBUTE3" FLOAT,"ATTRIBUTE_TIMESTAMP" TIMESTAMP NOT NULL,"STATUS" VARCHAR(254) ) IN DSNOPTDB.DSNOPTTS CCSID UNICODE;

55 CREATE INDEX DDL for SYSIBM.DSN_PROFILE_TABLE 55 CREATE UNIQUE INDEX SYSIBM.DSN_PROFILE_TABLE_IX_ALL ON SYSIBM.DSN_PROFILE_TABLE ( "PROFILEID"); CREATE INDEX SYSIBM.DSN_PROFILE_TABLE_IX2_ALL ON SYSIBM.DSN_PROFILE_TABLE ( "PROFILE_ENABLED","AUTHID","PLANNAME","COLLID","PKGNAME","LOCATION" -- this change is done via APAR PM28500,"PRDID","ROLE","CLIENT_APPLNAME" -- this change is done via APAR PM28500,"CLIENT_USERID" -- this change is done via APAR PM28500,"CLIENT_WRKSTNNAME" -- this change is done via APAR PM28500,"GROUP_MEMBER","PROFILE_TIMESTAMP" DESC);

56 CREATE INDEX DDL for SYSIBM.DSN_PROFILE_ATTRIBUTES 56 CREATE UNIQUE INDEX SYSIBM.DSN_PROFILE_ATTRIBUTES_IX_ALL ON SYSIBM.DSN_PROFILE_ATTRIBUTES ( "PROFILEID","ATTRIBUTE_TIMESTAMP" DESC,"KEYWORDS","ATTRIBUTE1","ATTRIBUTE2","ATTRIBUTE3");

57 Filtering Criteria Click to edit Master title style Client Application Name 57 Defaults: IBM Data Server Driver for JDBC and SQLJ: db2jcc_application IBM Data Server Driver for ODBC and CLI: db2cli.exe DB2 Connect CLP: db2bp.exe From application on DB2 for z/os Foreground TSO Background TSO RRS attach Call attach (CAF) CICS attach 1 st 8 bytes of IMS attach 8 bytes: PSB name TSO logon userid job name correlation ID job name correlation id program name

58 Filtering Criteria Click to edit Master title style Client Application Name, cont. 58 Client application name can be set by application explicitly: DB2Connection.setDB2ClientApplicationInformation(String info) Set Client Information (sqleseti) One of RRS DSNRLE functions: SIGNON AUTH SIGNON CONTEXT SIGNON SET_CLIENT_ID WLM_SET_CLIENT_INFO stored procedure

59 Filtering Criteria Client User ID Click to edit Master title style 59 Default client end user ID is the primary authorization ID used to establish the connection Client user ID can be set by application explicitly DB2Connection.setDB2ClientUser(String info) Set Client Information (sqleseti) One of RRS DSNRLE functions: SIGNON AUTH SIGNON CONTEXT SIGNON SET_CLIENT_ID WLM_SET_CLIENT_INFO stored procedure

60 Filtering Criteria Click to edit Master title style Client Workstation Name 60 Default client workstation name is client host name or, for DB2 for z/os, connection type name. For example IBM Data Server Driver or DB2 Connect: client host name For remote application running in DB2 for z/os environment TSO foreground TSO background RRS Call attach CICS attach IMS attach TSO BATCH RRSAF DB2CALL CICS region name IMS region ID

61 Filtering Criteria Click to edit Master title style Client Workstation Name, cont. 61 Client workstation name can be set by application explicitly: DB2Connection.setDB2ClientWorkstation(String info) Set Client Information (sqleseti) One of RRS DSNRLE functions: SIGNON AUTH SIGNON CONTEXT SIGNON SET_CLIENT_ID WLM_SET_CLIENT_INFO stored procedure