logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

get.1p (20899B)


  1. '\" et
  2. .TH GET "1P" 2017 "IEEE/The Open Group" "POSIX Programmer's Manual"
  3. .\"
  4. .SH PROLOG
  5. This manual page is part of the POSIX Programmer's Manual.
  6. The Linux implementation of this interface may differ (consult
  7. the corresponding Linux manual page for details of Linux behavior),
  8. or the interface may not be implemented on Linux.
  9. .\"
  10. .SH NAME
  11. get
  12. \(em get a version of an SCCS file (\fBDEVELOPMENT\fP)
  13. .SH SYNOPSIS
  14. .LP
  15. .nf
  16. get \fB[\fR-begkmnlLpst\fB] [\fR-c \fIcutoff\fB] [\fR-i \fIlist\fB] [\fR-r \fISID\fB] [\fR-x \fIlist\fB] \fIfile\fR...
  17. .fi
  18. .SH DESCRIPTION
  19. The
  20. .IR get
  21. utility shall generate a text file from each named SCCS
  22. .IR file
  23. according to the specifications given by its options.
  24. .P
  25. The generated text shall normally be written into a file called the
  26. .BR g-file
  27. whose name is derived from the SCCS filename by simply removing the
  28. leading
  29. .BR \(dqs.\(dq .
  30. .SH OPTIONS
  31. The
  32. .IR get
  33. utility shall conform to the Base Definitions volume of POSIX.1\(hy2017,
  34. .IR "Section 12.2" ", " "Utility Syntax Guidelines".
  35. .P
  36. The following options shall be supported:
  37. .IP "\fB\-r\ \fISID\fR" 10
  38. Indicate the SCCS Identification String (SID) of the version (delta)
  39. of an SCCS file to be retrieved. The table shows, for the most useful
  40. cases, what version of an SCCS file is retrieved (as well as the SID of
  41. the version to be eventually created by
  42. .IR delta
  43. if the
  44. .BR \-e
  45. option is also used), as a function of the SID specified.
  46. .IP "\fB\-c\ \fIcutoff\fR" 10
  47. Indicate the
  48. .IR cutoff
  49. date-time, in the form:
  50. .RS 10
  51. .sp
  52. .RS 4
  53. .nf
  54. \fIYY\fB[\fIMM\fB[\fIDD\fB[\fIHH\fB[\fIMM\fB[\fISS\fB]]]]]\fR
  55. .fi
  56. .P
  57. .RE
  58. .P
  59. For the
  60. .IR YY
  61. component, values in the range [69,99] shall refer to years 1969 to
  62. 1999 inclusive, and values in the range [00,68] shall refer to years
  63. 2000 to 2068 inclusive.
  64. .TP 10
  65. .BR Note:
  66. It is expected that in a future version of this standard the default
  67. century inferred from a 2-digit year will change. (This would apply
  68. to all commands accepting a 2-digit year as input.)
  69. .P
  70. .P
  71. No changes (deltas) to the SCCS file that were created after the
  72. specified
  73. .IR cutoff
  74. date-time shall be included in the generated text file. Units omitted
  75. from the date-time default to their maximum possible values; for
  76. example,
  77. .BR \-c
  78. 7502 is equivalent to
  79. .BR \-c
  80. 750228235959.
  81. .P
  82. Any number of non-numeric characters may separate the various 2-digit
  83. pieces of the
  84. .IR cutoff
  85. date-time. This feature allows the user to specify a
  86. .IR cutoff
  87. date in the form:
  88. .BR \-c
  89. "77/2/2\09:22:25".
  90. .RE
  91. .IP "\fB\-e\fR" 10
  92. Indicate that the
  93. .IR get
  94. is for the purpose of editing or making a change (delta) to the SCCS
  95. file via a subsequent use of
  96. .IR delta .
  97. The
  98. .BR \-e
  99. option used in a
  100. .IR get
  101. for a particular version (SID) of the SCCS file shall prevent further
  102. .IR get
  103. commands from editing on the same SID until
  104. .IR delta
  105. is executed or the
  106. .BR j
  107. (joint edit) flag is set in the SCCS file. Concurrent use of
  108. .IR get
  109. .BR \-e
  110. for different SIDs is always allowed.
  111. .RS 10
  112. .P
  113. If the
  114. .BR g-file
  115. generated by
  116. .IR get
  117. with a
  118. .BR \-e
  119. option is accidentally ruined in the process of editing, it may be
  120. regenerated by re-executing the
  121. .IR get
  122. command with the
  123. .BR \-k
  124. option in place of the
  125. .BR \-e
  126. option.
  127. .P
  128. SCCS file protection specified via the ceiling, floor, and authorized
  129. user list stored in the SCCS file shall be enforced when the
  130. .BR \-e
  131. option is used.
  132. .RE
  133. .IP "\fB\-b\fR" 10
  134. Use with the
  135. .BR \-e
  136. option to indicate that the new delta should have an SID in a new
  137. branch as shown in the table below. This option shall be ignored if the
  138. .BR b
  139. flag is not present in the file or if the retrieved delta is not a leaf
  140. delta. (A leaf delta is one that has no successors on the SCCS file tree.)
  141. .RS 10
  142. .TP 10
  143. .BR Note:
  144. A branch delta may always be created from a non-leaf delta.
  145. .P
  146. .RE
  147. .IP "\fB\-i\ \fIlist\fR" 10
  148. Indicate a
  149. .IR list
  150. of deltas to be included (forced to be applied) in the creation of the
  151. generated file. The
  152. .IR list
  153. has the following syntax:
  154. .RS 10
  155. .sp
  156. .RS 4
  157. .nf
  158. <list> ::= <range> | <list> , <range>
  159. <range> ::= SID | SID - SID
  160. .fi
  161. .P
  162. .RE
  163. .P
  164. SID, the SCCS Identification of a delta, may be in any form shown in
  165. the ``SID Specified'' column of the table in the EXTENDED DESCRIPTION
  166. section, except that the result of supplying a partial SID is
  167. unspecified. A diagnostic message shall be written if the first SID in
  168. the range is not an ancestor of the second SID in the range.
  169. .RE
  170. .IP "\fB\-x\ \fIlist\fR" 10
  171. Indicate a
  172. .IR list
  173. of deltas to be excluded (forced not to be applied) in the creation of
  174. the generated file. See the
  175. .BR \-i
  176. option for the
  177. .IR list
  178. format.
  179. .IP "\fB\-k\fR" 10
  180. Suppress replacement of identification keywords (see below) in the
  181. retrieved text by their value. The
  182. .BR \-k
  183. option shall be implied by the
  184. .BR \-e
  185. option.
  186. .IP "\fB\-l\fR" 10
  187. Write a delta summary into an
  188. .BR l-file .
  189. .IP "\fB\-L\fR" 10
  190. Write a delta summary to standard output. All informative output that
  191. normally is written to standard output shall be written to standard
  192. error instead, unless the
  193. .BR \-s
  194. option is used, in which case it shall be suppressed.
  195. .IP "\fB\-p\fR" 10
  196. Write the text retrieved from the SCCS file to the standard output. No
  197. .BR g-file
  198. shall be created. All informative output that normally goes to the
  199. standard output shall go to standard error instead, unless the
  200. .BR \-s
  201. option is used, in which case it shall disappear.
  202. .IP "\fB\-s\fR" 10
  203. Suppress all informative output normally written to standard output.
  204. However, fatal error messages (which shall always be written to the
  205. standard error) shall remain unaffected.
  206. .IP "\fB\-m\fR" 10
  207. Precede each text line retrieved from the SCCS file by the SID of the
  208. delta that inserted the text line in the SCCS file. The format shall be:
  209. .RS 10
  210. .sp
  211. .RS 4
  212. .nf
  213. "%s\et%s", <\fISID\fR>, <\fItext line\fR>
  214. .fi
  215. .P
  216. .RE
  217. .RE
  218. .IP "\fB\-n\fR" 10
  219. Precede each generated text line with the %\fBM\fP% identification
  220. keyword value (see below). The format shall be:
  221. .RS 10
  222. .sp
  223. .RS 4
  224. .nf
  225. "%s\et%s", <\fI%M% value\fR>, <\fItext line\fR>
  226. .fi
  227. .P
  228. .RE
  229. .P
  230. When both the
  231. .BR \-m
  232. and
  233. .BR \-n
  234. options are used, the <\fItext\ line\fP> shall be replaced by the
  235. .BR \-m
  236. option-generated format.
  237. .RE
  238. .IP "\fB\-g\fR" 10
  239. Suppress the actual retrieval of text from the SCCS file. It is
  240. primarily used to generate an
  241. .BR l-file ,
  242. or to verify the existence of a particular SID.
  243. .IP "\fB\-t\fR" 10
  244. Use to access the most recently created (top) delta in a given release
  245. (for example,
  246. .BR "\-r 1" ),
  247. or release and level (for example,
  248. .BR "\-r 1.2" ).
  249. .br
  250. .SH OPERANDS
  251. The following operands shall be supported:
  252. .IP "\fIfile\fR" 10
  253. A pathname of an existing SCCS file or a directory. If
  254. .IR file
  255. is a directory, the
  256. .IR get
  257. utility shall behave as though each file in the directory were
  258. specified as a named file, except that non-SCCS files (last component
  259. of the pathname does not begin with
  260. .BR s. )
  261. and unreadable files shall be silently ignored.
  262. .RS 10
  263. .P
  264. If exactly one
  265. .IR file
  266. operand appears, and it is
  267. .BR '\-' ,
  268. the standard input shall be read; each line of the standard input is
  269. taken to be the name of an SCCS file to be processed. Non-SCCS files
  270. and unreadable files shall be silently ignored.
  271. .RE
  272. .SH STDIN
  273. The standard input shall be a text file used only if the
  274. .IR file
  275. operand is specified as
  276. .BR '\-' .
  277. Each line of the text file shall be interpreted as an SCCS pathname.
  278. .SH "INPUT FILES"
  279. The SCCS files shall be files of an unspecified format.
  280. .SH "ENVIRONMENT VARIABLES"
  281. The following environment variables shall affect the execution of
  282. .IR get :
  283. .IP "\fILANG\fP" 10
  284. Provide a default value for the internationalization variables that are
  285. unset or null. (See the Base Definitions volume of POSIX.1\(hy2017,
  286. .IR "Section 8.2" ", " "Internationalization Variables"
  287. for the precedence of internationalization variables used to determine
  288. the values of locale categories.)
  289. .IP "\fILC_ALL\fP" 10
  290. If set to a non-empty string value, override the values of all the
  291. other internationalization variables.
  292. .IP "\fILC_CTYPE\fP" 10
  293. Determine the locale for the interpretation of sequences of bytes of
  294. text data as characters (for example, single-byte as opposed to
  295. multi-byte characters in arguments and input files).
  296. .IP "\fILC_MESSAGES\fP" 10
  297. .br
  298. Determine the locale that should be used to affect the format and
  299. contents of diagnostic messages written to standard error, and
  300. informative messages written to standard output (or standard error, if
  301. the
  302. .BR \-p
  303. option is used).
  304. .IP "\fINLSPATH\fP" 10
  305. Determine the location of message catalogs for the processing of
  306. .IR LC_MESSAGES .
  307. .IP "\fITZ\fR" 10
  308. Determine the timezone in which the times and dates written in the
  309. SCCS file are evaluated. If the
  310. .IR TZ
  311. variable is unset or NULL, an unspecified system default timezone is
  312. used.
  313. .SH "ASYNCHRONOUS EVENTS"
  314. Default.
  315. .SH STDOUT
  316. For each file processed,
  317. .IR get
  318. shall write to standard output the SID being accessed and the number of
  319. lines retrieved from the SCCS file, in the following format:
  320. .sp
  321. .RS 4
  322. .nf
  323. "%s\en%d lines\en", <\fISID\fR>, <\fInumber of lines\fR>
  324. .fi
  325. .P
  326. .RE
  327. .P
  328. If the
  329. .BR \-e
  330. option is used, the SID of the delta to be made shall appear after the
  331. SID accessed and before the number of lines generated, in the POSIX
  332. locale:
  333. .sp
  334. .RS 4
  335. .nf
  336. "%s\ennew delta %s\en%d lines\en", <\fISID accessed\fR>,
  337. <\fISID to be made\fR>, <\fInumber of lines\fR>
  338. .fi
  339. .P
  340. .RE
  341. .P
  342. If there is more than one named file or if a directory or standard
  343. input is named, each pathname shall be written before each of the lines
  344. shown in one of the preceding formats:
  345. .sp
  346. .RS 4
  347. .nf
  348. "\en%s:\en", <\fIpathname\fR>
  349. .fi
  350. .P
  351. .RE
  352. .P
  353. If the
  354. .BR \-L
  355. option is used, a delta summary shall be written following the format
  356. specified below for
  357. .BR l-files .
  358. .P
  359. If the
  360. .BR \-i
  361. option is used, included deltas shall be listed following the notation,
  362. in the POSIX locale:
  363. .sp
  364. .RS 4
  365. .nf
  366. "Included:\en"
  367. .fi
  368. .P
  369. .RE
  370. .P
  371. If the
  372. .BR \-x
  373. option is used, excluded deltas shall be listed following the notation,
  374. in the POSIX locale:
  375. .sp
  376. .RS 4
  377. .nf
  378. "Excluded:\en"
  379. .fi
  380. .P
  381. .RE
  382. .P
  383. If the
  384. .BR \-p
  385. or
  386. .BR \-L
  387. options are specified, the standard output shall consist of the text
  388. retrieved from the SCCS file.
  389. .SH STDERR
  390. The standard error shall be used only for diagnostic messages, except
  391. if the
  392. .BR \-p
  393. or
  394. .BR \-L
  395. options are specified, it shall include all informative messages
  396. normally sent to standard output.
  397. .SH "OUTPUT FILES"
  398. Several auxiliary files may be created by
  399. .IR get .
  400. These files are known generically as the
  401. .BR g-file ,
  402. .BR l-file ,
  403. .BR p-file ,
  404. and
  405. .BR z-file .
  406. The letter before the
  407. <hyphen-minus>
  408. is called the
  409. .IR tag .
  410. An auxiliary filename shall be formed from the SCCS filename: the
  411. application shall ensure that the last component of all SCCS filenames
  412. is of the form
  413. .BR s. \c
  414. .IR module-name ;
  415. the auxiliary files shall be named by replacing the leading
  416. .BR s
  417. with the tag. The
  418. .BR g-file
  419. shall be an exception to this scheme: the
  420. .BR g-file
  421. is named by removing the
  422. .BR s.
  423. prefix. For example, for
  424. .BR s.xyz.c ,
  425. the auxiliary filenames would be
  426. .BR xyz.c ,
  427. .BR l.xyz.c ,
  428. .BR p.xyz.c ,
  429. and
  430. .BR z.xyz.c ,
  431. respectively.
  432. .P
  433. The
  434. .BR g-file ,
  435. which contains the generated text, shall be created in the current
  436. directory (unless the
  437. .BR \-p
  438. option is used). A
  439. .BR g-file
  440. shall be created in all cases, whether or not any lines of text were
  441. generated by the
  442. .IR get .
  443. It shall be owned by the real user. If the
  444. .BR \-k
  445. option is used or implied, the
  446. .BR g-file
  447. shall be writable by the owner only (read-only for everyone else);
  448. otherwise, it shall be read-only. Only the real user need have write
  449. permission in the current directory.
  450. .P
  451. The
  452. .BR l-file
  453. shall contain a table showing which deltas were applied in generating
  454. the retrieved text. The
  455. .BR l-file
  456. shall be created in the current directory if the
  457. .BR \-l
  458. option is used; it shall be read-only and it is owned by the real user.
  459. Only the real user need have write permission in the current
  460. directory.
  461. .P
  462. Lines in the
  463. .BR l-file
  464. shall have the following format:
  465. .sp
  466. .RS 4
  467. .nf
  468. "%c%c%c %s\et%s %s\en", <\fIcode1\fR>, <\fIcode2\fR>, <\fIcode3\fR>,
  469. <\fISID\fR>, <\fIdate-time\fR>, <\fIlogin\fR>
  470. .fi
  471. .P
  472. .RE
  473. .P
  474. where the entries are:
  475. .IP "<\fIcode1\fP>" 10
  476. A
  477. <space>
  478. if the delta was applied;
  479. .BR '*'
  480. otherwise.
  481. .IP "<\fIcode2\fP>" 10
  482. A
  483. <space>
  484. if the delta was applied or was not applied and ignored;
  485. .BR '*'
  486. if the delta was not applied and was not ignored.
  487. .IP "<\fIcode3\fP>" 10
  488. A character indicating a special reason why the delta was or was not
  489. applied:
  490. .RS 10
  491. .IP "\fBI\fP" 6
  492. Included.
  493. .IP "\fBX\fP" 6
  494. Excluded.
  495. .IP "\fBC\fP" 6
  496. Cut off (by a
  497. .BR \-c
  498. option).
  499. .RE
  500. .IP "<\fIdate-time\fP>" 10
  501. Date and time (using the format of the
  502. .IR date
  503. utility's
  504. .BR %y /\c
  505. .BR %m /\c
  506. .BR %d
  507. .BR %T
  508. conversion specification format) of creation.
  509. .IP "<\fIlogin\fP>" 10
  510. Login name of person who created
  511. .IR delta .
  512. .P
  513. The comments and MR data shall follow on subsequent lines, indented one
  514. <tab>.
  515. A blank line shall terminate each entry.
  516. .P
  517. The
  518. .BR p-file
  519. shall be used to pass information resulting from a
  520. .IR get
  521. with a
  522. .BR \-e
  523. option along to
  524. .IR delta .
  525. Its contents shall also be used to prevent a subsequent execution of
  526. .IR get
  527. with a
  528. .BR \-e
  529. option for the same SID until
  530. .IR delta
  531. is executed or the joint edit flag,
  532. .BR j ,
  533. is set in the SCCS file. The
  534. .BR p-file
  535. shall be created in the directory containing the SCCS file and the
  536. application shall ensure that the effective user has write permission
  537. in that directory. It shall be writable by owner only, and owned
  538. by the effective user. Each line in the
  539. .BR p-file
  540. shall have the following format:
  541. .sp
  542. .RS 4
  543. .nf
  544. "%s %s %s %s%s%s\en", <\fIg-file SID\fR>,
  545. <\fISID of new delta\fR>, <\fIlogin-name of real user\fR>,
  546. <\fIdate-time\fR>, <\fIi-value\fR>, <\fIx-value\fR>
  547. .fi
  548. .P
  549. .RE
  550. .P
  551. where <\fIi\(hyvalue\fP> uses the format
  552. .BR \(dq\^\(dq
  553. if no
  554. .BR \-i
  555. option was specified, and shall use the format:
  556. .sp
  557. .RS 4
  558. .nf
  559. " -i%s", <-i option \fIoption-argument\fR>
  560. .fi
  561. .P
  562. .RE
  563. .P
  564. if a
  565. .BR \-i
  566. option was specified and <\fIx\(hyvalue\fP> uses the format
  567. .BR \(dq\^\(dq
  568. if no
  569. .BR \-x
  570. option was specified, and shall use the format:
  571. .sp
  572. .RS 4
  573. .nf
  574. " -x%s", <-x option \fIoption-argument\fR>
  575. .fi
  576. .P
  577. .RE
  578. .P
  579. if a
  580. .BR \-x
  581. option was specified. There can be an arbitrary number of lines in the
  582. .BR p-file
  583. at any time; no two lines shall have the same new delta SID.
  584. .P
  585. The
  586. .BR z-file
  587. shall serve as a lock-out mechanism against simultaneous updates. Its
  588. contents shall be the binary process ID of the command (that is,
  589. .IR get )
  590. that created it. The
  591. .BR z-file
  592. shall be created in the directory containing the SCCS file for the
  593. duration of
  594. .IR get .
  595. The same protection restrictions as those for the
  596. .BR p-file
  597. shall apply for the
  598. .BR z-file .
  599. The
  600. .BR z-file
  601. shall be created read-only.
  602. .br
  603. .SH "EXTENDED DESCRIPTION"
  604. .TS
  605. center tab(@) box;
  606. cB s s s s
  607. cB cB cB cB cB
  608. cB cB cB cB cB
  609. l c lw(4.5c) l l.
  610. Determination of SCCS Identification String
  611. =
  612. SID*@\-b Keyletter@Other@SID@SID of Delta
  613. Specified@Used\(dg@Conditions@Retrieved@to be Created
  614. .sp 1.5p
  615. =
  616. none\(dd@no@R defaults to mR@mR.mL@mR.(mL+1)
  617. _
  618. none\(dd@yes@R defaults to mR@mR.mL@mR.mL.(mB+1).1
  619. .sp 1.5p
  620. =
  621. R@no@R > mR@mR.mL@R.1***
  622. _
  623. R@no@R = mR@mR.mL@mR.(mL+1)
  624. _
  625. R@yes@R > mR@mR.mL@mR.mL.(mB+1).1
  626. _
  627. R@yes@R = mR@mR.mL@mR.mL.(mB+1).1
  628. _
  629. R@\-@T{
  630. R < mR and
  631. R does not exist
  632. T}@hR.mL**@hR.mL.(mB+1).1
  633. _
  634. R@\-@T{
  635. Trunk successor in release > R
  636. and R exists
  637. T}@R.mL@R.mL.(mB+1).1
  638. .sp 1.5p
  639. =
  640. R.L@no@No trunk successor@R.L@R.(L+1)
  641. _
  642. R.L@yes@No trunk successor@R.L@R.L.(mB+1).1
  643. _
  644. R.L@\-@T{
  645. Trunk successor
  646. in release \(>= R
  647. T}@R.L@R.L.(mB+1).1
  648. .sp 1.5p
  649. =
  650. R.L.B@no@No branch successor@R.L.B.mS@R.L.B.(mS+1)
  651. _
  652. R.L.B@yes@No branch successor@R.L.B.mS@R.L.(mB+1).1
  653. .sp 1.5p
  654. =
  655. R.L.B.S@no@No branch successor@R.L.B.S@R.L.B.(S+1)
  656. _
  657. R.L.B.S@yes@No branch successor@R.L.B.S@R.L.(mB+1).1
  658. _
  659. R.L.B.S@\-@Branch successor@R.L.B.S@R.L.(mB+1).1
  660. .TE
  661. .IP * 8
  662. R, L, B, and S are the release, level, branch, and sequence components
  663. of the SID, respectively; m means maximum. Thus, for example, R.mL
  664. means ``the maximum level number within release R''; R.L.(mB+1).1 means
  665. ``the first sequence number on the new branch (that is, maximum branch
  666. number plus one) of level L within release R''. Note that if the SID
  667. specified is of the form R.L, R.L.B, or R.L.B.S, each of the specified
  668. components shall exist.
  669. .IP ** 8
  670. hR is the highest existing release that is lower than the specified,
  671. nonexistent, release R.
  672. .IP *** 8
  673. This is used to force creation of the first delta in a new release.
  674. .IP "\(dg" 8
  675. The
  676. .BR \-b
  677. option is effective only if the
  678. .BR b
  679. flag is present in the file. An entry of
  680. .BR '\-'
  681. means ``irrelevant''.
  682. .IP "\(dd" 8
  683. This case applies if the
  684. .BR d
  685. (default SID) flag is not present in the file. If the
  686. .BR d
  687. flag is present in the file, then the SID obtained from the
  688. .BR d
  689. flag is interpreted as if it had been specified on the command line.
  690. Thus, one of the other cases in this table applies.
  691. .SS "System Date and Time"
  692. .P
  693. When a
  694. .BR g-file
  695. is generated, the creation time of deltas in the SCCS file may be taken
  696. into account. If any of these times are apparently in the future, the
  697. behavior is unspecified.
  698. .SS "Identification Keywords"
  699. .P
  700. Identifying information shall be inserted into the text retrieved from
  701. the SCCS file by replacing identification keywords with their value
  702. wherever they occur. The following keywords may be used in the text
  703. stored in an SCCS file:
  704. .IP "%\fBM\fP%" 10
  705. Module name: either the value of the
  706. .BR m
  707. flag in the file, or if absent, the name of the SCCS file with the
  708. leading
  709. .BR s.
  710. removed.
  711. .IP "%\fBI\fP%" 10
  712. SCCS identification (SID) (%\fBR\fR%.%\fBL\fR% or
  713. %\fBR\fR%.%\fBL\fR%.%\fBB\fR%.%\fBS\fR%) of the retrieved text.
  714. .IP "%\fBR\fP%" 10
  715. Release.
  716. .IP "%\fBL\fP%" 10
  717. Level.
  718. .IP "%\fBB\fP%" 10
  719. Branch.
  720. .IP "%\fBS\fP%" 10
  721. Sequence.
  722. .IP "%\fBD\fP%" 10
  723. Current date (\fIYY\fR/\fIMM\fR/\fIDD\fR).
  724. .IP "%\fBH\fP%" 10
  725. Current date (\fIMM\fR/\fIDD\fR/\fIYY\fR).
  726. .IP "%\fBT\fP%" 10
  727. Current time (\fIHH\fR:\fIMM\fR:\fISS\fR).
  728. .IP "%\fBE\fP%" 10
  729. Date newest applied delta was created (\fIYY\fR/\fIMM\fR/\fIDD\fR).
  730. .IP "%\fBG\fP%" 10
  731. Date newest applied delta was created (\fIMM\fR/\fIDD\fR/\fIYY\fR).
  732. .IP "%\fBU\fP%" 10
  733. Time newest applied delta was created (\fIHH\fR:\fIMM\fR:\fISS\fR).
  734. .IP "%\fBY\fP%" 10
  735. Module type: value of the
  736. .BR t
  737. flag in the SCCS file.
  738. .IP "%\fBF\fP%" 10
  739. SCCS filename.
  740. .IP "%\fBP\fP%" 10
  741. SCCS absolute pathname.
  742. .IP "%\fBQ\fP%" 10
  743. The value of the
  744. .BR q
  745. flag in the file.
  746. .IP "%\fBC\fP%" 10
  747. Current line number. This keyword is intended for identifying messages
  748. output by the program, such as ``this should not have happened'' type
  749. errors. It is not intended to be used on every line to provide
  750. sequence numbers.
  751. .IP "%\fBZ\fP%" 10
  752. The four-character string
  753. .BR \(dq@(#)\(dq
  754. recognizable by
  755. .IR what .
  756. .IP "%\fBW\fP%" 10
  757. A shorthand notation for constructing
  758. .IR what
  759. strings:
  760. .RS 10
  761. .sp
  762. .RS 4
  763. .nf
  764. %\^W\^%=%\^Z\^%%\^M\^%<tab>%\^I\^%
  765. .fi
  766. .P
  767. .RE
  768. .RE
  769. .IP "%\fBA\fP%" 10
  770. Another shorthand notation for constructing
  771. .IR what
  772. strings:
  773. .RS 10
  774. .sp
  775. .RS 4
  776. .nf
  777. %\^A\^%=%\^Z\^%%\^Y\^%%\^M\^%%\^I\^%%\^Z\^%
  778. .fi
  779. .P
  780. .RE
  781. .RE
  782. .SH "EXIT STATUS"
  783. The following exit values shall be returned:
  784. .IP "\00" 6
  785. Successful completion.
  786. .IP >0 6
  787. An error occurred.
  788. .SH "CONSEQUENCES OF ERRORS"
  789. Default.
  790. .LP
  791. .IR "The following sections are informative."
  792. .SH "APPLICATION USAGE"
  793. Problems can arise if the system date and time have been modified (for
  794. example, put forward and then back again, or unsynchronized clocks
  795. across a network) and can also arise when different values of the
  796. .IR TZ
  797. environment variable are used.
  798. .P
  799. Problems of a similar nature can also arise for the operation of the
  800. .IR delta
  801. utility, which compares the previous file body against the working file
  802. as part of its normal operation.
  803. .SH EXAMPLES
  804. None.
  805. .SH RATIONALE
  806. None.
  807. .SH "FUTURE DIRECTIONS"
  808. None.
  809. .SH "SEE ALSO"
  810. .IR "\fIadmin\fR\^",
  811. .IR "\fIdelta\fR\^",
  812. .IR "\fIprs\fR\^",
  813. .IR "\fIwhat\fR\^"
  814. .P
  815. The Base Definitions volume of POSIX.1\(hy2017,
  816. .IR "Chapter 8" ", " "Environment Variables",
  817. .IR "Section 12.2" ", " "Utility Syntax Guidelines"
  818. .\"
  819. .SH COPYRIGHT
  820. Portions of this text are reprinted and reproduced in electronic form
  821. from IEEE Std 1003.1-2017, Standard for Information Technology
  822. -- Portable Operating System Interface (POSIX), The Open Group Base
  823. Specifications Issue 7, 2018 Edition,
  824. Copyright (C) 2018 by the Institute of
  825. Electrical and Electronics Engineers, Inc and The Open Group.
  826. In the event of any discrepancy between this version and the original IEEE and
  827. The Open Group Standard, the original IEEE and The Open Group Standard
  828. is the referee document. The original Standard can be obtained online at
  829. http://www.opengroup.org/unix/online.html .
  830. .PP
  831. Any typographical or formatting errors that appear
  832. in this page are most likely
  833. to have been introduced during the conversion of the source files to
  834. man page format. To report such errors, see
  835. https://www.kernel.org/doc/man-pages/reporting_bugs.html .