CA SYSVIEW for DB2 on Z/OS Not generating AUDIT request report for secondary AUTHID option
Article ID: 72517
Updated On:
Products
SYSVIEW Performance Management Option for DB2 for z/OS
Issue/Introduction
starting a trace from 'User Started Report' option, under AUDITOR REQUEST, to capture secondary AUTHID option 'SECIDTR Secondary ID Utilization (7)',
when we select it, it states that there is no data to report.
We are starting a trace from 'User Started Report' option, under AUDITOR REQUEST, to capture secondary AUTHID option 'SECIDTR Secondary ID Utilization (7)', which seems to be producing data, but when we select it, it states that there is no data to report.
when we select it, it states that there is no data to report.
We are starting a trace from 'User Started Report' option, under AUDITOR REQUEST, to capture secondary AUTHID option 'SECIDTR Secondary ID Utilization (7)', which seems to be producing data, but when we select it, it states that there is no data to report.
Environment
z/os dB2
Resolution
Not all data is captured in the SECIDTR report.
THIS REQUEST TRACES AUTH-ID CHANGES THAT ARE OCCUR WHEN A TSO, CICS OR
IMS CONNECTION IS MADE TO DB2 AND ALSO WHEN SET CURRENT SQLID
STATEMENTS ARE EXECUTED.
*
THE WHERE CLAUSES IN EACH RECORD BLOCK RESTRICT THE TRACE TO ONLY
THOSE OCCURRANCES WHERE AN ATTEMPT IS MADE TO CHANGE AN AUTH-ID.
COMMENT OUT THOSE WHERE CLAUSES, IF YOU WANT TO SEE ALL SIGNON, TSO
IDENTIFY REQUESTS AND SET CURRENT SQLID OCCURRANCES
THIS REQUEST TRACES AUTH-ID CHANGES THAT ARE OCCUR WHEN A TSO, CICS OR
IMS CONNECTION IS MADE TO DB2 AND ALSO WHEN SET CURRENT SQLID
STATEMENTS ARE EXECUTED.
*
THE WHERE CLAUSES IN EACH RECORD BLOCK RESTRICT THE TRACE TO ONLY
THOSE OCCURRANCES WHERE AN ATTEMPT IS MADE TO CHANGE AN AUTH-ID.
COMMENT OUT THOSE WHERE CLAUSES, IF YOU WANT TO SEE ALL SIGNON, TSO
IDENTIFY REQUESTS AND SET CURRENT SQLID OCCURRANCES
Feedback
Yes
No
Powered by
