In PICK you'd create a single file which would place the data pointer
into the dictionary. If you wanted more data files to share the
dictionary you'd simply create another data file. e.g.
CREATE-FILE BPFILE 1 15
CREATE-FILE DATA BPFILE,INCLUDES 15
Then you could reference the new data file as BPFILE,INCLUDES...
$INCLUDE BPFILE,INCLUDES INIT.MY.COMMON
The primary purpose of this structure was to share a dictionary
amongst multiple data files. Since a BP file in PICK is nothing more
than another PICK file, one would ultimately find where the BP files
ended up as multi-level files. UniData, but not UniVerse (I believe),
has the ability to mimic these multi-level files, both as regular UD
files and as DIR type files.
When we migrated from PICK (D3) to UniData, we found the UniData
structure to be far more flexible than the old PICK (D3) file
structure. Now, our application account holds our source and compiled
code, our dictionaries, and some global configurations. The hosted
accounts hold the data file(s) and point to the application programs,
account dictionaries, and global configurations. They also have their
own local program file (not used much), local dictionaries (only
because of multi-level files; e.g. PAYROLL,2004 PAYROLL,2005 etc),
and configurations.
But, from a logical point of view, it seems perfectly rational to have
a single directory hold subdirectories, and, therefore, a DIR file to
contain multiple DATA directories. However, in the IT world, there
are always issues with anything. :-)
HTH,
Bill
------------------------------------------------------------------------
Anthony W. Youngman said the following on 3/25/2010 5:49 PM:
In message <00c201cacc68$af62e700$0e28b5...@com>, Larry Hiscock
<[email protected]> writes
Actually, you COULD do this on the Pr1me. Our application was
migrated to
Unidata from Pr1me Information. We always kept program sub-directories
segregated by application (e.g. AR, AP, GL, etc).
But I'm guessing you had *separate* VOC entries for AR, AP etc. At
the OS level they were under one sub-directory but inside of PI they
were separate FILEs.
What I'm talking about - what I think Pick has - is where you have -
at the *PICK* level, one BP FILE, and then loads of subfiles in it.
Which is stored (by default) as one directory with sub-directories at
the OS level.
In other words, in PI you're talking about the OS level - nothing to
with PI. In Pick you're actually IN PICK, it's nothing to do with the
OS.
--Larry
Cheers,
Wol
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Anthony W.
Youngman
Sent: Thursday, March 25, 2010 3:08 PM
To: [email protected]
Subject: Re: [U2] Unidata Silly Gripe
In message <031801cacc3b$feb964a0$fc2c2d...@com>, Symeon Breen
<[email protected]> writes
Just a different way of doing it i suppose - i do have separate sub
directories but they are under the dev account and not under say BP
Just a little point - bearing in mind I've never used genuine Pick
but I
think Larry et al are describing *TYPICAL* Pick usage. You couldn't do
that on Pr1me so anybody (like me) only used to the Pr1me approach this
would seem strange.
We had three (actually four) main program directories on our system,
called CBP, GBP and RBP. But on a Pick system they would typically have
been defined as subfiles of BP, eg BP,COL BP,GEN and BP,REM.
Cheers,
Wol
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Larry
Hiscock
Sent: 25 March 2010 16:23
To: 'U2 Users List'
Subject: Re: [U2] Unidata Silly Gripe
Really? We have more than 20 subdirectories in our program directory.
Each
of them is defined as a "DIR" in Unidata, but at the Unix level (and
convcode is a system-level command, not a Unidata verb) each is
simply a
sub-directory of the source directory.
Larry Hiscock
Western Computer Services
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Symeon
Breen
Sent: Thursday, March 25, 2010 5:35 AM
To: 'U2 Users List'
Subject: Re: [U2] Unidata Silly Gripe
Probably because you would never have subdirectories in your program
directory.
<snip>
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
