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



Try right-clicking your qddssrc file & click on refresh that should
"sync" up the source in WDSC 


Thanks,
Tommy Holden


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Buck
Sent: Wednesday, November 15, 2006 9:57 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] New fields not showing in outline

A recompile of the DDS is not an option
because the PF has 3 years of history in it.  
I did a CHGPF on it which

I understand exactly what you're saying.  What I'm suggesting is that 
there is no way that WDSC can know what happened on the OS400 side.  For

instance, if you use SEU to change a display file and PDM option 14 to 
compile it, your WDSC environment will not know about it.  In fact, the 
WDSC cache will remember only the last time you made changes within 
WDSC.  The WDSC 'process' if you will basically wants you to make your 
changes on the WDSC side and push them to OS400.  Doing it the other way

round will mean extra work.

If it really isn't the cache, then there is a very high probability that

it's the library list.  Look at the compile listing produced by WDSC to 
make certain.

I have this crazy idea that WDSC should 
work as well as SEU and STRDBG.

WDSC is a lot more complex than SEU/PDM.  It does a LOT more stuff and 
it's completely configurable.  That makes it hard to get up to speed in 
an hour.  No question about it.  Nobody but you can say if the extra 
stuff is worth it or not, and nobody but you can say if (or when) you 
should pull the plug and give it up.

I personally am as old school as they come, and I made it past the pain 
point to the point where I don't use SEU at all any more.  I do use 
green screen to run programs, inspect results and so on.  So I don't 
personally insist on doing _everything_ in WDSC.  If you find the 
compiles a problem then compile on the green screen side.

There aren't any WDSC police who will harass you because you still use 
green screen.  You can absolutely take things one step at a time.  And 
if you decide to never use anything except the editor, then that's fine.

  Do what you need to do.
   --buck

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.