´ð¸´: Re: MSTR info. about TLPLKNC3

[login to unmask email]

´ð¸´: Re: MSTR info. about TLPLKNC3

Mike

Thank you. What you "guess" is just the same as waht I thought, and we both
believe
it the truth. The modules function and reason codes can be matched
perfectly.
It is the first time that this inforamtion appears in the console, so it
was a very
strange information for me before today, now I am still curious about
TLPLKNC3.
Internal system task, no doubt, but what is its fuction?

______________________________

Huang Hao
DB2 Administrator
Data Center(Shanghai),ICBC
Shanghai,China




|---------+------------------------------->
| | Mike Turner |
| | <[login to unmask email]|
| | USERVE.COM> |
| | ·¢¼þÈË£º DB2 Data |
| | Base Discussion List|
| | <[login to unmask email]|
| | > |
| | |
| | |
|---------+------------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
| |
| ÊÕ¼þÈË£º [login to unmask email] |
| ³­ËÍ£º |
| Ö÷Ì⣺ Re: MSTR info. about TLPLKNC3 |
>------------------------------------------------------------------------------------------------------------------------------|




Huang Hao

I can make a guess. Member db22 attempted to drain the index. It sent a
global drain request to member db21. I assume that 010.TLPLKNC3 identifies
a
system task that is attempting the drain on db21. The drain on db21 fails,
presumably because of claims held by other work on db21 (reason code
00C200EA). This is reported back to db22 which reports failure of its
global
drain attempt (reason code 00C200EC). This is a normal process if a drain
on
one member is blocked by claims on the other member.

Regards
Mike Turner
Email: [login to unmask email]
Tel: +44 (0)1565 873702
web: www.michael-turner.ltd.uk

-----Original Message-----
From: [login to unmask email]
[mailto:[login to unmask email]On Behalf Of William Huang
Sent: Friday, 24 December 2004 10:55
To: [login to unmask email]
Subject: MSTR info. about TLPLKNC3



Hi, list! Merry Christmas!

But sorry to disturb you in such a holiday.

We are running on DB2 V7 z/OS datasharing.
Today I got some information in MSTR JESMSGLG form two members,
which never been seen before, listed following:

DSNT501I -db21 DSNB1LDA RESOURCE UNAVAILABLE
CORRELATION-ID=010.TLPLKNC3
CONNECTION-ID=db21
LUW-ID=*
REASON 00C200EA
TYPE 00000201
NAME dbname .ixspace
DSNT501I -db22 DSNB1DRA RESOURCE UNAVAILABLE
CORRELATION-ID=corr-id
CONNECTION-ID=cicsname
LUW-ID=*
REASON 00C200EC
TYPE 00000201
NAME dbname .ixspace

(Regrettably, some business sensitive names are substituted by
the lowercase words. And these two information are consecutive
when appearing in console log.)

I serched manual then found DSNB1LDA and DSNB1DRA are modules
for something related to local drain requests. And now, the
questions are:
What is TLPLKNC3 and its fuction?
How to expalin these two information?
Dose that indicate any potential problems within our DB2 DS system?

All your advice is appreciated! Thanks!


______________________________

Huang Hao
DB2 Administrator
Data Center(Shanghai),ICBC
Shanghai,China

----------------------------------------------------------------------------

-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org
.
The IDUG List Admins can be reached at [login to unmask email]
Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm



[login to unmask email]

´ð¸´: Re: MSTR info. about TLPLKNC3
(in response to hhuang@DCCSH.ICBC.COM.CN)

Mike

Thank you. What you "guess" is just the same as waht I thought, and we both
believe
it the truth. The modules function and reason codes can be matched
perfectly.
It is the first time that this inforamtion appears in the console, so it
was a very
strange information for me before today, now I am still curious about
TLPLKNC3.
Internal system task, no doubt, but what is its fuction?

______________________________

Huang Hao
DB2 Administrator
Data Center(Shanghai),ICBC
Shanghai,China





Mike Turner
<[login to unmask email] ÊÕ¼þÈË£º [login to unmask email]
USERVE.COM> ³­ËÍ£º
·¢¼þÈË£º DB2 Data Ö÷Ì⣺ Re: MSTR info. about TLPLKNC3
Base Discussion List
<[login to unmask email]
>







Huang Hao

I can make a guess. Member db22 attempted to drain the index. It sent a
global drain request to member db21. I assume that 010.TLPLKNC3 identifies
a
system task that is attempting the drain on db21. The drain on db21 fails,
presumably because of claims held by other work on db21 (reason code
00C200EA). This is reported back to db22 which reports failure of its
global
drain attempt (reason code 00C200EC). This is a normal process if a drain
on
one member is blocked by claims on the other member.

Regards
Mike Turner
Email: [login to unmask email]
Tel: +44 (0)1565 873702
web: www.michael-turner.ltd.uk

-----Original Message-----
From: [login to unmask email]
[mailto:[login to unmask email]On Behalf Of William Huang
Sent: Friday, 24 December 2004 10:55
To: [login to unmask email]
Subject: MSTR info. about TLPLKNC3



Hi, list! Merry Christmas!

But sorry to disturb you in such a holiday.

We are running on DB2 V7 z/OS datasharing.
Today I got some information in MSTR JESMSGLG form two members,
which never been seen before, listed following:

DSNT501I -db21 DSNB1LDA RESOURCE UNAVAILABLE
CORRELATION-ID=010.TLPLKNC3
CONNECTION-ID=db21
LUW-ID=*
REASON 00C200EA
TYPE 00000201
NAME dbname .ixspace
DSNT501I -db22 DSNB1DRA RESOURCE UNAVAILABLE
CORRELATION-ID=corr-id
CONNECTION-ID=cicsname
LUW-ID=*
REASON 00C200EC
TYPE 00000201
NAME dbname .ixspace

(Regrettably, some business sensitive names are substituted by
the lowercase words. And these two information are consecutive
when appearing in console log.)

I serched manual then found DSNB1LDA and DSNB1DRA are modules
for something related to local drain requests. And now, the
questions are:
What is TLPLKNC3 and its fuction?
How to expalin these two information?
Dose that indicate any potential problems within our DB2 DS system?

All your advice is appreciated! Thanks!


______________________________

Huang Hao
DB2 Administrator
Data Center(Shanghai),ICBC
Shanghai,China

----------------------------------------------------------------------------

-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org
.
The IDUG List Admins can be reached at [login to unmask email]
Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm



Mike Turner

RE: ´ð¸´: Re: MSTR info. about TLPLKNC3
(in response to hhuang@DCCSH.ICBC.COM.CN)
Huang Hao

As another lister said, it is the Recovery Manager for Notify Exit request.
I believe the following is a fairly accurate description:

A global drain request is sent between members via XCF message services.
DB2-related XCF messages are always sent by and received by IRLM. The
receiving XCF component drives the Notify exit of the receiving IRLM in
order to pass the global drain request to DB2. When the drain fails, the
recovery manager for the Notify Exit is invoked to issue the message with
reason code 00C200EA and to send an XCF message back to the requestor of the
global drain to say the drain failed.

Regards
Mike Turner
Email: [login to unmask email]
Tel: +44 (0)1565 873702
web: www.michael-turner.ltd.uk

-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]On
Behalf Of William Huang
Sent: Friday, 24 December 2004 14:07
To: [login to unmask email]
Subject: ´ð¸´: Re: MSTR info. about TLPLKNC3



Mike

Thank you. What you "guess" is just the same as waht I thought, and we both
believe
it the truth. The modules function and reason codes can be matched
perfectly.
It is the first time that this inforamtion appears in the console, so it
was a very
strange information for me before today, now I am still curious about
TLPLKNC3.
Internal system task, no doubt, but what is its fuction?

______________________________

Huang Hao
DB2 Administrator
Data Center(Shanghai),ICBC
Shanghai,China




|---------+------------------------------->
| | Mike Turner |
| | <[login to unmask email]|
| | USERVE.COM> |
| | ·¢¼þÈË£º DB2 Data |
| | Base Discussion List|
| | <[login to unmask email]|
| | > |
| | |
| | |
|---------+------------------------------->
>-------------------------------------------------------------------------
-----------------------------------------------------|
|
|
| ÊÕ¼þÈË£º [login to unmask email]
|
| ³­ËÍ£º
|
| Ö÷Ì⣺ Re: MSTR info. about TLPLKNC3
|
>-------------------------------------------------------------------------
-----------------------------------------------------|




Huang Hao

I can make a guess. Member db22 attempted to drain the index. It sent a
global drain request to member db21. I assume that 010.TLPLKNC3 identifies
a
system task that is attempting the drain on db21. The drain on db21 fails,
presumably because of claims held by other work on db21 (reason code
00C200EA). This is reported back to db22 which reports failure of its
global
drain attempt (reason code 00C200EC). This is a normal process if a drain
on
one member is blocked by claims on the other member.

Regards
Mike Turner
Email: [login to unmask email]
Tel: +44 (0)1565 873702
web: www.michael-turner.ltd.uk

-----Original Message-----
From: [login to unmask email]
[mailto:[login to unmask email]On Behalf Of William Huang
Sent: Friday, 24 December 2004 10:55
To: [login to unmask email]
Subject: MSTR info. about TLPLKNC3



Hi, list! Merry Christmas!

But sorry to disturb you in such a holiday.

We are running on DB2 V7 z/OS datasharing.
Today I got some information in MSTR JESMSGLG form two members,
which never been seen before, listed following:

DSNT501I -db21 DSNB1LDA RESOURCE UNAVAILABLE
CORRELATION-ID=010.TLPLKNC3
CONNECTION-ID=db21
LUW-ID=*
REASON 00C200EA
TYPE 00000201
NAME dbname .ixspace
DSNT501I -db22 DSNB1DRA RESOURCE UNAVAILABLE
CORRELATION-ID=corr-id
CONNECTION-ID=cicsname
LUW-ID=*
REASON 00C200EC
TYPE 00000201
NAME dbname .ixspace

(Regrettably, some business sensitive names are substituted by
the lowercase words. And these two information are consecutive
when appearing in console log.)

I serched manual then found DSNB1LDA and DSNB1DRA are modules
for something related to local drain requests. And now, the
questions are:
What is TLPLKNC3 and its fuction?
How to expalin these two information?
Dose that indicate any potential problems within our DB2 DS system?

All your advice is appreciated! Thanks!


______________________________

Huang Hao
DB2 Administrator
Data Center(Shanghai),ICBC
Shanghai,China

----------------------------------------------------------------------------

-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org
.
The IDUG List Admins can be reached at [login to unmask email]
Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm