×
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.
for things like that where i know i'm going to have lots of messages like
these i tend to use the (E) extender on the opcode then check %error
instead of using monitor blocks.
Thanks,
Tommy Holden
From: "Jose Antonio Salazar Montenegro" <0jsalazarm@xxxxxxxxxxxxx>
To: <rpg400-l@xxxxxxxxxxxx>
Date: 02/22/2010 12:56 PM
Subject: Quieter Monitors
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
Hi.
The Monitor opcode is my favorite approach to error catching, but it has
the disadvantage of filling your job log with already managed errors.
For example, there's a data file where a numeric field is validated to
see if it contains an *ISO date. If it doesn't, a default date value is
used, but the job log lists thousands of harmless but suspicious "Date,
Time or Timestamp value is not valid" RNX0112 messages.
Can Monitor be made less verbose?
--
Saludos
Antonio Salazar
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.
midrange.com
