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


  1.  Home
  2. MIDRANGE-L
  3. January 2010

Re: Who held *JOBQ?

Bryan,

This and the journaling idea are good ideas, assuming that I have control over the system. I was hoping that this info would be part of the *JOBQ attributes, retrievable by an API.

A commercial utility or even a full blown application would be hard pressed to assume that they could install a VCP on an OS command or to set up auditing for the command.

Are there any other suggestions?

-mark


At 1/14/10 09:22 PM, you wrote:
I have solved this exact problem by using a validity checking program
attached to the HLDJOBQ command.

I posted the simple code example here:
http://code.midrange.com/e4f847813f.html

I am pretty sure you could use the same type of program for the RLSJOBQ
command.

Bryan

M. Lazarus said the following on 1/14/2010 4:17 PM:
> Does the system keep track of who held/released a *JOBQ? The
> Retrieve Job Queue Information (QSPRJOBQ) API doesn't seem to return
> that info. TIA.
>
> -mark


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.