RE: Help needed on QCMDEXEC.

[bmorris@xxxxxxxxxx]

The big difference between QCMDEXC over system() is the amount
of information you can get about an error that occurs.  With
QCMDEXC, you can receive the error message and get any information
you want.  With system(), you can only get the message id, because
system removes the error from the joblog.

Having the error removed from the joblog can be nice, but it
only removes the final error, it doesn't completely clean up the
joblog.  (Which may be a good thing or a bad thing.)  Personally,
I'd rather have the message in the joblog and remove it myself.
It's very nasty to be debugging a system call and have only the
failing message-id to work with.  If you use QCMDEXC and
have code to remove the message, you can still see the message
in the joblog if you're in the debugger.

One place system() is nicer than QCMDEXC is with overrides.  If
you have a procedure wrappering QCMDEXC and you try to do an
override, a call-level override won't work correctly.  Since
you don't need to wrapper system() to make it nice to call,
you don't have this problem.

Barbara Morris


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---