× 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.



I know that when requesting an Outline, it is assembling a lot of cross reference information. For example, each Field in the program exists on specific lines or in files, and it determines if it is used for input (blank), is defined (D), or is modified (M). My thinking is that since it is assembling all this information it will take some time as it is looking at files, etc.

As for Verify, that has puzzled me as to why it takes longer than a compile. I like the interactive features when an error message is listed, in that you can click it and it will take you to that line in the LPEX editor. But why does it take so long?

So I can provide some insight on the first one, but am puzzled myself on the second one.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Darryl Freinkel
Sent: Tuesday, March 02, 2010 7:57 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Why does the outline take so long to complete

I am using V5R3 with WDSc 6.



I have 2 problems. Refreshing the outline or verifying the source, the
process is taking a few minutes to complete. It is as if the system is
waiting for a time out to complete.



Does anyone know what the problem is?



Thanks



Darryl Freinkel

Assignment 400 Group, Inc.

Tel: 770.321.8562 ext 111 | Fax 770.321.8562 | 2247 La Salle Dr, Marietta
GA, 30062, USA | PO Box 72556, Marietta, GA 30007-2556




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.