×
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.
Rod,
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
populated.
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.
http://www.itjungle.com/fhg/fhg080404-story01.html
Regards
Andrew
midrange.com
