Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.stsci.edu/ftp/documents/system-docs/vms-guide/html/VUG_19.html
Дата изменения: Wed Nov 1 17:38:23 1995 Дата индексирования: Sun Dec 23 18:29:59 2007 Кодировка: Поисковые слова: jupiter |
System messages have the format:
%XXX-L-CODE, textThe XXX portion of the message is a mnemonic for the program or system procedure which issued the message. Thus, if the error was in DEC FORTRAN the XXX portion of the message would be
FORT
.
The L is the severity level. The possible levels are shown in the following table.
The
Informational messages might look like the one below, which indicates that a tape was successfully mounted on tape drive
Error messages may seem difficult at first, but they become more useful as you gain experience.
To abort a runaway process:
Table 2.7: Error Message Severity Levels
Mistyping the TYPE
command as TYPR
results in a warning. No procedure is affected by the error and you can reenter the command:
$ TYPR FILE_NAME.TXT
%DCL-W-IVVERB, unrecognized command verb-check validity and spelling
\TYPR\
Notice that in the preceding example, the message was issued by the DCL command interpreter and that it is a warning message.CODE
portion of a system message is a shorthand for the description of the message given by the text. In the example above, the code is IVVERB
which is shorthand for "Invalid Verb." The text of the error message indicates that the DCL command interpreter did not recognize the command. The invalid command is displayed below the error message between the backslash (\
) characters.MTA0
:
%MOUNT-I-MOUNTED, TAPE mounted on MTA0:
The following example shows a fatal error.
%FORT-F-OPENIN, error opening DISK$SHARE0:[SMITH]PROG.FOR as input
-RMS-F-FNF, file not found
This message has two parts: the first says that FORTRAN could not open the specified file, the second says that the Record Management System (which tracks user files) could not locate the file in the current directory. Both are fatal errors, aborting the operation. Runaway Processes
Occasionally, a program will seem to be in an endless loop (consumes resources, but produces nothing), and you are sure that you did not press
-
or
. If this is the case, you may have a runaway process on your hands.*1
-
to interrupt the program.
-
to try a system interrupt. This will abort most runaway processes.
SHOW
USERS/FULL
to find out the process ID (PID) of the runaway process.STOP
/ID
=pid. Wait a bit. The process must be in a computable state before it is killed.SHOW
SYSTEM
. If your process has a state of RW
xxx (for example, RWAST
) then it may never become computable and cannot be killed. If this is the case, talk to the system manager, or send mail to SYSTEM.
Generated with CERN WebMaker