QAUDJRN had entries for all the QPWFSERVO jobs starting/ending, but no source IP address.
Paul
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Thursday, October 24, 2019 3:18 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: QPWFSERVSO job - what would cause thousands of these jobs to start/stop in a 2 hour window
First suggestion: check QAUDJRN.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Thursday, October 24, 2019 3:03 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: QPWFSERVSO job - what would cause thousands of these jobs to start/stop in a 2 hour window
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Noticed in QSYSOPR, QHST logs closing, quite often, every 7 seconds.
576 QHST logs were generated in this 2 hour window.
This pointed me to view QHST, where I saw the thousands of QPWFSERVSO starting and ending.
Based on the first and last message in QHST, using the job number as a reference, 292,571 QPWFSERVSO jobs started/end.
Job 392259/QUSER/QPWFSERVSO started on 10/23/19 at 13:58:38 in subsystem QSER
Job 684830/QUSER/QPWFSERVSO ended on 10/23/19 at 15:21:30; .002 seconds used;
The QPWFSERVSO jobs use jobd QPWFSPJ, which by default is set *NOLIST and LOG CL no, thus no joblogs were created by any of these jobs.
Without these joblogs, we could not identify the source IP requesting.
From IBM support, QPWFSERVSO jobs are file host server jobs that are used when a client connects to the IFS by some method other than mapping a network drive.
No performance issues were caused by this, just a lot of clutter in the logs.
Anyone in the group ever experience this issue, and/or know how to determine the source IP requesting.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
