|
Excellent. I almost replied the same. Didn't someone come up with a technique to call an api to remove the extraneous message in the on-error routine? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Christen, Duane J." <dchristen@xxxxxxxxxxxxx> Sent by: rpg400-l-bounces+rob=dekko.com@xxxxxxxxxxxx 04/26/2005 09:47 AM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To "'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx> cc Subject RE: Date TESTing Joel, Tony; The monitor construct will perform better IF you have a relativly small number of failures. The monitor intercepts an exception, compairs it to the on-error condition (if the condition exists) and performs the code following the on-error. Exception handling is expensive, performance wise, and our rule of thumb here is: If 10% or fewer of the tests will fail, then the monitor construct is acceptable, otherwise build/use a procedure to test the validity of the data. I have not done any formal testing on this assumption, but it seems to work for us. The other caviot with monitor is that it leave the exception in the job log, which can be confusing and generate a large job log full of exceptions. Duane Christen -----Original Message----- From: Joel Cochran [mailto:jrc@xxxxxxxxxx] Sent: Tuesday, April 26, 2005 3:56 AM To: RPG programming on the AS400 / iSeries Subject: Re: Date TESTing On Mon, 2005-04-25 at 23:21, Tony Carolla wrote: > Test(DE) *USA M(Loop).MsgDate; Tony, Since the TEST opcode won't accept the subfield, try using MONITOR instead... /free monitor ; dateField = %date( strDate : *USA ); on-error ; // Handle error endmon ; /end-free If I remember from a thread a while back, this is supposed to perform better than TEST also... For anyone interested, I have more on Handling Dates in RPGIV here: http://www.itjungle.com/fhg/fhg051904-story01.html Joel Cochran -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-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.