Or, you could enter the "way back" machine and code RPG to process all
members of the file and track member using
an INFDS - less system over head, more programmer bs&t
Richard Schoen <richard@xxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/28/2011 02:02 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"midrange-l@xxxxxxxxxxxx" <midrange-l@xxxxxxxxxxxx>
cc
Subject
ALIASING all source members for SQL Access - Good or Bad ?
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
midrange.com
