RE: SQL UDFS

["Neill Harper" <neill.harper@xxxxxxxx>]

Hi Sharon

Please could you share, how you found out who deleted the udf as this could
be helpful in the future.

Thanks 

neill

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wintermute, Sharon
Sent: 04 February 2010 18:35
To: Midrange Systems Technical Discussion
Subject: RE: SQL UDFS

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
>
>