Skip to content

Commit 80d8604

Browse files
josephsnyderjosephsnyder
committed
Add reStructuredText file for test troubleshooting
Take the content of the troubleshooting wiki page on the OSEHRA site and transform it into a reStructuredText file for the VistA repository. Add information on the M-Unit 1.3 troubleshooting. OSEHRA-Id: http://issues.osehra.org/browse/OAT-206 Change-Id: I6e8dbde0afe6dfaea5480edf7911265971123797
1 parent be67a79 commit 80d8604

2 files changed

Lines changed: 97 additions & 2 deletions

File tree

‎Documentation/README.rst‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -170,8 +170,7 @@ directory and includes:
170170
* `M Standards and Conventions`_
171171

172172
.. _testingChanges: testingChanges.rst
173-
.. _`Troubleshooting Page`:
174-
http://www.osehra.org/wiki/troubleshooting-installation-and-testing
173+
.. _`Troubleshooting Page`: Troubleshooting.rst
175174
.. _ObtainingandInstallAuxPrograms: ObtainingandInstallAuxPrograms.rst
176175
.. _ObtainingVistAMCode: ObtainingVistAMCode.rst
177176
.. _ChoosingMUMPSEnvironment: ChoosingMUMPSEnvironment.rst

‎Documentation/Troubleshooting.rst‎

Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
1+
Troubleshooting of Installation and Testing
2+
=============================================
3+
4+
5+
This page is for the aggregation of issues that have been experienced during
6+
the setup and testing of the OSEHRA Code Base. Check here first for solutions
7+
to the problems that you are encountering. If you cannot find a solution,
8+
leave a comment with the details of your issue or create an issue on the JIRA
9+
site found at http://issues.osehra.org/
10+
11+
1. I get a "GVSUBOFLOW" error while importing the Globals into the GT.M instance.
12+
----------------------------------------------------------------------------------
13+
14+
The max size of a string is set during the creation of the database.dat in the
15+
last step of the `Installing GT.M`_ process. It is set via the argument:::
16+
17+
-key_max=1023
18+
19+
To eliminate the overrun error: run the ``dse change`` command from within the
20+
directory that contains the database.dat, but increase the ``-key_max`` value
21+
to a larger number:
22+
23+
.. parsed-literal::
24+
25+
dse change -f -key_max=2046 -rec=4096
26+
27+
2. Errors appear during configuration of VistA on GT.M
28+
--------------------------------------------------------
29+
30+
During the configuration of GT.M, developers have reported errors appearing
31+
while the routines are being renamed for the system. This error occurs when
32+
GT.M attempts to compile code that was not intended to run on the system.
33+
These errors are to be expected and **will not** have a negative effect on
34+
the running of the system.
35+
36+
A JIRA bug report has been filed which can be found in the
37+
`OSEHRA JIRA instance`_ .
38+
39+
Example of Errors:
40+
41+
.. parsed-literal::
42+
43+
I will now rename a group of routines specific to your operating system.
44+
> Routine: ZOSVGUX Loaded, Saved as %ZOSV
45+
> . S (%,%1)=$ZGETDVI($I,"TT_ACCPORNAM")
46+
> ^-----
47+
> At column 14, line 48, source module
48+
> /home/karthik/Downloads/VistA/r/ZIS4GTM.m
49+
> %GTM-E-FNOTONSYS, Function or special variable is not supported by this
50+
> operating system
51+
>
52+
> Routine: ZIS4GTM Loaded, Saved as %ZIS4
53+
> Routine: ZISFGTM Loaded, Saved as %ZISF
54+
> Routine: ZISHGTM Loaded, Saved as %ZISH
55+
> Routine: XUCIGTM Loaded, Saved as %XUCI
56+
> Routine: ZOSV2GTM Loaded, Saved as %ZOSV2 O
57+
> NIO:(:SOCK:"AT"::512:512:10):30 Q:'$T S POP=0 U NIO
58+
> ^-----
59+
> At column 9, line 25, source module
60+
> /home/karthik/Downloads/VistA/r/ZISTCPS.m
61+
> %GTM-E-DEVPARUNK, Deviceparameter unknown ...
62+
63+
3. M-Unit 1.3 reports error during installation
64+
------------------------------------------------
65+
66+
The OSEHRA M-Unit tests check for and attempt to install a version of the
67+
M-Unit Test software before each test is run. If the test reports an error
68+
during the installation process, information will be displayed in the test run
69+
but the best information will be found in the ``UnitTest/Log/`` within the
70+
binary directory of the testing framework. The ``VistAInteraction*`` files
71+
in that directory contain the roll-and-scroll interactions and will display
72+
any errors sent by the system. Some known errors are found below:
73+
74+
a. ERROR #5002: Cache error: <UNDEFINED>zCreate+13^Config.CommonMapMethods.1 \*Properties
75+
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
76+
77+
**Cache Only**
78+
This is a known error which affects the M-Unit 1.3 release on more recent
79+
Cache instances. This error occurs when the framework attempts to generate a
80+
set of routine and global mappings for the ``%ut*`` namespace. To eliminate
81+
this error, use the ``System Management Portal`` to configure a routine and
82+
global mapping for the ``%ut*``. Examples of generating the routine and global
83+
mapping can be found in the `Install Cache`_ set of instructions.
84+
85+
After the mappings have been generated, run the test again and the KIDs patch
86+
should install and the testing continue.
87+
88+
89+
90+
To request an update to this document, generate an issue in the OSEHRA JIRA
91+
instance for the `OSEHRA Automated Testing`_ project.
92+
93+
.. _`OSEHRA JIRA instance`: http://issues.osehra.org/browse/VAF-2
94+
.. _`OSEHRA Automated Testing`: http://issues.osehra.org/projects/OAT
95+
.. _`Installing GT.M`: InstallGTM.rst
96+
.. _`Install Cache`: InstallCache.rst

0 commit comments

Comments
 (0)