HP3000-L Archives

June 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:
"F. Alfredo Rego" <[log in to unmask]>
Reply To:
F. Alfredo Rego
Date:
Mon, 26 Jun 2000 04:10:28 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (43 lines)
Russell Bevers <[log in to unmask]> wrote:

>I get errors if I define my detail datasets prior to the master datasets
>that their search items reference.  Is there any way around this?
>
>If not, why is this limitation imposed?


See http://www.adager.com/AdagerGuide12.html#79498 and, in particular:

        Adager honors IMAGE's requirement that a path's master must come
        before the detail, for DBLOAD's sake - as enforced by DBSCHEMA.
        If you specify a master that is currently "behind" the detail,
        Adager shuffles datasets to comply with IMAGE's rules.

--------------------------


Notice the crucial statement in Adager's Guide, "for DBLOAD's sake -
as enforced by DBSCHEMA."

DBLOAD loads datasets in sequence.  If a detail with a million entries
has a path to a MANUAL master, then such manual master must be loaded
BEFORE the detail (otherwise, DBLOAD would get lots of errors because the
necessary master entries would not exist).

Automatic masters don't present this problem, because they are not
unloaded by DBUNLOAD and automatic-master entries are created on the fly ad
DBLOAD time.

So, there is no reason to include automatic masters in the restriction.
But there are many things that happen without reason :-)

So, you are being held hostage by DBLOAD:

   - Adager could not care less, but it enforces the rule for DBLOAD's sake.

   - DBSCHEMA could not care less, but it also enforces the rule for DBLOAD's
     sake.


Alfredo

ATOM RSS1 RSS2