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



Fellow geeks and gurus:

We've got a customer whose QMSF seems to be crashing a lot, and it's interfering with our application's use of QMSF.

In the joblog I looked at, the first error message is TCP5184, something about a damaged IFS object ("/tmp/tl480_299801_133888"). While that looks suspiciously like the sort of pathname that would be used for the message to be sent, it definitely ain't one of ours.

Everything else after that seems to be messages to the effect of not being able to log the error, because it had already been logged.

There is currently no QMSF job active on their system; neither do there appear to be any of the QTSMTPxxxx jobs.

Anybody have any clue about what could be going on?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.