To do this you must already have the source code compiled on your multivalued database system.
To use MVtools from another account you must first create a Q-pointers to the MVBP file for the programs and either create a local MVOB file for the parameters (Settings) and properties or set up a Q-pointer to this file too.
MVSETSYS creates all the special TCL commands used in MVtools. Eg SORT4 , SE (screen editor) etc., It should also unpack a help file onto the system and various parameter items into MVOB. This should be done on each account immediately after each new release has been installed
After running MVSETSYS check the file MVOB for a number of new records/items created and unpacked. If there are a number of HLP_ (Help text) items then the unpack of MVRELDAT was successfull!!
This can be done using an editor to create MD (VOC) entries as follows:
Create a Q-pointer to the programs file MVBP
001 Q
002 MVT
003 MVBPversion
Where version is the version number of MVTOOLS
Eg if you downloaded Version 56 then create a file in MVT call MVBP.56 and set up the Q-pointer from each account named 'MVBP' to point to this version
This allows for 'switching' of versions Catalog all the programs in MVBP CATALOG MVBP * Create a Q-pointer to the parameter file MVOB.
Note: This file may be empty if you have just created the MVT account and loaded the programs. Items will appear in the MVOB file when you set up the system using MVCHECKS etc.,
Once all the programs have been compiled and catalogued. Run the MVSETSYS program to unpack all the help for the admin and development options.This program will ask you to create some files and re-run MVSETSYS if any files cannot be opened.
The tools may also ask you to create a workfile MVWORK. This file can be created 1,1 1,7 as the main data area is hardly used and the system will create other data areas as sub-files per user. The actual file name for this workfile will be on the SPCMAN settings screen..So can be changed if your existing system already has a workfile of this kind.
A default filename table is unpacked first onto MVOB item FILES and this has been set to unpack all object types into the same file MVOB. It achieves this by using suffixes and prefixes to the itemid. For example user profiles will be set to be stored on the MVOB file using a prefix USR_ This can be changed later using the FNMMAN screen. It was set up this way so that MVtools can be installed quickly after creating only one or two files. Because the filenames are defined in FNMMAN screen and the attributes for each file are defined using templates it is often possible to set up Mvtools to use an existing structure. MVtools tries to enhance your MV system and not dictate to you how things should be done. This is the reason for including a subroutine library resource for old legacy systems.