ca.portal.admin

LU 6.2 Question

Discussion created by ca.portal.admin on Feb 7, 2006
Hello All:

For those of you that have LU 6.2 in use in IDMS how many LTERM and
PTERM
pairs do you have defined to your communications line?

Bill Allen

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
IDMS with Z/OS 1.7
"We willing be upgrading Z/OS from 1.6 to 1.7. Are there any known
problems for IDMS, IDMS tools, or IDMS Server (mainframe CCITCP) with
Z/OS 1.7? We are running IDMS versions R14.1 SP6 and R16 SP2.

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
TF24501 and TF24477
"Some time ago, we applied TF24501 and TF24477 to our R16 SP2 system, to
fix an ADS linkage problem. These have been superceded by published
APAR's QO75016 and QO75389. We apparently had early versions of the
PTF's, because the published APAR's are different. When we replaced the
PTF's with the published versions, it fixed a second linkage problem
that the PTF's did not fix. So if you have these PTF's applied, you
might want to replace them.

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Performance Degradation after Database Enlarge/Expand
"From: Bill Vohs, SC Data Center, Monroe, Wi
Date: February 1, 2006

Subject: Enlarge/Expand IDMS Database Causes Severe Performance
Degradation

We are running:

z/OS 1.4
IDMS Release 16 SP02
EMC DMX2000 DASD

We have a need to enlarge a number of the IDMS databases.

Every time we do, we experience severe performance degradation.
Run times elongate by a factor of 3 to 5.
Job that ran in 30 minutes now takes 3-4 hours.

Our first attempt was back in November 2005.
The approach at that time was to do an UNLOAD and RELOAD to the enlarged
area.
This time we enlarged the databases by a factor of 3.
I.e. One database went from 15,000 tracks to 45,000 tracks.
Another database went from 7,000 tracks to 21,000 tracks.
These all on 3390 DASD on the EMC DMX2000.

Our run times were:

Before UNLOAD/RELOAD 11/09/2005 74 minutes
11/10/2005 46 minutes

After UNLOAD/RELOAD 11/16/2005 174 minutes
11/1/2005 198 minutes

This happened with almost every one of our jobs.

Our second attempt was January 29, 2006..
The approach this time was to do a EXPAND PAGE to an enlarged area
This time the databases were enlarged by a factor of 2.
One database went from PAGE SIZE 5064 to 10796 from 15,000 tracks to 30,000
tracks.
Another database went from PAGE SIZE 5064 to 10796 from 7,000 tracks to
14,000 tracks.

The run times are:

Before EXPAND PAGE 01/26/2006 64
minutes

After EXPAND PAGE 01/31/2006 209
minutes
02/01/2006 212 minutes


We have had an IDMS consultant review our work and he says every thing looks
great.

Our z/OS and IDMS statistics show nothing out of the ordinary.

We are at a bit of a loss.

Might anybody have any suggestion for us?

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] Performance Degradation after Database Enlarge/Expand
"what are your jobs doing? area sweeps? set navigation? random search?

did you increase the number of buffers for each area to reduce the
potential for buffer flushes?



more information would help us to offer suggestions


Chris Hoelscher
IDMS & DB2 Database Administrator
Humana Inc
502-580-2538
choelscher@humana.com




The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Performance Degradation after Database Enlarge/Expand
"Bill,

Assuming that you've already checked for other things, you are
suggesting that the longer run times are related to I/O. Check the
programs stats and then use dban see how the data is spread out. You
should have done this before the expansion and be able to compare it to
the after view. If you only have the current dban, then find out how the
program is accessing the data. With the dban report, you can tell the
nature of the I/O and what affect it would have.


Will Hathcock
Database Administrator
Sempra Energy Utilities
(858) 654-3524

Outcomes