GETRSX(1)           UNIX Programmer's Manual            GETRSX(1)



NAME
     getrsx, lsrsx - deal with RSX-11 filesystems

SYNOPSIS
     getrsx [options] rsxfile [rsxfile2,...]
     lsrsx rsxdir

DESCRIPTION
     G_e_t_r_s_x_ retrieves one or more files from an RSX-11 (ODS1)
     filesystem.  Files may be copied to disk or to standard out-
     put.  Transfer modes supported are "text" (FCS stuff is
     thrown away, newline is tacked on the end of each RSX
     record), and "image" (straight byte-by-byte transfer).
     Default output destination is disk, default transfer mode is
     "text".  These defaults may be overridden (see below).

     The input device and UFD, if omitted, will default to that
     of the previous filespec.  Note that this means that the
     first filespec m_u_s_t_ have a device and UFD specified.  The
     filename syntax is the same as the standard RSX naming
     scheme (dev:[g,m]file.ext;ver), except that a `.' may be
     used to separate the filetype from the version number.
     (This is to avoid having to escape the `;', which the shell
     treats as a command separator.) The device is the name of
     the UNIX special file in /dev, rather than what RSX thinks
     it would be.

     L_s_r_s_x_ lists the contents of an RSX-11 user file directory.
     At present, l_s_r_s_x_ exits after listing a directory, so only
     one UFD may be listed per command.

     Options:

     -d   Copy output to disk file (name is the same as the RSX
          filename)

     -f   Same as -d

     -s   Copy output to standard output

     -t   Set transfer mode to "text"

     -i   Set transfer mode to "image"

     -b   Set transfer mode to "binary" (not implemented)

     -l   List contents of UFD ("getrsx -l foo" is equivalent to
          "lsrsx foo")

     -c   Undo effect of -l (useless option at present)





Printed 6/15/82                HEP                              1






GETRSX(1)           UNIX Programmer's Manual            GETRSX(1)



     An option applies to all files which follow it, until over-
     ridden by yet another option specification.

     If the version number is omitted from a filespec, the ver-
     sion with the highest version number is copied.

     Examples:
          getrsx  rx0l:[300,320]foo.bar  [300,322]mumble.qyx
          getrsx  -i  rx0h:[100,200]data.dat.3  -t  whatzit.txt
          getrsx  -s  rx1l:[1,2]startup.com
          lsrsx  rx1h:[200,200]

FILES
     /dev/??        Special file for reading RSX filesystem

BUGS
     Probably.  Hasn't been extensively tested.

     No support for multi-header files.

     Should probably look at the file and record attributes, and
     do something sensible based on what they are, rather than
     use ``text'' mode as a default.

     It is possible (though extremely unlikely) that there could
     be problems if a file with a weird name exists in the
     current working directory, due to the way the shell deals
     with square brackets.  For example,
     getrsx rk0:[1,2]login.com would cause something to be passed
     to g_e_t_r_s_x_ different from what was intended if one or more of
     the UNIX files rk0:1login.com, rk0:,login.com, or
     rk0:2login.com existed.  You can always protect against this
     by escaping the `[', or by enclosing the entire argument in
     quotes.  Of course, it's not likely that files with names
     sufficiently weird to cause problems will actually exist, so
     the problem probably isn't worth worrying about.

HEP INFO
     Written by Mark Bartelt.  Inspired by an earlier program by
     Rob Pike.















Printed 6/15/82                HEP                              2