× 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 love the way CODE (and now WDSc) use event files to make it easier for
us to find program problems (mis-named fields, missing f-spec, etc.).
Most compile commands have this option and WDSc is making use of this
already.

Is it possible for us to create our own "events" or "event
files/members" for our own commands or from other IBM commands' spooled
files and have WDSc treat our versions like it does the ones created
from CRTxxxMOD and CRTBNDxxx commands?  Even if it couldn't point to a
source member/line-number, just seeing it in the iSeries Error List view
would be helpful.  For example, after creating modules via the CRTxxxMOD
commands, CRTPGM is needed to put them together.  CRTPGM creates a
report, but there is no option that I am aware of to create an event
file.  So, for one part of the process we can find errors in the iSeries
Error List view, and for another we must view a spooled file.

I didn't add this to my "Top 10 List" because I thought it might already
be possible, just that I am ignorant of the process.  If anyone is
already doing this or knows of reference materials, please let me know.

Thanks,
Bruce Guetzkow
Information Services Director
United Credit Service, Inc.
Phone: 262-723-2902
Fax: 262-723-5568
Email: bruceg@xxxxxxxxxxxxxxxxxxxxxxx
Web: www.unitedcreditservice.com



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-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.