Re: QtmmSendMail weirdness: as if two jobs were fighting over the same message *STMF -- MIDRANGE-L

× 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.

Subject: Re: QtmmSendMail weirdness: as if two jobs were fighting over the same message *STMF
From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Date: Wed, 11 Jan 2012 12:57:18 -0800
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

CRPence wrote:

None of the MSF problems I have debugged involved contention on a stream file. I recall past issues describing problems with messages for which the MSF feature would best be "reset" as resolution, using what I recall was a "clear" option on start; i.e. something like: STRMSF SomeParm(*reset|*clear)

I'm kind of leaning towards that explanation myself.

--
JHHL

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.