You ask if there is a way to get WDSC to open up the Event file?
You can code your own Compiler command, which can then be used to determine
which command to run, based on the source member type (you have to write
your own code here to retrieve the source type).

That will then run the command in question, i.e. CRTSQLCBL, CRTCICSCBL, etc.

Your own command has to have a parameter called OPTION, that will accept
*EVENTF or *NOEVENTF. The parameter doesn't have to do anything, but it
needs to be there.
When OPTION(*EVENTF) is specified, WDSC will look in the first 20 bytes of
the *LDA. This must contain the library and member for the compiled source,
so your compiler front end needs to ensure that the *LDA is correctly

Assuming that the *LDA is correct and that your IBM supplied compiler
command (called by your front end) has been called with OPTION(*EVENTF) -
WDSC will then automatically retrieve the correct event file and switch to
that tab in the table view.
Depending on your settings, this will also insert the error messages into
the source member in the Editor.

I spent a fair amount of time going through this, and found the following
article invaluable when creating our internal version for WDSC.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by 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.