HP3000-L Archives

May 1998, Week 3

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:
Ron Horner <[log in to unmask]>
Reply To:
Ron Horner <[log in to unmask]>
Date:
Fri, 15 May 1998 07:45:14 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
Trying to use that kind of a shortcut, may be more work than to know.  The
datasets within an image database should be considered as one database, and
not just a series of files that are linked together.  Believe me, it's
easier to re-do the tables.

Later




[log in to unmask] on 05/14/98 02:11:54 PM

To:   [log in to unmask]
cc:    (bcc: Ron Horner/MIS/CorpCtrl/STO)
Subject:  Store, Restore Dataset




We've recently upgraded a third party payroll package on our development
machine. This required setting up new tables which are included in a single
Image dataset. We're getting ready to run the upgrade again ( for practice
before upgrading our production machine) on the developmnent machine, but
we
would like to avoid re-doing all the table entries again. And those same
tables will be used on the production machine as well. So here's my
question:  What's the best way of storing/restoring that dataset?  We're
running MPE/ix 5.0 with Adager.
I know that you can  STORE the db and RESTORE individual datasets, but I'm
concerned that I might get into trouble with the root file.  The payoll
folks suggested a procedure to use Query to save the dataset entries to a
file and use Dbgeneral to write the info back into the dataset, but we
don't
have that option.
Thanks for any help....Cary Marshall

ATOM RSS1 RSS2