MVtools - Installation Example 1

Direct Cut and Paste from Web Site

Example MVtools Ver 71 Installation onto OpenQM for Windows. (Although should be similar for linux version accept for starting QMconsol from program manager etc.,)

Using source code downloaded from MVtools Source Library
Review of OpenQM

Simply work through each of these steps in turn

  1. Download Open QM From Ladybridge.
  2. Download MVtools source code From this site. Save into a subdirectory of QMSYS called MVBP. This will be used to store the source code programs.
  3. Create another subdirectory of QMSYS called MVOB. This is for storing the parameters and objects for MVtools.
  4. Run QMconsole from the QM program group on windows program manager
  5. At the logon prompt Account.. Enter QMSYS
  6. At the command line enter CREATE.ACCOUNT MVT MVT
    Yes the account name is entered twice in this command. Once for the account name and once to define the pathname at the host OS filesystem level. Answer Y to the question Create new directory for account (Y/N)?
  7. At the command line still in the QMSYS account. Enter LOGTO MVT. Now type WHO so that the QM system verifies that you are now logged to the MVT account
  8. We need a dictionary for the MVOB file which was created earlier at the host OS level. So create this with CREATE.FILE DICT MVOB
  9. We will need a User work file so create this with the command CREATE.FILE MVWORK

  10. Create voc entry definitions for the MVtools directories so that they appear as files in OpenQM. The MVBP directory and the MVOB directories are crucial, but also you will need the directory PACKDATA for downloading or automatically setting up system setup information, properties etc.,

    ED VOC MVBP MVOB PACKDATA. The Voc entries should look like this.
    0001 F
0002 @QMSYS\MVBP

0001 F
0002 @QMSYS\MVOB

0001 F
0002 @QMSYS\PACKDATA
    Note the unix style backslash used in the path name.
  11. Create a synonm of the VOC directory called MD for compatibility with other Pick Type systems where the VOC is the MD. 
    0001 F
0002 VOC
0003 @QMSYS\VOC.DIC
    This should match the definition of the VOC on the VOC. Eg CT VOC VOC
  12. Copy all the downloaded MVtools source code into the sub-directory QMSYS/MVBP if you haven't already done so. Each source code file will be a file item of the OpenQM directory type file MVBP. (MVtools Basic Programs)
  13. Compile all the programs in the MVBP program file. To do this, type BASIC MVBP * Note: Not all MVBP programs compile as:
    1. Some code is for inclusion when compiling programs but does not compile by it's self.
    2. Some code is for compilation on other platforms and will not compile on OpenQM as it contains functions or syntax perculiar to these platforms. This code is provided so that the MVtools can be migrated.
  14. Catalog all the programs. Enter the command CATALOG MVBP *
  15. Run the MVtools set up routine MVSETSYS From TCL type MVSETSYS. If this fails and askes for files to be created or programs to be catalogued then try to address these issues before continueing. If in doubt refer to the help files by typing HELP
  16. Start checking the MVtools functions and setting. Run the program MVCHECKS from TCL by typing MVCHECKS from the TCL command line.
    1. Test keyboard input Make sure that when ever a normal character such as 'f' is pressed, it is detected and displayed without requiring a return key to 'ENTER'
    2. Map keysAutodetect all the keys prompted and store the detected ascii sequences. This is required for all data entry forms and editing using MVtools
    3. Test the keymap using the editorCheck that the editor is able to function using the special keys detected already.
  17. Check that command line statements are visible to the tcl processor of mvtools. Test this with an MVtools TCL command that uses more than a single word. Eg SE FILENAME ITEMID or KE FILENAME ITEMID If the editor is not loaded with the correct item from the right file then this is probably due to a problem in mvtclrun failing to read the command line properly. Check the platform manual for Procread etc., This could be a good time to check that the editor is configured properly and all the keys listed in the editors F1 HELP FILE work well.
  18. Try to load the system setup properties form. Type SPCMAN from TCL and check that you can navigate this form using arrow keys and save changes using F2. Once you are happy with the navigation and behaviour of this form then check all the data entered is relevant to your system.
  19. Next check the behaviour of a small database and multivalued fields on forms. Use RPGMAN to fire up the query reports database form. This has multiple pages and a number of multivalued fields. Check the following:
    1. When more than two queries have been created can you select a query using f3 instead of typing in the query ID
    2. Can you insert and delete multivalued sets, even when these are made of a number of control/dependant field values?
  20. You are probably all set to build applications now using this site as a guide