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

Evan,

ENDHOSTSVR SERVER(*DATABASE) ENDACTCNN(*DATABASE) did end all QZDASSINIT locks.
However, after STRHOSTSVR SERVER(*DATABASE) RQDPCL(*ANY)
Only 1 occurrence of the QZDASSINIT started, not all 8 as expected.
I had to recycle the apps on all 5 remote servers to see all 8 jobs, (this was ugly and time intensive)
I need to do more testing, but ENDHOSTSVR may not be the final solution.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan Harris
Sent: Tuesday, October 29, 2013 5:16 PM
To: Midrange Systems Technical Discussion
Subject: Re: iSeries Service jobs creating locks, (QZDASSINIT, QZRCSRVS, etc)

Hi Paul

I'm no expert but I would guess it would depend on how they connected and how they disconnected.

Are you sure the jobs you perceive as old weren't still in use ?

What does the subsystem description show for the prestart job information for QZDASSINT ?

On Wed, Oct 30, 2013 at 9:14 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>wrote:

Evan,

I'm going to test ENDHOSTSVR SERVER(*DATABASE *FILE)
ENDACTCNN(*DATABASE *FILE), to confirm if this will end all QZDASSINIT locks .

I found something that is puzzling. One of our apps that does a
connection to the iSeries creates 8 occurrences of the QZDASSINIT job.
When refreshing a R&D environment last week, we saw 16 occurrences, (8
were current, and a 2nd set of 8 from over a month ago.
Is it possible that the iSeries can keep old QZDASSINT jobs, even if
the remote connections were closed?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan Harris
Sent: Friday, October 25, 2013 7:21 PM
To: Midrange Systems Technical Discussion
Subject: Re: iSeries Service jobs creating locks, (QZDASSINIT,
QZRCSRVS,
etc)

I'm curious as to why you don;t want to do an ENDHOSTSVR.

It doesn't seem like it would be a problem to me so long as you do a
STRHOSTSVR afterwards.

If you don't end it then it's perfectly possible for something to
start and grab a lock after your process has started.

On Sat, Oct 26, 2013 at 5:05 AM, Steinmetz, Paul
<PSteinmetz@xxxxxxxxxx

wrote:

Now that I've identified the source of the QZRCSRVS job, is there a
way to have the QZRCSRVS job end. The program that ran in this job
ended weeks ago, no open files, however, the QZRCSRVS job still has
a lock on all the libraries in the lib list. I really don't want to
ENDHOSTSVR simply get rid of the lib list locks for an environment

refresh.

This is on an R&D LPAR.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Thursday, October 24, 2013 1:43 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: iSeries Service jobs creating locks, (QZDASSINIT,
QZRCSRVS,
etc)

Rob,

Not working at V6R1, only 2 months back on PTFs.
Based on what I read below, I have the required PTF installed

When you visit the DB2 Technology Update Wiki, you'll find the
details on these two catalog views in the DB2 for i Management
Enhancements

category.

Support for the GROUP_PTF_INFO and TCPIP_INFO was delivered
initially with level 19 of the IBM i 6.1 database group PTF and
level 6 of the IBM i 7.1 database group PTF. The TCPIP_INFO view was
enhanced with level 21 of the IBM i 6.1 database group PTF and level
10 of the IBM i
7.1 database group PTF.

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

Hey Paul, I'm having a devil enough of a time finding the list of
new views (even using Infocenter) for the current OS let alone for
one that's old and I don't use.
But, the link of views I sent you was ptf'd back to 6.1.

I think the TR7 announcement did say a bunch of new views that will
help to eliminate a lot of API usage came out.

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

Rob,

This will only work on V7R1, not V6R1, correct.

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

No kicking new views available like this article talked about in the
past, is there?
http://www.ibm.com/developerworks/ibmi/library/i-db2_catalog/index.h
tm
l

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: "Monnier, Gary" <Gary.Monnier@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/24/2013 12:56 PM
Subject: RE: iSeries Service jobs creating locks, (QZDASSINIT,
QZRCSRVS, etc)
Sent by: midrange-l-bounces@xxxxxxxxxxxx

Try displaying the job's log with WRKACTJOB. You can also write up
something that utilizes API QUSRJOBI to retrieve the IPV4 IP address
for the job. You can also go to the extent of using the
QtocRtvNetCnnDta API to retrieve the network connection.

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

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.

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

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

--

Regards
Evan Harris
--
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.

--

Regards
Evan Harris
--
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.