Creating a Unidata account from a Universe account

[Jonathan Wells]

Hi all,

I recently started a new job with the Aptron Corporation.  I use to work for Campbell University (and Beloit College before that) working with Colleague which runs on Unidata.  I'm still learning their products, which includes MVQuery.  They have a (Windows) server setup with Unidata (ver 8.2) that I was starting to look at as part of learning MVQuery.  [I was use to Linux/Unix, so getting into Unidata on Windows has been interesting.]  Aptron's main product with is called Collegix runs on Universe.  A now retired employee wrote a program (or programs?) that would take one of their Universe accounts and create a Unidata account out of it.  I went into one of these converted accounts, and started to poke around.  I wanted to see what  "F" pointers lived in the VOC, and was met with strange error messages: -> " 'NEWACC' does not exist in VOC file".  I had to Ctrl-C out of that.  [SELECT VOC WITH F1 LIKE F... -->  then -->  SORT VOC] As I understand it 'NEWACC' is a Universe thing, so apparently the account conversion did not work completely.  BTW - The server has the 'U2 Extensible Administration Tool" loaded, and it is able to show me a list of files in that account.

-> If anyone has successfully converted a Universe account to a Unidata account, what methods/tools did you use? 

-> Or - if you have an idea on how to fix the plumbing in this converted account, I'd love to hear about it.

Thank you,

Jon Wells

[Douglas Tatelman]

Why not just stick with UV?  

[Wol]

On 22/05/2025 00:15, 'Jonathan Wells' via Pick and MultiValue Databases
wrote:

> I wanted to see what  "F" pointers lived in the VOC, and was met with
> strange error messages: -> " 'NEWACC' does not exist in VOC file".  I
> had to Ctrl-C out of that.  [SELECT VOC WITH F1 LIKE F... -->  then -->
> SORT VOC] As I understand it 'NEWACC' is a Universe thing, so apparently
> the account conversion did not work completely.  BTW - The server has
> the 'U2 Extensible Administration Tool" loaded, and it is able to show
> me a list of files in that account.

That makes me think the tool converted all the files etc across, but did
not mess with the contents of those files. So you have a UV VOC file in
a UD file structure.

I remember something like the ACCOUNT.UPDATE command in UV. Is there
something similar in UD? You'll have to set it up manually, but it will
then hopefully go through the VOC etc making sure everything is set up
how UD likes it.

Cheers,
Wol

[Rex Gozar]

At a prior job, we would build our product for both UV and UD. Our source code repository contained the source, metadata, dictionary, and data records needed to build an entire account.

At a later job, I wrote ACCOUNT2DIR (account to directory) that extracted source, metadata, dictionary, and data records into a text file / directory structure that could be stored in SCC. I also wrote DIR2ACCOUNT to reverse the process, recreating files from the metadata and reloading records. These utilities became a part of our SCC and software build processes.

You could write your own version of these utilities, taking into consideration your application's file structure.

--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+un...@googlegroups.com
For more options, visit http://groups.google.com/group/mvdbms
---
You received this message because you are subscribed to the Google Groups "Pick and MultiValue Databases" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mvdbms+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/mvdbms/2283b8b6-cc6a-42bd-bb53-e2fda61e4cb3%40youngman.org.uk.

[Jonathan Wells]

Since MVQuery can connect to Universe, Unidata, and D3, a now retired employee created a routine to create UD accounts out of existing UV accounts in order to create a development environment.  Apparently this routine did not work as hoped.  I have since discovered issues with some of the dictionary entries.  

Cheers,

Jon Wells