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



There is a so-called job notification API or exit point. It is actually maintained with the WRKREGINF command. The exit point is QIBM_QWT_JOBNOTIFY. It uses a data queue, to which an entry is added for every job-related event you specify in a subsystem. There are 3 or 4 such events, including being put on a job queue, starting, and ending. You can tell the system you want only the end job notification. Look up the exit point name in InfoCenter for more information.

This approach might work for subsystem jobs, as well, as they are, in fact, just a job with a different type. I have not tested this. The benefit of using the notification exit point is, you get this before the job ends, whereas the QHST info is after the fact.

There are also a couple exit points for commands, Change command exit programs (QIBM_QCA_CHG_COMMAND) & Retrieve command exit program (QIBM_QCA_RTV_COMMAND). I do not have the details under my tongue, so look them up - if you can specify certain commands here, not just all, then you could set up a program to handle ENDSBS. You still have the problem of ending a subsystem from a system screen such as WRKSBS or even option 4 from WRKACTJOB,since they might not use the ENDSBS command. You will need to test these situations.

The exit point program for commands is called within the job where the command is being executed, so you can get the actual user.

HTH
Vern

At 06:16 AM 1/17/2005, you wrote:
HI Goran

When the ENDJOB command is processed, message CPC1125 (Job 123456/user/jobname was ended by user XXXXXXXX) is written to the history log (QHST) and you could pick that up from there. Looking at our QHST log, there are messages that subsystems are ending, but not that they were ended by a particular user. There are CPC1125 messages for some of the subsystem jobs, so that may help.

I don't know if there are any exit points associated with the END* commands, hopefully one of the more knowledgeable list members can answer that. If there are then you could use an exit program to log the end request.

All the best

Jonathan

-----Original message-----
From: "Gÿfffff6ran" Almvik goran_almvik@xxxxxxxxx
Date: Mon, 17 Jan 2005 10:34:22 +0000
To: midrange Q midrange-l@xxxxxxxxxxxx
Subject: Logging jobs/sbs

> Hi,
> Anybody got an idea of how to log when a subsystem/job is ended? Is it possible to log who ends jobs and/or subsystems?
>
> /G
>
>
> ---------------------------------
> Do you Yahoo!?
> All your favorites on one personal page ­ Try My Yahoo!
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>



Jonathan Mason www.astradyne-uk.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



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.