|
I understand. I wouldn't think people would be writing the local system's VRM to a database. Well, I suppose they could do that if they wanted to use a DDM file on the remote system to read the VRM of the local system. But maybe adopting the Linux concept would be more standardized. If it just was easier to handle IFS files in RPG though... Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com James Rich <james@xxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 12/14/2004 04:46 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Re: The Day the Music Dies (was: RE: backup spool file) On Tue, 14 Dec 2004, James Rich wrote: > That's only if it is a database field. Are people really writing the VRM > into the database? (This is a serious question) What for? > > I don't think a database field is necessary. In fact, it seems like a waste. I think I was unclear. "Are people writing the VRM to the datase?" is my question. The follow up things about a database field not being necessary is written from the point of view of how to find out what VRM you are running on, not how to write to disk somewhere. IOW, I'm suggesting what IBM could do to tell us the VRM, not what we could do to write it down. James Rich It's not the software that's free; it's you. - billyskank on Groklaw -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.