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



Dennis,

The last user that held or released the queue. If I really want all the transactions I'd probably make the audit journaling a requirement.

-mark

At 1/18/10 07:22 PM, you wrote:
> The idea here is for a utility to be able to be able to report back
> to the user (or possibly a program) the event or the status, without
> being intrusive. So that would eliminate reliance on changing the
> system *LIBL, VCP's on system commands and audit journaling.


Understood. But it IS another way.

> I'm surprised that that info is not updated with the *JOBQ.

I'm not. You're talking about transaction-type data. Consider that
technically a job queue may be released and held several times per second.
Given that situation, would you really expect to see who held/released the
job queue? Would this be the most recent time, or some specific time?

It is entirely possible I don't understand what it is you thought you'd see
via API. In that case, please enlighten. :)

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
If all of life's a stage, then I want to operate the trap door.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.