RE: Quieter Monitors

Why yes, they are. That's why I'm changing them.

I'm sure it's not the formal name, what I meant was doing what could
trigger an error and monitor for it rather than programmatically prevent
all possible error conditions and only act until you think all bases are
covered.

Some languages, like Python, make it easy to use this approach. When
Monitors were introduced, RPG did too, with the minor inconvenient of
spamming the job log.

--
Saludos
Antonio Salazar

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rory Hewitt
Sent: Monday, February 22, 2010 6:09 PM
To: RPG programming on the IBM i / System i
Subject: Re: Quieter Monitors

Antonio,

Whilst I agree with you, surely your "shoot first, ask later" programs
aren't going into production where their job logs are going to be seen
by
operators, are they?

Regards,

Rory

On Mon, Feb 22, 2010 at 3:08 PM, Jose Antonio Salazar Montenegro <
0jsalazarm@xxxxxxxxxxxxx> wrote:

That's exactly what I needed, although my job log is not filling, just

a

few hundred messages.

Maybe I'm using Monitor wrong, but it just feels perfect for the

"shoot

first, ask later" kind of programming. The workarounds (removal via
message APIs, TEST, Ifs) all seem a little messy.

Anyway, I'll get a little messy, since these harmless messages really
get on the nerves of the current operator. Who knew they actually
checked job logs?

Thanks to all for your suggestions.

--
Saludos
Antonio Salazar