Troubleshooting
Problem
My report of traffic from DB2 z/OS S-TAP has missing database name. Same report for distributed DB2 has the database name populated.
Cause
The concept of a database is not the same on z/OS compared to distributed DB2. See Definition of DB2 database on z/OS for full details.
In DB2 on z/OS a database is a grouping of objects that can be administered, not a grouping of processes that supports the operation of the database management system. There can be more than one 'database' defined within a DB2 Subsystem in DB2 on z/OS.
Due to this difference, the Guardium sniffer does not consider database name to be session level information for DB2 z/OS and the Session->Database Name attribute in reports will be blank.
Resolving The Problem
For DB2 z/OS traffic, the Guardium sniffer evaluates the database name on a per SQL basis. The database name can be found for reporting in Access Period->DB2 i/z Database attribute.
Session->Database Name attribute is expected to be blank.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22013735