Difference between revisions of "GTM errors"

From VistApedia
Jump to: navigation, search
(Created page with "This pages lists various GT.M errors and tries to tie them to particular VistA specific conditions. == %GDE-I-NOACTION == If you get an error: <pre> %GDE-I-NOACTION, Not updat...")
 
 
Line 1: Line 1:
 +
= Introduction =
 
This pages lists various GT.M errors and tries to tie them to particular VistA specific conditions.
 
This pages lists various GT.M errors and tries to tie them to particular VistA specific conditions.
  
 +
= Error list =
 
== %GDE-I-NOACTION ==
 
== %GDE-I-NOACTION ==
  

Latest revision as of 20:36, 9 November 2011

Introduction

This pages lists various GT.M errors and tries to tie them to particular VistA specific conditions.

Error list

%GDE-I-NOACTION

If you get an error:

 %GDE-I-NOACTION, Not updating Global Directory 

then you were probably using the GDE command. You should check that you intended for it to write results to the global directory. Did you do a CHANGE command ?

%GTM-E-JNLOPNER & %GTM-E-FILEIDMATCH

%GTM-E-JNLOPNERR, Error opening journal file /directory/filename.mjl, for database /directory/mumps.dat, %GTM-E-FILEIDMATCH, Saved File ID does not match the current ID - the file appears to have been moved

This can happen when you change the MUMPS data file (probably with a CHANGE command in ^GDE) and don't change journalling at the same time.

%GTM-E-DBFILERR & %SYSTEM-E-ENO13

%GTM-E-DBFILERR, Error with database file /directory/mumps.dat, %SYSTEM-E-ENO13, Permission denied

If you copied a directory that had mumps running to another linux user name you might have a problem with the mumps.gld file referring to the old mumps.dat file