|
IBM can not only add fields to a file, but I have seen cases where they have renamed the files and/or totally changed the structure of how the files worked. Such as the files behind the system directory back in the V2 days. And back then, the interfaces into the system directory where not near as robust as they are today. You can go after the files for years and not have a problem. Then you put a new release on and you are toast. It is not always just a recompile. Bob -----Original Message----- From: Joe Teff [SMTP:jteff19@idt.net] Sent: Monday, February 08, 1999 5:39 PM To: MIDRANGE-L@midrange.com Subject: Re: QADBXREF & CL To see all of the fields for a file, why not use the system catalog QADBIFLD? It's an externally defined file. You may have to recompile a program at some point in the future. API's would protect you from that, but cannot be easier or faster. > I can remember when IBM introduced the concept of security states for > objects a few years ago. Boy did that screw things up for anyone going > behind the covers to access information> Thankfully most good stuff is > now available through API's. The lesson was simple: Internal objects and > methods are subject to change without notice. If you've got alternatives > why create possible future problems. >> Why do you say "MUCH safer than going after the IBM internal xref >> files"? I would think that this is the safest and fastest! >>> the member name...so unless there are no members in the file, it >>> should work...be a lot easyier than API's and MUCH safer than going >>> after the IBM internal xref files +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | 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 subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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.