CV Tuning Tips

Discussion created by ca.portal.admin on Jul 31, 2008
Latest reply on Jul 31, 2008 by ca.portal.admin
Hello All:

Can you share tips for saving CPU Cycles inside the Central Version.

We are running 16.0 SP2 on Z/OS 1.7 very soon to be 1.9. We have a lot of
ADS/O and a lot of DC-COBOL programs. ON Production we only do a load module
migration, there is no source code.

I am aware of turning off symbol tables, what about diagnostic Tables?
Modules Only, in Production)

I am aware of including the Built in Functions in ADSOMAIN.

We are using the High Speed Storage Protection option, we have five storage
pools, 0,1, 128,129 and 255.

We also have PREFETCH on in the central version as we have very large
pools, is this a big CPU eater?

Any other things that we can do to save some CPU Cycles?

Bill Allen
ARCH Consulting Associates, Ltd.
(704) 641-0296

**************Get fantasy football with free live scoring. Sign up for
FanHouse Fantasy Football today.
IDMS 3rd-party providers forum


Re: CV Tuning Tips

Turn off diagnostic tables too in production. I did a quick test and the
load module size went from 9412 to 7452 when I turned off Diagnostic Tables.
Diagnostic tables help developers find and fix programming errors. When a
dialog which has diagnostic tables enabled aborts, process commands which
were executing at the time of the abend appear on the Dialog Abort
Information Screen. ADSODBUG is able to display the code by using the line
numbers from the diagnostic table and then accessing the dictionary for the
actual process code. This display of the actual code which was executing at
the time of the abend makes it easier for developers to quickly pinpoint the
errant code. Since you don't have the source in production, the code the
diagnostic table points at is in another dictionary. I'm not sure you can
get there from here.


Linda J. Casey, PMP
Managing Member
Run Right, LLC