DROP DATABASE: Help me understand this Unit of Work - Attn: Rich Fazio

Jay Reavill

DROP DATABASE: Help me understand this Unit of Work - Attn: Rich Fazio
Hello all,

I found the following post in the archives from back in August of 2005.
I'm wondering if there is any overall time savings between the IDCAMS
delete/DB2 drop combination and the DB2 drop by itself? Or is the main
benefit just the avoidance of extended locks? Here's the post by Rich
Fazio...



>>>>>>>

From: DB2 Data Base Discussion List [mailto:[log in to unmask]] On
Behalf Of Richard Fazio
Sent: 24. august 2005 11:38
To: [log in to unmask]
Subject: Re: [DB2-L] DROP DATABASE: Help me understand this Unit of Work


I've read the rest of the thread and wanted to add a point about DROP
DATABASE/TABLESPACE.

Issuing DROP is a synchronous process which removes entries from the DB2
Catalog, Directory, MVS Catalog and Disk volumes. As pointed out by
Phil, DB2 does not care if the datasets are there or not...so, you can
reduce the LOCKING overhead of dropping objects by deleting the
underlying DB2 datasets first.

I have a database structure that has upwards of 20,000 datasets per
database. Occasionally, I have to drop all or most of the tablespaces.
But, I can't stand the locks held on the DB2 Catalog or DBD. So, I
wrote a Rexx Exec that will take a list of objects and generate the JCL
needed to STOP all objects involved (indexes too), IDCAMS delete the
VSAM files, and DROP the tablespaces.

DROP TABLESPACE for a 254 partition tablespace with zero underlying VSAM
datasets takes less than a second :-)

I put this code on "The IDUG Code Place" titled "Drop Tablespace(s) with
very low catalog contention
< http://idug.org/files/CodePlaceFiles/TSDROP%20Rexx%20Exec.txt > ".
Give it a try.
faz

Rich Fazio
DB2 OS390 DBA

TransUnion, LLC
SSG/Data Services Team, 5th Floor
555 West Adams St. Chicago, IL 60661
Phone (312) 985-3270 Fax (312) 466-8398

Talk to teach - Listen to learn


<<<<<<<<<





Thanks,
Jay


----------------------------------------
Jay Reavill DBA
Certegy Card Services
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
----------------------------------------



------------------------------------------------------------------------------
This message contains information from Certegy, Inc which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e:mail [login to unmask email]
======

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

Re: DROP DATABASE: Help me understand this Unit of Work - Attn: Rich Fazio
(in response to Jay Reavill)
The typical DBA response..."it depends" applies.

If you run your IDCAMS synchronously and on the same LPAR as the DB2
subsystem...I've seen no difference.

However, you can run the IDCAMS job on a different LPAR that may have
more CPU and run more jobs concurrently, you can achieve a runtime
improvement.

The level of concurrency is really more a function of your zOS catalog
configuration.
I tried running a few tests regarding throughput a few months ago. The
following times are exaggerated and simply to demonstrate the point...
I do not have exact numbers

1 job ran 1 hour
2 concurrent jobs ran 30 min
3 concurrent jobs ran 20 min
4 concurrent jobs ran 20 min
10 concurrent jobs ran 25 min

At some point more parallel processes did not help.
I hope this helps,
faz

Rich Fazio
Information Architecture

TransUnion, LLC
Marketing Services, 8th Floor
555 West Adams St. Chicago, IL 60661
Phone (312) 985-3270 Fax (312) 466-6453

Talk to teach - Listen to learn


>>> [login to unmask email] 2006-01-18 11:45:48 AM >>>
Hello all,

I found the following post in the archives from back in August of
2005.
I'm wondering if there is any overall time savings between the IDCAMS
delete/DB2 drop combination and the DB2 drop by itself? Or is the main
benefit just the avoidance of extended locks? Here's the post by Rich
Fazio...



>>>>>>>

From: DB2 Data Base Discussion List [mailto:[log in to unmask]] On
Behalf Of Richard Fazio
Sent: 24. august 2005 11:38
To: [log in to unmask]
Subject: Re: [DB2-L] DROP DATABASE: Help me understand this Unit of
Work


I've read the rest of the thread and wanted to add a point about DROP
DATABASE/TABLESPACE.

Issuing DROP is a synchronous process which removes entries from the
DB2
Catalog, Directory, MVS Catalog and Disk volumes. As pointed out by
Phil, DB2 does not care if the datasets are there or not...so, you can
reduce the LOCKING overhead of dropping objects by deleting the
underlying DB2 datasets first.

I have a database structure that has upwards of 20,000 datasets per
database. Occasionally, I have to drop all or most of the tablespaces.
But, I can't stand the locks held on the DB2 Catalog or DBD. So, I
wrote a Rexx Exec that will take a list of objects and generate the
JCL
needed to STOP all objects involved (indexes too), IDCAMS delete the
VSAM files, and DROP the tablespaces.

DROP TABLESPACE for a 254 partition tablespace with zero underlying
VSAM
datasets takes less than a second :-)

I put this code on "The IDUG Code Place" titled "Drop Tablespace(s)
with
very low catalog contention
< http://idug.org/files/CodePlaceFiles/TSDROP%20Rexx%20Exec.txt > ".
Give it a try.
faz

Rich Fazio
DB2 OS390 DBA

TransUnion, LLC
SSG/Data Services Team, 5th Floor
555 West Adams St. Chicago, IL 60661
Phone (312) 985-3270 Fax (312) 466-8398

Talk to teach - Listen to learn


<<<<<<<<<





Thanks,
Jay


----------------------------------------
Jay Reavill DBA
Certegy Card Services
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
----------------------------------------



------------------------------------------------------------------------------
This message contains information from Certegy, Inc which may be
confidential and privileged. If you are not an intended recipient,
please refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have
received this transmission in error, please notify by e:mail
[login to unmask email] .
=====

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

Jay Reavill

Re: DROP DATABASE: Help me understand this Unit of Work - Attn: Rich Fazio
(in response to Richard Fazio)
Thanks Rich, that's exactly what I was looking for.

----------------------------------------
Jay Reavill DBA
Certegy Card Services
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
----------------------------------------




"Richard Fazio"
<[login to unmask email] To: [login to unmask email]
ON.COM> cc:
Sent by: "DB2 Subject: Re: [DB2-L] DROP DATABASE: Help me understand this Unit of Work - Attn: Rich
Data Base Fazio
Discussion List"
<[login to unmask email]
.ORG>


01/18/2006 02:34
PM
Please respond
to "DB2 Database
Discussion list
at IDUG"





The typical DBA response..."it depends" applies.

If you run your IDCAMS synchronously and on the same LPAR as the DB2
subsystem...I've seen no difference.

However, you can run the IDCAMS job on a different LPAR that may have more
CPU and run more jobs concurrently, you can achieve a runtime improvement.

The level of concurrency is really more a function of your zOS catalog
configuration.
I tried running a few tests regarding throughput a few months ago. The
following times are exaggerated and simply to demonstrate the point...
I do not have exact numbers

1 job ran 1 hour
2 concurrent jobs ran 30 min
3 concurrent jobs ran 20 min
4 concurrent jobs ran 20 min
10 concurrent jobs ran 25 min

At some point more parallel processes did not help.
I hope this helps,
faz

Rich Fazio
Information Architecture

TransUnion, LLC
Marketing Services, 8th Floor
555 West Adams St. Chicago, IL 60661
Phone (312) 985-3270 Fax (312) 466-6453

Talk to teach - Listen to learn


>>> [login to unmask email] 2006-01-18 11:45:48 AM >>>
Hello all,

I found the following post in the archives from back in August of 2005.
I'm wondering if there is any overall time savings between the IDCAMS
delete/DB2 drop combination and the DB2 drop by itself? Or is the main
benefit just the avoidance of extended locks? Here's the post by Rich
Fazio...



>>>>>>>

From: DB2 Data Base Discussion List [mailto:[log in to unmask]] On
Behalf Of Richard Fazio
Sent: 24. august 2005 11:38
To: [log in to unmask]
Subject: Re: [DB2-L] DROP DATABASE: Help me understand this Unit of Work


I've read the rest of the thread and wanted to add a point about DROP
DATABASE/TABLESPACE.

Issuing DROP is a synchronous process which removes entries from the DB2
Catalog, Directory, MVS Catalog and Disk volumes. As pointed out by
Phil, DB2 does not care if the datasets are there or not...so, you can
reduce the LOCKING overhead of dropping objects by deleting the
underlying DB2 datasets first.

I have a database structure that has upwards of 20,000 datasets per
database. Occasionally, I have to drop all or most of the tablespaces.
But, I can't stand the locks held on the DB2 Catalog or DBD. So, I
wrote a Rexx Exec that will take a list of objects and generate the JCL
needed to STOP all objects involved (indexes too), IDCAMS delete the
VSAM files, and DROP the tablespaces.

DROP TABLESPACE for a 254 partition tablespace with zero underlying VSAM
datasets takes less than a second :-)

I put this code on "The IDUG Code Place" titled "Drop Tablespace(s) with
very low catalog contention
< http://idug.org/files/CodePlaceFiles/TSDROP%20Rexx%20Exec.txt > ".
Give it a try.
faz

Rich Fazio
DB2 OS390 DBA

TransUnion, LLC
SSG/Data Services Team, 5th Floor
555 West Adams St. Chicago, IL 60661
Phone (312) 985-3270 Fax (312) 466-8398

Talk to teach - Listen to learn


<<<<<<<<<





Thanks,
Jay


----------------------------------------
Jay Reavill DBA
Certegy Card Services
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
----------------------------------------



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

This message contains information from Certegy, Inc which may be
confidential and privileged. If you are not an intended recipient, please
refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have received
this transmission in error, please notify by e:mail [login to unmask email]
.
=====


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

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




------------------------------------------------------------------------------
This message contains information from Certegy, Inc which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e:mail [login to unmask email]
=====

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

Jay Reavill

Re: DROP DATABASE: Help me understand this Unit of Work - Attn: Rich Fazio
(in response to Jay Reavill)
Thanks Rich, that's exactly what I was looking for.

----------------------------------------
Jay Reavill DBA
Certegy Card Services
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
----------------------------------------




"Richard Fazio"
<[login to unmask email] To: [login to unmask email]
ON.COM> cc:
Sent by: "DB2 Subject: Re: [DB2-L] DROP DATABASE: Help me understand this Unit of Work - Attn: Rich
Data Base Fazio
Discussion List"
<[login to unmask email]
.ORG>


01/18/2006 02:34
PM
Please respond
to "DB2 Database
Discussion list
at IDUG"





The typical DBA response..."it depends" applies.

If you run your IDCAMS synchronously and on the same LPAR as the DB2
subsystem...I've seen no difference.

However, you can run the IDCAMS job on a different LPAR that may have more
CPU and run more jobs concurrently, you can achieve a runtime improvement.

The level of concurrency is really more a function of your zOS catalog
configuration.
I tried running a few tests regarding throughput a few months ago. The
following times are exaggerated and simply to demonstrate the point...
I do not have exact numbers

1 job ran 1 hour
2 concurrent jobs ran 30 min
3 concurrent jobs ran 20 min
4 concurrent jobs ran 20 min
10 concurrent jobs ran 25 min

At some point more parallel processes did not help.
I hope this helps,
faz

Rich Fazio
Information Architecture

TransUnion, LLC
Marketing Services, 8th Floor
555 West Adams St. Chicago, IL 60661
Phone (312) 985-3270 Fax (312) 466-6453

Talk to teach - Listen to learn


>>> [login to unmask email] 2006-01-18 11:45:48 AM >>>
Hello all,

I found the following post in the archives from back in August of 2005.
I'm wondering if there is any overall time savings between the IDCAMS
delete/DB2 drop combination and the DB2 drop by itself? Or is the main
benefit just the avoidance of extended locks? Here's the post by Rich
Fazio...



>>>>>>>

From: DB2 Data Base Discussion List [mailto:[log in to unmask]] On
Behalf Of Richard Fazio
Sent: 24. august 2005 11:38
To: [log in to unmask]
Subject: Re: [DB2-L] DROP DATABASE: Help me understand this Unit of Work


I've read the rest of the thread and wanted to add a point about DROP
DATABASE/TABLESPACE.

Issuing DROP is a synchronous process which removes entries from the DB2
Catalog, Directory, MVS Catalog and Disk volumes. As pointed out by
Phil, DB2 does not care if the datasets are there or not...so, you can
reduce the LOCKING overhead of dropping objects by deleting the
underlying DB2 datasets first.

I have a database structure that has upwards of 20,000 datasets per
database. Occasionally, I have to drop all or most of the tablespaces.
But, I can't stand the locks held on the DB2 Catalog or DBD. So, I
wrote a Rexx Exec that will take a list of objects and generate the JCL
needed to STOP all objects involved (indexes too), IDCAMS delete the
VSAM files, and DROP the tablespaces.

DROP TABLESPACE for a 254 partition tablespace with zero underlying VSAM
datasets takes less than a second :-)

I put this code on "The IDUG Code Place" titled "Drop Tablespace(s) with
very low catalog contention
< http://idug.org/files/CodePlaceFiles/TSDROP%20Rexx%20Exec.txt > ".
Give it a try.
faz

Rich Fazio
DB2 OS390 DBA

TransUnion, LLC
SSG/Data Services Team, 5th Floor
555 West Adams St. Chicago, IL 60661
Phone (312) 985-3270 Fax (312) 466-8398

Talk to teach - Listen to learn


<<<<<<<<<





Thanks,
Jay


----------------------------------------
Jay Reavill DBA
Certegy Card Services
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
----------------------------------------



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

This message contains information from Certegy, Inc which may be
confidential and privileged. If you are not an intended recipient, please
refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have received
this transmission in error, please notify by e:mail [login to unmask email]

=====


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

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




------------------------------------------------------------------------------
This message contains information from Certegy, Inc which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e:mail [login to unmask email]
=====

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

Jay Reavill

Re: DROP DATABASE: Help me understand this Unit of Work - Attn: Rich Fazio
(in response to Jay Reavill)
Thanks Rich, that's exactly what I was looking for.

----------------------------------------
Jay Reavill DBA
Certegy Card Services
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
----------------------------------------




"Richard Fazio"
<[login to unmask email] To: [login to unmask email]
ON.COM> cc:
Sent by: "DB2 Subject: Re: [DB2-L] DROP DATABASE: Help me understand this Unit of Work - Attn: Rich
Data Base Fazio
Discussion List"
<[login to unmask email]
.ORG>


01/18/2006 02:34
PM
Please respond
to "DB2 Database
Discussion list
at IDUG"





The typical DBA response..."it depends" applies.

If you run your IDCAMS synchronously and on the same LPAR as the DB2
subsystem...I've seen no difference.

However, you can run the IDCAMS job on a different LPAR that may have more
CPU and run more jobs concurrently, you can achieve a runtime improvement.

The level of concurrency is really more a function of your zOS catalog
configuration.
I tried running a few tests regarding throughput a few months ago. The
following times are exaggerated and simply to demonstrate the point...
I do not have exact numbers

1 job ran 1 hour
2 concurrent jobs ran 30 min
3 concurrent jobs ran 20 min
4 concurrent jobs ran 20 min
10 concurrent jobs ran 25 min

At some point more parallel processes did not help.
I hope this helps,
faz

Rich Fazio
Information Architecture

TransUnion, LLC
Marketing Services, 8th Floor
555 West Adams St. Chicago, IL 60661
Phone (312) 985-3270 Fax (312) 466-6453

Talk to teach - Listen to learn


>>> [login to unmask email] 2006-01-18 11:45:48 AM >>>
Hello all,

I found the following post in the archives from back in August of 2005.
I'm wondering if there is any overall time savings between the IDCAMS
delete/DB2 drop combination and the DB2 drop by itself? Or is the main
benefit just the avoidance of extended locks? Here's the post by Rich
Fazio...



>>>>>>>

From: DB2 Data Base Discussion List [mailto:[log in to unmask]] On
Behalf Of Richard Fazio
Sent: 24. august 2005 11:38
To: [log in to unmask]
Subject: Re: [DB2-L] DROP DATABASE: Help me understand this Unit of Work


I've read the rest of the thread and wanted to add a point about DROP
DATABASE/TABLESPACE.

Issuing DROP is a synchronous process which removes entries from the DB2
Catalog, Directory, MVS Catalog and Disk volumes. As pointed out by
Phil, DB2 does not care if the datasets are there or not...so, you can
reduce the LOCKING overhead of dropping objects by deleting the
underlying DB2 datasets first.

I have a database structure that has upwards of 20,000 datasets per
database. Occasionally, I have to drop all or most of the tablespaces.
But, I can't stand the locks held on the DB2 Catalog or DBD. So, I
wrote a Rexx Exec that will take a list of objects and generate the JCL
needed to STOP all objects involved (indexes too), IDCAMS delete the
VSAM files, and DROP the tablespaces.

DROP TABLESPACE for a 254 partition tablespace with zero underlying VSAM
datasets takes less than a second :-)

I put this code on "The IDUG Code Place" titled "Drop Tablespace(s) with
very low catalog contention
< http://idug.org/files/CodePlaceFiles/TSDROP%20Rexx%20Exec.txt > ".
Give it a try.
faz

Rich Fazio
DB2 OS390 DBA

TransUnion, LLC
SSG/Data Services Team, 5th Floor
555 West Adams St. Chicago, IL 60661
Phone (312) 985-3270 Fax (312) 466-8398

Talk to teach - Listen to learn


<<<<<<<<<





Thanks,
Jay


----------------------------------------
Jay Reavill DBA
Certegy Card Services
11601 Roosevelt Blvd.
St. Petersburg, FL. 33716
Office (727) 227-2144
----------------------------------------



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

This message contains information from Certegy, Inc which may be
confidential and privileged. If you are not an intended recipient, please
refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have received
this transmission in error, please notify by e:mail [login to unmask email]
.
=====


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

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




------------------------------------------------------------------------------
This message contains information from Certegy, Inc which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e:mail [login to unmask email]
=====

---------------------------------------------------------------------------------
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 e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.

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