HP3000-L Archives

January 2003, 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:
Dennis Hassell <[log in to unmask]>
Reply To:
Dennis Hassell <[log in to unmask]>
Date:
Fri, 24 Jan 2003 17:04:58 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (127 lines)
Friedrich,

I can't quite tell what the problem is about sharing the database with
new companies.
- Is there a security issue where some records or datasets need to be
hidden from the various companies?
- Is there a sizing issue where all the possible users cannot log onto
the same machine?
- Is there another issue?

Usually, you'd just add the logons to the security system you are using
and let people in. What is the issue with just opening the database up
to the new companies?

Dennis Hassell


-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Friedrich Harasleben
Sent: Thursday, January 23, 2003 5:02 AM
To: [log in to unmask]
Subject: [HP3000-L] sharing datasets in POWERHOUSE (long)


 Our POWERHOUSE application is not mandateable, nevertheless we need to
handle a second (and maybe third) company with the same environment
shortly.

We think of dublicating all our databases into a new account (OEKVP), do
some slight program modifications (for currency adjustments) and that
should do the trick. Nevertheless we want to "share" 2 detail datasets
(and their masters if necessary) from one central database among the
different accounts.

To be more specific:

Database OEKV has detail set RIS-D (linked to automatic master RIS-A and
VERSFALL-A) and detail FREMNR-D (linked to automatic masters RIS-A,
FREMDNR-A, FREMDBEZ-M) and many other details (some of them also link to
RIS-A) and masters.

As RIS-D contains several millions entries and the entries are the same
for all accounts (companies) it does not make sense to copy them.

1) Idea:

In the new account OEKVP we create a dictionary containing database OEKV
with all datasets except RIS-D and FREMDNR-D. And create an additional
entry for a "fake" database OEKVX with definitions for RIS-D and
FREMDNR-D and an open statement, which directs the program to the
central account OEKVC.

like
  File
OEKV
&  -> for the local copies of DB OEKV (without RIS-D)
  Organization
Database                                                      &
  Password
"XXXXXX"                                                           &
  Open OEKV.PHDB

and
File
OEKVX
& -> for the central copie of DB OEKVE with RIS-D
  Organization
Database                                                      &
  Password
"XXXXXX"                                                           &
  Open OEKV.PHDB.OEKVC                                              &

My main questions are:
a) is this possible or is it necessary to define all the master
(automatic or manual) datasets necessary to access the key items of
RIS-D and FREMDNR-D  in the fake DB too?
b) if yes - how can we differentiate them from those master (automatic
or manual) datasets, which have the same name but link to different sets
in database OEKV (instead of the sets in OEKVX), like dataset RISOBPOD-D
also is linked to RIS-A?

I added some FO PATHS information from QUERY

FREMDBEZ-M        FREMDNR-D         KZNR
FREMDNR-A         FREMDNR-D         FREMDNUMMER
RIS-A             ANBOPOS-D         RISIKONUMMER
                  ANBOPOS1-D        RISIKONUMMER
                  ANTRISOB-D        RISIKONUMMER
                  FREMDNR-D         RISIKONUMMER      KZNR
                  PROTRIS-D         RISIKONUMMER
                  RIRV-D            RISIKONUMMER
                  RIS-D             RISIKONUMMER
                  RISAUSK-D         RISIKONUMMER      BONIDAT
                  RISHIS-D          RISIKONUMMER      BONIDAT
                  RISOBPOS-D        RISIKONUMMER      DATAB
                  SOKOND-D          RISIKONUMMER
                  SOKONDTX-D        RISIKONUMMER
                  UERISOB-D         RISIKONUMMER      DATAB
                  VN-D              RISIKONUMMER
                  VSSUMMEN-D        RISIKONUMMER
                  VSUMMEN-D         RISIKONUMMER
VERSFALL-A        ANBOPOS-D         VERSFALLNR
                  ANBOPOS1-D        VERSFALLNR
                  RIS-D             VERSFALLNR
                  UERISOB-D         VERSFALLNR
FREMDNR-D         RISIKONUMMER      KZNR              RIS-A
                 !FREMDNUMMER                         FREMDNR-A
                  KZNR                                FREMDBEZ-M
RIS-D            !RISIKONUMMER                        RIS-A
                  VERSFALLNR                          VERSFALL-A



2) other Ideas????

Is there an alternative to do the same thing?

best regards
Friedrich

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2