Rob,
Is it possible that the port closed, and it will not appear in NETSTAT. I went through every job, could not find  Job . . :   QZRCSRVS      User . . :   QUSER         Number . . . : 481981
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, October 24, 2013 10:07 AM
To: Midrange Systems Technical Discussion
Subject: RE: iSeries Service jobs creating locks, (QZDASSINIT, QZRCSRVS, etc)
There's a difference between 'USER' and current user.  On WRKACTJOB you can hit F11 and toggle between the two.  The user for the job is, as you've noticed, QUSER.  Of course all of my Current Users for that job are QSECOFR.
If you could find a way to tie NETSTAT *CNN with every connection expanded with option 8 to work with the jobs used by that IP address, you might be able to determine it that way.  Perhaps there's some related API.
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
From:   "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To:     "'Midrange Systems Technical Discussion'" 
<midrange-l@xxxxxxxxxxxx>
Date:   10/24/2013 09:46 AM
Subject:        RE: iSeries Service jobs creating locks, (QZDASSINIT, 
QZRCSRVS, etc)
Sent by:        midrange-l-bounces@xxxxxxxxxxxx
For one of the QZRCSRVS jobs, is there any way to identify the source IP 
for the Client request.
                                                            System: 
PENCOR06
Job . . :   QZRCSRVS      User . . :   QUSER         Number . . . : 481981 
 
  
    Client request - run program QSYS/QWCRTVCA.  
    Client request - run program BRCPGMS/QCCEE12R.  
    Client request - run program QSYS/QWCRTVCA.  
    Client request - run program BRCPGMS/QCCEE12R.  
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Monnier, Gary
Sent: Wednesday, October 23, 2013 3:55 PM
To: Midrange Systems Technical Discussion
Subject: RE: iSeries Service jobs creating locks, (QZDASSINIT, QZRCSRVS, 
etc) 
If you want to remove the locks when performing a backup end the host 
servers 
                 ENDHOSTSVR SERVER(*DATABASE *FILE) ENDACTCNN(*DATABASE 
*FILE)
and end the TCP DDM server
                 ENDTCPSVR SERVER(*DDM)
Restart them once your backup has completed.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Wednesday, October 23, 2013 12:43 PM
To: 'Midrange Systems Technical Discussion'
Subject: iSeries Service jobs creating locks, (QZDASSINIT, QZRCSRVS, etc) 
We've been seeing many more iSeries service jobs, (QZDASSINIT, QZRCSRVS, 
etc) which create locks, etc, and cause problems when attempting 
maintenance.
Once these jobs become active, they do not end, even though they may not 
be used.
Is there any easy way to identify the source?
How can we stop/prevent them from running?
I've ended these jobs, (to get rid an object lock) and a minute later a 
new occurrence became active, with a another lock.
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<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/
--
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.
--
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.