te
 @(#)what.1 1.18 20/08/05 Copyright 2007-2020 J. Schilling
 Copyright (c) 2002, Sun Microsystems, Inc. All Rights Reserved.
 Copyright 1989 AT&T
 Copyright 2007-2016 J. Schilling
 CDDL HEADER START

 The contents of this file are subject to the terms of the
 Common Development and Distribution License ("CDDL"), version 1.0.
 You may use this file only in accordance with the terms of version
 1.0 of the CDDL.

 A full copy of the text of the CDDL should have accompanied this
 source. A copy of the CDDL is also available via the Internet at
 http://www.opensource.org/licenses/cddl1.txt

 When distributing Covered Code, include this CDDL HEADER in each
 file and include the License file at usr/src/OPENSOLARIS.LICENSE.
 If applicable, add the following below this CDDL HEADER, with the
 fields enclosed by brackets "[]" replaced with your own identifying
 information: Portions Copyright [yyyy] [name of copyright owner]

 CDDL HEADER END
 what 1 "2020/08/05" "SunOS 5.11" "User Commands"
 NAME
what - extract SCCS version information from a file

 SYNOPSIS


 what \c  [ -s "] \c  filename... 



 DESCRIPTION



The
 what utility searches each
 filename for occurrences of the pattern
 @(#) that the
 SCCS get command (see 
 sccs-get (1)) substitutes for the
 %Z% ID keyword, and prints what follows up to a ",
 > ,  NEWLINE ,  \e , or
 NULL character.


 OPTIONS



The following option is supported:





 -s Stops after the first occurrence of the pattern.






 0
 -V 

 -version 

 --version 

Prints the
 what version number string and exists.
This option is a
 \s-1SCHILY\s+1 extension that does not exist in historic
 sccs implementations.


 EXAMPLES

 Example 1 Extracting SCCS version information



If a C program in file
 program.c contains




char sccsid[\|] = "\|@(#)identification information\|";





and
 program.c is compiled to yield
 program.o and
 a.out , the command:




example% \c
 what program.c program.o a.out 




produces:




 12n
 program.c : identification information





 program.o : identification information





 a.out : identification information


 ENVIRONMENT VARIABLES



See 
 environ (5) for descriptions of the following environment variables that affect the
execution of
 what : LANG, LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH.


 EXIT STATUS

The following exit values are returned:




 0 Any matches were found.




 1 No matches found.


 ATTRIBUTES



See 
 attributes (5) for descriptions of the following attributes:










ATTRIBUTE TYPEATTRIBUTE VALUE
AvailabilitySUNWsprot
Interface StabilityStandard



 SEE ALSO

 sccs (1),  sccs-add (1),  sccs-admin (1),  sccs-branch (1),  sccs-cdc (1),  sccs-check (1),  sccs-clean (1),  sccs-comb (1),  sccs-commit (1),  sccs-create (1),  sccs-cvt (1),  sccs-deledit (1),  sccs-delget (1),  sccs-delta (1),  sccs-diffs (1),  sccs-edit (1),  sccs-editor (1),  sccs-enter (1),  sccs-fix (1),  sccs-get (1),  sccs-help (1),  sccs-histfile (1),  sccs-info (1),  sccs-init (1),  sccs-istext (1),  sccs-ldiffs (1),  sccs-log (1),  sccs-print (1),  sccs-prs (1),  sccs-prt (1),  sccs-rcs2sccs (1),  sccs-remove (1),  sccs-rename (1),  sccs-rmdel (1),  sccs-root (1),  sccs-sact (1),  sccs-sccsdiff (1),  sccs-status (1),  sccs-tell (1),  sccs-unedit (1),  sccs-unget (1),  sccs-val (1),  sccschangeset (4),  sccsfile (4),  attributes (5),  environ (5),  standards (5). 

 DIAGNOSTICS



Use the SCCS
 help command for explanations (see 
 sccs-help (1)). 

 BUGS



There is a remote possibility that a spurious occurrence of the
 ` @(#) ' pattern could be found by
 what . 

 AUTHORS
The
 SCCS suite was originally written by Marc J. Rochkind at Bell Labs in 1972.
Release 4.0 of
 SCCS , introducing new versions of the programs
 admin (1),  get (1),  prt (1), and
 delta (1) was published on February 18, 1977; it introduced the new text based
 SCCS v4 history file format (previous
 SCCS releases used a binary history file format).
The
 SCCS suite
was later maintained by various people at AT&T and Sun Microsystems.
Since 2006, the
 SCCS suite is maintained by J\*org Schilling.




 "SOURCE DOWNLOAD"
A frequently updated source code for the
 SCCS suite is included in the
 schilytools project and may be retrieved from the
 schilytools project at Sourceforge at:


  http://sourceforge.net/projects/schilytools/


The download directory is:


  http://sourceforge.net/projects/schilytools/files/


Check for the
 schily-*.tar.bz2 archives.


Less frequently updated source code for the
 SCCS suite is at:


  http://sourceforge.net/projects/sccs/files/


Separate project informations for the
 SCCS project may be retrieved from:


  http://sccs.sf.net