× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thank you. This gave me enough to get what I needed.

Sharon Wintermute


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Thursday, February 04, 2010 12:25 PM
To: Midrange Systems Technical Discussion
Subject: Re: SQL UDFS

Sharon

These are not system objects. All of these are actually just records in
the various system tables in QSYS2 - names like SYSTABLES, SYSFUNCS,
etc. These are generally not actual iSeries objects. Tables, yes, are
implemented as physical files, etc. Some of these records have
references to real system objects.

UDFs are in the afore-mentioned SYSFUNCS view. Maybe something that'd
recognize that a record has been deleted from it. I don't know if there
are journals on the tables that the view is constructed over, but you
could see.

Beyond that, I don't know quite an approach to use.

HTH
Vern

Wintermute, Sharon wrote:


In the IBM documentation it states:



SQL objects are schemas, journals, catalogs, tables, aliases, views,
indexes, constraints, triggers, sequences, stored procedures,
user-defined functions, user-defined types, and SQL packages. SQL
creates and maintains these objects as system objects.



How do I audit these system objects? Someone deleted a UDF causing
havoc and now I need to figure out how to capture that.



TIA,





Sharon Wintermute



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.