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:
K N Kumar <[log in to unmask]>
Reply To:
K N Kumar <[log in to unmask]>
Date:
Mon, 26 Aug 1996 12:10:45 IST
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines)
Stan wrote:
 
>
> Neil asks:
>
> > Well, we've hit the (previous) limits of TurboImage!
> ...
>
> > How do I build one of the new Jumbo datasets? I've scanned the CD-ROM,
> > and I can't find it.
>
> First, you must be on MPE/iX 5.0 or later.
>
> Second, you need the version of TurboIMAGE that supports Jumbo
> datasets.  Unfortunately, I can't remember the version number, but here's
> one way you can determine if you have it.  Do the following, and see if
> DBSCHEMA reports an error on the "$CONTROL JUMBO" line:
>
>    :run dbschema.pub.sys
>    $control jumbo
>    :eod
>
> If no error from "$CONTROL JUMBO", then you are on the jumbo-capable
> IMAGE.  If you got an error like:
>    ***** ERROR *****  IMPROPER COMMAND PARAMETER
> then you aren't.
 
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.
 
 
Kumar
CSY R&D, Bangalore

ATOM RSS1 RSS2