Configuration How To HOME DEVICE DOES NOT EXIST - Revision history

DavidWhitten: /* Technical Details */

2015-04-28T18:45:47Z

Technical Details

← Older revision		Revision as of 18:45, 28 April 2015
Line 35:		Line 35:
	== Technical Details ==		== 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		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

DavidWhitten: /* Technical Details */

2015-04-28T18:44:39Z

Technical Details

← Older revision		Revision as of 18:44, 28 April 2015
Line 35:		Line 35:
	== Technical Details ==		== Technical Details ==

	This message occurs because the device name fails in a ^DIC lookup in the ~~DEVICE~~ [[~~file~}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		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

NeilArmstrong: Added a glossary link to file

2013-06-10T17:47:04Z

Added a glossary link to file

← Older revision		Revision as of 17:47, 10 June 2013
Line 3:		Line 3:
	A common problem that people have who are trying to configure VistA is a message:		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!

Line 26:		Line 26:
	# lookup the device specified in the {{FILE\|DEVICE}}.		# lookup the device specified in the {{FILE\|DEVICE}}.
	## VA FileMan 22.0		## VA FileMan 22.0
	## Select OPTION: INQUIRE TO FILE ENTRIES		## Select OPTION: INQUIRE TO [[FILE~\|file]] ENTRIES
	## OUTPUT FROM WHAT FILE: NEW PERSON// DEVICE (32 entries)		## OUTPUT FROM WHAT [[FILE~\|file]]: NEW PERSON// DEVICE (32 entries)
	## Select DEVICE NAME:		## Select DEVICE NAME:
	# input the name of the device printed above (between the << and >> )		# input the name of the device printed above (between the << and >> )
Line 35:		Line 35:
	== Technical Details ==		== 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		This message occurs because the device name fails in a ^DIC lookup in the DEVICE [[file~}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

NeilArmstrong: Added glossary link to Configuration~

2012-10-05T17:47:24Z

Added glossary link to Configuration~

← Older revision		Revision as of 17:47, 5 October 2012
Line 8:		Line 8:
	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}}, specifically for the current MUMPS level $IO 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 ==		== Troubleshooting ==

Ftrotter at 16:27, 7 March 2007

2007-03-07T16:27:45Z

← Older revision		Revision as of 16:27, 7 March 2007
Line 1:		Line 1:
	__TOC__		__TOC__
	== Description ==		== Description ==
	A common problem that people have who are trying to configure ~~OpenVistA and~~ VistA is a message:		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

152.131.9.69 at 22:32, 7 March 2005

2005-03-07T22:32:29Z

← Older revision		Revision as of 22:32, 7 March 2005
Line 21:		Line 21:
	# enter programming mode (if not part of login process)		# enter programming mode (if not part of login process)
	# use the MUMPS command		# use the MUMPS command
	## <mcode>WRITE "{{",$IO,"}}",!</mcode>		## <mcode>WRITE "<<",$IO,">>",!</mcode>
	# go into programmer's FileMan		# go into programmer's FileMan
	## <mcode>DO P^DI</mcode>		## <mcode>DO P^DI</mcode>
Line 29:		Line 29:
	## OUTPUT FROM WHAT FILE: NEW PERSON// DEVICE (32 entries)		## OUTPUT FROM WHAT FILE: NEW PERSON// DEVICE (32 entries)
	## Select DEVICE NAME:		## Select DEVICE NAME:
	# input the name of the device printed above (between the {{ and }} )		# 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 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}}.		# if it is not found, decide if the DEVICE should be a virtual device or not, and then add it to the {{FILE\|DEVICE}}.

152.131.9.69 at 18:32, 7 March 2005

2005-03-07T18:32:12Z

@@ Line 1: / Line 1: @@
 A common problem that people have who are trying to configure OpenVistA and VistA is a message:
@@ Line 6: / Line 8: @@
 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 did not have a proper setup in the {{FILE|DEVICE}}, specifically for the current MUMPS level $IO device.

152.131.9.69 at 18:16, 7 March 2005

2005-03-07T18:16:17Z

← Older revision		Revision as of 18:16, 7 March 2005
Line 6:		Line 6:
	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 did not have a proper setup in the {{FILE\|DEVICE}}

152.131.9.69 at 18:16, 7 March 2005

2005-03-07T18:16:00Z

New page

A common problem that people have who are trying to configure OpenVistA and 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 {{FILE:DEVICE}}