Re: [WDSCI-L] WDSc for iSeries 5.1 and compile commands

[MichaelQuigley@xxxxxxxxxx]

   I don't have the notes from when we worked this out on a PMR with
   SupportLine, but here's what I recall and what we've got set in our
   Compile Commands.  The needed options vary for different kinds of objects:

   RPGLE          - SRCMBR(&N) OPTION(*EVENTF) DBGVIEW(*SOURCE)
   CBLLE          - SRCMBR(&N) OPTION(*EVENTF) DBGVIEW(*SOURCE)
   RPG            - SRCMBR(&N) OPTION(*SRCDBG)
   CBL            - SRCMBR(&N) OPTION(*SRCDBG)
   DSPF           - SRCMBR(&N) OPTION(*EVENTF)
   PF             - SRCMBR(&N) OPTION(*EVENTF)
   LF             - SRCMBR(&N) OPTION(*EVENTF)
   SQLRPGLE       - SRCMBR(&N) OPTION(*EVENTF) DBGVIEW(*SOURCE)
   SQLCBLLE       - SRCMBR(&N) OPTION(*EVENTF) DBGVIEW(*SOURCE)
   SQLCBL         - SRCMBR(&N) OPTION(*LSTDBG)

   The one that surprised me was the debugging options.  Then I'm not certain
   about this, but we modified the batch program from when it was strictly
   5250 such that it receives the completion message from IBM compile
   command.  e.g., "Program .......... created in library .......... on
   05/14/04 13:08:34." or "Program .......... placed in library ...........
   00 highest severity. Created on 05/14/04 at 13:27:46.".

   I think either this will work or unchecking the "Compile in batch" option
   under "Window, Preferences then Remote Systems, iSeries, Command
   Execution" as suggested by Kushal Munir of IBM.  I believe this is
   required because the server job is watching for that message before
   retrieving the events file.

   Hope this helps.

   Michael Quigley
   Systems-Analyst
   The Way International
   www.TheWay.org

   Original message:
   ------------------------------

   date: Thu, 13 May 2004 10:57:18 +0200
   from: Brian Andersen <BIA@xxxxxxxxxxxxx>
   subject: [WDSCI-L] WDSc for iSeries 5.1 and compile commands

   Hi all,

   I'm new to WDSc for iSeries and have ran into a problem. I've tried to
   search the web but with no luck.

   I work for a software company and when using 5250 we have programs to do
   the compile of our RPGLE programs where all sorts of stuff is going on. So
   when using WDSc I cannot just use the CRTRPGMOD compile program. Therefor
   I
   have tried to make my own compile command in WDSc.

   The compile command works fine meaning that the programs gets compiled as
   they should. But compared to the CRTRPGMOD I am not getting the errors in
   the iSeries Error List when I'm compiling using my own command and there
   are compile errors. My command does have the OPTION[*EVENTF] and
   SRCMBR[member-name] parameters and at some time the CRTRPGMOD is issued
   using OPTION[*EVENTF]. I can see that the errors are collected in EVFEVENT
   file. They are just not being shown in WDSc.
   Can anybody tell me what I might do wrong? Are there any guidelines I need
   to follow when creating my own compile command? What triggers the iSeries
   Error List to be built?

   Any help is much appreciated.

   Thanks!

   Yours sincerely,

   Brian Andersen
   Software Architect
   EDB Gruppen AS