Examples

   1.$ RUN LIBRA

     The image LIBRA.EXE starts executing in the process. If the
     image LIBRA has been installed with amplified privileges, it
     runs with those privileges because you have not explicitly
     specified a version number or a semicolon. Alternatively, the
     image LIBRA.EXE still runs with its amplified privileges, if
     you enter the RUN command as follows:

       $ RUN LIBRA.EXE

   2.$ MACRO/ENABLE=DEBUG ORION
     $ LINK/DEBUG ORION
     $ RUN ORION

      OpenVMS I64 DEBUG64 Version V8.3-014

     %DEBUG-I-INITIAL, Language:IMACRO, Module:ORION
     DBG>
        .
        .
        .
     $ RUN/NODEBUG ORION

     A program is compiled, linked, and run with the debugger.
     Subsequently, a RUN/NODEBUG command requests that the debugger,
     which is present in the image, not issue a prompt. If an error
     occurs while the image executes, the debugger can perform
     traceback and report on the error.

   3.$ RUN AQUARIUS.EXE;1

     The image AQUARIUS.EXE starts executing in the process. If
     the image AQUARIUS.EXE has been installed with amplified
     privileges, it does not run with those privileges because you
     have specified a version number. Instead, the image runs with
     current process privileges only. When you specify a version
     number (or even just a semicolon), the image activator does not
     search its list of special images that have been installed with
     privileges. The process AQUARIUS still runs with only normal
     process privileges if you enter the RUN command as follows:

       $ RUN AQUARIUS.EXE;

     In this case, however, the highest version of the image
     AQUARIUS runs.