VMS Differences
Most EVE commands and keys work the same on VMS and ULTRIX. Here is a list
of important differences:
Features Effects or differences on VMS
----------------------------------------------------------------------
File names On VMS, file names are not case-sensitive---you can
use uppercase, lowercase, or mixed case. For example,
MEMO.TXT and memo.txt specify the same file. On
ULTRIX, file names are case-sensitive.
File versions If you edit an existing file, then exiting or writing
out the buffer creates a new version of the file
without deleting or renaming previous versions. This
also applies to creating or updating a section file or
command file with SAVE ATTRIBUTES. On ULTRIX systems,
EVE copies the existing file to a backup file before
overwriting the existing file. EVE appends a version
number to the default name of the backup file that
increments with each new backup file. The commands are
not available on VMS that let the user enable or
disable the feature, or customize the way EVE creates
the backup file spec.
Buffer names On VMS, buffer names are not case-sensitive---you can
use uppercase, lowercase, or mixed case. For example,
MAIN and main specify the same buffer. On ULTRIX,
buffer names are case-sensitive; EVE system buffers
are named in all uppercase (for example, MESSAGES,
INSERT HERE, $RESTORE$, and so on).
Journaling On VMS, buffer-change journal files are created in the
directory defined by the TPU$JOURNAL logical name
(default is SYS$SCRATCH which is usually your top-
level, login directory). Default file type is
.TPU$JOURNAL. It is possible to have two or more
buffer-change journal files of the same name, such as
two MAIN.TPU$JOURNAL files from different editing
sessions. For more information, see help on Journal
Files.
Wildcards Default wildcards match the system you are using.
Thus, on VMS, the default is SET WILDCARD VMS; on
ULTRIX, it is SET WILDCARD ULTRIX. The setting applies
only to WILDCARD FIND and SHOW WILDCARDS---it does not
affect wildcards in file names, which are determined
by the operating system.
DCL or SHELL The DCL and SHELL commands are synonyms appropriate to
the operating system you are using. Thus, on VMS
systems, the SHELL command lets you execute a command
like DIRECTORY or PRINT. Similarly, on ULTRIX, the DCL
command lets you execute a command for the command
shell you are using. For example, the following
commands are equivalent---listing in a single-column
the files in your current, default directory:
On VMS On ULTRIX
-------------------- -----------
DCL DIRECTORY /COL=1 SHELL ls -1
(For more information, see help on the DCL command.)
CTRL/Z exit On VMS systems, EVE defines CTRL/Z and F10 as EXIT,
but does not define CTRL/D. On ULTRIX systems, EVE
defines CTRL/D as EXIT. Other EVE keys are defined the
same on both systems.
File types On VMS, the EVE and TPU default file types are as
follows:
.EVE ............. Initialization file
.TJL ............. Keystroke journal file
.TPU ............. Command file or debug file
.TPU$JOURNAL ..... Buffer-change journal file
.TPU$SECTION ..... Section file
.TPU$WORK ........ Work file
Qualifiers In invoking EVE, command-line qualifiers are not
positional (they can be placed before or after the
input file). Also, some qualifiers use an equal sign
(=) to distinguish a file associated with an option
and the input file (if any). For example, the
following command invokes EVE using an initialization
file named MYINIT.EVE to create or edit a file named
MEMO.TXT:
$ EDIT/TPU /INITIALIZATION=myinit memo.txt
Startup files On VMS, the EVE and TPU default startup file names are
as follows:
EVE$INIT.EVE .............. Initialization file
TPU$COMMAND.TPU ........... Command file
TPU$DEBUG.TPU ............. Debug file (with /DEBUG)
EVE$SECTION.TPU$SECTION ... Section file
Logical names On VMS, you can define the following EVE and TPU
logical names:
EVE$INIT ...... Initialization file
EVE$KEYPAD .... Keypad (EDT, EVE, NUMERIC, VT100, WPS)
TPU$COMMAND ... Command file
TPU$DEBUG ..... Debug file (with /DEBUG)
TPU$JOURNAL ... Buffer-change journaling directory
TPU$SECTION ... Section file
For example, if there is an initialization file you
want to use for all or most editing sessions, you can
define EVE$INIT to specify that file so when you
invoke EVE, that file is executed without having to
use the /INITIALIZATION qualifier. Typically, you put
the definition in your LOGIN.COM file.
$ DEFINE EVE$INIT [user.tools]myinit.eve
$ EDIT/TPU
On VMS you can define the EVE$KEYPAD logical name to
select an EVE keypad. Valid names are EDT, EVE,
NUMERIC, VT100, and WPS. If you do not define the
logical name, the keypad defaults to EVE which gives
the VT100 keypad on VT100 terminals or the NUMERIC
keypad on VT200 and later terminals.
On VMS, to invoke EVE with the Motif DECwindows
interface, use one of the following command:
$ EDIT/TPU/DISPLAY=DECWINDOWS
$ EDIT/TPU/DISPLAY=MOTIF
MAIL editing On VMS, you can use EVE as the editor in MAIL, VAX
BASIC, and Datatrieve. For more information, see help
on Mail Editing.
SPELL The SPELL command on VMS lets you modify your text by
spawning a subprocess in which you interact with the
VMS DECspell utility. When you exit DECspell, your
text is modified with the spelling corrections. SPELL
on ULTRIX does not modify your text, but simply
produces a list of any misspelled words in a second
window.
If you are accustomed to pressing CTRL/L to refresh (redraw) the screen,
you can redefine CTRL/L as REFRESH. By default, EVE defines CTRL/W as
REFRESH and defines CTRL/L as INSERT PAGE BREAK.
If you are accustomed to the vi editor, you may want to define the ESCAPE
key or CTRL/[ (left bracket) as DO to emulate vi. However, on VMS systems,
EVE does not let you define ESCAPE or CTRL/[.
By default, EVE defined CTRL/Z as EXIT (ending the editing session). You
may want to redefine CTRL/Z as SPAWN or as SHELL. On ULTRIX systems, EVE
also defines CTRL/D as exit.
For more information about EVE and TPU, see the EVE Reference Manual and
VSI Text Processing Utility Manual.
+----------------------------------------------------------------+
| You can create a section file on VMS and use it on ULTRIX (or |
| conversely). However some procedures and key definitions may |
| not work or may not work properly if they use system-specific |
| features or differences, such as file names and directories. |
+----------------------------------------------------------------+
Related topics:
Defaults Journal Files ULTRIX Differences