× 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 have a Make tool that I use to created objects that I have used for
years. 

Compile just reads headers in the source file like the following to
create an object. 

      *_> CNLLSTSPLF SRCFILE(@2/@1) SRCMBR(@3)
      *_> DLTMOD MODULE(@5/@4)
      *_> CRTRPGMOD MODULE(@5/@4) SRCFILE(@2/@1) SRCMBR(@3) +
      *_>   DBGVIEW(@9) OPTIMIZE(@8) OPTION(*EVENTF)
      *_> CRTPGM PGM(@5/@4) +
      *_>    MODULE(@5/@4) +
      *_>    BNDSRVPGM(XVXMLP) +
      *_>    ACTGRP(QILE)            

So I have my command setup in WDSC using Work with Compile Commands like
the following

Compile

COMPILE OBJ(&L/&N) SRCFILE(&L/&F) SRCMBR(&N) ENV(*GUI) BATCH(*NO)

Now if I run Verify against a source member, I get back errors lists but
if I compile using my command and there are errors, I do not get back an
error list. 

If I use the CRT* commands like CRTRPGMOD, etc and I have errors, I do
get back error lists. 

Does anybody have any idea what triggers WDSC to return error lists? 

The EVEVENT file is being generated and the errors are listed but
nothing is returned to WDSC.

I just verify before I compile and it solves 99% of the problems but
still would like to get this one piece to work.  

Incidentally, the Make tool is available as a free download at
http://www.think400.dk/downloads.htm under the name Compile.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.