Hi all,
I am working with a client who is still using IDMS Release 14.1; they
are aware that CA has dropped support. Their systems people plan to
upgrade from z/OS 1.4 to z/OS 1.7, and the timing, of course, coincides
will the release of another system - of a critical nature.
I have been asked to find any information that I can regarding the
compatibility of IDMS 14.1 with z/OS 1.7. I'd greatly appreciate any
information that you can share.
While it is my client's hope that it has been others' experiences that
14.1 and z/OS 1.7 does not have any compatibility issues, I also would
appreciate any feedback how ""easy"" the upgrade from 14.1 to 15.0 is.
When the client contacted CA regarding the compatibility issue, they
were referred to Support and told there was no information available.
Also the manager stated:
""I have heard that it's very easy to upgrade to 15.0 from 14.1,
so you may
have to do that.""
Thanks for your help.
Cindy Kline
cakask@aol.com
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
Re: PAGE RESERVE AND CALC ALGORITHM
"Usually don't reply, but am bored today
Page reserve for calc records, not a good idea. Why? Your calc
algorithm and your number of pages should be such that there is (more or
less) an even fill factor across all pages. If you have a lot of calcs
going to the same page, then maybe you need to pick a better number of
pages (does prime+1 still make a difference?) or fix up the calc key to
be more random (there are a number of ways to do that)
So lets say you have 100 records, and 10 pages, and each page can hold
15 pages.
So let's say that the number of records per page after the load is
something like this (x-y where x is the page number and y is the number
of recs)
1-10 2-9 3-12 4-12 5-13 6-8 7-11 8-10 9-7 10-10
Now let's say that you pick a max of 10 records per page for you page
reserve thing - so now what you have is
1-10 2-9 3-11 4-11 5-11 6-11 7-11 8-11 9-7 10-10
A lot more even with room on each page - except that 1 of the calcs for
page 3 is on page 6, one of the calcs for page 4 is on page 6, one of
the calcs for page 5 is on page 6 and another one is on page 8. (and
exactly how they get spread around would really depend on how they were
loaded and could be more convoluted then this, but I think you might get
the idea)
So although you might have accomplished leaving more room on each page,
you haven't helped the calc situation at all, and even at the start, you
have unnecessary calc overflow situations.
If you run out of space with a calc area you could use an expand page
first. If that is not possible, then extending would work, but the
extended portion would only be used for overflow and no calc records
would 'calc' to those pages. When you extend, if done correctly, there
is no change in the calc algorithm - if there is, you did something
wrong and will be in major big trouble.
As an aside, you can check out your fill factor prior to loading by
using idmscalc and some quick programming - obviously depends on the
number of records, pages, etc. as to what is involved
Mark judd
Long time dba