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



Mike wrote:

> It was actually an IBMer who suggested trying
> to stick with this as we might find the upgrade
> too demanding on hardware. Do you
> have a different view?

Scott wrote:

>Yes, the latest version of WDSC takes a lot of
>resources, but you can still just use CODE/400
>and not the rest.

This is presuming that you can _load_ WDSCi.  My PII 450 with 128 megs of
RAM refuses to load WDSCi.  And there's no option to load only a part of it,
either.  It's all or nothing.

Scott also wrote:
>The older version of CODE/400 may not support
>everything you need it to.  If you are on V5R1 or
>V5R2, there may be some RPG IV features that
>came available that the older version of CODE/400 will
>not support.  So if you plan on doing free format RPG,
>you will need the newer version of CODE/400 in WDSC 5.0.

I can't speak to whatever enhancements IBM may have made to WDSCi - Code/400
but it is my understanding that there aren't many.  Maybe bug fixes?  I use
/free with WDT 5.1 - Code/400 and have no problems at all.  Since I have to
target V5R1 systems, I don't know what V5R2 features the old verifier
doesn't check for.  It would be interesting to see if WDSCi - Code/400
handles V5R2 code any better than WDT 5.1 - Code/400.  A quick experiment
shows that the verifier doesn't understand %bitand, so that might make for a
quickie test for the folks on WDSCi to try with Code.
  --buck




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.