SBCS : nunget manpage

Current Supported Releases: Sablime® v6.0 & v5.2


Updated Tuesday,30-Sep-03 14:28:07 EDT


NAME
     nunget - undo a previous nget on an SBCS file

SYNOPSIS
     nunget [-nsRNY] [-r sid] s-file ...

DESCRIPTION
     nunget undoes the effect of a previous nget -e  on  an  SBCS
     s-file before the file is returned with ndelta(1).

     A command line begins with option arguments  and  ends  with
     s-file  arguments.   s-file  arguments  can be any mix of s-
     files, directories and a single - character (see nadmin(1)).

     For each valid s-file, nunget removes  the  relevant  record
     from  the  p-file,  effectively cancelling the edit request.
     nunget also removes the gotten file unless the option -n  is
     used,  or  the g-file name begins with ..  In the first case
     the file is still writable, while in the second case  it  is
     made read-only.

OPTIONS
     -n   Do not remove the g-file.  Like with ndelta, the g-file
          is  normally  removed  after a successful nunget, and a
          new g-file requires another nget call.   With  -n,  the
          g-file  is  left behind, untouched.  This is a special-
          ized option since the g-file, its permissions and  key-
          words  in  the  wrong state, will eventually have to be
          removed.  Unlike ndelta, there  is  no  -G  option  for
          nunget  because,  in  general,  the  g-file  no  longer
          matches any s-file version.

     -s   Run silently. Suppress display of the ungotten SID.

     -N   No execution. nunget simply prints the  s-file  and  g-
          file pairs it would normally process, but no processing
          is done.  Useful to preview what nunget would  do  when
          s-file arguments represent many files.

     -R   Recursive mode.  For  all  s-file  arguments  that  are
          directories,  descend  recursively  into  all subdirec-
          tories to search for  s-files.   The  g-files  will  be
          removed   from   corresponding  subdirectories  of  the
          current directory (unless -n is specified, or the  file
          names begin with .).  The sbcsenv variable recursive [=
          no] can be reset to y to keep recursive mode on at  all
          times.

     -Y   Suppress any  y/n  prompt  that  may  arise  by  always
          answering  y.   Such prompts are not always predictable
          and can arise from requests to restore the s-file.  The
          sbcsenv variable answer_yes [= no] can be reset to y to

SBCS Release 1.2    Last change: 1 April 1994                   1

          imply the -Y option for all commands.  See NOTES on Y/N
          Prompts in nadmin(1) and below.

     -r sid
          Specify the gotten version to cancel.  This  option  is
          only needed if the user is editing more than one g-file
          from this s-file, because nunget looks  up  the  p-file
          information.   sid  can  be  a  complete  SID  (R.L  or
          R.L.B.S) or a version name.  The value  specified  must
          specify a unique record in the p-file.

NOTES
     Multiple Files
          nunget works effectively on  multiple  s-files  because
          most of the time the intended version can be determined
          from the p-file and need not be specified.

     Multi-User
          nunget modify the p-files.  When used in  a  multi-user
          project,  nunget  needs  to  run  set-UID with the SBCS
          administrator's permissions (see nadmin(1) - MULTI USER
          ACCESS and sbcsproj(1)).

     Code The nunget and nsact commands share the same code.

DIAGNOSTICS
     Warning and error messages have error codes that can be used
     with nhelp for a more detailed explanation.

SEE ALSO
     nadmin(1), ncdc(1), ndelta(1), nget(1),  nhelp(1),  nprs(1),
     nrmdel(1), nsact(1), nunget(1), sbcsenv(1).

SBCS Release 1.2    Last change: 1 April 1994                   2

Return to SBCS Commands manpage index


Sablime® HOME | Availability | Ordering | Download | Documentation | FAQ's | Support | Training | Newsletter


LUCENT TECHNOLOGIES Copyright © 2003 Lucent Technologies
All Rights Reserved.