|
On 23/11/2006, at 12:50 AM, rob@xxxxxxxxx wrote:
Why do a delete before creation on a library other than QTEMP? If the object already exists and it shouldn't, doesn't that mean that theprevious run abnormally terminated and restart procedures should be used?
Not necessarily. It would depend very much on the purpose and design of the process that encountered the problem. It may indicate a restart should be performed automatically or at the least prompt a qualified user to decide. Perhaps the failure of a previous run is no reason to stop a later run (self-recovering)? Perhaps the later run is days or weeks after the failed run in which case it might be too late to do anything about it? Perhaps the failed run does not change data but just reports on it in which case a rerun is unlikely to be a problem. If the failure of the previous run is a problem it should have been detected and notified during the previous run and recovery attempted then.
The existence of an object that is not expected to exist is one of the things the programmer must make a decision about. If it is an error condition then the global exception handler should catch it and the process should fail. Otherwise the program can handle the condition (i.e., it's an expected possibility) by monitoring the exception and either continue using the existing object or delete the object and recreate it. Either way the exception is handled so the exception messages should also be removed from the log.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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
