Re: SPAM-LOW: Re: [Hardhats-members] Volume Sets

2005-03-23 Thread Greg Kreis




I can understand that the Volume concept is handled by the idea of a
path in Linux, right? Hmm... Are the globals just Linux files? If so,
wouldn't the directory take the place of the UCI? But I guess the next
question is how is this exposed inside GT.M?

K.S. Bhaskar wrote:

  GT.M does not have the concept of UCI and Volume, so I think for the
GT.M port they're always VAH  ROU.  (Or am I getting things mixed up?) 
Also, when VistA is ported to GT.M, I believe the routines look for the
hostname from the Linux command "hostname -s".

Perhaps Chris Richardson, Rick Marshall, Wally Fort or Dave Whitten
could comment?

-- Bhaskar

On Sun, 2004-11-21 at 23:21, Nancy E. Anthracite wrote:
  
  
I have OV3 and Fedora Core 2.  

I bet you are using the version on the VA ftp site.  That is available 
preinstalled on Knoppix on Sourceforge thanks to Bhaskar in the VivAFOIAGold 
on the WorldVistA project site.  It can be installed right on your machine if 
you want or run off of the DVD.

 Anyway, I would suggest you don't spend a lot of time looking at man hostname 
and the like unless you REALLy want to spend a lot of time because you end up 
going in a circle from hostname to something else to something else that ends 
up referring back to hostname again.  I got dizzy when I tried it.  

The best I was able to do with Fedora was to figure it out with experiments 
and to find out the machine name probably has to be changed in multiple 
places to really change the machine name for Fedora  
including /etc/hosts,  /etc/config/network and 
sysctl -w kernel.hostname="newhostname" .  

After that, I decided that was really much more than I needed to know or cared 
to know about machine names and Fedora, as long as I could figure out where 
to get at hostname -s changed.

As for the ^ZOSF("PROD") and where that is set, it looks like im my ^ZTMGRSET, 
it  just gets the UCI and Volume it from ^ZOSF("PROD"), so that didn't help 
figure out how that is set.  



On Sunday 21 November 2004 08:54 pm, Daniel Gray wrote:


  Thanks Fil, I take that as a great compliment.  And you knew I would.

All other readers:  Fil has exaggerated my reputation as a hacker, but
maybe it was because of something I said . . .

Nancy:  I'm not too sure what information will help, but here is a
paragraph from Krn8_Osm.pdf

==
BOX-VOLUME PAIR
This field identifies a volume set and the CPU on which it is available. It
contains the name of a volume set concatenated to the CPU ("box") name:
first the volume set name and then the CPU name. For example, if the
volume set name is "KRN" and the name of the CPU (e.g., box) is "ISC6A1",
then the box-volume pair would be "KRN:ISC6A1".

For systems on which each CPU tends to have a unique volume set, and vice
versa, you may enter just the volume set name (e.g., "PSA" or "AAA"). This
field's value for the current process can be found by doing GETENV^%ZOSV
and checking the fourth ^-piece of Y. Since the volume set and CPU are
identified, the TaskMan site parameters can be tuned for each specific
volume set and CPU affected. Systems running Managers on more than one
CPU need one entry for each CPU where a manager is running.
=

So for Kernel to work, VOL:BOX has to be set up right.  But why do they
call it Box-Volume, why not call it Volume-Box?  The name of it caused me
some confusion when I was setting up taskman.  And yes, the ^%ZOSF("PROD")
and ^%ZOSF("MGR") and ^%ZOSF("VOL") have to be all set right, and that is
done when you do ^ZTMGRSET.  Maybe ^ZTMGRSET should get "BOX" name, and at
least begin setup of KERNEL SITE PARAMETERS.  Maybe it does.

The version of Kernel I am running, has the code I showed below, that is,
the call to GETENV^%ZOSV calling RETURN^%ZOSV which evoked the GTM function
ZSYSTEM("hostname -s")
>From the GTM documentation, it looks like the ZSYSTEM call is a way to
generate a "plainjane" Linux command.  And I would suppose that one could
say, to Linux
#hostname -s
and you would get a parameter out of the etc/hosts file, hopefully the
"box" name, or the short name of your computer.

I think that Linux uses different names for different things, Redhat9, I
think, provides for a longname and a shortname, and whoever wrote the
^%ZOSF that I have, knew to look for the short name (thus "-s").  One could
do $man hostname and see what it says there, I will do that when I get a
chance.  But there should be some documentation somewhere that tells the
nave user to name his computer with a short and sweet alias, and to check
KERNEL SITE PARAMS to make sure taskman will run.

It looks like the Linux configuration provides for three fields in the
hosts file.  The first is IP address, the second is the name of your
computer (a shortname), and the longname might be the URL of your system. 
If this is really the case, then Kernel could use that shortname as a "box"
name, to identify your "box" on a network.

Maybe there is a difference between Redhat9 and 

Re: SPAM-LOW: Re: [Hardhats-members] Volume Sets

2005-03-23 Thread Bhaskar, KS
Greg --

Not quite.  In GT.M globals and routines are configured completely
independently of each other.  If you have the chance, just download the
GT.M Acculturation CD (from http://sourceforge.net/projects/sanchez-gtm)
and go through it - it explains things much better than I could in a
short post to the mailing list.

-- Bhaskar

On Wed, 2005-03-23 at 11:28 -0500, Greg Kreis wrote:
 I can understand that the Volume concept is handled by the idea of a
 path in Linux, right?  Hmm... Are the globals just Linux files? If so,
 wouldn't the directory take the place of the UCI?  But I guess the
 next question is how is this exposed inside GT.M?
 
 K.S. Bhaskar wrote: 
  GT.M does not have the concept of UCI and Volume, so I think for the
  GT.M port they're always VAH  ROU.  (Or am I getting things mixed up?) 
  Also, when VistA is ported to GT.M, I believe the routines look for the
  hostname from the Linux command hostname -s.
  
  Perhaps Chris Richardson, Rick Marshall, Wally Fort or Dave Whitten
  could comment?
  
  -- Bhaskar
  
  On Sun, 2004-11-21 at 23:21, Nancy E. Anthracite wrote:

   I have OV3 and Fedora Core 2.  
   
   I bet you are using the version on the VA ftp site.  That is available 
   preinstalled on Knoppix on Sourceforge thanks to Bhaskar in the 
   VivAFOIAGold 
   on the WorldVistA project site.  It can be installed right on your 
   machine if 
   you want or run off of the DVD.
   
Anyway, I would suggest you don't spend a lot of time looking at man 
   hostname 
   and the like unless you REALLy want to spend a lot of time because you 
   end up 
   going in a circle from hostname to something else to something else that 
   ends 
   up referring back to hostname again.  I got dizzy when I tried it.  
   
   The best I was able to do with Fedora was to figure it out with 
   experiments 
   and to find out the machine name probably has to be changed in multiple 
   places to really change the machine name for Fedora  
   including /etc/hosts,  /etc/config/network and 
   sysctl -w kernel.hostname=newhostname .  
   
   After that, I decided that was really much more than I needed to know or 
   cared 
   to know about machine names and Fedora, as long as I could figure out 
   where 
   to get at hostname -s changed.
   
   As for the ^ZOSF(PROD) and where that is set, it looks like im my 
   ^ZTMGRSET, 
   it  just gets the UCI and Volume it from ^ZOSF(PROD), so that didn't 
   help 
   figure out how that is set.  
   
   
   
   On Sunday 21 November 2004 08:54 pm, Daniel Gray wrote:
   
Thanks Fil, I take that as a great compliment.  And you knew I would.

All other readers:  Fil has exaggerated my reputation as a hacker, but
maybe it was because of something I said . . .

Nancy:  I'm not too sure what information will help, but here is a
paragraph from Krn8_Osm.pdf

==
BOX-VOLUME PAIR
This field identifies a volume set and the CPU on which it is 
available. It
contains the name of a volume set concatenated to the CPU (box) name:
first the volume set name and then the CPU name. For example, if the
volume set name is KRN and the name of the CPU (e.g., box) is 
ISC6A1,
then the box-volume pair would be KRN:ISC6A1.

For systems on which each CPU tends to have a unique volume set, and 
vice
versa, you may enter just the volume set name (e.g., PSA or AAA). 
This
field's value for the current process can be found by doing GETENV^%ZOSV
and checking the fourth ^-piece of Y. Since the volume set and CPU are
identified, the TaskMan site parameters can be tuned for each specific
volume set and CPU affected. Systems running Managers on more than one
CPU need one entry for each CPU where a manager is running.
=

So for Kernel to work, VOL:BOX has to be set up right.  But why do they
call it Box-Volume, why not call it Volume-Box?  The name of it caused 
me
some confusion when I was setting up taskman.  And yes, the 
^%ZOSF(PROD)
and ^%ZOSF(MGR) and ^%ZOSF(VOL) have to be all set right, and that 
is
done when you do ^ZTMGRSET.  Maybe ^ZTMGRSET should get BOX name, and 
at
least begin setup of KERNEL SITE PARAMETERS.  Maybe it does.

The version of Kernel I am running, has the code I showed below, that 
is,
the call to GETENV^%ZOSV calling RETURN^%ZOSV which evoked the GTM 
function
ZSYSTEM(hostname -s)
From the GTM documentation, it looks like the ZSYSTEM call is a way to
generate a plainjane Linux command.  And I would suppose that one 
could
say, to Linux
#hostname -s
and you would get a parameter out of the etc/hosts file, hopefully the
box name, or the short name of your computer.

I think that Linux uses different names for different things, Redhat9, I
think, provides for a longname and a shortname, and whoever wrote the
^%ZOSF