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

RE: Logging jobs/sbs

If you look in the earlier posts in this thread, I had mentioned a couple exit points that are called for commands. They are in the first couple entries of WRKREGINF. Rob Berendt had offered some sample code using these, IIRC. These exit points define a program of yours that is called whenever a certain command is run. This is done in the job running the command, so you can retrieve user, etc, all you want in order to log things. This could be done for ENDSBS.

Also, you could set up security auditing on certain commands, to see when they have been used. The problem still is, there are non-command ways to end subsystems, such as option 10, I think, in WRKSBS. Or just using option 4 against the SBS job in WRKACTJOB. But maybe you could audit all the entry points for ending a SBS, such as the ones mentioned, log them, get QHST info, and correlate them in some way.

HTH
Vern

At 01:00 AM 1/18/2005, you wrote:

Well, the question wasn't if a user should be able to stop jobs/subsystems (because in this server they need to be able too) but how to log who did it. The little buggers don't always start it up again... I've noticed not all facts are being logged in QHST. Often the entry exist about a subsystem is being ended but no info regarding who did it. Anybody know of any good exit programs that could be used?

/G



---------------------------------
Do you Yahoo!?
 The all-new My Yahoo! ­ What will yours do?
--
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.