×
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.
Thanks Chuck but I already di that with the *PRTSECLVL. It shows nothing more than what I have already seen, that QSECOFR issued an immed. This is pretty much how all the second level messages look:
Job 168511/QPGMR/QZLSSERVER was ended by user QSECOFR.
User QSECOFR issued an immediate end job request for job 168511/QPGMR/QPGMR/QZLSSERVER.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, July 06, 2016 10:25 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: NetServer
On 06-Jul-2016 10:04 -0500, Dave DeBoe wrote:
We had our Netserver end out of the blue the other day. Looking at
theQSYSOPR msgq, and the QHST log, I found jobs related to the
Netserver that were ended by QSECOFR. When I looked at the previos
sign on date for this profile, it had not been used to sign on in over
a month prior to this event happening the other day. I have no idea
how this is possible. A couple of messages in QHST showing that
QSECOFR ended these jobs which ultimately took down our Netserver:
Job 168511/QPGMR/QZLSSERVER was ended by user QSECOFR.
All prestart jobs are ending for program QZLSFILET in QSYS.
Job 168515/QUSER/QZLSFILET was ended by user QSECOFR.
Job 208298/QUSER/QZLSFILE was ended by user QSECOFR.
[...]
The Display Log (DSPLOG) [feature used to display the History Log (QHST)] offers a means to include worthwhile context [second-level text and job issuing the message], rather than showing solely those first-level message text, using a form of spooled output [similar to how the spooled joblog can include significantly more context than just the first-level text of messages visible in an active job message queue]:
DSPLOG ... OUTPUT(*PRTSECLVL)
--
Regards, Chuck
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
midrange.com
