On GTM the HOME device is as follows: NAME: CONSOLE $I: /dev/tty ASK DEVICE: YES ASK PARAMETERS: YES LOCATION OF TERMINAL: CONSOLE SUBTYPE: C-VT100 TYPE: VIRTUAL TERMINAL
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoffry Roberts Sent: Friday, April 14, 2006 7:27 AM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Home Device Not Found Nancy, I did as you asked and the interaction sequence is shown below. Apparently, I need to have a home device entry in the device file. If someone could coach me on this I would appreciate it. VISTA 7d2>D Q^DI VA FileMan 22.0 Select OPTION: 5 INQUIRE TO FILE ENTRIES OUTPUT FROM WHAT FILE: DOMAIN// DEVICE (46 entries) Select DEVICE NAME: CONSOLE 1 CONSOLE CONSOLE |TNT| 2 CONSOLE GTM-UNIX-CONSOLE Console (GT.M) /dev/tty CHOOSE 1-2: 1 CONSOLE CONSOLE |TNT| ANOTHER ONE: TELNET 1 TELNET TELNET TNA VISTA 2 TELNET GTM-UNIX-TELNET TELNET /dev/pts/ CHOOSE 1-2: 1 TELNET TELNET TNA VISTA ANOTHER ONE: NULL 1 NULL NT SYSTEM NLA0: 2 NULL GTM-UNIX-NULL Bit Bucket (GT.M-Unix) /dev/null 3 NULL-DSM Bit Bucket _NLA0: CHOOSE 1-3: 1 NULL NT SYSTEM NLA0: ANOTHER ONE: STANDARD CAPTIONED OUTPUT? Yes// YES (Yes) Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and Record Number (IEN) HOME DEVICE DOES NOT EXIST IN THE DEVICE FILE PLEASE CONTACT YOUR SYSTEM MANAGER! NUMBER: 5 NAME: CONSOLE $I: |TNT| ASK DEVICE: YES ASK PARAMETERS: YES LOCATION OF TERMINAL: CONSOLE SUBTYPE: C-VT100 TYPE: VIRTUAL TERMINAL NUMBER: 22 NAME: TELNET $I: TNA ASK DEVICE: YES ASK PARAMETERS: YES VOLUME SET(CPU): VISTA LOCATION OF TERMINAL: TELNET SUBTYPE: C-VT320 TYPE: VIRTUAL TERMINAL LAST SIGN-ON USER (c): SPIVEY,RICK NUMBER: 8 NAME: NULL $I: NLA0: ASK DEVICE: YES ASK PARAMETERS: NO SIGN-ON/SYSTEM DEVICE: YES LOCATION OF TERMINAL: NT SYSTEM SUBTYPE: C-VT100 TYPE: TERMINAL Select DEVICE NAME: On 4/13/06, Greg Woodhouse <[EMAIL PROTECTED]> wrote: > I hope everyone understands that the two (three?) types of devices > mentioned here are not the same thing! One meaning of "device" is an > entry in the DEVICE file. yet another meaning of device is the logical > name associated with that device by the underlying MUMPS system (in > this case, it's the value of the intrinsic variable $PRINCIPAL, or just > $P). This is not all unlike the name of the file associated with that > device under Unix (say, /dev/console or /dev/pty1). In each case, the > device is JUST A NAME, a way of referring to some physical device (like > a terminal and keyboard or modem or serial port) or a virtual (also > called logical!) device like a network connection, FIFO, or a > pseudo-TTY). > > What's happening here is that VistA is a layered system, including at > least > > 1. Actual hardware (cables, keyboards, CPUs, etc.) > 2. An operating system (OS X, Windows, Linux) > 3. A MUMPS implementation > 4. Fileman and the VistA Kernel > 5. VistA applications > > Sometimes similar concepts appear at different layers. For example, a > physical keyboard may be attached to a real computer, that is connected > over the network to VistA system (via SSH or telnet). That system, in > turn is running an operating system, hich has to have its own way of > referring to devices. The reason is that operating systems support > multiple processes and multiple users, and need to provide those > processes with the illusion that they are interacting with actual > devices when, in fact, many different processes may be making use of > the same physical device (say an Ethernet cable, Network Interface Card > or NIC, a CPU, memory, etc.) (Interesting aside: Did you ever wonder > why so-called physical network addresses like Ethernet addresses are > called MAC addressess? Well, MAC is an acronym for Medium Access > Control, and the lower half of the link layer of the network manages > acces to the physical medium, resulting in the name MAC address for the > addresses used at this level.) > > What next? Well MUMPS is an application that runs under control of the > operating system, but it has its own names for the virtual devices > supported at the OS level. There are a couple of reasons for this, one > is that different MUMPS jobs need not correspond to operating system > level processes or threads (though in GTM and Cache they do), another > is that MUMPS may need to add its own semantics, possibly reulting in > different names for the same OS level device (needed because the MUMPS > subsystem interacts with them in different ways). > > Next, of course, there is VistA. In VistA a device is an entry in the > DEVICE file, and it serves, among other things, to allow VistA > applications to refer to devices in the same way, regardless of the > underlying MUMPS system, and also to insulate your applications from > having to know how the underlying system is configured (allowing you to > change it). It even allows VistA to create its own logical devices like > P-MESSAGE (allowing you to "print" to a mail message) or the Browser > (allowing you to scroll through the output directed to that device). > > Of course, to make this all work, devices at the different layers need > to be chained together somehow. Well, when you log in the VistA Kernel > looks at $I and tries to find an entry in the DEVICE file such that the > value of the *field* called $I is a prefix of the value of the > intrisinc variable $I (modulo punctuation). When (if) it finds one, it > selects this as your home device. (Note, BTW, that different users > might have the same home device according to VistA, but the principal > devicers at the MUMPS level will be different!) If no such DEVICE (I'm > using capitals here because I'm referring to the DEVICE file) exists, > then you see the error message "Home Device Not Found", and the fix is > to add an entry to the DEVICE file or modify an existing one, so that > your device (MUMPS level this time) will be recognized, and Kernel > knows which DEVICE (VistA level this time) to assign to you. > > It's really not so bad as it sounds at first. > > === > Gregory Woodhouse <[EMAIL PROTECTED]> > > "It is foolish to answer a question that > you do not understand." > --G. Polya ("How to Solve It") > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Hardhats-members mailing list > Hardhats-members@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hardhats-members > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
