RE: Checking if a program is active

>From: Bernard Burchell [mailto:bburch@connexus.net.au]
>Another method of finding active jobs is to get a
>list of object locks on QSYS *LIB.

I know this is old, but I'm just reading it now. My only caveat to this
would be that V5R1 allows you to specify that a job shouldn't lock libraries
in the library list. I don't know why you would do this, (maybe
performance?) but at any rate, IF this was done then the lock list on QSYS
would be quite small.

-Walden

------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


-----Original Message-----
From: Bernard Burchell [mailto:bburch@connexus.net.au]
Sent: Tuesday, November 12, 2002 6:45 AM
To: mi400@midrange.com
Subject: Re: [MI400] Checking if a program is active


> Actually the DIAGnose MI-instruction can give you the basis for
> a tool to find out what processes are active. Then you can go
> walk their descriptions to find all active programs, but you are
> correct that this is not kosher.

Another method of finding active jobs is to get a list of object locks on
QSYS *LIB.  Since every active job has QSYS in its library list MATOBJLK
will return a list of PCS pointers to every job.  Although I prefer to read
through the QWCBTnn tables which I understand is the 'proper' method of
finding jobs and their PCS pointers.

_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/mi400
or email: MI400-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.