[KSB] <...snip...>
> 1. Forgetting to run the the database down after a system restart, for
> anyone needing to know how...
>
> $gtm_dist/mupip rundown -FILE /opt/gtmdat/cobalt/mumps.dat
[KSB] My strong recommendation is to run before image journaling on the
database, and as part of bootup to perform a mupip journal -recover
-backward. If the database was cleanly shut down, this is effectively a
no-op; if it was not cleanly shut down, it recovers the database.
Remember to delete old journal files to save space on the virtual disk.
See /etc/init.d/wvehr on the virtual machine on the VistA Tour CD
(http://downloads.sourceforge.net/fis-gtm/VistATour20081118.iso) for an
example of how this is done.
Rundown after a dirty shut down can mask database damage caused by
shutting down the system while the database is still active, and should
be followed by a mupip integ. Not recommended for a virtual machine demo.
<...snip...>
> Bhaskar: Thanks for the response, this type of tuning sounds very
> logical, something that I should try simulating. I do wonder what the
> difference would be to store a large stream in many 4k blocks as
> opposed to one 32k block (apart from having to code around it).
[KSB] In a virtual machine, you may not see much difference. The
overhead of going through two file systems will probably overwhelm any
other difference.
Regards
-- Bhaskar
Regards
-- Bhaskar
LOL!
So... everyone, when you see the "modernization"
of the GT.M defaults, you'll know that GT.M owners
are in the disk drive business!!!
Cheers,
--ldl
On Fri, Feb 20, 2009 at 8:28 AM, K.S. Bhaskar <ks.bh...@fnis.com> wrote:
> ...
> Rob, as for comparisons between GT.M and other MUMPS implementations, in
> the open source business, even more so than in the proprietary software
> business, we do the development that attracts funding by being worth
> something to someone who is using it to generate revenue in turn.
>
> Regards
> -- Bhaskar
>
> On 02/20/2009 06:27 AM, rtweed wrote:
>>...
>> Indeed I'm surprised how limited the standard default global record
>> size is in GT.M - in this day and age it's way too limiting in my
>> view. Even 32k can be a problem, and of course it's interesting to
>> see Cache's new increased configurable maximum string length in that
>> respect.
>>
>
--
---
NOTE: If it is important CALL ME - I may miss email
---
LD Landis - N0YRQ - de la tierra del encanto
3960 Schooner Loop, Las Cruces, NM 88012
651/340-4007 N32 21'48.28" W106 46'5.80"
"If a thing is worth doing,
it is worth doing badly." –GK Chesterton.
An interpretation: For things worth doing: Doing them, even if badly,
is better than doing nothing perfectly (on them).
"but I trust my family jewels only to Linux." -- DE Knuth
(http://www.informit.com/articles/article.aspx?p=1193856)
One should always run MUMPS (GT.M, M21, Cache, etc),
with the default for globals being "journalling enabled".
For globals that are journalled in GT.M, you should enable
"before image" journals, which, write the block that is being
changed to the journal "before" it is changed. This allows
efficient recovery.
Now, every SET and KILL causes the block in which the
global node is located (and any block splits/merges, etc)
to be written to the journal before the SET or KILL is done.
If you are running a production system, it is not unusual
to see transaction rates of several million per 5 minute
interval... So, at that rate, is it clear that writing some
number of many several millions of transactions per hour,
that having 4k blocks vs 32k blocks makes a difference.
Also, GT.M enables/disables journalling at the data
base file level. Therefore reasons for having separate
database files (and hence, journals) are for such things
as:
- journalling requirements
- block sizes
- insertion/deletion styles
- other factors (size of a global).
Also, with GT.M, a global must exist entirely within
a single database data file... so for a large global,
you may want a separate data file just for that global.
Currently, GT.M does not support the concept frequently
called "subscript level mapping", which allows a global
to be spread across several database files.
There are many things to consider at the lower (DBA)
level of all MUMPS implementations.
Cheers,
--ldl
On Fri, Feb 20, 2009 at 9:28 AM, Sean Connelly
<seanatc...@googlemail.com> wrote:
> ...
> Bhaskar: Thanks for the response, this type of tuning sounds very
> logical, something that I should try simulating. I do wonder what the
> difference would be to store a large stream in many 4k blocks as
> opposed to one 32k block (apart from having to code around it).
>
> Next up, installing EWD and building an EWD page...
>
> Sean.
>
--
[KSB] <...snip...>
> find the routine.. Bhaskar, I forget, what is the way
> to see which path element in gtmroutines produced
> the hit for where the routine found is stored?
[KSB] I believe you want SILENT^%RSEL() - see
http://www.fidelityinfoservices.com/user_documentation/html/rn_tb/GTM_V5.1-000A_Release_Notes.html#ch.hi.id.03
for more information.
Regards
-- Bhaskar
_____________
The information contained in this message is proprietary and/or confidential. If you are not the
intended recipient, please: (i) delete the message and all copies; (ii) do not disclose,
distribute or use the message in any manner; and (iii) notify the sender immediately. In addition,
please be aware that any message addressed to our domain is subject to archiving and review by
persons other than the intended recipient. Thank you.
_____________
You shouldn't have to. But a process that uses EWD will need a
different global directory (pointed to by $gtmgbldir) and routine search
path (pointed to by $gtmroutines). Unless you are running replication,
traditional VistA processes can continue to run side by side with
processes that access both EWD and VistA.
-- Bhaskar
On 04/09/2009 01:29 PM, I, Valdes wrote:
>
> What if you already have an existing database? Do you have to start
> over? -- IV
>
> On 19 Feb, 14:24, rtweed <rob.tw...@gmail.com> wrote:
> > Just digging the info out of the Virtual Appliance so it's here in one
> > place. Here's how to create a global database suitable for EWD's DOM
> > processing, ie capable of handling records up to 32k long:
> >
> > cd /usr/local/gtm/ewd
> > $gtm
> > GTM>d ^GDE
> > change -segment default -block=32256
> > change -region default -key=255 -record=32240
> > exit
> > mupip create
> >
> > Note that, as Sean described earlier, if you use these settings, you
> > must increase the kernel shared memory to 134217728
> >
> > On 19 Feb, 19:08, st...@stevenowen.com wrote:
> >
> > > Tks Sean! This will be a great howto...
> >
> > > seanatconne...@googlemail.com writes:
> >
> > > > (part 2)
> >
> > > > I downloaded the latest version of GT.m (for Linux)...
> >
> > > >
> http://sourceforge.net/project/showfiles.php?group_id=11026&package_i
On 04/09/2009 02:26 PM, Ignacio Valdes wrote:
> So I assume that you would have two gld's? If so, then what would be the
> syntax for the env variable for two gld's? For example, my current one is:
>
> export gtmgbldir="$vista_path/g/mumps.gld"
>
> -- IV
_____________
You have two different threads going on two different groups on the same
topic.
Also, I am afraid you are shooting from the hip and hoping that your
random shots will find a target. If you want to configure GT.M
databases, you really need to understand how GT.M databases are
configured. I have spent time creating a GT.M Acculturation live CD
with a bunch of exercises that include database configuration. Please
refer to that.
I reproduce below something I posted to hardhats a couple of years ago.
Sometimes half knowledge is less than ideal.
Regards
-- Bhaskar
------------------------------------------------------------
In high school biology, I was expert at dissection. In the late 1960s,
I was impressed by the pioneering heart transplant work of Drs.
Christiaan Barnard, Denton Cooley and Michael Debakey. Since the
mechanics of transplanting hearts seemed simple, since I was so handy
with the scalpel, and since frog hearts keep beating for an impressively
long time on their own in Ringers solution, one evening I attempted side
by side frog heart transplants, exchanging the hearts of two frogs I
caught in my back yard. Neither of my victims awoke from surgery, and
the most important thing I learned was how much there was that I didn't
know. It wasn't that I couldn't learn enough to be a heart surgeon -
the fact was that I didn't know enough to be a heart surgeon.
------------------------------------------------------------
On 04/09/2009 05:17 PM, I, Valdes wrote:
>
> I did the following, restarted httpd, but I'm still getting 404 Not
> Found on http://192.168.1.101/ewd/ewdMgr/index.mgwsi
> netstat on 7041 shows it is listening:
>
> GTM>D ^GDE
> %GDE-I-LOADGD, Loading Global Directory file
> /opt/worldvista/EHR/g/mumps.gld
> %GDE-I-VERIFY, Verification OK
>
>
> GDE> change -segment default -block=32256
> GDE> change -region default -key=255 -record=32240
> GDE> exit
> %GDE-I-VERIFY, Verification OK
>
> %GDE-I-GDUPDATE, Updating Global Directory file
> /opt/worldvista/EHR/g/mumps.gld
> [vista@dune ~]$ mupip create
> Error opening file /opt/worldvista/EHR/g/mumps.dat
> : File exists
> %GTM-F-DBNOCRE, Not all specified database files, or their associated
> journal files were created
[KSB] <...snip...>
> I did the following, restarted httpd, but I'm still getting 404 Not
> Found on http://192.168.1.101/ewd/ewdMgr/index.mgwsi
> netstat on 7041 shows it is listening:
>
> GTM>D ^GDE
> %GDE-I-LOADGD, Loading Global Directory file
> /opt/worldvista/EHR/g/mumps.gld
> %GDE-I-VERIFY, Verification OK
>
>
> GDE> change -segment default -block=32256
> GDE> change -region default -key=255 -record=32240
> GDE> exit
> %GDE-I-VERIFY, Verification OK
>
> %GDE-I-GDUPDATE, Updating Global Directory file
> /opt/worldvista/EHR/g/mumps.gld
> [vista@dune ~]$ mupip create
> Error opening file /opt/worldvista/EHR/g/mumps.dat
> : File exists
> %GTM-F-DBNOCRE, Not all specified database files, or their associated
> journal files were created
[KSB] <...snip...>
I'm happy to provide consultancy to get you up and running but.....not for free :-)
Rob
Ignacio --
I can see from your posts that you are struggling with concepts. It is
not an efficient use of my time - or yours for that matter - to try to
teach you concepts in a series of posts when I have already created and
posted tutorials on the concepts.
Getting EWD packaged with VistA is no big deal, but I have not yet done
it. So if you want to be the first, I see no way but for you to master
the concepts.
So, Read The Fine Manuals is the best advice I can offer at this time.
If something is not clear in them, please do ask.
-- Bhaskar
On 04/09/2009 06:01 PM, Ignacio Valdes wrote:
On the Acculturation live CD, please remember the errata I wrote about
earlier: when you get to the dd command (it will be obvious when you get
there) use count=800000 rather than count=716800 as noted in the
documentation.
Cheers
-- Bhaskar
P.S. I never was very good at poker. I was able to master tic-tac-toe
(which we called noughts and crosses), but that was about as good as I got.
There is a thread (started by Larry Landis) in yet another discussion
group: http://tinyurl.com/cvmnv2 - it is important to note that what
Larry discusses and what Ignacio is attempting here are apples and
oranges, web enabling two different parts of VistA with EWD with two
different techniques.
On the Acculturation live CD, please remember the errata I wrote about
earlier: when you get to the dd command (it will be obvious when you get
there) use count=800000 rather than count=716800 as noted in the
documentation.
Cheers
-- Bhaskar
P.S. I never was very good at poker. I was able to master tic-tac-toe
(which we called noughts and crosses), but that was about as good as I got.
On 04/09/2009 07:06 PM, Ignacio Valdes wrote:
> I pay exactly as much as I am being paid for this which is: 1) Benefit
> society. 2) A better health care system for my 3 young boys. -- IV
>
> On Thu, Apr 9, 2009 at 5:20 PM, Rob Tweed <rob.tw...@gmail.com> wrote:
> > I'm happy to provide consultancy to get you up and running but.....not for
> > free :-)
>
> > Rob
>
> > 2009/4/9 K.S. Bhaskar <ks.bhas...@fnis.com>
> >> > > Found onhttp://192.168.1.101/ewd/ewdMgr/index.mgwsi
This is because m_apache22.so is built for Apache v2.2.x whereas the web server you have is Apache v2.4.x.
You will need to rebuild the Apache module from source using the Apache Group’s procedures for v2.4.x.
Chris.
--
You received this message because you are subscribed to the Google Groups "Enterprise Web Developer Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enterprise-web-develope...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/enterprise-web-developer-community/16bb669b-51c6-4944-b2cf-815d324fa1d2n%40googlegroups.com.