RE: Logging jobs/sbs

["Dwayne Allison" <Dwayne.Allison@xxxxxxxxxxxxxxxxxxxxxxxx>]

We had this problem several year ago.  It wasn't a user ending the subsystem, 
but a command within a CL program.  So, the system would use the program name 
that ended the job.  

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Ingvaldson, Scott
Sent: Monday, January 17, 2005 8:43 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Logging jobs/sbs


I think I'll go out on a limb here and say that I can't think of any good 
reason why a "user" should even be able to end a subsystem.

Regards,
 
Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group

-----Original Message-----
date: Mon, 17 Jan 2005 12:16:30 +0000
from: Jonathan Mason <masonjo1@xxxxxxxxxxxxxxxx>
subject: Re: Logging jobs/sbs

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

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