|
Wilt, Charles wrote:that takes *EVENTF as a
You should still be able to get the error message back to WDSCi.
The key is to make sure your custom command has a parameter named OPTION
specifies OPTION(*EVENTF).value.
Then when your program runs CRTRPGMOD, CRTBNDRPG, ect. make sure it
mailing list
Also make sure you reference the OPTION and SRCMBR parameters when you
invoke your program.
You can add the parms as a comment appended to the program you invoke
... "/* OPTION(*EVENTF) SRCMBR(&N) */"
david
--
System i ... for when you can't afford to be out of business
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
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.