RE: **SPAM** Re: Happy Thanksgiving, and a quick question

One minor difference from Barbara's example...

Monitor;
  QCMDEXC(cmd:%len(cmd));
On-Error;
EndMon;

I just prefer monitor blocks ;-) 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Monday, November 27, 2006 12:30 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: **SPAM** Re: Happy Thanksgiving, and a quick question

James H H Lampert wrote:

...
I found that prototyping and calling the C "system()"
function was better suited to the problems at hand than
calling "QCMDEXC," since "system()" doesn't blow up if the
command fails ...

You can use a CALL(E) or CALLP(E) on the call to QCMDEXC to stop it
blowing up your program.
    callp(e)  qcmdexc(cmd : %len(cmd));
    if %error;
      ...

(Broken-record alert) I prefer QCMDEXC() to system() because QCMDEXC()
leaves the exception message in the joblog, which makes it much easier
to debug in cases where you get an unexpected exception.  With system(),
you only get the message ID, you don't get the replacement values.  And
once your program has ended, you don't even have the message id unless
you logged it somewhere.