× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This seems good at first glance - it might run into problems because we are able to put DCL-F and DCL-S and DCL-DS stuff all together, grouped by their relationship to each other.

So this be nice to have, with the ability to bundle related stuff together.

Just thinking!
Vern

On 3/13/2019 3:00 PM, Joe Pluta wrote:
I like that a lot, Steve.  I've gone so far as to take source, stick it in Excel, sort it, and put it back.

It does really cause grief with compare utilities, as you might guess.  :)


On 3/13/2019 2:58 PM, Steve M via WDSCI-L wrote:
Let me start by saying I've never done an RFE, so I know just enough to ask
a question and be dangerous.

As I am sure many of us encounter, we enter a program and find many DCL-F or
DCL-S lines.  Wouldn't it be nice if we could, in some way, identify the
range of lines of the DCL-F and then have them sorted by the file name
immediately to the right of the DCL-F?  Same thing with dozens of DCL-S
lines; identify the range (a highlight or something) and then have RDi sort
the range in alphabetical order of the DCL-S names.

I know I can see the files in order in the outline area by opening the Files
section, but in the Fields section it contains all of the fields of the
files as well as the DCL-S lines.

If you personally, or your company, follow any kind of naming standard,
being able to see what's already been declared certainly saves time of
reading every DCL-S line looking for something that may, or many not, exist.

Thoughts everyone?

Thanks,

Steve Meisinger





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.