RE: Storing /Copy modules locally

["Brian D. James" <bjames@xxxxxxxxxxxxxxxx>]

Hello Reeve,

Thanks for the information on how the verifier works and for the workaround.

What compiler issues would be involved if the preprocessor generated a
"temporary" source member that extracted the /Copy modules and uploaded this
complete "temporary" source member to the host to be compiled?

I'll look for Bob Cozzi's comments on preprocessors but I'm not talking
about a sophisticated one like the RPG/free preprocessor that Paul Conte
created about a decade ago. I'm talking about a relatively unsophisticated
one that would do no more than what I could do myself with cut and paste
except that it would do it much faster and much more accurately.

Thanks again for your comments and the information.

Regards,

Brian

-----Original Message-----
From: code400-l-admin@midrange.com
[mailto:code400-l-admin@midrange.com]On Behalf Of Reeve Fritchman
Sent: Thursday, November 08, 2001 4:33 PM
To: code400-l@midrange.com
Subject: RE: Storing /Copy modules locally



When you "Verify", CODE/400 downloads everything it needs (including /COPY
books, DDS, etc.).  But it's stored in an unfriendly format with an
unfriendly name in WDT400\CACHE.  Verify works well if you're changing the
code in one member only; if you have /COPY books open and are changing a
couple of related source members, I don't know of a good way to force a
refresh of the cached-but-changed source (easiest way: make a dummy member
with the changed /COPY books only, "Verify with prompt", "Refresh cache",
wait for it to bomb, then go back and "Verify" your main member).

I suspect the WDT/400 team is aware of shortcoming with source management.
There may be a big emotional issue with having source not iSeries-resident;
there are compiler issues unless you remember *QINLINE (there may be issues
even if you do remember it!).  As of right now, source has to be on the
iSeries to get compiled.

IMHO, preprocessors are ungood.  Somebody else (maybe Bob Cozzi) offered a
coherent explanation of the problems with relying on preprocessors.  I know
it wasn't me...