|
Did not want to do a dspobjd if there was a file maintained by the OS. ____________________________________________________ J. Scott Carter Programmer/Analyst e-mail: Mailto:scarter@rsrcorp.com Phone: 214.583.0348 It's not the destination that counts in life it's the journey. The journey with the people we love is all that really matters. Such a simple truth so easily forgotten. "Mark Phippard" <MarkP@softlanding.c To: Midrange Systems Technical Discussion <midrange-l@midrange.com> om> cc: Sent by: Subject: Re: Program Cross reference file midrange-l-bounces@m idrange.com 02/03/2003 05:45 PM Please respond to Midrange Systems Technical Discussion Why not just do a DSPOBJD to a *OUTFILE? You can even setup a job schedule entry to just run it every night. Or even just make your program do it as part of doing the lookup. Mark To: Midrange Systems Technical Discussion <midrange-l@midrange.com> cc: bcc: Subject: Program Cross reference file SCarter@rsrcorp.com Sent by: midrange-l-bounces@midrange.com 02/03/2003 04:00 PM CST Please respond to Midrange Systems Technical Discussion <font size=-1></font> I am looking to find a program cross Reference file like QADBIFLD or QADBXREF for physical files. I am trying to find a way to determine what name I can use for new objects. Based on our naming convention we are starting to run out of valid names. sar001 for RPF I know we have situations like sar001,sar002,sar004,sar005 where sar003 has never been used but it is hard to see when you are scanning manually. I want to create a program that will scan a file and show me the usable names... ____________________________________________________ J. Scott Carter Programmer/Analyst e-mail: Mailto:scarter@rsrcorp.com Phone: 214.583.0348 It's not the destination that counts in life it's the journey. The journey with the people we love is all that really matters. Such a simple truth so easily forgotten. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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.
midrange.com
