Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ get(1) — Reliant UNIX 5.44c4

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

admin(1)

bdiff(1)

delta(1)

help(1)

prs(1)

what(1)

get(1)                                                               get(1)

NAME
     get - get a version of an SCCS file

SYNOPSIS
     get [option...] file...

DESCRIPTION
     get generates an ASCII text file from each named SCCS file according
     to the specifications given by its keyletter arguments. The options
     may be specified in any order, but all keyletter arguments apply to
     all named SCCS files. If a directory is named, get behaves as though
     each file in the directory were specified as a named file, except that
     non-SCCS files (i.e. those for which the filename does not begin with
     s., ignoring the path name) and unreadable files; these files are
     ignored without comment. If a name of - is given, the standard input
     is read; each line of the standard input is taken to be the name of an
     SCCS file to be processed.

     The generated text is normally written into a file called the g-file
     whose name is derived from the SCCS filename by simply removing the
     leading s. (see the FILES section).

OPTIONS
     Each of the keyletters is explained below as though only one SCCS file
     is to be processed, but the effects of any keyletter apply to each
     named file.

     -r SID
          The SCCS identification string (SID) of the version (delta) of an
          SCCS file to be retrieved.

          The table below shows what version of an SCCS file is retrieved,
          as a function of the SID specified.

     -c cutoff
          Cutoff point (date/time) after which changes are to be ignored,
          in the form:

              YY[MM[TT[HH[MM[SS]]]]]

          No changes (deltas) to the SCCS file that were created after the
          specified cutoff date-time are included in the generated ASCII
          text file. Parts of the cutoff which are not specified default to
          their maximum possible values; that is, -c 7502 is equivalent to
          -c 750228235959. Any number of non-numeric characters may
          separate the two-digit parts of the cutoff date-time. This
          feature allows one to specify a cutoff date in the following
          form: -c "77/2/2 9:22:25".







Page 1                       Reliant UNIX 5.44                Printed 11/98

get(1)                                                               get(1)

     -i list
          A list of deltas to be included (forced to be applied) in the
          creation of the generated file. The list has the following syn-
          tax:

              <list> ::= <range> | <list> , <range>
              <range> ::= SID | SID - SID

          SID, the SCCS Identification of a delta, may be in any form shown
          in the "SID Specified" column of the table.

     -x list
          A list of deltas to be excluded in the creation of the generated
          file. The format of the list is as for -i.

     -e   Indicates that the get is for the purpose of editing or making a
          change (delta) to the SCCS file via a subsequent use of delta(1).
          The -e keyletter used in a get for a particular version (SID) of
          the SCCS file prevents further calls of get for editing on the
          same SID until delta is executed or the j (joint edit) flag is
          set in the SCCS file [see admin(1)]. Concurrent use of get -e for
          different SIDs is always allowed.

          SCCS file protection specified via the ceiling, floor, and
          authorized user list stored in the SCCS file [see admin(1)] are
          enforced when the -e keyletter is used.

     -b   Used together with the -e keyletter to indicate that the new
          delta should have a SID in a new branch as shown in the table.
          This keyletter is ignored if the b flag is not set in the file
          [see admin(1)] or if the retrieved delta is not a leaf delta (a
          leaf delta is one that has no successors on the SCCS file tree).
          A branch delta may always be created from a non-leaf delta. Par-
          tial SIDs are interpreted as shown in the "SID Retrieved" column
          in the table below.

     -k   Suppresses replacement of keywords in the retrieved text by their
          value. The -k keyletter is implied by the -e keyletter.

     -l   Causes a delta summary to be written into an l-file. The format
          of the l-file will be found in the section on Keywords.

     -L   The delta summary is written to the standard output. Additional
          information that is normally written to the standard output is
          written to the standard error output in this case.

          This corresponds to the old option -lp, which will continue to be
          supported.

     -p   The text retrieved from the SCCS file is written on the standard
          output. No g-file is created. All output that normally goes to
          the standard output goes to the standard error output instead,


Page 2                       Reliant UNIX 5.44                Printed 11/98

get(1)                                                               get(1)

          unless the -s keyletter is used. In the latter case these outputs
          will disappear.

     -s   Suppresses all output normally written on the standard output.
          However, fatal error messages, which always go to the standard
          error output, remain unaffected.

     -m   Each text line retrieved from the SCCS file is preceded by the
          SID of the delta that inserted the text line in the SCCS file.
          The format is: SID, followed by a horizontal tab, followed by the
          text line.

     -n   Each generated text line is preceded by the %M% keyword value.
          The format is: %M% value, followed by a horizontal tab, followed
          by the text line. When both the -m and -n keyletters are used,
          the format is: %M% value, followed by a horizontal tab, followed
          by the -m keyletter generated format.

     -g   Suppresses the actual retrieval of text from the SCCS file. It is
          primarily used to generate an l-file, or to verify the existence
          of a particular SID.

     -t   Used to access the most recently created delta in a given release
          (e.g., -r 1), or release and level (e.g., -r 1.2).

     -w string
          Substitute string for all occurrences of %W% when getting the
          file. Substitution occurs prior to keyword expansion.

     -a seq-no.
          The delta sequence number of the SCCS file delta (version) to be
          retrieved. This keyletter is used by the comb command. If both
          the -r and -a keyletters are specified, only the -a keyletter is
          used. Care should be taken when using the -a keyletter in con-
          junction with the -e keyletter, as the SID of the delta to be
          created may not be what one expects. The -r keyletter can be used
          with the -a and -e keyletters to control the naming of the SID of
          the delta to be created.

     --   If the first filename begins with a dash (-), the end of the
          command-line options must be marked with --.

     For each file processed, get responds (on the standard output) with
     the SID being accessed and with the number of lines retrieved from the
     SCCS file.

     If the -e keyletter is used, the SID of the delta to be made appears
     after the SID accessed and before the number of lines generated. If
     there is more than one named file or if a directory or standard input
     is named, each filename is printed, preceded by a new-line, before it
     is processed. If the -i keyletter is used, included deltas are listed
     following the notation Included; if the -x keyletter is used, excluded


Page 3                       Reliant UNIX 5.44                Printed 11/98

get(1)                                                               get(1)

     deltas are listed following the notation Excluded.





















































Page 4                       Reliant UNIX 5.44                Printed 11/98

get(1)                                                               get(1)

     ______________________________________________________________________
    |SID         |-b keyletter |other conditions |SID      |SID of delta  |
    |specified 1)|used 5)      |                 |retrieved|to be created |
    |____________|_____________|_________________|_________|______________|
    |none 6)     |no           |R default to mR  |mF.mL    |mR.(mL+l)     |
    |            |             |                 |         |              |
    |none 6)     |yes          |R default to mR  |mF.mL    |mR.mL.(mB+1).1|
    |            |             |                 |         |              |
    |R           |no           |R > mR           |mR.mL    |R.1 3)        |
    |            |             |                 |         |              |
    |R           |no           |R = mR           |mR.mL    |mR.(mL+1)     |
    |            |             |                 |         |              |
    |R           |yes          |R > mR           |mR.mL    |mR.mL.(mB+1).1|
    |            |             |                 |         |              |
    |R           |yes          |R = mR           |mR.mL    |mR.mL.(mB+1).1|
    |            |             |                 |         |              |
    |R           |-            |R < mR and R     |hR.mL 2) |hR.mL.(mB+1).1|
    |            |             |does not exist   |         |              |
    |            |             |                 |         |              |
    |R           |-            |Trunk succ. 4)   |R.mL     |R.mL.(mB+1).1 |
    |            |             |in release > R   |         |              |
    |            |             |and R does       |         |              |
    |            |             |not exist        |         |              |
    |            |             |                 |         |              |
    |R.L         |no           |No trunk succ.   |R.L      |R.(L+1)       |
    |            |             |                 |         |              |
    |R.L         |yes          |No trunk succ.   |R.L      |R.L.(mB+1).1  |
    |            |             |                 |         |              |
    |R.L         |-            |Trunk succ. in   |R.L      |R.L(mB+1).1   |
    |            |             |release = R      |         |              |
    |            |             |                 |         |              |
    |R.L.B       |no           |No branch succ.  |R.L.B.mS |R.L.B.(mS+1)  |
    |            |             |                 |         |              |
    |R.L.B       |yes          |No branch succ.  |R.L.B.mS |R.L.(mB+1).1  |
    |            |             |                 |         |              |
    |R.L.B.S     |no           |No branch succ.  |R.L.B.S  |R.L.B.(S+1)   |
    |            |             |                 |         |              |
    |R.L.B.S     |yes          |No branch succ.  |R.L.B.S  |R.L.(mB+1).1  |
    |            |             |                 |         |              |
    |R.L.B.S     |-            |Branch succ.     |R.L.B.S  |R.L.(mB+1).1  |
    |____________|_____________|_________________|_________|______________|













Page 5                       Reliant UNIX 5.44                Printed 11/98

get(1)                                                               get(1)

     1)  R, L, B, or S are the release (version), level, branch and
         sequence components of the SID, respectively; m means maximum.
         Thus for example, R.mL means the maximum level number within
         release R; R.L.(mB+1).1 means the first sequence number on the new
         branch (i.e., maximum branch number plus one) of level L within
         release R. Note that if the SID specified is of the form R.L,
         R.L.B, or R.L.B.S, each of the specified components must exist.

     2)  hR is the highest existing release that is lower than the speci-
         fied, nonexistent, release R.

     3)  This is used to force creation of the first delta in a new
         release.

     4)  Successor.

     5)  The -b keyletter is effective only if the b flag [see admin(1)] is
         present in the file. An entry of - means "irrelevant".

     6)  This case applies if the d (default SID) flag is not present in
         the file. If the d flag is present in the file, then the SID
         obtained from the d flag is interpreted as if it had been speci-
         fied on the command line. Thus, one of the other cases in this
         table applies.






























Page 6                       Reliant UNIX 5.44                Printed 11/98

get(1)                                                               get(1)

   Keywords

     Identifying information is inserted into the text retrieved from the
     SCCS file by replacing identification keywords with their value wher-
     ever they occur. If the keyletters -b or -k are used, the keywords in
     the text are not expanded. The following keywords may be used in the
     text stored in an SCCS file:

     %M%  Module name: either the value of the m flag in the file [see
          admin(1)], or if absent, the name of the SCCS file with the lead-
          ing s removed.

     %I%  SCCS identification (SID) (%R%.%L%.%B%.%S%) of the retrieved
          text.

     %R%  Release

     %L%  Level

     %B%  Branch

     %S%  Sequence

     %D%  Current date (YY/MM/DD)

     %H%  Current date (MM/DD/YY)

     %T%  Current time (HH:MM:SS)

     %E%  Date newest applied delta was applied (YY/MM/DD)

     %G%  Date newest applied delta was applied (MM/DD/YY)

     %U%  Time newest applied delta was created (HH:MM:SS)

     %Y%  Module type: value of the t flag in the SCCS file [see admin(1)]

     %F%  SCCS filename

     %P%  Full pathname of the SCCS file

     %Q%  The value of the q flag in the file [see admin(1)]

     %C%  Current line number

     %Z%  The four-character string @(#) recognizable by the what command

     %W%  A shorthand notation for constructing what strings for Reliant
          UNIX System program files: %W% = %Z%%M%<Horizontal-Tab>%I%

     %A%  Another shorthand notation for constructing what strings for non
          Reliant UNIX System program files: %A% = %Z%%Y% %M% %I%%Z%


Page 7                       Reliant UNIX 5.44                Printed 11/98

get(1)                                                               get(1)

     Several auxiliary files may be created by get. These files are called
     the g-file, l-file, p-file, and z-file. The letter before the hyphen
     is called the tag. An auxiliary filename is formed from the SCCS
     filename: the filename must be of the form s.modulename, the auxiliary
     files are named by replacing the leading s with the tag.

     The g-file is an exception to this scheme: the name of the g-file is
     formed by removing the s. prefix. For example, for s.xyz.c the auxili-
     ary filenames would be xyz.c, l.xyz.c, p.xyz.c, and z.xyz.c, respec-
     tively.

     The g-file, which contains the generated text, is created in the
     current directory, unless the -p keyletter is used. A g-file is
     created in all cases, whether or not any lines of text were generated
     by the get. It is owned by the real user. If the -k keyletter is used
     or implied, its mode is 644; otherwise its mode is 444 (provided the
     permissions have not been restricted by umask). Only the real user
     need have write permission in the current directory.

     The l-file contains a list of the deltas applied in generating the
     retrieved text. The l-file is created in the current directory if the
     -l keyletter is used; its mode is 444 (provided the permissions have
     not been restricted by umask) and it is owned by the real user. Only
     the real user need have write permission in the current directory.

     Lines in the l-file have the following format:

          <a><b><c> <SID><TAB><date time> <login>

     Whereby:

     a   A blank character if the delta was applied; * otherwise.

     b   A blank character if the delta was applied or was not applied and
         ignored; * if the delta was not applied and was not ignored.

     c   A code indicating a "special" reason why the delta was or was not
         applied: "I" included), "X" (excluded), or "C" (cut off by a -c
         keyletter).

     SID SCCS identification (SID).

     date time
         Date and time (in the form YY/MM/DD HH:MM:SS) of creation.

     login
         Login name of person who created delta.







Page 8                       Reliant UNIX 5.44                Printed 11/98

get(1)                                                               get(1)

     The comments and MR data follow on subsequent lines, indented one hor-
     izontal tab character. A blank line terminates each entry.

     The p-file is used to pass information resulting from a get with an e
     keyletter along to delta. Its contents are also used to prevent a sub-
     sequent execution of get with an -e keyletter for the same SID until
     delta is executed or the joint edit flag, j, [see admin(1)] is set in
     the SCCS file. The p-file is created in the directory containing the
     SCCS file and the effective user must have write permission in that
     directory. Its mode is 644 and it is owned by the effective user. Any
     line in the p-file has the following format:

          SID newSID login date/timeofget [argumentfor-i]
          [argumentfor-x]\n

     There can be an arbitrary number of lines in the p-file at any time;
     no two lines can have the same new delta SID.

     The z-file serves as a lock-out mechanism against simultaneous
     updates. Its contents are the binary (2 bytes) process ID of the com-
     mand (i.e., get) that created it. The z-file is created in the direc-
     tory containing the SCCS file for the duration of get. The same pro-
     tection restrictions as those for the p-file apply for the z-file. The
     z-file is created with mode 444.

NOTES
     If the effective user has write permission in the directory containing
     the SCCS files, but the real user does not, then only one file may be
     named when the -e keyletter is used.

























Page 9                       Reliant UNIX 5.44                Printed 11/98

get(1)                                                               get(1)

LOCALE
     The language of the message texts is governed by the environment vari-
     able LCALL, LCMESSAGES or LANG.

     When the default is set, the system behaves as if it were not interna-
     tionalized, i.e. the message texts are in English. You must change one
     of these variables in order to change the language of the message
     texts.

     Detailed information on the dependencies of the environment variables
     and on internationalization in general can be found in the manual
     "Programmer's Guide: Internationalization - Localization". Refer also
     to environ(5) for information on setting the user environment.

FILES
     s file: prefix: s. (e.g. s.xyz.c)
          Contains the current information stored in SCCS on the contents
          and history of a module

          Is created by admin -n, and never deleted. The directory contain-
          ing the s file is identified as an administration directory
          below.

     g file: prefix: none (e.g. xyz.c)
          Contains an expression of the module stored in the s file, i.e.
          the current status of a source file.

          Is created in the local directory by get and deleted by unget or
          delta (exception: if the -n switch is used for unget or delta,
          the g file is retained).

     p file: prefix: p. (e.g. p.xyz.c)
          Contains information on current processing of the module (who is
          processing which SID). Prevents parallel access to the same SID
          of the same module.

          Is created in the administration directory by get -e and deleted
          by unget or delta.

     l file: prefix: l. (e.g. l.xyz.c)
          Contains information in table format as to which deltas were used
          for creating a g file.

          Is created in the local directory by get -l (in addition to the
          g-file).

     z file: prefix: z. (e.g. z.xyz.c)
          Temporary lock file, prevents simultaneous write access to the
          files in the administration directory.

          Is created by all write SCCS commands (get -e, unget, delta,
          admin) and deleted after access is terminated, and is stored in


Page 10                      Reliant UNIX 5.44                Printed 11/98

get(1)                                                               get(1)

          the administration directory.

     x file: prefix: x. (e.g. x.xyz.c)
          Temporary file, created as a copy of the s file in the adminis-
          tration directory. Changes to the s file are made in this tem-
          porary copy. This copy is then renamed as the s file after the
          action has been performed successfully. This prevents the s file
          from being destroyed in the event of an error during write
          access.

          Is also used by admin or delta.

SEE ALSO
     admin(1), bdiff(1), delta(1), help(1), prs(1), what(1).








































Page 11                      Reliant UNIX 5.44                Printed 11/98

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026