Installation How To Vista/Cache for Windows - Revision history

NeilArmstrong: Added glossary link to Configuration~

2012-10-10T20:47:38Z

Added glossary link to Configuration~

← Older revision		Revision as of 20:47, 10 October 2012
Line 372:		Line 372:
	NAME OF MANAGER'S NAMESPACE: VISTA// Hit enter.<br>		NAME OF MANAGER'S NAMESPACE: VISTA// Hit enter.<br>
	PRODUCTION (SIGN-ON) NAMESPACE: VISTA// Hit enter.<br>		PRODUCTION (SIGN-ON) NAMESPACE: VISTA// Hit enter.<br>
	NAME OF THIS CONFIGURATION: VISTA// Hit enter.		NAME OF THIS [[CONFIGURATION~\|Configuration]]: VISTA// Hit enter.
	<br>		<br>
	</td>		</td>

NeilArmstrong: Added glossary link to Prompt~

2012-03-05T07:49:11Z

Added glossary link to Prompt~

Show changes

NeilArmstrong: Added glossary link to Prompt~

2012-03-05T03:11:35Z

Added glossary link to Prompt~

← Older revision		Revision as of 03:11, 5 March 2012
Line 311:		Line 311:
	<tr>		<tr>
	<td valign="top" width=25>29.</td>		<td valign="top" width=25>29.</td>
	<td>At User prompt Type <span style="font-family: 'verdana';">D ^%CD</span> (or ZN "%SYS").<br>		<td>At User [[prompt~\|Prompt]] Type <span style="font-family: 'verdana';">D ^%CD</span> (or ZN "%SYS").<br>
	</td>		</td>
	</tr>		</tr>
Line 340:		Line 340:
	<tr>		<tr>
	<td valign="top" width=25>32.</td>		<td valign="top" width=25>32.</td>
	<td>At User prompt Type "D ^%CD".</td>		<td>At User [[prompt~\|Prompt]] Type "D ^%CD".</td>
	</tr>		</tr>
	<tr>		<tr>
Line 397:		Line 397:
	<tr>		<tr>
	<td valign="top" width=25>36.</td>		<td valign="top" width=25>36.</td>
	<td>Initialize FileMan to set your site name and number by running "D ^DINIT" from the VISTA> prompt. Say yes to Intilialize VA Fileman if it isn't already initialized. Give your site a site name and a 4 digit site number that is preferably not a round number like 1000 or 5000 so you have less chance of file number collisions when you make your own files in the future. You can run D ^DINIT again to see if you changes were successful and choose Cache/OpenM when offered a choice of MUMPS system you are using.</td>		<td>Initialize FileMan to set your site name and number by running "D ^DINIT" from the VISTA> [[prompt~\|Prompt]]. Say yes to Intilialize VA Fileman if it isn't already initialized. Give your site a site name and a 4 digit site number that is preferably not a round number like 1000 or 5000 so you have less chance of file number collisions when you make your own files in the future. You can run D ^DINIT again to see if you changes were successful and choose Cache/OpenM when offered a choice of MUMPS system you are using.</td>
	</tr>		</tr>
	<tr>		<tr>
Line 594:		Line 594:
	<tr>		<tr>
	<td valign="top" width=25>41.</td>		<td valign="top" width=25>41.</td>
	<td>Now to create your own domain. From the VISTA prompt, start VA FileMan by typing "D Q^DI". At the Select OPTION: prompt. Type "1". (You can see why you typed 1 if you type "??" at the option prompt. That will give you the list of options you can choose from and 1 is ENTER OR EDIT FILE ENTRIES.) At INPUT TO WHAT FILE: type "DOMAIN" and accept the ALL// default to EDIT WHICH FIELD. At Select DOMAIN NAME: enter a local domain name. Substitute an appropriate value for VISTA.MYDOMAIN.COM in the example below.<br>		<td>Now to create your own domain. From the VISTA [[prompt~\|Prompt]], start VA FileMan by typing "D Q^DI". At the Select OPTION: [[prompt~\|Prompt]]. Type "1". (You can see why you typed 1 if you type "??" at the option [[prompt~\|Prompt]]. That will give you the list of options you can choose from and 1 is ENTER OR EDIT FILE ENTRIES.) At INPUT TO WHAT FILE: type "DOMAIN" and accept the ALL// default to EDIT WHICH FIELD. At Select DOMAIN NAME: enter a local domain name. Substitute an appropriate value for VISTA.MYDOMAIN.COM in the example below.<br>
	</td></tr>		</td></tr>

Line 636:		Line 636:
	<tr>		<tr>
	<td valign="top" width=25>42.</td>		<td valign="top" width=25>42.</td>
	<td>Now to complete the DOMAIN set up by Christening the new domain. Go back to the VISTA> prompt and type "D CHRISTEN^XMUDCHR".</td>		<td>Now to complete the DOMAIN set up by Christening the new domain. Go back to the VISTA> [[prompt~\|Prompt]] and type "D CHRISTEN^XMUDCHR".</td>
	</tr>		</tr>
	<tr><td colspan="2"> </td></tr>		<tr><td colspan="2"> </td></tr>
Line 683:		Line 683:
	<tr>		<tr>
	<td valign="top" width=25>43.</td>		<td valign="top" width=25>43.</td>
	<td>Determine the internal entry of the new domain. Remember this number as it will be used in subsequent steps. Get back to the Select OPTION: prompt and enter "INQUIRE" or "5" (once again, you can type ?? to see the available options and 5 is INQUIRE TO FILE ENTRIES) then at the Select DOMAIN NAME: prompt, enter the new domain name you just created. Answer "N" to STANDARD CAPTIONED OUTPUT and at PRINT FIELD: answer "NUMBER". The domain number is "printed" to the screen.		<td>Determine the internal entry of the new domain. Remember this number as it will be used in subsequent steps. Get back to the Select OPTION: [[prompt~\|Prompt]] and enter "INQUIRE" or "5" (once again, you can type ?? to see the available options and 5 is INQUIRE TO FILE ENTRIES) then at the Select DOMAIN NAME: [[prompt~\|Prompt]], enter the new domain name you just created. Answer "N" to STANDARD CAPTIONED OUTPUT and at PRINT FIELD: answer "NUMBER". The domain number is "printed" to the screen.
	</td>		</td>
	</tr>		</tr>
Line 719:		Line 719:
	<td style="padding:0.5em;">		<td style="padding:0.5em;">
	<p><strong>HOME DEVICE DOES NOT EXIST IN THE DEVICE FILE</strong></p>		<p><strong>HOME DEVICE DOES NOT EXIST IN THE DEVICE FILE</strong></p>
	<p>At the VISTA> prompt, type "W $I". The first set of characters needs to match your DEVICE settings for $I.</p>		<p>At the VISTA> [[prompt~\|Prompt]], type "W $I". The first set of characters needs to match your DEVICE settings for $I.</p>
	<p>Start Fileman (D Q^DI)<br/>		<p>Start Fileman (D Q^DI)<br/>
	<code>Select OPTION: 1 (for ENTER OR EDIT...)<br/>		<code>Select OPTION: 1 (for ENTER OR EDIT...)<br/>
Line 739:		Line 739:
	<tr>		<tr>
	<td valign="top" width=25>44.</td>		<td valign="top" width=25>44.</td>
	<td>From the VISTA prompt repoint the KERNEL SYSTEM PARAMETERS and RPC BROKER PARAMETERS files to the new domain, go back to the VISTA> prompt and enter 'S $P(^XTV(8989.3,1,0),"^")=3' and 'S $P(^XWB(8994.1,1,0),"^")=3' where 3 is the internal number of the new domain we just created in the previous step.</td>		<td>From the VISTA [[prompt~\|Prompt]] repoint the KERNEL SYSTEM PARAMETERS and RPC BROKER PARAMETERS files to the new domain, go back to the VISTA> [[prompt~\|Prompt]] and enter 'S $P(^XTV(8989.3,1,0),"^")=3' and 'S $P(^XWB(8994.1,1,0),"^")=3' where 3 is the internal number of the new domain we just created in the previous step.</td>
	</tr>		</tr>
	<tr><td colspan="2"> </td></tr>		<tr><td colspan="2"> </td></tr>

NeilArmstrong: Added glossary link to Application~

2012-02-22T12:31:38Z

Added glossary link to Application~

← Older revision		Revision as of 12:31, 22 February 2012
Line 336:		Line 336:
	<tr><td colspan="2"> </td></tr>		<tr><td colspan="2"> </td></tr>
	==Begin to set up the VistA System==		==Begin to set up the VistA System==
	<h5>The routine ZTMGRSET defines VistA global variables and saves system wide M routines that are Caché specific. FileMan is the database system used by all VistA ~~applications~~.</h5>		<h5>The routine ZTMGRSET defines VistA global variables and saves system wide M routines that are Caché specific. FileMan is the database system used by all VistA [[application~\|Application]]s.</h5>

	<tr>		<tr>
Line 454:		Line 454:
	<tr>		<tr>
	<td valign="top"> </td>		<td valign="top"> </td>
	<td class="small">If you run an RPCBroker application, server opens a new session with<br>		<td class="small">If you run an RPCBroker [[application~\|Application]]], server opens a new session with<br>
	XWBTCPC routine for the client but it does not return what it should for<br>		XWBTCPC routine for the client but it does not return what it should for<br>
	the XUS SIGNON SETUP (volume set, namespace, device, ...)<br>		the XUS SIGNON SETUP (volume set, namespace, device, ...)<br>
Line 1,214:		Line 1,214:

	<h4>Set Up More Parameters</h4>		<h4>Set Up More Parameters</h4>
	<h5>These are parameters that are more applicable to the VistA application software.</h5>		<h5>These are parameters that are more applicable to the VistA [[application~\|Application]] software.</h5>

	<table border="0" cellpadding="2" cellspacing="2">		<table border="0" cellpadding="2" cellspacing="2">
Line 1,220:		Line 1,220:
	<td valign="top" width=25>78.</td>		<td valign="top" width=25>78.</td>
	<td>		<td>
	If you are planning to use the VistA ~~applications~~ such as Registration, Scheduling etc. you need to add new Institution to the INSTITUTION File. Go back to the VISTA> prompt and "SET XUMF=1" then "D Q^DI". Select Option #1 and edit File #4. Edit the field STATION NUMBER. For Station Number, you must enter the same number as the Site Number when you initialized FileMan. (See Start FileMan and <a href="#Vista_Setup">Begin Setting Up Vista section</a>.)		If you are planning to use the VistA [[application~\|Application]]s such as Registration, Scheduling etc. you need to add new Institution to the INSTITUTION File. Go back to the VISTA> prompt and "SET XUMF=1" then "D Q^DI". Select Option #1 and edit File #4. Edit the field STATION NUMBER. For Station Number, you must enter the same number as the Site Number when you initialized FileMan. (See Start FileMan and <a href="#Vista_Setup">Begin Setting Up Vista section</a>.)
	</td>		</td>
	</tr>		</tr>
Line 1,554:		Line 1,554:
	<td valign="top" width=25>97.</td>		<td valign="top" width=25>97.</td>
	<td>		<td>
	Now to update devices. The Platinum CACHE.DAT already comes with preconfigured devices. It is best to leave the VOLUME SET(CPU) field blank. The help text for the field states: <em>"If no name has been entered for this field, this device is assumed to be accessible from all CPUs in the network. In other words, when this device is referenced, the device handler will operate as if this device is resident on the local CPU</em>". The SIGN-ON/SYSTEM DEVICE: field should be set to NO or left blank for output devices and YES if the device is used to log on to the system. Use FileMan to edit the CONSOLE, NULL, HFS, and TELNET devices. CONSOLE is the primary logon device. The NULL device is used by the Vista RPC Broker and HFS is used by the Kernel Installation and Distribution System (KIDS) to install application patches and new ~~applications~~ when they are released. On the single user Caché PC you will not need the TELNET device since it does not allow remote access. At the VISTA> prompt, type "D Q^DI" to invoke VA Fileman. At Select OPTION: type "1" (ENTER OR EDIT FILE ENTRIES) and at INPUT TO WHAT FILE:, enter "3.5".		Now to update devices. The Platinum CACHE.DAT already comes with preconfigured devices. It is best to leave the VOLUME SET(CPU) field blank. The help text for the field states: <em>"If no name has been entered for this field, this device is assumed to be accessible from all CPUs in the network. In other words, when this device is referenced, the device handler will operate as if this device is resident on the local CPU</em>". The SIGN-ON/SYSTEM DEVICE: field should be set to NO or left blank for output devices and YES if the device is used to log on to the system. Use FileMan to edit the CONSOLE, NULL, HFS, and TELNET devices. CONSOLE is the primary logon device. The NULL device is used by the Vista RPC Broker and HFS is used by the Kernel Installation and Distribution System (KIDS) to install [[application~\|Application]] patches and new [[application~\|Application]]s when they are released. On the single user Caché PC you will not need the TELNET device since it does not allow remote access. At the VISTA> prompt, type "D Q^DI" to invoke VA Fileman. At Select OPTION: type "1" (ENTER OR EDIT FILE ENTRIES) and at INPUT TO WHAT FILE:, enter "3.5".
	</td>		</td>
	</tr>		</tr>

NeilArmstrong: Added glossary link to Security Key~

2012-02-18T03:20:14Z

Added glossary link to Security Key~

← Older revision		Revision as of 03:20, 18 February 2012
Line 1,128:		Line 1,128:
	<td valign="top" width=25>75.</td>		<td valign="top" width=25>75.</td>
	<td>		<td>
	At Select Menu Management Option: type "KEY" Management; then at Select Key Management Option: "ALLO"cation of Security ~~Keys~~.		At Select Menu Management Option: type "KEY" Management; then at Select Key Management Option: "ALLO"cation of [[Security Key~\|Security Key]]s.
	</td>		</td>
	</tr>		</tr>
Line 1,164:		Line 1,164:
	Select Menu Management Option: <b>KEY</b> Management<br>		Select Menu Management Option: <b>KEY</b> Management<br>
	<br>		<br>
	Select Key Management Option: <b>ALLO</b>cation of Security ~~Keys~~<br>		Select Key Management Option: <b>ALLO</b>cation of [[Security Key~\|Security Key]]s<br>
	<br>		<br>
	Allocate key: <b>XUMGR</b><br>		Allocate key: <b>XUMGR</b><br>

Anthracite at 22:15, 11 March 2007

2007-03-11T22:15:15Z

← Older revision		Revision as of 22:15, 11 March 2007
Line 625:		Line 625:
	<tr>		<tr>
	<td style="padding:0.5em;">		<td style="padding:0.5em;">
	<p><strong>~~Prompted~~ for ACCESS CODE:</strong></p>		<p><strong>If you are prompted for ACCESS CODE:</strong></p>
	<p>Type <b>S DUZ=1</b> before entering into D Q^DI</p>		<p>Type <b>S DUZ=1</b> before entering into D Q^DI</p>
	</td>		</td>

Anthracite at 22:12, 11 March 2007

2007-03-11T22:12:03Z

← Older revision		Revision as of 22:12, 11 March 2007
Line 410:		Line 410:
	<tr>		<tr>
	<td valign="top">38.</td>		<td valign="top">38.</td>
	<td>This step may not be needed in newer versions of VistA, but check anyway. The VA does not allow then number of available remaining Cache licenses to go below 5 so that whatever situation led to exceeding the number allowed can be corrected. However, for small users, they may only have 5 licenses total, so it is necessary to block that prohibition.<BR>Go to the blue cube ~~and~~ choose Studio and choose the proper namespace either by choosing it in a window that pops up or by choosing File, Change Namespace. Then choose Open and search for %ZOSV* and the type if file is .int . Chose %ZOSV. </BR><BR> Line numbers are included below to help you find what to edit. Put a semicolon ~~without the quotes~~ in front of the lines 23 and 24 and add Q 99; to the front of line 26 and save it, which will compile it. You may ~~with~~ to add another line with a comment saying that you edited the file and put your name or initials so you can find it again later should you need to search the files for changes you have made.</BR></td>		<td>This step may not be needed in newer versions of VistA, but check anyway. The VA does not allow then number of available remaining Cache licenses to go below 5 so that whatever situation led to exceeding the number allowed can be corrected. However, for small users, they may only have 5 licenses total, so it is necessary to block that prohibition.<BR></BR><BR>Go to the Cache blue cube on the Windows task bar, choose Studio and then choose the proper namespace either by choosing it in a window that pops up or by choosing File, Change Namespace. Then choose Open and search for %ZOSV* and the type if file is .int . Chose %ZOSV. </BR><BR></BR><BR> Line numbers are included below to help you find what to edit. Put a semicolon ; in front of the lines 23 and 24 and add Q 99; to the front of line 26 and save it, which will compile it for you automatically. The semicolon turns the lines of code into comments instead of active code. You may want to add another line with your own comment saying that you edited the file and put your name or initials so you can find it again later should you need to search the files for changes you have made.</BR></td>
	</tr>		</tr>
	<TR></TR><TD></TD><TD><P><BR>ORIGINAL</BR><BR></BR>		<TR></TR><TD></TD><TD><P><BR>ORIGINAL</BR><BR></BR>
Line 511:		Line 511:
	<td style="padding:0.5em;">		<td style="padding:0.5em;">
	<p><strong> TROUBLE - CALL IRM NOW! </strong></p>		<p><strong> TROUBLE - CALL IRM NOW! </strong></p>
	<p>This message may appear when you first log into D^ZU in step 91 ~~below.~~</p>		<p>This message may appear when you first log into D ^ZU. Edit the routine ZU now instead of later in step 91 as follows:</p>
	<p>Open up routine ZU.INT, locate the following line:<br/>		<p>Open up routine ZU.INT in Studio and locate the following line which is on or about the 8th line:<br/>
	<code>JOBCHK    I $$AVJ^%ZOSV()<3 W $C(7),!!," TROUBLE - CALL IRM NOW! " G HALT</code><br/>		<code>JOBCHK    I $$AVJ^%ZOSV()<3 W $C(7),!!," TROUBLE - CALL IRM NOW! " G HALT</code><br/>
	And place a semi-colon (;) before the I, it should now look like this:<br/>		And place a semi-colon (;) before the I, it should now look like this:<br/>

Anthracite at 21:18, 11 March 2007

2007-03-11T21:18:02Z

@@ Line 410: / Line 410: @@
 <tr>
    <td valign="top">38.</td>
-   <td>This step may not be needed in newer versions of VistA, but check anyway.  (verified not required for cache.dat dated 2005-08-25)<br>Highlight LOCALTCP-VISTA, then File, Open and enter "%ZOSV.INT". Open it and see if the first several lines are as follows:</td>
+   <td>This step may not be needed in newer versions of VistA, but check anyway.  The VA does not allow then number of available remaining Cache licenses to go below 5 so that whatever situation led to exceeding the number allowed can be corrected. However, for small users, they may only have 5 licenses total, so it is necessary to block that prohibition.<BR>Go to the blue cube and choose Studio and choose the proper namespace either by choosing it in a window that pops up or by choosing File, Change Namespace. Then choose Open and search for %ZOSV* and the type if file is .int .  Chose %ZOSV. </BR><BR> Line numbers are included below to help you find what to edit.  Put a semicolon  without the quotes in front of the lines 23 and 24 and add Q 99; to the front of line 26 and save it, which will compile it. You may with to add another line with a comment saying that you edited the file and put your name or initials so you can find it again later should you need to search the files for changes you have made.</BR></td>
 </tr>
-<tr>
+<TR></TR><TD></TD><TD><P><BR>ORIGINAL</BR><BR></BR>
-  <td valign="top">&nbsp;</td>
+<Br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;22&nbsp;&nbsp;&nbsp;;To get available jobs from Cache 5.0 up</Br><Br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;23 &nbsp;&nbsp;&nbsp;I V'&lt;5 D  Q AVJ</BR><Br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;24&nbsp;&nbsp;&nbsp;        . X &quot;S ZOSV=$ZU(5),%=$ZU(5,&quot;&quot;%SYS&quot;&quot;) S AVJ=$system.License.LUAvailable(),%=$ZU(5,ZOSV)&quot;</BR><Br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;25&nbsp; &nbsp;&nbsp;       ;Return fixed value not known version</BR><Br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;26&nbsp;&nbsp;&nbsp;        Q 15</BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;27&nbsp;&nbsp;        ;</BR></TD></tr>
-  <td class="plain">%ZOSV&nbsp;&nbsp; ;SFISC/AC - $View commands for Open M for NT. ;12/04/2001 15:30<br>
+<tr><td></td><td><BR>EDITED</BR><BR></BR>
-&nbsp;&nbsp; ;;8.0;KERNEL;**34,94,107,118,136,215**;Jul 10, 1995<br>
+<Br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;22&nbsp;&nbsp;&nbsp;;To get available jobs from Cache 5.0 up</Br><Br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;23 &nbsp;&nbsp;&nbsp;;I V'&lt;5 D  Q AVJ</BR><Br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;24&nbsp;&nbsp;        ;. X &quot;S ZOSV=$ZU(5),%=$ZU(5,&quot;&quot;%SYS&quot;&quot;) S AVJ=$system.License.LUAvailable(),%=$ZU(5,ZOSV)&quot;</BR><Br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;25 &nbsp;       ;Return fixed value not known version</BR><Br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;26&nbsp;&nbsp;&nbsp;Q 99;        Q 15</BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;27&nbsp;&nbsp;        ;</BR></P>
-    ACTJ()&nbsp;&nbsp; ;# Active jobs<br>
+  </td><TR><TD></TD>
-&nbsp;&nbsp; N Y,% S %=0 F Y=0:1 S %=$ZJ(%) Q:%=""<br>
+   <td><P>Now if you made changes, click File, Save and then Build, Compile. At the bottom of the window you should soon see the message "Compilation finished successfully." &nbsp;</P></td>
 </tr>
 <tr>

Anthracite: /* Install Cache */

2006-10-02T03:16:07Z

Install Cache

← Older revision		Revision as of 03:16, 2 October 2006
Line 45:		Line 45:
	<h5>This phase of the installation creates an area (a namespace)		<h5>This phase of the installation creates an area (a namespace)
	for you to work in and point that namespace to the distributed VistA		for you to work in and point that namespace to the distributed VistA
	database.</h5>		database. The instructions below are for Cache 5.0 and below. The instructions for the installation and mapping of the VistA Routines and Globals for using Cache 5.2 may be downloaded from http://OpenSourceVistA.net:8888/NancysVistAServer . They are available in Open Document Format and in Word format and are titled InstallingVistAWithSingleUserVersionOfCache5.2 </h5>
			<p></p>
	<table border="0" cellpadding="2" cellspacing="2">		<table border="0" cellpadding="2" cellspacing="2">
	<tr>		<tr>
Line 174:		Line 174:
	</table>		</table>
	<table>		<table>

	==Mapping Globals and Routines to Datasets==		==Mapping Globals and Routines to Datasets==
	Globals are persistent M data structures where files and data are stored and routines are M programs. Mapping is a way to tell Caché where to look for globals and routines. By default, Caché maps routines and globals that start with the "%" character to a namespace separate from the routines and globals that do not start with the "%" character. With VistA, it is recommended that all VistA routines and globals that start with the character "%" be mapped to the same namespace as non-% routines and globals overriding the Caché default. The primary reason for this is to preserve these VistA globals and routines when Caché is upgraded to a new version.</td></tr>		Globals are persistent M data structures where files and data are stored and routines are M programs. Mapping is a way to tell Caché where to look for globals and routines. By default, Caché maps routines and globals that start with the "%" character to a namespace separate from the routines and globals that do not start with the "%" character. With VistA, it is recommended that all VistA routines and globals that start with the character "%" be mapped to the same namespace as non-% routines and globals overriding the Caché default. The primary reason for this is to preserve these VistA globals and routines when Caché is upgraded to a new version.</td></tr>

69.15.33.3: minor changes to dsommers' comments

2005-10-11T21:41:22Z

minor changes to dsommers' comments

@@ Line 653: / Line 653: @@
     <tr>
      <td style="padding:0.5em;">
-     <p><strong>Prompted for ACCESS CODE option #1:</strong></p>
+     <p><strong>Prompted for ACCESS CODE:</strong></p>
      <p>Type <b>S DUZ=1</b> before entering into D Q^DI</p>
      </td>
@@ Line 760: / Line 749: @@
      <p>At the VISTA> prompt, type "W $I".  The first set of characters needs to match your DEVICE settings for $I.</p>
      <p>Start Fileman (D Q^DI)<br/>
-        Select OPTION: 1 (for ENTER OR EDIT...)<br/>
+        <code>Select OPTION: 1 (for ENTER OR EDIT...)<br/>
         INPUT TO WHAT FILE: DEVICE<br/>
         EDIT WHICH FIELD: $I<br/>
         THEN EDIT FIELD:<br/>
         Select DEVICE NAME: CONSOLE<br/>
-        $I: |TNT|// |TRM|<br/>
+        $I: |TNT|// |TRM|</code><br/>
      </p>
      <p>Note my setting is |TRM| while CACHE.DAT was defaulted to |TNT|</p>
@@ Line 1,484: / Line 1,473: @@
 </td>
 </tr>
 <tr><td colspan="2">&nbsp;</td></tr>