HP3000-L Archives

August 1996, 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, 26 Aug 1996 10:55:24 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
Kumar writes:
 
> You can build an IMAGE database in which only some of the datasets are
> jumbo sets. You need to precede the set definition with the directive
> $CONTROL JUMBO
> to make it a jumbo set. You can turn the condition off with
> $CONTROL NOJUMBO
> In effect, all sets following this directive in the schema will be
> non-jumbo sets.
>
> By default, all sets are non-jumbo.
 
Actually, $CONTROL JUMBO simply says "it's ok to make subsequent
datasets jumbo IF their capacities would result in a file of more than
4GB".   I.e., it doesn't force small datasets to become jumbo format.
(If you wanted to do that, for testing purposes, use $CONTROL FORCEJUMBO)
 
$CONTROL NOJUMBO says "don't make any subsequent datasets jumbo, even
if their capacities would result in a file of more than 4GB".
 
--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html

ATOM RSS1 RSS2