|
Sorry for no reference to educational tools. I'll offer some tips, (this should get a flurry of differing opinions!) Get SQL. If you can't convince mgmt, then learn about Query Management Facility to do much of the same except imbedded SQL. Build libraries using the SQL command CREATE COLLECTION instead of CRTLIB. Learn about journalling. Learn about journals, journal receivers, and techniques for backing them up. Learn about Referential Integrity. How to install it in each database. How do I handle the exceptions in RPG when I violate RI? Why RI offers 400 database protection superior to manually coding RI in your RPG programs like some CASE tools do. (Think client server!) People, by manually coding RI I meant why write code to check detail files prior to deleting the master file record when you can check for an exception on the delete statement. Learn about triggers. I've worked with people who've got enamoured with using them for RI - they aren't getting the point. Use RI for RI. Use triggers for things like: when a client adds a record to the transaction file the 400 trigger can determine whether to fax out an acknowledgement right away. Again, this is a shift away from putting this code into green screen, or, batch program on your 400. But you can see the flexibility when one migrates into client server. ---------- From: David[SMTP:MIDRANGE-L@midrange.com] Sent: Tuesday, July 29, 1997 10:53 PM To: ROB; MIDRANGE-L Subject: Seeking Database Design Guide Greetings! I've long been a critic of companies (I worked for one!) that put the PC-based "database du jour" in the hands of employees with a semester of DBase, expecting them to whip up a new database with important business data. I keep arguing that without an understanding of database design concepts, the most adept PC user will still end up creating a database that looks like it was whipped up -- in a blender! Now it's time for the critic to take some of his own medicine. My heritage as an RPG programmer is long on the "flat file" hardware -- the 5280, the S/34 and S/36 -- but short on the relational aspects of the AS/400 (just since '94). I want to bring my design skills up to standard to take advantage of the features DB2/400 offers. Your advice, please! I've had lots of experience learning what _doesn't_ work. I'd like to know what books or other sources this group would recommend -- not necessarily related to the 400, of course. It's the relational design concepts and "lingo" I'm after. Thanks! David Thomas | Phone: 416-922-3899 | Fax: 416-922-2213 | E-Mail: dg.thomas@sympatico.ca * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the Midrange System Mailing List! To submit a new message, * * send your mail to "MIDRANGE-L@midrange.com". To unsubscribe from * * this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe MIDRANGE-L' in the body of your message. Questions * * should be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the Midrange System Mailing List! To submit a new message, * * send your mail to "MIDRANGE-L@midrange.com". To unsubscribe from * * this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe MIDRANGE-L' in the body of your message. Questions * * should be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
As an Amazon Associate we earn from qualifying purchases.
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.