|
And on some systems, that file itself may be one of the top 10 largest on
the system. (Or in your case 5 of the top 10).
Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin
SCarter@rsrcorp.com
Sent by: midrange-l-bounces@midrange.com
02/04/2003 12:26 PM
Please respond to Midrange Systems Technical Discussion
To: Midrange Systems Technical Discussion
<midrange-l@midrange.com>
cc:
Fax to:
Subject: Re: Program Cross reference file
Thanks for the comments Vern. I will have to do a bit of work after all
;->
I do need to create a system soon. What happens is each developer does
the
dspobjd and after the information is gathered the file is forgotten and
never cleared. This causes a headache because the next time the developer
does DSPOBJD they will probably create with a different name causing
versions of DSPOBJD *OUTFILE to propagate like rabbits...
____________________________________________________
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.
Vern Hamberg
<vhamberg@centerfieldtech To: Midrange
Systems Technical Discussion <midrange-l@midrange.com>
nology.com> cc:
Sent by: Subject: Re:
Program Cross reference file
midrange-l-bounces@midran
ge.com
02/04/2003 09:50 AM
Please respond to
Midrange Systems
Technical Discussion
This makes me think you could do the DSPFD type(*MBRLIST) against all
source files you are interested in (could be generated from the DSPOBJD
list, as the x-ref products do, at least). You might want to correlate
these lists together somehow.
To find gaps in the names, you can go through them in order, checking that
each one is in sequence with the previous one. Control level processing in
RPG could be useful, I would think.
You might be able to cobble together an SQL statement that returns a
record
where the sequence number (substrung and converted to numeric) is more
than
1 higher than the max of that sequence number for all records with the
name
less than the one from the current record. It feels doable with subqueries
- don't have time to work out the details. You'd group, possibly on the
first 3 characters, if your naming convention is really well-managed.
HTH
Vern
_______________________________________________
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-2025 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.