RE: Who held *JOBQ?

Hi Mark

I seem to remember that these events turn up in the History log;
unfortunately I can't verify this at the moment.
If so you could write a program to monitor QHST - not exactly elegant, but
that might help you.

Regards
Evan Harris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of M. Lazarus
Sent: Tuesday, 19 January 2010 12:02 p.m.
To: Midrange Systems Technical Discussion
Subject: 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