|
-----Original Message-----
From: Leland, David [mailto:dleland@Harter.com]
Sent: Monday, June 26, 2000 1:39 PM
To: 'RPG400-L@midrange.com'
Subject: RE: (2) The target for a numeric operation is too small!!!!!I understand your point, however, we are a small shop and have only 35+ users, most of whom work within shouting distance of my office. I've trained them pretty well to never answer any messages - they have to call me. We get very few errors but every once in a while we do get one. For me, I really like the way CL handles messages because I can often fix the problem and then respond w/ "R" or "I" and don't have to end the job and find a way to restart it. Sure would make it nice if RPG had the same ability. I understand it doesn't really make sense for divide by 0 errors, overflow errors, etc., but for things like times where a called program ended in error, it would be nice to fix the called program and have the RPG program which called it just retry the call.
We also have a lot of batch jobs and our user's don't even have access to answer messages on them. Coding a PSSR, INFSR, etc. for every program just doesn't make sense because these jobs are sometimes not too easy to restart after an ABEND. I always try to fix the problem and allow the job to continue on. "Job restartability" is a big issue to me.
Dave
-----Original Message-----
From: bmorris@ca.ibm.com [mailto:bmorris@ca.ibm.com]
Sent: Monday, June 26, 2000 2:19 PM
To: RPG400-L@midrange.com
Subject: RE: (2) The target for a numeric operation is too small!!!!!
>Date: Mon, 26 Jun 2000 08:11:03 -0500
>From: "Leland, David" <dleland@Harter.com>
>
>There are a number of RPG messages which I wish you could do an "I" or "R"
>on (such as the failure of a called program) but that's just the way
>messages work in RPG. I doubt that'll change either.Do you really want your users to reply I or R to inquiry messages? How
are they supposed to know when it's ok? What if they answer 'G'?By the way, I include myself in the list of users of a program I write
that has a life of more than a few hours.A simple rule to live by: Never let users see an inquiry message. Use
a PSSR, INFSRs, whatever - if you can rely on a human who doesn't know
your code to decide what to do with an inquiry message, you can rely
on your code to decide what to do with an error.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
+---
@
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.