|
That might work. But it has too many drawbacks. The biggest being that if the QMSF jobs are down then the user(s) sit until the timeout. I am thinking of using a UUID. That should be unique enough. Then maybe I'll combine that with an api to check for existence. If it exists call the UUID again. I need to do something like this because of the problem when QMSF is down and the fact that the three digit roll over isn't large enough. However based on journal analysis I don't think that this is the issue. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Steve Richter" <srichter@xxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 07/09/2004 11:37 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc Subject RE: SNDEMAIL - volumne testing accepting that this is not an IBM bug, the error proof way to handle this is to poll for the existance of the file passed to the QtmmSendMail api until the file does not exist. The mail server framework job probably deletes that file after the actual send of the email message. This would also catch the situation where QMSF does not send the message because of whatever problem and never deletes the mime message file. So there would be a timeout on the "poll for file existance" loop. -Steve Richter -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx Sent: Friday, July 09, 2004 12:20 PM To: Midrange Systems Technical Discussion Subject: RE: SNDEMAIL - volumne testing We use a unique serial number also. However we only use three digits. This might be a problem if our qmsf jobs were down for a day as we generate over 1,500 emails per day. I will put this on the project list to fix. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-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.