Specifications
SYSTEM MESSAGES
Error Messages
VX 520 R
EFERENCE GUIDE 163
STARTUP ERRORS
DOWNLOAD NEEDED
<error message>
The following error messages may occur if a defect is
found on the *GO variable. *GO is a variable in the
CONFIG.SYS file and is the first thing that runs on
startup if available.
• NO *GO VARIABLE - There is no *GO environment
variable in the group one CONFIG.SYS file.
• *GO NOT FOUND - The *GO variable is set but the
executable file is missing.
• *GO NOT AUTHENTICATED - The *GO variable is set
but the executable file is not authenticated.
• NOT ENOUGH MEMORY - The *GO variable is set
but there is not enough memory to execute the file.
• INVALID *GO VARIABLE - This is the defalut error
condition. The system could not run the *GO
variable eventhough it is set, authenticated, and
enough memory is available to execute the file.
FLASH CHKSUM ER Gnn
A corrupt file is detected in the flash file system during
terminal start up, after power on, or during restart. This
message may indicate a hardware problem; the error
condition may be resolved through another download
of the file.
RAM CHKSUM ERROR Gnn
A corrupt file is detected in the RAM file system at
terminal start up, after power-on, or during restart. This
message may indicate a hardware problem; the error
condition may be resolved through another download
of the file.
**VERIFYING FILES**
COMPARE SIGNATURE
FILENAME.P7S
FILENAME.OUT
*FAILED*
This message appears on screen when the file
authentication module fails to authenticate a new
signature file.
*FAILED* appears for five seconds and
the terminal beeps three times to draw attention to the
filename of the certificate that could not be
authenticated.
This message remains on screen until all new
signature files are checked. New digital certificates are
always checked first, followed by new signature files,
in an uninterrupted process.
Table 23 Error Messages
Display Action