Menu
▾
▴
RE: [Sanchez-gtm-core] Successful GT.M Vista Installation
|
From: Roger P. <rog...@sa...> - 2002-04-16 16:11:44
|
Todd:
Looks good!
DSE is a good thing to avoid except when you really need it. Since it can
be used in times of desperation, by design it lets you do things that
typically should not be done. In your case, you have effectively disabled
the protection against attempting to put records that won't fit into your
database. As long as you don't actually attempt it, all will be well, but
if you happen to try a record longer than 1016 (the way it appears you
configured things), really bad things will happen.
GDE maintains the [maximum] key and record sizes that are used by MUPIP
CREATE, so if you add to your GDE commands:
change -seg DEFAULT -block=4096
change -reg DEFAULT -key=255 -record=4088
You will get a database with a block size of 4096 and a maximum record size
of 4088, which just fits, so things will work fine. GDE, being much more
user friendly than DSE, won't let you screw this up.
It would be well to set appropriate allocation and extension sizes, because
the default sizes are tiny (for demos, experiments and limited development
environments), so add -alloc=???? - extension=???? to the change -seg, where
???? stands for your anticipated number of 4096 byte blocks. There are
efficiency penalties for failing to do this, especially on VMS.
Performance can also be significantly affected by the number of global
buffers used for database caching. This optimal number varies with your
circumstance, but the default is again tiny, so add -global=1024 (or 2048 or
4096) to the change -seg.
So, for a 20MB database, you'd end up with (say) the following GDE commands
(minimum distinguishable prefixes work for commands and qualifiers, but I
compromised to make them more meaningful):
change -seg DEFAULT -block=4096 -glo=1024 -alloc=6000 -extension=1000
-file=/gtm_vista/g/mumps.dat
change -reg DEFAULT -key=255 -record=4088
And - skip the DSE command!
Roger
-----Original Message-----
From: Smith, Todd [mailto:Tod...@ca...]
Sent: Tuesday, April 16, 2002 11:31 AM
To: har...@to...; 'san...@li...'
Cc: 'har...@li...';
ope...@mi...; 'Mike Baker'
Subject: [Sanchez-gtm-core] Successful GT.M Vista Installation
Hello,
I am cross-posting these instructions to several lists that might not have
seen them. If you have, please hit DELETE or forward to someone that needs
them. NOTE These instructions were originally posted by that paragon of
virtue, Mike Baker on the Hardhats list and he holds ALL RIGHTS RESERVED and
no responsibility for destroying your system through this instructions.
I was successful in installing GT.M and the GT.M port of Vista on my P166MMX
Laptop, 64MB RAM and 3GB HD. Thanks Mike for the hard work!
Mike Baker's Setup Instructions
To setup GT.M on my RedHat Linux 7.2 system here is what I did:
1. Log in to Linux box as a normal user.
2. Make a directory for the downloaded files:
A. mkdir gtm
3. Download GT.M from www.sourceforge.net into the gtm directory you just
made.
A. I selected the gtm_V43FT06_linux_pro.tar.gz file.
4. Change directory to ~/gtm
A. cd ~/gtm
5. Gunzip the file to extract the tar file.
A. gunzip gtm_V43FT06_linux_pro.tar.gz
6. Extract the files from the archive:
A. tar xovf gtm_V43FT06_linux_pro.tar
7. Become the super user.
A. su
8. Create a link to the ncurses library that is installed with RH Linux from
the ncurses libary that is used by the GT.M configure script.
A. ln -s /usr/lib/libncurses.so.5 usr/lib/libncurses.so.4
9. Run the configure script from the gtm directory
A. sh configure
B. I just accepted the defaults where available.
C. I selected /usr/local/gtm as the directory for install.
10. Make a directory for the logs:
A. cd /usr/local/gtm
B. mkdir logs
C. chmod 777 logs
1. This is probably too many privs for this.
11. Exit superuser
12. Edit .bash_profile to setup the environment varibles when you log in:
A. cd ~
B. pico .bash_profile
1. I added the following to my .bash_profile
gtm_dist=/usr/local/gtm
export gtm_dist
gtmroutines=". $gtm_dist /gtm_vista/r"
export gtmroutines
gtmgbldir=/gtm_vista/g
export gtmgbldir
PATH=$PATH:$gtm_dist
export PATH
2. Yours could look different: I have added a directory
called gtm_vista
that contains subdirectories for routines,(r), and
globals,(g).
13. You should now be able to log out and log in and run:
A. mumps -direct to get a mumps > prompt.
14. This is how I got the VistA stuff running on this system:
15. Download the global and routine files at:
http://hardhats.sourceforge.net/pub/steel/1.08
16. Create a directory for the Vista stuff.
A. su
B. cd /
C. mkdir gtm_vista
D. chmod 777 gtm_vista
1. Again these privs are much too lenient I'm sure.
E. exit ; su
E. cd /gtm_vista
F. mkdir g
G. cd g
H. mv ~/globals-1.08.zip globals-1.08.zip
I. unzip globals-1.08.zip
J. cd ..
K. mv ~/routines-1.08.zip routines-1.08.zip
L. unzip routines-1.08.zip
17. Now run:
A. mumps -r GDE
B. At the GDE prompt type:
1. change -s DEFAULT -f=/gtm_vista/g/mumps.dat
2. exit
C. Now type:
1. mupip create && dse change -f -key_max=255 -rec=4096
b 2. mupip load /gtm_vista/g/globals.zwr
D. I got these instructions from the Readme file when I downloaded
the
routines and globals. I modified slightly to make it work for me
but
it seems that this also works ok.
18. GETTING EXCITED YET?
19. Now I went into the mumps system:
A. mumps -direct
B. S DUZ=1
C. D ^XUP
1. EVE
2. USER
3. ADD
4. Set yourself up as a user.
5. Give yourself the EVE Menu.
6. Give yourself an access and verify code.
7. Make sure you give yourself a SERVICE/SECTION
8. exit
9. Answer yes to allocating keys
a. Give yourself:
b. XUMGR
c. XUPROG
d. XUPROGMODE
20. Now go to programmer mode through the options:
A. K DUZ
B. D ^XUP
C. Sign in using your access code
D. Hit return until you are back at a programmer prompt.
E. W DUZ - This is your DUZ
F. S $P(^VA(200,DUZ,0),"^",4)="@"
_______________________________________________
Sanchez-gtm-core mailing list
San...@li...
https://lists.sourceforge.net/lists/listinfo/sanchez-gtm-core
***************************************************************************
This electronic mail transmission contains confidential and/or privileged
information intended only for the person(s) named. Any use, distribution,
copying or disclosure by another person is strictly prohibited.
***************************************************************************
|