ca.portal.admin

Why 1211?

Discussion created by ca.portal.admin on Mar 13, 2009
Latest reply on Mar 13, 2009 by ca.portal.admin
A batch job received a 1211 abend on an index area that was 72% full. A FI=
ND for ""orph"" in the B-tree output did not get very many hits, but each ORP=
H=3D statement showed thousands of orphans. When the index was rebuilt it =
went down to 68% and the job was rerun successfully. My guess is that ther=
e is a really bad SR8 length on the index. Is that the most likely cause, =
or should I be looking elsewhere?

We're on Release 16. The index has been around for years with no other pro=
blems.

TIA,

Jerry



=20
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Why 1211?
"Hi Jerry,

The index ""being around for years"" might be the problem. Over the years, modifying this index caused fragmentation. I don't think TUNE INDEX would have helped because you had so many orphans.
You did the right thing by rebuilding the index. We schedule regular index rebuild jobs on our most actively updated indexes.
It wouldn't hurt to review your page size, SR8 size, index key length, etc.
Sixty eight percent utilization does not leave much room for growth. This must be a fairly static index to have been around for years with no issues.
There is a calculation that you can use in the IDMS documentation to maximize to efficiency of your index areas.

Best of luck,

Jim

Outcomes