|
Hey guys, This is a very interesting approach and I would like to read more about it. Is there a reference book, IBM or other, that I can purchase that will explain in more detail the philosohpy, approach, and implementation of such processing. Sincerely, Bill Graziano -----Original Message----- From: James W. Kilgore [mailto:qappdsn@attglobal.net] Sent: Thursday, February 03, 2000 6:14 AM To: RPG400-L@midrange.com Subject: Re: Objects and Source Paul, I concur, we have a file that is mandatory for the application to execute and we retrieve it's library name. Having a manually controlled date area, or writing a command that does the library duplication and data area maintenance is just one more thing to manage. Because we are an application provider, (BTW, I get a kick out of the new buzz about ASP 'cause we've been doing it since the S/34), we have a CRTUSRENV (Create User Environment) which asks for the names of libraries to be used, creates job descriptions and job queues to isolate a user community from all others. The user community created could be "developer". But the bottom line is that we made a design choice to use RTVOBJD to determine where you are instead of some other, hopefully, synchronized value. IMHO, RTVOBJD never lies. pcunnane@learningco.com wrote: > > >> For this to work, there should not be any hard-coded library names except > QTEMP. Each database library should contain a data area with its own name. > If a program needs the database library name for some reason, retrieve the > contents of the data area (which would have the same name in each database > library) and plug it in. << > > I like this approach. One change I would make (because I'm a paranoid > SOB, and I rarely trust the contents of data areas unless absolutely > necessary) -- instead of reading the contents of the data area, do a > RTVOBJD on it, and check the RTNLIB. Or use an API. Or something. > otherwise, I could see some genius copying a library and forgetting to > change the data area contents. +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | 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.