DELTA(1)			 HP-UX 5.0		      DELTA(1)

     NAME
	  delta - make a delta (change) to an SCCS file

     SYNOPSIS
	  delta files

     HP-UX COMPATIBILITY
	  Level:    HP-UX/STANDARD

	  Origin:   System III

     DESCRIPTION
	  Delta is used to permanently introduce into the named	  file
	  changes  that	 were  made  to	 the  file retrieved by get(1)
	  (called the g-file, or generated file).

	  Delta makes a delta to each named  file.  If a directory  is
	  named,  delta	 behaves  as though each file in the directory
	  were specified as a named file, except that non- files (last
	  component  of	 the  path  name  does	not begin with s.) and
	  unreadable files are silently ignored.  If a name  of	 -  is
	  given,  the  standard input is read (see ); each line of the
	  standard input is taken to be the name of  an	  file	to  be
	  processed.

	  Delta may issue prompts on  the  standard  output  depending
	  upon	certain	 keyletters specified and flags (see admin(1))
	  that may be present in the  file (see -m and	-y  keyletters
	  below).

	  Keyletter arguments apply independently to each named	 file.
	  identifies  which delta is to be made to the	file.  The use
	  of  this  keyletter  is  necessary  only  if	two  or	  more
	  outstanding gets for editing (get -e) on the same  file were
	  done by the same person (login name).	 The  value  specified
	  with	the  -r	 keyletter can be either the  specified on the
	  get command line or the  to be made as reported by  the  get
	  command (see get(1)).	 A diagnostic results if the specified
	  is ambiguous, or, if necessary and omitted  on  the  command
	  line.	  the  issue,  on  the standard output, of the created
	  delta's , as well as the number of lines  inserted,  deleted
	  and unchanged in the
	   file.  g-file (normally  removed  at	 completion  of	 delta
	  processing).	a list (see get(1) for the definition of list)
	  of deltas which are to be ignored when the file is  accessed
	  at the change level () created by this delta.	 the  file has
	  the v flag set (see admin(1)) then a Modification Request ()
	  number  must	be supplied as the reason for creating the new
	  delta.  -m is not used and the standard input is a terminal,
	  the  prompt MRs? is issued on the standard output before the
	  standard input is read; if  the  standard  input  is	not  a
	  terminal,  no	 prompt	 is  issued.   The  MRs? prompt always
	  precedes the comments? prompt (see -y keyletter).

	  in a list are separated by blanks and/or tab characters.  An
	  unescaped  new-line character terminates the	list.  that if
	  the v flag has a value (see admin(1)), it is taken to be the
	  name	of  a program (or shell procedure) which will validate
	  the correctness of the  numbers.  If a non-zero exit	status
	  is   returned	  from	  number   validation  program,	 delta
	  terminates (it is assumed that the   numbers	were  not  all
	  valid).   text  used	to  describe the reason for making the
	  delta.  A null string is considered a valid comment.	-y  is
	  not  specified  and  the  standard  input is a terminal, the
	  prompt comments? is issued on the standard output before the
	  standard  input  is  read;  if  the  standard input is not a
	  terminal,  no	 prompt	 is  issued.   An  unescaped  new-line
	  character  terminates	 the comment text.  delta to print (on
	  the standard output) the  file differences before and	 after
	  the delta is applied in a diff(1) format.

     FILES
	  All files of the form ?-file are  explained  in  the	Source
	  Code Control System User's Guide.  The naming convention for
	  these files is also described there.	All files below except
	  the  g-file are created in the same directory as the s-file.
	  The g-file is created in the user's working directory.

	  g-file	   Existed  before  the	 execution  of	delta;
			   removed  after  completion of delta (unless
			   -n was specified).
	  p-file	   Existed before the execution of delta;  may
			   exist after completion of delta.
	  q-file	   Created  during  the	 execution  of	delta;
			   removed after completion of delta.
	  x-file	   Created  during  the	 execution  of	delta;
			   renamed to  file after completion of delta.
	  z-file	   Created  during  the	 execution  of	delta;
			   removed during the execution of delta.
	  d-file	   Created  during  the	 execution  of	delta;
			   removed after completion of delta.
	  /usr/bin/bdiff   Program to compute differences between  the
			   ``gotten'' file and the g-file.
     DIAGNOSTICS
	  Use help(1) for explanations.
     WARNINGS
	  Lines beginning with an  SOH	ASCII  character  (octal  001)
	  cannot  be  placed  in  the  file unless the SOH is escaped.
	  This character has special meaning to (see sccsfile(5))  and
	  will cause an error.
	  A get of many	 files, followed by a delta  of	 those	files,
	  should  be  avoided when the get generates a large amount of
	  data.	 Instead, multiple get/delta sequences should be used.
	  If the standard input (-) is specified on the delta  command
	  line,	 the  -m (if necessary) and -y keyletters must also be
	  present.  Omission of these keyletters causes	 an  error  to
	  occur.
	  Comments  are	 limited  to  text  strings  of	 at  most  512
	  characters.
     SEE ALSO
	  admin(1),  bdiff(1),	cdc(1),	  get(1),   help(1),   prs(1),
	  rmdel(1), sccsfile(4).

	  SCCS User's Guide in HP-UX Concepts and Tutorials.