Use of QMF/Auditing

Steve Whittaker

Use of QMF/Auditing
I know this may be to general a question but I'll put it out there: (one of our application mgrs asked this):
We are currently using DB2 v7 OS/390 with QMF V7 Release 2. In one of our production environments we have Procs that are set up that run Queries that pull in Forms that create reports. These Procs/Queries/Forms were created by various people over the years and have been 'shared'. So anyone can run them.
His question to me is: Is there any 'change control' type of mechanism that can be used to trace when these Procs/Queries/Forms have been changed, ie; an audit trail.
I know I can look at the q.object_directory to get when the object was last modified and/or used but not by 'who'.
Does anyone out there, using QMF, have any 'controls' in place for tracking changes, etc?
Appreciate any insight.

Thanks:
--Steve....

email: [login to unmask email]

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Dave Nance

Re: Use of QMF/Auditing
(in response to Steve Whittaker)
Stephen,
One of the things we have done is set up an endevor processor group to maintain our QMF objects. When an object is moved in this processor group, the endevor job submits a QMF proc that copies the object into QMF. That proc saves the object(s) under a creator ID that the developer's cannot use, though the queries are saved as shared. If you want I can give you the proc that I wrote for this task, and I can give you the rules to be set up in endevor.

Dave Nance
First Health Services, Corp.
(804)527-6841


>>> [login to unmask email] 12/5/03 7:04:05 AM >>>
I know this may be to general a question but I'll put it out there: (one of our application mgrs asked this):
We are currently using DB2 v7 OS/390 with QMF V7 Release 2. In one of our production environments we have Procs that are set up that run Queries that pull in Forms that create reports. These Procs/Queries/Forms were created by various people over the years and have been 'shared'. So anyone can run them.
His question to me is: Is there any 'change control' type of mechanism that can be used to trace when these Procs/Queries/Forms have been changed, ie; an audit trail.
I know I can look at the q.object_directory to get when the object was last modified and/or used but not by 'who'.
Does anyone out there, using QMF, have any 'controls' in place for tracking changes, etc?
Appreciate any insight.

Thanks:
--Steve....

email: [login to unmask email]

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

This message, including any attachments, is intended solely for the use
of the named recipient(s) and may contain confidential and/or
privileged information. Any unauthorized review, use, disclosure or
distribution of this communication(s) is expressly prohibited.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy any and all copies of the original message.
Thank you.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Riyaz

Re: Use of QMF/Auditing
(in response to Dave Nance)
At our installation we use DB2 V7 OS/390 with QMF V7R2, and we use a tool called Endevor by CA to track chagnes to QMF related entities.
-Riyaz.

>>> [login to unmask email] 12-5-03 7:04:05 AM >>>
I know this may be to general a question but I'll put it out there: (one of our application mgrs asked this):
We are currently using DB2 v7 OS/390 with QMF V7 Release 2. In one of our production environments we have Procs that are set up that run Queries that pull in Forms that create reports. These Procs/Queries/Forms were created by various people over the years and have been 'shared'. So anyone can run them.
His question to me is: Is there any 'change control' type of mechanism that can be used to trace when these Procs/Queries/Forms have been changed, ie; an audit trail.
I know I can look at the q.object_directory to get when the object was last modified and/or used but not by 'who'.
Does anyone out there, using QMF, have any 'controls' in place for tracking changes, etc?
Appreciate any insight.

Thanks:
--Steve....

email: [login to unmask email]

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm


This message, including any attachments, is intended solely for the use
of the named recipient(s) and may contain confidential and/or
privileged information. Any unauthorized review, use, disclosure or
distribution of this communication(s) is expressly prohibited.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy any and all copies of the original message.
Thank you.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm