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



I wish I had posted this question while QHST still had this message. My loss.

Early last week, a program bombed. It is an RPG III program written a LONG time
ago. This program is a NEP that reads from a data queue and prints data. First
thing the program does at startup is a call to QCMDEXC to delete the data queue.

For whatever reason, the data queue was gone when this program was started.
Since QCMDEXEC ended in error, and no error monitoring was done, the program
died.

Quick fix was to create a data queue that it could subsequently delete and
recreate.

I did look at QHST at the time, but only found the message that the data queue
object had been destroyed. Nothing near it that seemed to be related to why
the object had been destroyed.

No other odd events, as far as I know.

As I said, I wish I had looked closer at QHST before it got deleted.

This may be either a) a dumb question or b) unanswerable based on limited
information provided, but: What would typically lead to a "object destroyed"
message being sent to QSYSOPR?

Thanks.

John McKee


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.