RE: iSeries Service jobs creating locks, (QZDASSINIT, QZRCSRVS, etc)

Web Service points to an RPGLE wrapper, which points another RPGLE pgm

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, October 24, 2013 10:49 AM
To: Midrange Systems Technical Discussion
Subject: RE: iSeries Service jobs creating locks, (QZDASSINIT, QZRCSRVS, etc)

Does the web service have any odbc type stuff where it 'connects' to DB2 on i and processes data? Even though the web service is local to the lpar it may be doing the connection this way.


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 10:31 AM
Subject: RE: iSeries Service jobs creating locks, (QZDASSINIT,
QZRCSRVS, etc)
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Vern,

That helped, but confused, the client is the iSeries LPAR.
The user, BRWEBMIS, points me to a HTTP Web Service

Message ID . . . . . . : CPIAD09 Severity . . . . . . . : 00
Message type . . . . . : Information
Date sent . . . . . . : 10/09/13 Time sent . . . . . . : 14:56:53


Message . . . . : User BRWEBMIS from client PENCOR06.PENCOR.COM
connected to
job 481981/QUSER/QZRCSRVS in subsystem QUSRWRK in QSYS on 10/09/13
14:56:53.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Thursday, October 24, 2013 10:18 AM
To: Midrange Systems Technical Discussion
Subject: Re: iSeries Service jobs creating locks, (QZDASSINIT, QZRCSRVS,
etc)

Look for the last (maybe only) CPIAD02 message - this says user
such-and-such from client some-IP-address connected to server.

At least I think that should work.

Vern

On 10/24/2013 8:46 AM, Steinmetz, Paul wrote:

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.

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