INSTALLING FILEMAN VERSION 22.2

(From the VA FileMan Installation Guide)
The installation is similar to that of earlier version of FileMan.

1. Be sure that your M[UMPS] system supports the 1995 Standard

VA FileMan no longer supports the following operating systems:

CCSM MICROMUMPS (UC DAVIS)
DATA GENERAL TANDEM
DSM(V3 & V4) UNIX MUMPS(PLUS 5)
HARRIS VAX DSM(V3)
LMS-1(IBM SERIES 1) VAX DSM(V4 & V5)
M/11 VISTA(AOS)
M/SQL-PDP

VA FileMan will not run properly under these operating systems since they do not support the 1995 M Standard.

NOTE: If you are running under any of these operating systems, you SHOULD NOT proceed with the installation of VA FileMan V. 22.0. After updating to an M operating system that supports the 1995 M Standard environment, kill ^DD("OS") in order to proceed with the installation.

In VA FileMan V. 21.0 the VAX DSM(V6) entry was renamed to DSM for OpenVMS and the entry M/SQL-VAX was deleted.

In VA FileMan V. 22.0, the M/SQL operating system is no longer supported. The M/SQL entry in the MUMPS OPERATING SYSTEM file (#.7) is renamed CACHE/OpenM. Caché/OpenM sites should select this entry.

2. Delete Old VA FileMan Routines in the Production Account

It is recommended that you delete the old VA FileMan routines just before loading in the new ones to ensure that the only routines in FileMan's namespace are those coming in with V. 22.0. Use your M system routine deletion utility to delete the following routines:

DD*
DI*
DM*

3. Load Routines in the Production Account

Use your M system's routine loading utility to load the VA FileMan V. 22.0 routines from the distribution file (FM22.msm) into your Production account (of course, if you want, you can initially load the routines into a test account and install there).

4. Move Routines into the Manager Account

Caché and OpenM sites that map the %Z*, %DT*, and %RCR routines back to the Production account can skip this step.

Some of VA FileMan's routines must reside in the Manager (Library) account on your system. Using the utilities available with your M system, move the following routines to the Manager account:

DIDT
DIDTC
DIRCR
DIISC
DIIS
DIISS
DINZ* (includes: DINZDTM, DINZMGR, DINZMGR1, DINZMSM, DINZONT, DINZVXD)
DINV* (includes: DINV1DTM, DINV1VXD, DINVDTM, DINVMSM, DINVONT, DINVVXD)

5. Run DINZMGR in the Manager Account

A routine has been provided to set up your Manager account, DINZMGR. You MUST run this routine in your Manager account; be sure to move there. Online help is provided to aid in running this routine. DINZMGR accomplishes two tasks:

1. Renames routines in the Manager account to a new name.

2. Sets ^%ZOSF global nodes that are used by the screen-oriented features of VA FileMan.

DINZMGR references M implementation-specific information contained in other DINZ* and DINV* routines. The versions of M currently supported by DINZMGR are:

CACHE/OpenM
DSM for OpenVMS
DTM-PC
MSM

If you are using another version of M or if your version does not support the ZLOAD and ZSAVE commands, you cannot use DINZMGR. The next section describes how to accomplish DINZMGR's tasks manually.

Routines with the following names will be created in your Manager account by running DINZMGR:

%DT
%DTC
%RCR
%ZIS
%ZISS
%ZOSV
%ZOSV1

In addition, DINZMGR will set nodes in the ^%ZOSF global. Note that on some M systems, executing some of these ^%ZOSF nodes also causes ^XUTL global nodes to be set in the Production account.

DINZMGR gives you the chance to select which actions it will perform. So, if you already have routines with these %-names or data in the ^%ZOSF global that you do not want overwritten, you can tell DINZMGR not to change them. Note, however, that if you choose not to replace the %- routines or the data in ^%ZOSF, parts of VA FileMan may not work correctly unless the existing % routines and data in ^%ZOSF provide the functionality required by FileMan.

If your M system supports global protection, the ^%ZOSF global should be able to be read from any account (UCI) that uses the Manager account. Write and Delete access should be limited.

If you do not use DINZMGR or do not use it completely, you must either rename the following routines or have another version of the resulting %-routines in your Manager account. Otherwise, VA FileMan will not work. Rename, using the commands available with your M implementation.

DIDT rename to %DT
DIDTC rename to %DTC
DIRCR rename to %RCR
DIIS rename to %ZIS
DIISC rename to %ZISC

Also, in order to use VA FileMan's screen-oriented utilities, you should rename the following routine.

DIISS rename to %ZISS

You must also set executable M code into certain ^%ZOSF nodes in the Manager account. The specific nodes and what they should contain are described in the Device Handling section of the Package Management chapter of the Programmer Manual.

NOTE: The %ZOSV or %ZOSV1 routines are created by DINZMGR to support calls made by the ^%ZOSF nodes it creates. (Appropriate DINV* routines are renamed by DINZMGR.) If you are creating your own ^%ZOSF nodes, these routines are not needed.

6. Run DINIT in the Production Account

Finally, return to the Production account and run the DINIT routine. DINIT prompts you for a site name and number like this:

SITE NAME:

SITE NUMBER:

NOTE: The site number entered by the installer will be multiplied by 1000 to determine the beginning number of the default file number assignment, when using the Modify File Attributes option to add a new file.

After entering the site number, there will be a slight pause while VA FileMan installs the MUMPS OPERATING SYSTEM file (#.7), DIALOG file (#.84) and the LANGUAGE file (#.85). The installer will then be asked:

TYPE OF MUMPS SYSTEM YOU ARE USING:

Type a question mark ("?") at this point to see your choices. If you do not see your M operating system vendor listed, or you are unsure, enter OTHER in answer to this prompt.

Then the other VA FileMan files will be initialized.

The PACKAGE file (#9.4) will be initialized next. The PACKAGE file is necessary if you want to bundle an application package together for export using DIFROM. (In the Programmer Manual, see the DIFROM section of the Programmer Utilities chapter.) The PACKAGE file will not be updated if you have a File #9.4 with a name other than "PACKAGE."

When the initialization has completed, you will see the statement:

INITIALIZATION COMPLETED IN nnnn SECONDS.

Example:

>D ^DINIT
VA FileMan V.22.0
Initialize VA FileMan now? NO// Y
SITE NAME: KDEMO// <----------------- Enter your site name here
SITE NUMBER: 16// <----------------- Enter your site number here
Now loading MUMPS Operating System File..
Now loading DIALOG and LANGUAGE Files
...............................................................
TYPE OF MUMPS SYSTEM YOU ARE USING: DSM for OpenVMS// ?
Answer with MUMPS OPERATING SYSTEM NAME
Choose from:
CACHE/OpenM
   DSM for OpenVMS
   DTM-PC
   GT.M(VAX)
   MSM
   OTHER
TYPE OF MUMPS SYSTEM YOU ARE USING: DSM for OpenVMS//<------Enter Your
M operating system here
Now loading other FileMan files--please wait...................
The following files have been installed:
   .11     INDEX
   .2      DESTINATION
   .31     KEY
   .4      PRINT TEMPLATE
   .401    SORT TEMPLATE
   .402    INPUT TEMPLATE
   .403    FORM
   .404    BLOCK
   .44     FOREIGN FORMAT
   .5      FUNCTION
   .6      DD AUDIT
   .7      MUMPS OPERATING SYSTEM
   .81     DATA TYPE
   .83     COMPILED ROUTINE
   .84     DIALOG
   .85     LANGUAGE
1        FILE
1.1      AUDIT
1.11     ARCHIVAL ACTIVITY
1.12     FILEGRAM HISTORY
1.13     FILEGRAM ERROR LOG
1.2      ALTERNATE EDITOR
1.521    SQLI_SCHEMA
1.52101 SQLI_KEY_WORD
1.5211   SQLI_DATA_TYPE
1.5212   SQLI_DOMAIN
1.5213   SQLI_KEY_FORMAT
1.5214   SQLI_OUTPUT_FORMAT
1.5215   SQLI_TABLE
1.5216   SQLI_TABLE_ELEMENT
1.5217   SQLI_COLUMN
1.5218   SQLI_PRIMARY_KEY
1.5219   SQLI_FOREIGN_KEY
1.52191 SQLI_ERROR_TEXT
1.52192 SQLI_ERROR_LOG
Your Package file will now be updated.
I AM GOING TO SET UP THE FOLLOWING FILES:
   9.4 PACKAGE
...HMMM, I'M WORKING AS FAST AS I CAN................................
...........
OK, I'M DONE.
NOTE THAT FILE SECURITY-CODE PROTECTION HAS BEEN MADE
Re-indexing in the DIALOG file....
Compiling all forms ...
   .
   .
   .
DICATT                          (#.001)
DIPTED                          (#.1001)
DIKC EDIT                       (#.1101)
DIKC EDIT UI                    (#.1102)
DIKK EDIT                       (#.3101)
DIBTED                          (#.40001)
DIETED                          (#.40101)
DIEDIT                          (#.40201)
DDGF BLOCK EDIT                 (#.40301)
DDGF PAGE ADD                   (#.40302)
DDGF PAGE EDIT                  (#.40303)
DDGF PAGE SELECT                (#.40304)
DDGF FORM EDIT                  (#.40305)
DDGF HEADER BLOCK EDIT          (#.40306)
DDGF FIELD ADD                  (#.40401)
DDGF FIELD CAPTION ONLY         (#.40402)
DDGF FIELD DD                   (#.40403)
DDGF FIELD FORM ONLY            (#.40404)
DDGF FIELD COMPUTED             (#.40405)
DDGF BLOCK ADD                  (#.40406)
DDGF BLOCK DELETE               (#.40407)
DDGF HEADER BLOCK SELECT        (#.40408)
DDXP FF FORM1                   (#.441)
DDMP SPECIFY IMPORT             (#.461)
   .
   .
   .
INITIALIZATION COMPLETED IN 100 SECONDS.
>

VA FileMan is now ready to use.

The menu choices for programmer-mode FileMan are invoked by typing

DO P^DI