I am trying to remote bind of dsntiaul from a DB2 mainframe subsystem
to a UDB LUW. It looks like it could be a syntax problem but I do not
see it. Any ideas?
Thanks in advance

The bind cards are:
//SYSTSIN DD *
DSN SYSTEM(DBT0)
BIND PACKAGE (EISENGARD.DSNTIB71) -
COPY(DSNTIB71.DSNTIAUL) -
ACTION(ADD) -
EXPLAIN(NO) -
ISOLATION (CS) -
SQLERROR(NOPACKAGE) -
VALIDATE(BIND)
/*

eisengard is the remote UDB LUW system

I get the following information on mainframe when I do bind.

BIND PACKAGE (EISENGARD.DSNTIB71) COPY(DSNTIB71.DSNTIAUL)
ACTION(ADD) EXPLAIN(NO) ISOLATION (CS) SQLERROR(NOPACKAGE)
VALIDATE(BIND)
DSNE932I WARNING, ONLY IBM-SUPPLIED COLLECTION-IDS SHOULD BEGIN WITH
"DSN"
DSNE932I WARNING, ONLY IBM-SUPPLIED COLLECTION-IDS SHOULD BEGIN WITH
"DSN"
DSNE932I WARNING, ONLY IBM-SUPPLIED PACKAGE-IDS SHOULD BEGIN WITH "DSN"

DSNT408I SQLCODE = -30020, ERROR: EXECUTION FAILED DUE TO A
DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION
REASON 124C (011D)
DSNT233I -DBT0 UNSUCCESSFUL BIND FOR
PACKAGE = EISENGARD.DSNTIB71.DSNTIAUL.()
DSN
END

I get the following info on the UDB LUW diaglog

2007-12-18-15.43.09.989377-360 I9777C482 LEVEL: Severe
PID : 200748 TID : 1 PROC : db2agent (idle)
0
INSTANCE: db2inst3 NODE : 000 DB : LAB_DB
APPHDL : 0-322 APPID: NETFDR.FDRDBT0.C1AA6B2E775F
FUNCTION: DB2 UDB, Connection Manager, sqleUCagentConnect, probe:7
RETCODE : ZRC=0x8034006D=-2144075667=SQLZ_RC_CA_BUILT, SQLT_SQLEU
"SQLCA has been built and saved in component specific control
block."

db2diag -rc 0x8034006D

Input ZRC string '0x8034006D' parsed as 0x8034006D (-2144075667).

ZRC value to map: 0x8034006D (-2144075667)

ZRC class :
SQL Error, User Error,... (Class Index: 0)
Component:
SQLEU ; Connection Manager (Component Index: 52)
Reason Code:
109 (0x006D)

Identifer:
ERROR: no mapping found
Identifer (without component):
SQLZ_RC_CA_BUILT

Description:
No known description

Associated information:
Sqlcode -902
SQL0902C A system error (reason code = "") occurred. Subsequent SQL
statements cannot be processed.

Number of sqlca tokens : 0
Diaglog message number: 1




-----------------------------------------
The information in this message may be proprietary and/or
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your
computer.

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Try this...

BIND PACKAGE (EISENGARD.XXXTIB71) -

In other words, make the new collection, DSNTIB71, something else.

Lynne Flatley


"There are two ways to live your life. One is as though nothing is a
miracle. The other is as though everything is a miracle."

~Albert Einstein, quoted in Des MacHale, Wisdom (London, 2002).







________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email]
On Behalf Of Morrison, Steve D.
Sent: Tuesday, December 18, 2007 6:16 PM
To: [login to unmask email]
Subject: [DB2-L] remote bind of dsntiaul from MF to LUW


I am trying to remote bind of dsntiaul from a DB2 mainframe
subsystem to a UDB LUW. It looks like it could be a syntax problem but I
do not see it. Any ideas?
Thanks in advance

The bind cards are:
//SYSTSIN DD *
DSN SYSTEM(DBT0)
BIND PACKAGE (EISENGARD.DSNTIB71) -
COPY(DSNTIB71.DSNTIAUL) -
ACTION(ADD) -
EXPLAIN(NO) -
ISOLATION (CS) -
SQLERROR(NOPACKAGE) -
VALIDATE(BIND)
/*

eisengard is the remote UDB LUW system


I get the following information on mainframe when I do bind.

BIND PACKAGE (EISENGARD.DSNTIB71) COPY(DSNTIB71.DSNTIAUL)
ACTION(ADD) EXPLAIN(NO) ISOLATION (CS) SQLERROR(NOPACKAGE)
VALIDATE(BIND)
DSNE932I WARNING, ONLY IBM-SUPPLIED COLLECTION-IDS SHOULD BEGIN
WITH "DSN"
DSNE932I WARNING, ONLY IBM-SUPPLIED COLLECTION-IDS SHOULD BEGIN
WITH "DSN"
DSNE932I WARNING, ONLY IBM-SUPPLIED PACKAGE-IDS SHOULD BEGIN
WITH "DSN"
DSNT408I SQLCODE = -30020, ERROR: EXECUTION FAILED DUE TO A
DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION
REASON 124C (011D)
DSNT233I -DBT0 UNSUCCESSFUL BIND FOR
PACKAGE = EISENGARD.DSNTIB71.DSNTIAUL.()
DSN
END



The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Thanks I tried that I still am getting:
DSNT408I SQLCODE = -30020, ERROR: EXECUTION FAILED DUE TO A
DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION
REASON 124C (011D)
DSNT233I -DBT0 UNSUCCESSFUL BIND FOR
PACKAGE = EISENGARD.DSNTIB71.DSNTIAUL.()
The DSN is just a warning message.
Thanks
Steve Morrisoon

________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Flatley, Lynne
Sent: Wednesday, December 19, 2007 6:39 AM
To: [login to unmask email]
Subject: Re: [DB2-L] remote bind of dsntiaul from MF to LUW


Try this...

BIND PACKAGE (EISENGARD.XXXTIB71) -

In other words, make the new collection, DSNTIB71, something else.

Lynne Flatley


"There are two ways to live your life. One is as though nothing is a
miracle. The other is as though everything is a miracle."

~Albert Einstein, quoted in Des MacHale, Wisdom (London, 2002).







________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email]
On Behalf Of Morrison, Steve D.
Sent: Tuesday, December 18, 2007 6:16 PM
To: [login to unmask email]
Subject: [DB2-L] remote bind of dsntiaul from MF to LUW


I am trying to remote bind of dsntiaul from a DB2 mainframe
subsystem to a UDB LUW. It looks like it could be a syntax problem but I
do not see it. Any ideas?
Thanks in advance

The bind cards are:
//SYSTSIN DD *
DSN SYSTEM(DBT0)
BIND PACKAGE (EISENGARD.DSNTIB71) -
COPY(DSNTIB71.DSNTIAUL) -
ACTION(ADD) -
EXPLAIN(NO) -
ISOLATION (CS) -
SQLERROR(NOPACKAGE) -
VALIDATE(BIND)
/*

eisengard is the remote UDB LUW system


I get the following information on mainframe when I do bind.

BIND PACKAGE (EISENGARD.DSNTIB71) COPY(DSNTIB71.DSNTIAUL)
ACTION(ADD) EXPLAIN(NO) ISOLATION (CS) SQLERROR(NOPACKAGE)
VALIDATE(BIND)
DSNE932I WARNING, ONLY IBM-SUPPLIED COLLECTION-IDS SHOULD BEGIN
WITH "DSN"
DSNE932I WARNING, ONLY IBM-SUPPLIED COLLECTION-IDS SHOULD BEGIN
WITH "DSN"
DSNE932I WARNING, ONLY IBM-SUPPLIED PACKAGE-IDS SHOULD BEGIN
WITH "DSN"
DSNT408I SQLCODE = -30020, ERROR: EXECUTION FAILED DUE TO A
DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION
REASON 124C (011D)
DSNT233I -DBT0 UNSUCCESSFUL BIND FOR
PACKAGE = EISENGARD.DSNTIB71.DSNTIAUL.()
DSN
END



The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at www.idug.org
< http://www.idug.org/lsidug > under the Listserv tab. While at the site,
you can also access the IDUG Online Learning Center, Tech Library and
Code Place, see the latest IDUG conference information
< http://www.idug.org/lsconf > , and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on Member Services < http://www.idug.org/lsms >



-----------------------------------------
The information in this message may be proprietary and/or
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your
computer.

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Hi Steve,

You might be right. A lot of the DB2 for z/OS bind parms aren't known
to UDB. Try a vanilla remote bind, something like:

DSN SYSTEM(DBT0)
BIND PACKAGE (EISENGARD.DSNTIB71) -
COPY(DSNTIB71.DSNTIAUL) -

And go from there. If the above works, it's syntax. If it still don't
work, well, let us know.

Cheers,


Raymond

_____

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Morrison, Steve D.
Sent: 19 December 2007 14:02
To: [login to unmask email]
Subject: Re: [DB2-L] remote bind of dsntiaul from MF to LUW

Thanks I tried that I still am getting:
DSNT408I SQLCODE = -30020, ERROR: EXECUTION FAILED DUE TO A
DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION
REASON 124C (011D)
DSNT233I -DBT0 UNSUCCESSFUL BIND FOR
PACKAGE = EISENGARD.DSNTIB71.DSNTIAUL.()
The DSN is just a warning message.
Thanks
Steve Morrisoon


_____

The information in this message may be proprietary and/or confidential,
and protected from disclosure. If the reader of this message is not the
intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please
notify First Data immediately by replying to this message and deleting
it from your computer.

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at
< http://www.idug.org/lsidug > www.idug.org under the Listserv tab. While
at the site, you can also access the IDUG Online Learning Center, Tech
Library and Code Place, see the latest < http://www.idug.org/lsconf >
IDUG conference information, and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on < http://www.idug.org/lsms > Member Services
The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at
< http://www.idug.org/lsidug > www.idug.org under the Listserv tab. While
at the site, you can also access the IDUG Online Learning Center, Tech
Library and Code Place, see the latest < http://www.idug.org/lsconf >
IDUG conference information, and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on < http://www.idug.org/lsms > Member Services

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Thanks for suggestion. Still did not work have same error.
DSN

BIND PACKAGE (EISENGARD.EISTIB71) COPY(DSNTIB71.DSNTIAUL)

DSNE932I WARNING, ONLY IBM-SUPPLIED COLLECTION-IDS SHOULD BEGIN WITH
"DSN"
DSNE932I WARNING, ONLY IBM-SUPPLIED PACKAGE-IDS SHOULD BEGIN WITH "DSN"
DSNT408I SQLCODE = -30020, ERROR: EXECUTION FAILED DUE TO A
DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION
REASON 124C (011D)
DSNT233I -DBT0 UNSUCCESSFUL BIND FOR
PACKAGE = EISENGARD.DSNTIB71.DSNTIAUL.()
Thanks
Steve Morrison

________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Bell, Raymond
Sent: Wednesday, December 19, 2007 8:13 AM
To: [login to unmask email]
Subject: Re: [DB2-L] remote bind of dsntiaul from MF to LUW


Hi Steve,

You might be right. A lot of the DB2 for z/OS bind parms aren't known
to UDB. Try a vanilla remote bind, something like:

DSN SYSTEM(DBT0)
BIND PACKAGE (EISENGARD.DSNTIB71) -
COPY(DSNTIB71.DSNTIAUL) -

And go from there. If the above works, it's syntax. If it still don't
work, well, let us know.

Cheers,


Raymond

________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Morrison, Steve D.
Sent: 19 December 2007 14:02
To: [login to unmask email]
Subject: Re: [DB2-L] remote bind of dsntiaul from MF to LUW

Thanks I tried that I still am getting:
DSNT408I SQLCODE = -30020, ERROR: EXECUTION FAILED DUE TO A
DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION
REASON 124C (011D)
DSNT233I -DBT0 UNSUCCESSFUL BIND FOR
PACKAGE = EISENGARD.DSNTIB71.DSNTIAUL.()
The DSN is just a warning message.
Thanks
Steve Morrisoon

________________________________

The information in this message may be proprietary and/or confidential,
and protected from disclosure. If the reader of this message is not the
intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please
notify First Data immediately by replying to this message and deleting
it from your computer.

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at www.idug.org
< http://www.idug.org/lsidug > under the Listserv tab. While at the site,
you can also access the IDUG Online Learning Center, Tech Library and
Code Place, see the latest IDUG conference information
< http://www.idug.org/lsconf > , and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on Member Services < http://www.idug.org/lsms >
The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at www.idug.org
< http://www.idug.org/lsidug > under the Listserv tab. While at the site,
you can also access the IDUG Online Learning Center, Tech Library and
Code Place, see the latest IDUG conference information
< http://www.idug.org/lsconf > , and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on Member Services < http://www.idug.org/lsms >
The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at www.idug.org
< http://www.idug.org/lsidug > under the Listserv tab. While at the site,
you can also access the IDUG Online Learning Center, Tech Library and
Code Place, see the latest IDUG conference information
< http://www.idug.org/lsconf > , and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on Member Services < http://www.idug.org/lsms >



-----------------------------------------
The information in this message may be proprietary and/or
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your
computer.

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Did you get any of the possible DSNL03nI messages? Are the z/OS and LUW servers at
compatible release levels (fixpaks etc)? You may need to start Statistics class 4 and see if
there is anything there (note the hint about only one set of errors being captured means you
might need to bounce DDF to get a fresh set).

James Campbell

On 18 Dec 2007 at 17:15, Morrison, Steve D. wrote:

>
> I am trying to remote bind of dsntiaul from a DB2 mainframe subsystem to a UDB LUW. It looks
> like it could be a syntax problem but I do not see it. Any ideas? Thanks in advance
>
> The bind cards are:
> //SYSTSIN DD *
> DSN SYSTEM(DBT0)
> BIND PACKAGE (EISENGARD.DSNTIB71) -
> COPY(DSNTIB71.DSNTIAUL) -
> ACTION(ADD) -
> EXPLAIN(NO) -
> ISOLATION (CS) -
> SQLERROR(NOPACKAGE) -
> VALIDATE(BIND)
> /*
>
> eisengard is the remote UDB LUW system
>
> I get the following information on mainframe when I do bind.
>
> BIND PACKAGE (EISENGARD.DSNTIB71)COPY(DSNTIB71.DSNTIAUL)
> ACTION(ADD)EXPLAIN(NO) ISOLATION (CS) SQLERROR(NOPACKAGE)
> VALIDATE(BIND)
> DSNE932I WARNING, ONLY IBM-SUPPLIED COLLECTION-IDS SHOULD BEGIN WITH "DSN"
> DSNE932I WARNING, ONLY IBM-SUPPLIED COLLECTION-IDS SHOULD BEGIN WITH "DSN"
> DSNE932I WARNING, ONLY IBM-SUPPLIED PACKAGE-IDS SHOULD BEGIN WITH "DSN"
> DSNT408I SQLCODE = -30020, ERROR: EXECUTION FAILED DUE TO A DISTRIBUTION
> PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION
> REASON 124C (011D)
> DSNT233I -DBT0 UNSUCCESSFUL BIND FOR
> PACKAGE = EISENGARD.DSNTIB71.DSNTIAUL.()
> DSN
> END
>
> I get the following info on the UDB LUW diaglog
>
> 2007-12-18-15.43.09.989377-360 I9777C482LEVEL: Severe
> PID : 200748TID : 1 PROC : db2agent (idle) 0
> INSTANCE: db2inst3NODE : 000DB : LAB_DB
> APPHDL : 0-322APPID: NETFDR.FDRDBT0.C1AA6B2E775F
> FUNCTION: DB2 UDB, Connection Manager, sqleUCagentConnect, probe:7
> RETCODE : ZRC=0x8034006D=-2144075667=SQLZ_RC_CA_BUILT, SQLT_SQLEU
> "SQLCA has been built and saved in component specific control block."
>
> db2diag -rc 0x8034006D
>
> Input ZRC string '0x8034006D' parsed as 0x8034006D (-2144075667).
>
> ZRC value to map: 0x8034006D (-2144075667)
>
> ZRC class :
> SQL Error, User Error,... (Class Index: 0)
> Component:
> SQLEU ; Connection Manager (Component Index: 52)
> Reason Code:
> 109 (0x006D)
>
> Identifer:
> ERROR: no mapping found
> Identifer (without component):
> SQLZ_RC_CA_BUILT
>
> Description:
> No known description
>
> Associated information:
> Sqlcode -902
> SQL0902C A system error (reason code = "") occurred.Subsequent SQL
> statements cannot be processed.
>
> Number of sqlca tokens : 0
> Diaglog message number: 1
>
>
>
>
> The information in this message may be proprietary and/or confidential, and protected
> from disclosure. If the reader of this message is not the intended recipient, or an employee
> or agent responsible for delivering this message to the intended recipient, you are hereby
> notified that any dissemination, distribution or copying of this communication is strictly
> prohibited. If you have received this communication in error, please notify First Data
> immediately by replying to this message and deleting it from your computer.
>
> The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ,
> and delivery preferences are at www.idug.org under the Listserv tab. While at the site, you can
> also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG
> conference information, and much more.
> If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on
> Member Services

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

OK, no it's not syntax. The other thing to check is privileges. You
might want to add the owner clause, just to make sure you know who the
owner will be, and check that both you and the owner - if different -
appear in you USERNAMES table (if you change them) and that they both
appear in, er, SYSCAT.DBAUTH (I think). If you can, get the binder and
the owner temporarily granted DBADM in UDBLand and see how you go.
After that I'm out of ideas as I don't work in this world anymore.

Have fun.


Raymond
PS. Just a thought, but I'm not sure if you can copy a package from a
collection down to UDB. Wee voice at the back of my head is saying you
have to bind it from the DBRM library. Could be talking rubbish -
usually are - but might be worth a go.

_____

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Morrison, Steve D.
Sent: 19 December 2007 20:48
To: [login to unmask email]
Subject: Re: [DB2-L] remote bind of dsntiaul from MF to LUW

Thanks for suggestion. Still did not work have same error.
DSN

BIND PACKAGE (EISENGARD.EISTIB71) COPY(DSNTIB71.DSNTIAUL)

DSNE932I WARNING, ONLY IBM-SUPPLIED COLLECTION-IDS SHOULD BEGIN WITH
"DSN"
DSNE932I WARNING, ONLY IBM-SUPPLIED PACKAGE-IDS SHOULD BEGIN WITH "DSN"
DSNT408I SQLCODE = -30020, ERROR: EXECUTION FAILED DUE TO A
DISTRIBUTION PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION
REASON 124C (011D)
DSNT233I -DBT0 UNSUCCESSFUL BIND FOR
PACKAGE = EISENGARD.DSNTIB71.DSNTIAUL.()
Thanks
Steve Morrison

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at
< http://www.idug.org/lsidug > www.idug.org under the Listserv tab. While
at the site, you can also access the IDUG Online Learning Center, Tech
Library and Code Place, see the latest < http://www.idug.org/lsconf >
IDUG conference information, and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on < http://www.idug.org/lsms > Member Services
The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at
< http://www.idug.org/lsidug > www.idug.org under the Listserv tab. While
at the site, you can also access the IDUG Online Learning Center, Tech
Library and Code Place, see the latest < http://www.idug.org/lsconf >
IDUG conference information, and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on < http://www.idug.org/lsms > Member Services

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

I agree with Raymond (there's a scary thought!). Do the bind specifying
the DBRM library, not copy.

Lynne Flatley


"There are two ways to live your life. One is as though nothing is a
miracle. The other is as though everything is a miracle."

~Albert Einstein, quoted in Des MacHale, Wisdom (London, 2002).


________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email]
On Behalf Of Bell, Raymond
Sent: Thursday, December 20, 2007 4:42 AM
To: [login to unmask email]
Subject: Re: [DB2-L] remote bind of dsntiaul from MF to LUW


OK, no it's not syntax. The other thing to check is privileges.
You might want to add the owner clause, just to make sure you know who
the owner will be, and check that both you and the owner - if different
- appear in you USERNAMES table (if you change them) and that they both
appear in, er, SYSCAT.DBAUTH (I think). If you can, get the binder and
the owner temporarily granted DBADM in UDBLand and see how you go.
After that I'm out of ideas as I don't work in this world anymore.

Have fun.


Raymond
PS. Just a thought, but I'm not sure if you can copy a package
from a collection down to UDB. Wee voice at the back of my head is
saying you have to bind it from the DBRM library. Could be talking
rubbish - usually are - but might be worth a go.


________________________________


The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

I wouldn't be too scared; lots of people do - ask Rick! It took me
awhile to work out what 'Barney' was about. The real scary thought is
that he's probably right.

I suspect it's still a syntax problem of some sort - kind of. As far as
I can see, COPY isn't valid on a UDB bind command, which is (kind of)
why maybe you have to specify the DBRM library rather than copying it
from an existing collection. Mind you, LIB is also missing from the UDB
Bind command syntax, so who knows?

Steve, give it a go binding from the DBRM library and see what happens.

Cheers,


Raymond
PS. Is it just me that gets posts rejected for being allegedly > 500
lines, when they're apparently not?

_____

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Flatley, Lynne
Sent: 20 December 2007 11:46
To: [login to unmask email]
Subject: Re: [DB2-L] remote bind of dsntiaul from MF to LUW

I agree with Raymond (there's a scary thought!). Do the bind specifying
the DBRM library, not copy.

Lynne Flatley

"There are two ways to live your life. One is as though nothing is a
miracle. The other is as though everything is a miracle."

~Albert Einstein, quoted in Des MacHale, Wisdom (London, 2002).

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at
< http://www.idug.org/lsidug > www.idug.org under the Listserv tab. While
at the site, you can also access the IDUG Online Learning Center, Tech
Library and Code Place, see the latest < http://www.idug.org/lsconf >
IDUG conference information, and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on < http://www.idug.org/lsms > Member Services
The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at
< http://www.idug.org/lsidug > www.idug.org under the Listserv tab. While
at the site, you can also access the IDUG Online Learning Center, Tech
Library and Code Place, see the latest < http://www.idug.org/lsconf >
IDUG conference information, and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on < http://www.idug.org/lsms > Member Services

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

The COPY shouldn't be the problem. We used it when running a similar
bind here. This is the syntax we used:



BIND PACKAGE(remlocation.remcollid) +

COPY(loccollid.DSNTIAUL) COPYVER(version) +

VALIDATE(RUN) ISOLATION(CS) +

QUALIFIER (qual) +

RELEASE(DEALLOCATE) +

ACTION(REPLACE) +

CURRENTDATA(YES) +

EXPLAIN(NO)



And, yes, I'm also getting posts rejected for being allegedly over 500
lines. That's the reason this response didn't appear yesterday.



________________________________

The information in this message may be proprietary and/or confidential,
and protected from disclosure. If the reader of this message is not the
intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please
notify First Data immediately by replying to this message and deleting
it from your computer.


The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at www.idug.org
< http://www.idug.org/lsidug > under the Listserv tab. While at the site,
you can also access the IDUG Online Learning Center, Tech Library and
Code Place, see the latest IDUG conference information
< http://www.idug.org/lsconf > , and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on Member Services < http://www.idug.org/lsms >

--------------------------------------------------------------------------------------------------------------------------------------------------
Note: The information contained in this message may be privileged and confidential
and protected from disclosure. If the reader of this message is not the intended recipient,
or an employee or agent responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or copying of this communication
is strictly prohibited. If you have received this communication in error, please notify us
immediately by replying to the message and deleting it from your computer. Thank you.
--------------------------------------------------------------------------------------------------------------------------------------------------

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

When I was college co-op, we spent a lot of time playing StarTrek on
what looked like IBM Selectric Typewriters (but they weren't) using APL.

we used to run stuff for professors using SPSS (???)

I even took a class in something called SNOBOL

BTW, APL has got to be one of the great acronyms.. APL - A Programming
Language

Willie

[login to unmask email] wrote:
> Did you get any of the possible DSNL03nI messages? Are the z/OS and LUW servers at
> compatible release levels (fixpaks etc)? You may need to start Statistics class 4 and see if
> there is anything there (note the hint about only one set of errors being captured means you
> might need to bounce DDF to get a fresh set).
>
> James Campbell
>
> On 18 Dec 2007 at 17:15, Morrison, Steve D. wrote:
>
>
>> I am trying to remote bind of dsntiaul from a DB2 mainframe subsystem to a UDB LUW. It looks
>> like it could be a syntax problem but I do not see it. Any ideas? Thanks in advance
>>
>> The bind cards are:
>> //SYSTSIN DD *
>> DSN SYSTEM(DBT0)
>> BIND PACKAGE (EISENGARD.DSNTIB71) -
>> COPY(DSNTIB71.DSNTIAUL) -
>> ACTION(ADD) -
>> EXPLAIN(NO) -
>> ISOLATION (CS) -
>> SQLERROR(NOPACKAGE) -
>> VALIDATE(BIND)
>> /*
>>
>> eisengard is the remote UDB LUW system
>>
>> I get the following information on mainframe when I do bind.
>>
>> BIND PACKAGE (EISENGARD.DSNTIB71)COPY(DSNTIB71.DSNTIAUL)
>> ACTION(ADD)EXPLAIN(NO) ISOLATION (CS) SQLERROR(NOPACKAGE)
>> VALIDATE(BIND)
>> DSNE932I WARNING, ONLY IBM-SUPPLIED COLLECTION-IDS SHOULD BEGIN WITH "DSN"
>> DSNE932I WARNING, ONLY IBM-SUPPLIED COLLECTION-IDS SHOULD BEGIN WITH "DSN"
>> DSNE932I WARNING, ONLY IBM-SUPPLIED PACKAGE-IDS SHOULD BEGIN WITH "DSN"
>> DSNT408I SQLCODE = -30020, ERROR: EXECUTION FAILED DUE TO A DISTRIBUTION
>> PROTOCOL ERROR THAT CAUSED DEALLOCATION OF THE CONVERSATION
>> REASON 124C (011D)
>> DSNT233I -DBT0 UNSUCCESSFUL BIND FOR
>> PACKAGE = EISENGARD.DSNTIB71.DSNTIAUL.()
>> DSN
>> END
>>
>> I get the following info on the UDB LUW diaglog
>>
>> 2007-12-18-15.43.09.989377-360 I9777C482LEVEL: Severe
>> PID : 200748TID : 1 PROC : db2agent (idle) 0
>> INSTANCE: db2inst3NODE : 000DB : LAB_DB
>> APPHDL : 0-322APPID: NETFDR.FDRDBT0.C1AA6B2E775F
>> FUNCTION: DB2 UDB, Connection Manager, sqleUCagentConnect, probe:7
>> RETCODE : ZRC=0x8034006D=-2144075667=SQLZ_RC_CA_BUILT, SQLT_SQLEU
>> "SQLCA has been built and saved in component specific control block."
>>
>> db2diag -rc 0x8034006D
>>
>> Input ZRC string '0x8034006D' parsed as 0x8034006D (-2144075667).
>>
>> ZRC value to map: 0x8034006D (-2144075667)
>>
>> ZRC class :
>> SQL Error, User Error,... (Class Index: 0)
>> Component:
>> SQLEU ; Connection Manager (Component Index: 52)
>> Reason Code:
>> 109 (0x006D)
>>
>> Identifer:
>> ERROR: no mapping found
>> Identifer (without component):
>> SQLZ_RC_CA_BUILT
>>
>> Description:
>> No known description
>>
>> Associated information:
>> Sqlcode -902
>> SQL0902C A system error (reason code = "") occurred.Subsequent SQL
>> statements cannot be processed.
>>
>> Number of sqlca tokens : 0
>> Diaglog message number: 1
>>
>>
>>
>>
>> The information in this message may be proprietary and/or confidential, and protected
>> from disclosure. If the reader of this message is not the intended recipient, or an employee
>> or agent responsible for delivering this message to the intended recipient, you are hereby
>> notified that any dissemination, distribution or copying of this communication is strictly
>> prohibited. If you have received this communication in error, please notify First Data
>> immediately by replying to this message and deleting it from your computer.
>>
>> The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ,
>> and delivery preferences are at www.idug.org under the Listserv tab. While at the site, you can
>> also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG
>> conference information, and much more.
>> If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on
>> Member Services
>>
>
> The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms
>
>
>

--
Willie
My DB2 blog --> http://blogs.ittoolbox.com/database/db2zos

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms