Poor performance for OS/390 updating Win2K UDB

Joel Pankonin

Poor performance for OS/390 updating Win2K UDB
We have a batch process running on the OS/390 platform that updates tables
on a Win2k platform and it runs for 12 hours. We duplicated the objects/
data on OS/390 and it runs in 5 minutes. We are at UDB v7.2 fixpack 6 on
client and DB2 v7.1 on OS/390.



Venkatesh Mokshagundam

Re: Poor performance for OS/390 updating Win2K UDB
(in response to Joel Pankonin)
Joel, first thing I would check is the WLM settings, particularly for DDF.
We have been bitten by this (there is a bunch of replies to my performance
problem question if you search archives - our problem was the other way
around, application to DB2 OS/390). We did not have an enclave for DDF set
in WLM. IBM has an informational APAR as well (II10488). See if it applies
to your scenario.

There are other components like VTAM TCP/IP, Network, DB2 Connect (if
applicable) which can affect performance as well that you may want to
monitor.

HTH,

Venkatesh Mokshagundam
Database Administrator
Corporate Systems,
Amarillo, TX 79102
Ph: 806-337-3374
Fax: 806-345-2736

-----Original Message-----
From: Joel Pankonin [mailto:[login to unmask email]
Sent: Friday, December 13, 2002 12:38 PM
To: [login to unmask email]
Subject: Poor performance for OS/390 updating Win2K UDB


We have a batch process running on the OS/390 platform that updates tables
on a Win2k platform and it runs for 12 hours. We duplicated the objects/
data on OS/390 and it runs in 5 minutes. We are at UDB v7.2 fixpack 6 on
client and DB2 v7.1 on OS/390.






The information contained in this communication,
including attachments, is strictly confidential
and for the intended use of the addressee only;
it may also contain proprietary, price sensitive,
or legally privileged information. Notice is
hereby given that any disclosure, distribution,
dissemination, use, or copying of the information
by anyone other than the intended recipient is
strictly prohibited and may be illegal. If you have
received this communication in error, please notify
the sender immediately by reply e-mail, delete this
communication, and destroy all copies.


Corporate Systems, Inc. has taken reasonable precautions
to ensure that any attachment to this e-mail has been
swept for viruses. We specifically disclaim all liability
and will accept no responsibility for any damage sustained
as a result of software viruses and advise you to carry out
your own virus checks before opening any attachment.



Edward Long

Re: Poor performance for OS/390 updating Win2K UDB
(in response to Venkatesh Mokshagundam)
Hi Joel.
If it were me, I'd start by copying the data down to
the PC and run the same SQL locally on the WINDOWS
box.
This would bracket the problem.
If the same SQL run on WIN2k also runs in 5 minutes
then its something in between(like the network) or
WLM.
If the same SQL on WIN2K takes 12 hours, time to tune
WIN2k.

--- Joel Pankonin <[login to unmask email]> wrote:
> We have a batch process running on the OS/390
> platform that updates tables
> on a Win2k platform and it runs for 12 hours. We
> duplicated the objects/
> data on OS/390 and it runs in 5 minutes. We are at
> UDB v7.2 fixpack 6 on
> client and DB2 v7.1 on OS/390.
>
>
> To change your subscription options or to cancel
> your subscription visit the DB2-L webpage at
> http://listserv.ylassoc.com. The owners of the list
> can be reached at
[login to unmask email]


=====
Edward Long