Re: ALIASING all source members for SQL Access - Good or Bad ?

DSPOBJD will tell you nothing about members. There is the RTVMBRD command and the QUSRMBRD API that will tell you when the member itself was last changed.

I suspect that the aliases are to find out specific source records' change dates.

SYSTABLES - I do see some alias name column.
Eh?

On 1/28/2011 3:02 PM, Richard Schoen wrote:

I saw that a vendor package we had on our system for testing had created an SQL ALIAS for each source member within a source file.

I'm assuming this helps them do SQL analysis on a source member as well as access the last changed time info via an SQL query against SYSTABLES

Looks like an interesting technique.

However, is that the best way of determining if a member has had activity or changes or is there a better way such as running DSPOBJD against each library source file ?

SYSTABLES seems cool because a single SQL statement can get me access to all changed source members if they are ALIASed.

I would be interested to hear thoughts on whether this is a good technique for accessing system-wide source member change info.

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT