DB2 v8 for z/OS distributed processing question

Sandra Lakenburger

DB2 v8 for z/OS distributed processing question
I have an application team that has found since migrating their subsystems to
v8 CM, several of their distributed jobs are failing. The one example they gave
me was a COBOL program that under v7 runs successfully as bound and
installed. It contains no SQL requests that execute against the local DB2 for
z/OS subsystem, so in v7, they did not have a package bound locally. All of
the SQL that the program contains is executed once a CONNECT is issued to
the REMOTE LUW location and they did have a package bound with this
location.

Now in v8, they are getting a -805 with a reason of 03 looking for the package
to be bound locally. The resolution has been to also bind the package locally
(with VALIDATE set to RUN) and then make sure that the PKLIST in the plan
bind has an "*" specified for the location.

Is there somewhere in the v8 documentation that I can point them to explain
what changed and why? I found a brief blurb in the Application Programming
Guide, but I'm hoping there's somewhere that spells out specifically what
changed and why.

Thanks
Sandra Lakenburger
USDA-NITC

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

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

Richard Gugel

Re: DB2 v8 for z/OS distributed processing question
(in response to Sandra Lakenburger)
Sandra

I'll bet your running into this

PKGLDTOL is no longer supported: The subsystem parameter PKGLDTOL is no

| longer supported. DB2 Version 8 requires the package or plan for
| applications with the following SQL statements:


| COMMIT

| CONNECT

| DESCRIBE TABLE

| RELEASE

| ROLLBACK

| SET CONNECTION

| SET host-variable = CURRENT SERVER

| VALUES CURRENT SERVER INTO host-variable


| You must bind the DBRM into a plan or package.

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

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

Marcel Harleman

Re: DB2 v8 for z/OS distributed processing question
(in response to Richard Gugel)
Hi,

I'm not sure if it relates to your problem (don't know what the code
in the COBOL program looks like), but perhaps you could have a look at
the installation guide (GC18-7418-06), chapter 6 "Installing,
migrating, and updating system parameters" and then look at the
remarks under "Database protocol" for panel DSNTIP5 (Distributed data
facility panel 2). Perhaps that explains a little bit of what is
happening.

A fragment: "To use DRDA access for applications with three-part
names, you must bind packages for those applications at each location
that the applications access, then bind all packages into a plan."

To emphasize: "at each location that the applications access".

Not sure if this applies to aliases as well, but it looks that way and
might therefore be what your programmers are experiencing. I don't
have the manuals of V7 by hand to check what it said before, but you
probably have ...

Marcel.

On Thu, 29 Nov 2007 13:31:28 -0500, you wrote:

>I have an application team that has found since migrating their subsystems to
>v8 CM, several of their distributed jobs are failing. The one example they gave
>me was a COBOL program that under v7 runs successfully as bound and
>installed. It contains no SQL requests that execute against the local DB2 for
>z/OS subsystem, so in v7, they did not have a package bound locally. All of
>the SQL that the program contains is executed once a CONNECT is issued to
>the REMOTE LUW location and they did have a package bound with this
>location.
>
>Now in v8, they are getting a -805 with a reason of 03 looking for the package
>to be bound locally. The resolution has been to also bind the package locally
>(with VALIDATE set to RUN) and then make sure that the PKLIST in the plan
>bind has an "*" specified for the location.
>
>Is there somewhere in the v8 documentation that I can point them to explain
>what changed and why? I found a brief blurb in the Application Programming
>Guide, but I'm hoping there's somewhere that spells out specifically what
>changed and why.
>
>Thanks
>Sandra Lakenburger
>USDA-NITC
>
>IMPORTANT NOTICE:
>
>IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org
>
>---------------------------------------------------------------------------------
>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

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

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

Sandra Lakenburger

Re: DB2 v8 for z/OS distributed processing question
(in response to Marcel Harleman)
Rich,

I think you're right. Thanks for the reminder about PKGLDTOL. I inherited
these subsystems and not sure why, but someone coded PKGLDTOL as YES in
all of them. I didn't have enough time to explore changing it back before
having to get v8 rolling, so I figured that we'd just deal with anything that
came up.

Thanks again,

Sandra Lakenburger
USDA-NITC

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L discussion listserv that are being implemented to improve reliability and the overall user experience of DB2-L. These changes are coming on November 30th. Details at http://www.idug.org

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