Manpages - prs.1p

This manual page is part of the POSIX Programmer’s Manual. The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux.

prs — print an SCCS file (DEVELOPMENT)

  prs [-a] [-d dataspec] [-r[SID]] file...
  prs [-e|-l] -c cutoff [-d dataspec] file...
  prs [-e|-l] -r[SID] [-d dataspec] file...

The prs utility shall write to standard output parts or all of an SCCS file in a user-supplied format.

The prs utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines, except that the -r option has an optional option-argument. This optional option-argument cannot be presented as a separate argument. The following options shall be supported:

-d dataspec

Specify the output data specification. The dataspec shall be a string consisting of SCCS file data keywords (see Data Keywords) interspersed with optional user-supplied text.

-r[SID]

Specify the SCCS identification string (SID) of a delta for which information is desired. If no SID option-argument is specified, the SID of the most recently created delta shall be assumed.

-e

Request information for all deltas created earlier than and including the delta designated via the -r option or the date-time given by the -c option.

-l

Request information for all deltas created later than and including the delta designated via the -r option or the date-time given by the -c option.

-c cutoff

Indicate the cutoff date-time, in the form:

      YY[MM[DD[HH[MM[SS]]]]]

For the YY component, values in the range [69,99] shall refer to years 1969 to 1999 inclusive, and values in the range [00,68] shall refer to years 2000 to 2068 inclusive.

Note:

It is expected that in a future version of this standard the default century inferred from a 2-digit year will change. (This would apply to all commands accepting a 2-digit year as input.)

No changes (deltas) to the SCCS file that were created after the specified cutoff date-time shall be included in the output. Units omitted from the date-time default to their maximum possible values; for example, -c 7502 is equivalent to -c 750228235959.

-a

Request writing of information for both removed—that is, delta type/= /R (see /rmdel )— and existing—that is, /delta type/= /D,— deltas. If the -a option is not specified, information for existing deltas only shall be provided.

The following operand shall be supported:

file

A pathname of an existing SCCS file or a directory. If file is a directory, the prs utility shall behave as though each file in the directory were specified as a named file, except that non-SCCS files (last component of the pathname does not begin with s.) and unreadable files shall be silently ignored.

If exactly one file operand appears, and it is ’-’, the standard input shall be read; each line of the standard input shall be taken to be the name of an SCCS file to be processed. Non-SCCS files and unreadable files shall be silently ignored.

The standard input shall be a text file used only when the file operand is specified as ’-’. Each line of the text file shall be interpreted as an SCCS pathname.

Any SCCS files displayed are files of an unspecified format.

The following environment variables shall affect the execution of prs:

LANG

Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of POSIX.1‐2017, Section 8.2, Internationalization Variables the precedence of internationalization variables used to determine the values of locale categories.)

LC_ALL

If set to a non-empty string value, override the values of all the other internationalization variables.

LC_CTYPE

Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments and input files).

LC_MESSAGES

Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.

NLSPATH

Determine the location of message catalogs for the processing of LC_MESSAGES.

Default.

The standard output shall be a text file whose format is dependent on the data keywords specified with the -d option.

The standard error shall be used only for diagnostic messages.

None.

None.

The following exit values shall be returned:

 0

Successful completion.

>0

An error occurred.

Default.

The following sections are informative.

None.

1.

The following example:

      prs -d "User Names for :F: are:\n:UN:" s.file

might write to standard output:

      User Names for s.file are:
      xyz
      131
      abc

2.

The following example:

      prs -d "Delta for pgm :M:: :I: - :D: By :P:" -r s.file

might write to standard output:

      Delta for pgm main.c: 3.7 - 77/12/01 By cas

3.

As a special case:

      prs s.file

might write to standard output:

      s.file:
      <blank line>
      D 1.1 77/12/01 00:00:00 cas 1 000000/00000/00000
      MRs:
      bl78-12345
      bl79-54321
      COMMENTS:
      this is the comment line for s.file initial delta
      <blank line>

for each delta table entry of the D type. The only option allowed to be used with this special case is the -a option.

None.

None.

/admin , //delta , //get , //what /

The Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables, Section 12.2, Utility Syntax Guidelines

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology – Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .