Difference between revisions of "Configuration How To HOME DEVICE DOES NOT EXIST"
DavidWhitten (talk | contribs) (→Technical Details) |
|||
| (7 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | A common problem that people have who are trying to configure | + | __TOC__ |
| + | == Description == | ||
| + | A common problem that people have who are trying to configure VistA is a message: | ||
| − | HOME DEVICE DOES NOT EXIST IN THE DEVICE FILE | + | HOME DEVICE DOES NOT EXIST IN THE DEVICE [[FILE~|file]] |
PLEASE CONTACT YOUR SYSTEM MANAGER! | PLEASE CONTACT YOUR SYSTEM MANAGER! | ||
This means that VA Kernel ran into a problem when trying to output information to a $IO device. | This means that VA Kernel ran into a problem when trying to output information to a $IO device. | ||
| − | The most common situation is that the configuration did not have a proper setup in the {{FILE:DEVICE}} | + | The most common situation is that the [[configuration~|Configuration]] did not have a proper setup in the {{FILE|DEVICE}}, specifically for the current MUMPS level $IO device. |
| + | |||
| + | == Troubleshooting == | ||
| + | |||
| + | Make sure you have all of the devices listed on the [[Standard VistA Devices]]. | ||
| + | A VistA based system requires all of them to be setup properly. | ||
| + | |||
| + | |||
| + | === Step by Step === | ||
| + | |||
| + | # login using the device | ||
| + | # enter programming mode (if not part of login process) | ||
| + | # use the MUMPS command | ||
| + | ## <mcode>WRITE "<<",$IO,">>",!</mcode> | ||
| + | # go into programmer's FileMan | ||
| + | ## <mcode>DO P^DI</mcode> | ||
| + | # lookup the device specified in the {{FILE|DEVICE}}. | ||
| + | ## VA FileMan 22.0 | ||
| + | ## Select OPTION: INQUIRE TO [[FILE~|file]] ENTRIES | ||
| + | ## OUTPUT FROM WHAT [[FILE~|file]]: NEW PERSON// DEVICE (32 entries) | ||
| + | ## Select DEVICE NAME: | ||
| + | # input the name of the device printed above (between the << and >> ) | ||
| + | # if it is found, make sure the field SIGN-ON/SYSTEM DEVICE: is set to YES | ||
| + | # if it is not found, decide if the DEVICE should be a virtual device or not, and then add it to the {{FILE|DEVICE}}. | ||
| + | |||
| + | == Technical Details == | ||
| + | |||
| + | This message occurs because the device name fails in a [[^DIC lookup]] in the [[FILE 3.5|DEVICE File]]. Normally, devices have the field SIGN-ON/SYSTEM DEVICE set to YES, and they are virtual devices. So the code progressively takes letters off the end of the lookup variable storing the device name, and tries to find them in the G crossref of the DEVICE [[File~|file]], ie: ^%ZIS(1,"G","SYS.."_something | ||
Latest revision as of 18:45, 28 April 2015
Description
A common problem that people have who are trying to configure VistA is a message:
HOME DEVICE DOES NOT EXIST IN THE DEVICE file PLEASE CONTACT YOUR SYSTEM MANAGER!
This means that VA Kernel ran into a problem when trying to output information to a $IO device.
The most common situation is that the Configuration did not have a proper setup in the VA FileMan DEVICE File, specifically for the current MUMPS level $IO device.
Troubleshooting
Make sure you have all of the devices listed on the Standard VistA Devices. A VistA based system requires all of them to be setup properly.
Step by Step
- login using the device
- enter programming mode (if not part of login process)
- use the MUMPS command
- <mcode>WRITE "<<",$IO,">>",!</mcode>
- go into programmer's FileMan
- <mcode>DO P^DI</mcode>
- lookup the device specified in the VA FileMan DEVICE File.
- input the name of the device printed above (between the << and >> )
- if it is found, make sure the field SIGN-ON/SYSTEM DEVICE: is set to YES
- if it is not found, decide if the DEVICE should be a virtual device or not, and then add it to the VA FileMan DEVICE File.
Technical Details
This message occurs because the device name fails in a ^DIC lookup in the DEVICE File. Normally, devices have the field SIGN-ON/SYSTEM DEVICE set to YES, and they are virtual devices. So the code progressively takes letters off the end of the lookup variable storing the device name, and tries to find them in the G crossref of the DEVICE file, ie: ^%ZIS(1,"G","SYS.."_something
