sql store procedure multi row fetch

Fotis Fragos

sql store procedure multi row fetch
Hello I was wondering
How is it possible to use multi row fetch within an sql store procedure;

If cannot use will it be a new feature in db2 v9

Please answer me;


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************

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

Phil Grainger

Re: sql store procedure multi row fetch
(in response to Fotis Fragos)
I'm not aware of any limitations that say you cannot use a multi-row
cursor in a stored procedure in version 8


Phil Grainger
CA
Product Management Director
Phone: +44 (0)1753 577 733
Mobile: +44 (0)7970 125 752
eMail: [login to unmask email]

Ditton Park
Riding Court Road
Datchet
Slough
SL3 9LL

CA plc a company registered in England and Wales under company
registration number 1282495 with its registered office at the address
set out above. VAT number 697904179.



-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Fotis Fragos
Sent: 28 November 2007 10:01
To: [login to unmask email]
Subject: [DB2-L] sql store procedure multi row fetch

Hello I was wondering
How is it possible to use multi row fetch within an sql store procedure;

If cannot use will it be a new feature in db2 v9

Please answer me;


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
system manager.
**********************************************************************

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

Fotis Fragos

Re: sql store procedure multi row fetch
(in response to Phil Grainger)
How can I define array in SQL store procedure?

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Grainger, Phil
Sent: Wednesday, November 28, 2007 4:36 PM
To: [login to unmask email]
Subject: Re: [DB2-L] sql store procedure multi row fetch

I'm not aware of any limitations that say you cannot use a multi-row
cursor in a stored procedure in version 8


Phil Grainger
CA
Product Management Director
Phone: +44 (0)1753 577 733
Mobile: +44 (0)7970 125 752
eMail: [login to unmask email]

Ditton Park
Riding Court Road
Datchet
Slough
SL3 9LL

CA plc a company registered in England and Wales under company
registration number 1282495 with its registered office at the address
set out above. VAT number 697904179.



-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Fotis Fragos
Sent: 28 November 2007 10:01
To: [login to unmask email]
Subject: [DB2-L] sql store procedure multi row fetch

Hello I was wondering
How is it possible to use multi row fetch within an sql store procedure;

If cannot use will it be a new feature in db2 v9

Please answer me;


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
system manager.
**********************************************************************

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

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

Phil Grainger

Re: sql store procedure multi row fetch
(in response to Fotis Fragos)
Ahh - now I understand your question

You are creating a SQL stored procedure (I didn't notice that in your
original post - I just saw "stored procedure")

So I change my answer from "yes" to "no" (sorry)

And it doesn't appear to be possible in DB2 9 either - only variables
may be declared not arrays

I hadn't noticed this limitation, so thanks for pointing it out

Phil Grainger
CA
Product Management Director
Phone: +44 (0)1753 577 733
Mobile: +44 (0)7970 125 752
eMail: [login to unmask email]

Ditton Park
Riding Court Road
Datchet
Slough
SL3 9LL

CA plc a company registered in England and Wales under company
registration number 1282495 with its registered office at the address
set out above. VAT number 697904179.



-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Fotis Fragos
Sent: 28 November 2007 15:09
To: [login to unmask email]
Subject: Re: [DB2-L] sql store procedure multi row fetch

How can I define array in SQL store procedure?

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Grainger, Phil
Sent: Wednesday, November 28, 2007 4:36 PM
To: [login to unmask email]
Subject: Re: [DB2-L] sql store procedure multi row fetch

I'm not aware of any limitations that say you cannot use a multi-row
cursor in a stored procedure in version 8


Phil Grainger
CA
Product Management Director
Phone: +44 (0)1753 577 733
Mobile: +44 (0)7970 125 752
eMail: [login to unmask email]

Ditton Park
Riding Court Road
Datchet
Slough
SL3 9LL

CA plc a company registered in England and Wales under company
registration number 1282495 with its registered office at the address
set out above. VAT number 697904179.



-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Fotis Fragos
Sent: 28 November 2007 10:01
To: [login to unmask email]
Subject: [DB2-L] sql store procedure multi row fetch

Hello I was wondering
How is it possible to use multi row fetch within an sql store procedure;

If cannot use will it be a new feature in db2 v9

Please answer me;


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
system manager.
**********************************************************************

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

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

M. Khalid Khan

Re: sql store procedure multi row fetch
(in response to Phil Grainger)
Sure the answer is no but I don't think it matters in DB2 9. The whole
point of multi row fetch is the reduce the number of (cross memory) calls
between client address space and DBM1. For DB2 9, a SQL SP actually runs
in DBM1making it a non issue.
Hope this helps
Khalid





"Grainger, Phil" <[login to unmask email]>
Sent by: "DB2 Data Base Discussion List" <[login to unmask email]>
11/28/2007 09:13 AM
Please respond to
"DB2 Database Discussion list at IDUG" <[login to unmask email]>


To
[login to unmask email]
cc

Subject
Re: [DB2-L] sql store procedure multi row fetch






Ahh - now I understand your question

You are creating a SQL stored procedure (I didn't notice that in your
original post - I just saw "stored procedure")

So I change my answer from "yes" to "no" (sorry)

And it doesn't appear to be possible in DB2 9 either - only variables
may be declared not arrays

I hadn't noticed this limitation, so thanks for pointing it out

Phil Grainger



**********

The information contained in this communication is confidential, private, proprietary, or otherwise privileged and is intended only for the use of the addressee. Unauthorized use, disclosure, distribution or copying is strictly prohibited and may be unlawful. If you have received this communication in error, please notify the sender immediately at (312)653-6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in Oklahoma; or (972)766-6900 in Texas.

**********

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

John Miller

Re: sql store procedure multi row fetch
(in response to M. Khalid Khan)
It's not that you can't use multi-row fetch. You just can't use arrays
in conjunction with multi-row fetch. You can do the following:



FETCH NEXT ROWSET FROM curname FOR 5 ROWS
INTO
(vCOL1_1, vCOL2_1, vCOL3_1),
(vCOL1_2, vCOL2_2, vCOL3_2),
(vCOL1_3, vCOL2_3, vCOL3_3),
(vCOL1_4, vCOL2_4, vCOL3_4),
(vCOL1_5, vCOL2_5, vCOL3_5);



Each variable will have to be declared separately.

It's ugly (and maybe not practical) but doable.



Thanks,

John Miller





The information transmitted is intended only for the addressee and may contain confidential, proprietary and/or privileged material. Any unauthorized review, distribution or other use of or the taking of any action in reliance upon this information is prohibited. If you receive this in error, please contact the sender and delete or destroy this message and any copies.

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

John Panopoulos

Re: sql store procedure multi row fetch
(in response to John Miller)
I am using an SQL store Procedure in DB2 V8 and it seems that the
compiler does not know

this syntax



FETCH NEXT ROWSET FROM curname FOR 5 ROWS

INTO ...............

ILLEGAL SYMBOL "ROWSET".



I have used multi row fetch in a Cobol Store Procedure.

What is your opinion about store procedures regarding performance?

SQL Store Procedures or Cobol Store Procedures (multi row fetch)?



________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of [login to unmask email]
Sent: Wednesday, November 28, 2007 6:30 PM
To: [login to unmask email]
Subject: Re: [DB2-L] sql store procedure multi row fetch



It's not that you can't use multi-row fetch. You just can't use arrays
in conjunction with multi-row fetch. You can do the following:



FETCH NEXT ROWSET FROM curname FOR 5 ROWS
INTO
(vCOL1_1, vCOL2_1, vCOL3_1),
(vCOL1_2, vCOL2_2, vCOL3_2),
(vCOL1_3, vCOL2_3, vCOL3_3),
(vCOL1_4, vCOL2_4, vCOL3_4),
(vCOL1_5, vCOL2_5, vCOL3_5);



Each variable will have to be declared separately.

It's ugly (and maybe not practical) but doable.



Thanks,

John Miller



The information transmitted is intended only for the addressee and may
contain confidential, proprietary and/or privileged material. Any
unauthorized review, distribution or other use of or the taking of any
action in reliance upon this information is prohibited. If you receive
this in error, please contact the sender and delete or destroy this
message and any copies.

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

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************


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

Agus Kwee

Re: sql store procedure multi row fetch
(in response to John Panopoulos)
I also encountered a similar problem on my FETCH statetement,
in my case the error message is about the 'FOR' keyword.
When I deleted the 'FOR' keyword, I received another error message
that mentioned that the 'FOR' keyword is required.
I deployed the DSNTPSMP program preparation in DB2 for z/OS Version 8.

Agus Kwee
Themis Training
http://www.themisinc.com

----- Original Message -----
From: John Panopoulos
Date: Thursday, November 29, 2007 5:08 am
Subject: Re: [DB2-L] sql store procedure multi row fetch
To: [login to unmask email]

> I am using an SQL store Procedure in DB2 V8 and it seems that the
> compiler does not know
>
> this syntax
>
>
>
> FETCH NEXT ROWSET FROM curname FOR 5 ROWS
>
> INTO ...............
>
> ILLEGAL SYMBOL "ROWSET".
>
>
>
> I have used multi row fetch in a Cobol Store Procedure.
>
> What is your opinion about store procedures regarding performance?
>
> SQL Store Procedures or Cobol Store Procedures (multi row fetch)?
>
>
>
> ________________________________
>
> From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
> Behalf Of [login to unmask email]
> Sent: Wednesday, November 28, 2007 6:30 PM
> To: [login to unmask email]
> Subject: Re: [DB2-L] sql store procedure multi row fetch
>
>
>
> It's not that you can't use multi-row fetch. You just can't use
> arraysin conjunction with multi-row fetch. You can do the following:
>
>
>
> FETCH NEXT ROWSET FROM curname FOR 5 ROWS
> INTO
> (vCOL1_1, vCOL2_1, vCOL3_1),
> (vCOL1_2, vCOL2_2, vCOL3_2),
> (vCOL1_3, vCOL2_3, vCOL3_3),
> (vCOL1_4, vCOL2_4, vCOL3_4),
> (vCOL1_5, vCOL2_5, vCOL3_5);
>
>
>
> Each variable will have to be declared separately.
>
> It's ugly (and maybe not practical) but doable.
>
>
>
> Thanks,
>
> John Miller
>
>
>
> The information transmitted is intended only for the addressee
> and may
> contain confidential, proprietary and/or privileged material. Any
> unauthorized review, distribution or other use of or the taking
> of any
> action in reliance upon this information is prohibited. If you receive
> this in error, please contact the sender and delete or destroy this
> message and any copies.
>
> IMPORTANT NOTICE:
>
> IDUG is pleased to announce a series of upgrades to the DB2-L
> discussionlistserv 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
> conferencesat http://conferences.idug.org/index.cfm
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
> **********************************************************************
>
>
> 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

John Miller

Re: sql store procedure multi row fetch
(in response to Agus Kwee)
My apologies to everyone! This is one of those things that I thought I
tested, but I guess I didn't :-(

When I responded I was certain it worked. My apologies again, hope I
didn't waste anybodies time.

On the plus side, Multi-Row fetch is used by distributed applications
which call SQL stored procedures who return a non-ambiguous cursor.
This functionality is available in CM mode with no code changes
required.



Sorry again,

John Miller



________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of [login to unmask email]
Sent: Thursday, November 29, 2007 6:35 AM
To: [login to unmask email]
Subject: Re: [DB2-L] sql store procedure multi row fetch



I also encountered a similar problem on my FETCH statetement,

in my case the error message is about the 'FOR' keyword.

When I deleted the 'FOR' keyword, I received another error message

that mentioned that the 'FOR' keyword is required.

I deployed the DSNTPSMP program preparation in DB2 for z/OS Version 8.



Agus Kwee

Themis Training

http://www.themisinc.com






The information transmitted is intended only for the addressee and may contain confidential, proprietary and/or privileged material. Any unauthorized review, distribution or other use of or the taking of any action in reliance upon this information is prohibited. If you receive this in error, please contact the sender and delete or destroy this message and any copies.

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