HP3000-L Archives

May 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Mon, 22 May 2000 13:11:10 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
Re:
> two datasets, on has 32 chunks and one has only six (from two different data
> bases -- I've telescoped the listings)? Is this documented anywhere? Except for
> the 32-chunk dataset, all of our other jumbo datasets have what I would call a
> reasonable quantity of chunks: 2 - 6.
> Does this unusually large quantity of chunks indicate some problem?

That's not a problem.

The jumbo code allows up to 99 chunks (easily expanded to 999 by a recompilation
of IMAGE source code, if ever needed).

There's a chance that the 32 chunks was caused by some early version of
IMAGE and/or a tool, perhaps trying to allocate space on a checkerboarded
system.

If you were to repack the dataset with a current version of ADAGER,
the result will be a dataset with the minimal number of chunks.  I can't
speak for other tools or versions.


Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler

ATOM RSS1 RSS2