Below is a list of some NOS/VE commands. It follows the convention of showing the allowable abbreviated version of the commands in uppercase: the first three characters of the command followed by the first character of each next command name part. Commands always started with a verb and the plural version of the command name was allowed when it made sense (e.g. ATTACH-FILES).
For instance, the short form of SET_Working_Catalog was SETWC. The commands and abbreviations were not case-sensitive.
Catalog and File Commands
Creates catalog (directory), like UNIX or MS-DOS mkdir.
Delete a catalog, like UNIX rmdir.
Displays names of files in a catalog, like UNIX ls.
Show filesystem-related attributes of file, such as time of last access, like UNIX ls -l.
Renames a file, like MS-DOS REN. The logic behind this weird name is that you aren’t changing the file, but rather the catalog containing the name of the file.
Assign permissions to catalog.
Are you getting it? What is the name of the command to remove the permit?
Assign permissions to a file.
Associates file with a name in $LOCAL (usually not needed), or accesses a file with specific permissions for later use. In some cases, the system would access a file with different permissions than you want.
Explicitly releases file or disassociates file from name in $LOCAL.
Set attributes of file, such as record size, default position ($BOI, $EOI), access type, start access log. Files had many more system-recognized attributes than in MS-DOS and UNIX, for instance.
Similar to SET_File_Attribute, but the change was not made permanent.
Show file attributes of a file, such as open status, access log and so on.
Associate a file with the terminal.
Create a file based from $INPUT. Depending on the source (batch or terminal) this took input from the command source until the end string (default “**”) was detected or from a usual terminal input stream.
Binary file compare; not very full-featured. There were CDC unsupported (say “public domain”) libraries with helpful SCL coded procedures that displayed the differences in ASCII format.
Dump file in various formats, like UNIX od. Not very good.
Obvious function. It had, however, a large number of options allowing only the restore of catalogs, selected catalog entries and so on. The input to RESPF could be a large file with descriptions with what to include, what to exclude and what and how to display a logging.
Job and Job Attributes Commands
Like MS-DOS or UNIX cd.
Sets list of libraries searched for commands, like MS-DOS PATH.
Shows list of libraries searched for commands, like MS-DOS PATH.
Change job limit, such as the number of CPU seconds allowed before job aborts.
Set various job settings, such as the list of libraries searched when looking for object files.
Displays various job settings.
Tells system about attributes of a terminal associated with this job.
Places message in job log or operator console.
Display the job log.
Pauses job, waiting for operation action.
Submit a file of commands as a batch job.
Send file to a printer.
Display status of a given job.
Display status of a given queued print file.
Magnetic Tape Commands
Assign a tape drive or other resource to the job. Only required when more than one tape unit at the same time was required. Otherwise, a scheduling conflict with another job might occur.
Return resource to the operating system; most often used with tape drives.
Couples magnetic tape information (VSN, tape density and write or read/only (RING)) to a local file name. When that file was accessed, the tape request flashed on the console and became visible in the Display_Operator_Status display.
Rewind tape or move the file pointer to the beginning of a file.
Skip to next tape mark on the tape.
Text editor; full-screen if you had a decent terminal. The terminal possibilities could be specified and converted to a special terminal library using the Terminal_Description_Utility (TDU). A personal terminal description was useful for having other colours and character sizes.
Maintain source code library. A newer version of the old UPDATE. Features included version control of different acceptance stages of software.
Create a library file, which contains SCL procedures, object files, maybe also executables (?).
Display of all the command parameters and the acceptable values of a command. This powerful informational command also worked for system SCL procedures and user procedures. The command was initiated, but short-stopped (a kind of breakpoint). This command always gave the appropriate list of parameters (on-line manuals were sometimes behind).
Display of all the function parameters and the acceptable values of command. Note that this also worked for system SCL functions and user functions.