Re: Who killed me? -- MIDRANGE-L

Subject: Re: Who killed me?
From: PaulMmn <PaulMmn@xxxxxxxxxxxxx>
Date: Mon, 1 Aug 2016 20:10:25 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Do you have control over who has authority to shut down the subsystem in the first place?

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx

.

At 4:04 PM +0200 8/1/16, Tim Bronski wrote:

One of our server processes reports when it has been ended and tries to determine and report the user that ended it. It does this by trapping SIGTERM and then looking at the *EXT message Q for CPC1126. This message has the user name that did the end job. The problem is that this message isn't sent when the subsystem is ended (which also triggers SIGTERM and ends the job). Then we just get CPC1206 that has no info. Is there any API that will give me the information on who initiated the ENDSBS?

As an Amazon Associate we earn from qualifying purchases.

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.