Command-Line and Configuration File Remote Name Notation

Most files that can be named on the command line or defined in the runtime configuration file can be specified with remote name notation. There are two general exceptions to this:

  1. If you are redirecting standard input or standard output to a file, the file cannot have remote name notation.
  2. If you are using an indexed file system other than Vision, those indexed files cannot have remote name notation.

Files that can have remote name notation include the following:

configuration files (-c runtime option)
error files (-e runtime option)
object file libraries (-y runtime option)
object files     (specified on runtime command line or DEFAULT_PROGRAM configuration variable or CODE_PREFIX configuration variable)
hot-key programs (HOT_KEY configuration variable)
data files (FILE_PREFIX configuration variable or name aliases in the configuration file or specified in the program)
log files (LOG_FILE and filename_LOG configuration variables)
log directory (LOG_DIR configuration variable)
xfd directory (XFD_DIRECTORY configuration variable)

Note that AcuServer may not be used for sort files with the SORT_DIR configuration variable.

Files that cannot have remote name notation include:

keyboard input file     (-I runtime option)
keystroke playback file (-k runtime option)
display output file (-o runtime option)
debug input file (-r runtime option)

Below is an example of a runtime command line that uses remote name notation to specify some of its runtime files:

runcbl -c @host1:/usr1/config/cblconfig
     -e @host2:/usr2/errors/err.out

The following are example definitions for runtime configuration variables that can have remote name notation.

CODE_PREFIX @host3:/usr3/objects
DEFAULT_PROGRAM @host3:/usr3/objects/sample.obj
FILE_PREFIX @host3:/usr3/data
HOT_KEY "@host3:/usr3/objects/sample.obj"=100,200
LOG_DIR @host3:/usr3/log
LOG_FILE @host3:/usr3/log/log.out
XFD_DIRECTORY @host3:/usr3/dictionaries