Changed Commands in Section 1

This section summarizes changes to commands in Section 1 of the HP-UX Reference manual (and the online manpages) that are not discussed elsewhere in this document. Unless specified otherwise, the changes occurred at 10.0.

Commands changed at 10.30:

ipcs(1) — (a future consideration)
uname(1) — (a future consideration)

Commands changed at 10.20:

cancel(1)
cpio(1)
ex(1)
findmsg(1)
ftio(1)
iconv(1)
lp(1)
lpstat(1)
pax(1)
tar(1)
vi(1)

Commands changed at 10.10:

admin(1)
ar(1)
asa(1)
at(1)
bc(1)
cal(1)
cancel(1)
cksum(1)
compress (1)
crontab(1)
csh(1)
ctags(1)
cu(1)
date(1)
dd(1)
diff(1)
du(1)
eucset(1)
ex/vi(1)
expand(1)
expr(1)
find(1)
ftio(1)
getconf(1)
grep(1), egrep(1), fgrep(1)
id(1)
initstate()
ksh(1)
lex(1)
lpstat(1)
ls(1)
mail(1)
make(1)
man(1)
mkfifo(1)
nice(1)
nl(1)
nohup(1)
od(1)
pack(1)
patch(1)
pathchk(1)
pax(1)
pr(1)
prs(1)
ps(1)
renice(1)
rmdel(1)
sact(1)
sccs(1)
sed(1)
sh-posix(1)
split(1)
strings(1)
strip(1)
tar(1)
time(1)
top(1)
tput(1)
tsort(1)
uncompress(1)
unexpand(1)
uniq(1)
unpack(1)
uuencode(1)
uulog(1)
uupick(1)
uustat(1)
uuto(1)
uux(1)
val(1)
vi(1)
wc(1)
what(1)
who(1)
xargs(1)
zcat(1)

Commands changed at 10.01:

cu(1)
man(1)
uucp(1)

Commands changed at 10.0:

adjust(1)
awk(1)
cat(1)
chown(1), chgrp(1)
cp(1)
cpio(1)
doschmod(1), etc.
echo(1)
ftio(1)
gencat(1)
help(1), sccshelp(1)
iconv(1)
iostat(1)
join(1)
locale(1)
lp(1), lpadmin(1)
mesg(1)
mkdir(1)
mm(1)
more(1)
mt(1)
mv(1)
nljust(1)
nroff(1)
passwd (1)
paste (1)
rm(1)
rmdir(1)
sar(1)
sort(1)
sum(1)
tar(1)
tr(1)

adjust(1)

Modified to support Japanese line-breaking rules:

No line will start with a bkinsoku character
No line will end with a ekinsoku character

One or other of these rules will be broken if the line cannot be ended any other way.

The japanese locale has two new char classes, bkinsoku and ekinsoku.

admin(1)

For 10.10:

Now conforms to XPG4 specifications.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
When "-" is specified as an argument, SCCS directory names given on standard input are processed (they were ignored on earlier releases).
Unreadable files are now silently ignored.

ar(1)

For 10.10:

Now conforms to XPG4 XBD Utility Syntax Guidelines.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).

asa(1)

For 10.10:

Now conforms to XPG4 specifications.
The output from asa depends on the first character removed from the input line:

When the first           asa outputs:
character is:
============================================================================
 
 a blank space           the rest of the input line without changes
 
       0                 a newline character followed by the rest of
                         the input line
 
       1                 one or more characters that causes an advance
                         to the next page, followed by the rest of the
                         input line.
 
       +                 asa replaces the newline character of the previous
                         line with one or more implementation-dependent
                         characters that causes printing to return to
                         column position 1 followed by the rest of the
                         input line.
 
 (no file operands       standard input
  are specified)

"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
asa processes operands in the order specified on the command line.
When an input file is defined as a text file, at least 2048 bytes can be accumulated from a set of continued input lines.
When no error occurs during the execution of a utility, no error messages are written to standard error and the exit status from the utility is zero.
When a utility is unable to perform the requested action on an external object (such as a file, directory, user, process, and so on) specified by an operand, the utility issues a diagnostic message to standard error and continues processing subsequent operands. The final exit status of the utility is non-zero.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

at(1)

For 10.10:

Now conforms to XPG4 XBD Utility Syntax Guidelines.
The "Usage" message has been changed to reflect the availability of the t option.
Option arguments for the -f and -q options are mandatory.
The abday keyword is accepted.

See the at(1) manpage for details and syntax.

awk(1)

For 10.0:

Variable assignment
srand()
FS and newline characters
Backslash character

Variable assignment

awk will make the variable assignment just before processing the file operand that follows the variable, which will not be visible for the rest of the unprocessed files.

Uninitialized variables and strings will be printed as empty strings.

srand()

The arithmetic built-in function srand() returns the previous seed value.

FS and newline characters

The FS character, and the newline character followed by the last field, are no longer considered in the computation of NF.

backslash character

Within strings defined by double quotes, the backslash character (\) serves as an escape character to introduce escape sequences, as shown below.

Supported sequences introduced by the backslash are:

Escape     Meaning/Representation
Sequence
========================================================
\a         <alert>
\b         <backspace>
\f         <form-feed>
\n         <new-line>
\r         <carriage-return>
\t         <tab>
\v         <vertical-tab>
\ddd       The character whose encoding is represented by a
           one-, two-, or three-digit octal integer.
\<char>    (where <char> is any character not specified
           in this table): the character <char>.

In previous releases, the sequence \<char> was interpreted literally (for example, \e in 9.x was interpreted as \e; whereas in 10.x, \e is interpreted as e).

This change brings HP's treatment of the backslash into conformity with other implementations of awk.

bc(1)

For 10.10:

Very large numbers will be split across lines with 70 characters (this includes \ and \n characters.
scale(zero) is 0 even though bc is invoked with the -l option.

cal(1)

For 10.10:

Now handles different international locales.
The output of cal(1) has changed:
- The column width of a multi-byte character can be at most 4. At least one multi-byte character will be printed.
- It is only possible to format two months per row in the calendar.
- The column width of a day has increased from 3 to 5.
The internationalized environment variables, such as LANG are now supported.
The day and month names have been replaced by corresponding abbreviated day and month versions of nl_langinfo items.
Hard-coded values have been changed to #defined values whenever possible.
Error messages are written to the standard error file (stderr).

cancel(1)

For 10.20:

These model script files are added for new printers:

deskjet850C
deskjet855C
deskjet1600CM

You will be able to select these model scripts for configuring your printers.

The cancel(1) command is enhanced to interoperate with the new HP Distributed Print Services (HPDPS), a separate print spooling system. The command can submit jobs to the HPDPS, cancel HPDPS jobs, and list HPDPS printers and jobs.

For 10.10:

Now conforms to XPG4 specifications.
cancel(1) can be localized; a code for internationalization has been added.
Error messages are written to the standard error file (stderr).
Whenever an error occurs, the exit status is non-zero.

cat(1)

New options:

-b: Omits line numbers from blank lines; -n option is assumed.
-n: Displays lines preceded by line numbers, starting with 1.
-r: Replaces multiple consecutive empty lines with one empty line.

Changed options:

The options -e and -t no longer require -v.

chown(1), chgrp(1)

These commands now behave the same way (following SVID3) on the Series 700 and 800 when they encounter symbolic links. The default action is to follow the link.

New option:

-h: Do not follow the symbolic link.

The hpux_aes_override kernel flag is no longer needed.

cksum(1)

For 10.10:

"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).

For 10.0:

Checksum values are generated according to a new algorithm as of 10.0 to ensure conformance with the latest POSIX.2 standard.

This means that checksum values will differ between 9.x and 10.x for the same input. If you need to obtain checksum values calculated by the 9.x algorithm, you can use the old version of the command, delivered with 10.x as /usr/old/usr/bin/cksum. If you are using these values in a script, use /usr/old/usr/bin/cksum to verify them, then update them to the 10.x values using the 10.x command.

cksum now also supports piped input.

compress (1)

For 10.10:

Now conforms to XPG4 specifications.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
If no file is specified or if the file operand is "-", standard input is compressed to standard output.
Returns a value of 1 whenever it fails on one of the operands (previous versions returned a value of 0).
The XPG4 behavior is activated if you set the UNIX95 environment variable.

For 10.0:

New option -z:
-z is same as -f except that it does not force compression when there is null compression.

cp(1)

cp will provide warning messages whenever extent attributes of a file are lost. You can use the -e option to control what cp does if it cannot copy extent attributes.

New option: -e

This option can have one of the following three parameters:

-e [warn | force | ignore]

-e warn is the default behavior of the command.

If the extent attributes of a file cannot be copied, then:

If -e warn is specified, or if the -e option is not used, cp will issue a warning message and copy the file.
If -e force is specified, cp will not copy the file.
If -e ignore is specified, cp will ignore extent attributes.

See also entries for “cpio(1) ”, “ftio(1) ”, and “mv(1) ” in this section.

cpio(1)

For 10.20:

Because of industry standards and interoperability goals, files larger than 2GB cannot be archived using cpio(1). You will receive an error message if archival is attempted for a file that is larger than 2GB in size.

User and group IDs larger than 60K are not supported. Files with user/group IDs greater than 60K are archived and restored under the user/group IDs of the current process.

The fbackup and frecover command set is recommended for backing up files that are larger than 2GB or are owned by user/group IDs that are greater than or equal to 60000.

For 10.0:

cpio will provide warning messages whenever extent attributes of a file are lost. You can use the -e option to control what cpio does if it cannot copy extent attributes.

cpio will not allow files from pre-10.0 systems to be restored onto a 10.x system because the device files are different and some of them are invalid for 10.x.

See the entry “cp(1) ” in this document for more information; for full details, see the cpio(1) manpage.

crontab(1)

For 10.10:

A new -e option has been added. When specified, -e edits a copy of your crontab file or creates an empty file to edit if the crontab file does not exist. When editing is complete, the file is copied into the crontab directory as your crontab file.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).

csh(1)

For 10.10:

The limit built-in command is now available. This command allows you to access and/or modify system resources for the following: cputime, filesize, datasize, stacksize, coredumpsize, and file descriptors.

For 10.01:

exit in .cshrc now works correctly.
set nonomatch now always works correctly.
foreach var (wordlist) syntax now allows alphanumeric variables in the var field.
csh no longer hangs if SIGUSR1 is ignored and csh is exec'ed.
LINES and COLUMNS are set by default when csh starts up.

See “Shells ” for more information on HP-UX shells for 10.x.

ctags(1)

For 10.10:

Now conforms to XPG4 XBD Utility Syntax Guidelines.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
The -f option for specifying tags-file name has been added. When -f is not specified, the output tags-file-name is tags.
The actions of the -t option are now the defaults; the -t option has been made redundant for backward compatibility.
The usage message has been changed to add the -f option.
If an error occurs when processing one of the operands, the final exit value has been changed to be non-zero.
The global variable lineftell has been fixed. lineftell is now initialized to zero for each file.

cu(1)

For 10.10:

Now conforms to XPG4 specifications.
The -d level option has been renamed to a -D level. This option prints diagnostic traces. The level specified can be from 0 to 9, where high levels produce more detail in the diagnostic messages.
The -d option has been added to write diagnostic traces. This option is equivalent to a -D 9 option.
The usage message has been modified to reflect the above changes.
If the -n option is used, a message prompting for the telephone number is delayed until the command line processing is complete.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

For 10.01:

As a consequence of the new NFS file-sharing paradigm, the uucp(1) and cu(1) commands are now supported on client systems.

This change applies to all commands in the UUCP fileset, as well as the commands in the SYSCOM fileset:

cu
ct
uupath
kermit
umodem
vt
vtdaemon
vtgateway
vtserver

Refer to the section in this chapter on the uucp(1) command for additional information.

date(1)

For 10.10:

Now conforms to XPG4 specifications.
No response is required from the user if the date is being set backward.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

dd(1)

For 10.10:

dd(1) can now copy disk devices larger than 4Gb.

diff(1)

For 10.10:

When the command fails, a return value will be non-zero.

doschmod(1), etc.

The following commands support wildcard characters in MSDOS file names:

doschmod(1)
doscp(1)
dosls(1)
dosrm(1)
dosrmd(1)

You can use the metacharacters *, ? , and [] when specifying DOS file names. You must enclose them in quotes, because file name expansion must be performed by the DOS utilities, not by the shell. DOS utilities expand file names as described in the regexp(5) manpage under "PATTERN MATCHING NOTATION."

du(1)

For 10.10:

Now conforms to XPG4 XBD Utility Syntax Guidelines.
A new option k has been added, which give the file size in units of 1024 bytes, rather than the default 512-byte unit.
Option r is the default.
Options s and a are mutually exclusive. If both are specified, a usage message will be displayed.
If an error occurs, a final exit value has been changed to be non-zero.

For 10.0:

Now supports multiple file system types.

Enhanced option:

Title not available (du(1) )

-t [type]: now works with all supported file system types.

echo(1)

Recognizes two additional special characters:

\a       write an alert character
\0[num]  write an 8-bit value representing the octal number [num]

eucset(1)

For 10.10:

A new option -c codeset has been added to support the HP-15 codesets. Options to -c can be one of the following, depending on the codeset:
- BIG5
- CCDC
- GB
- SJIS
This enables you to set the cswidth parameter for HP-15 codesets. You do not have to explicitly specify the cs width parameter (it is derived from the locale).

ex/vi(1)

Changes at 10.20 for ex(1):

Now conforms to XPG4 specifications.
The XPG4 behavior is activated if you set the UNIX95 environment variable.
If the implementation supports the ctags utility, when -t tagstring is specified with either -c or +command, ex processes the -t tagstring first and then executes the command.
The ex command does not read the .exrc file unless it is owned by the same user ID as the effective user ID of the invoking process.
When autowrite is set and the current buffer has been modified, a next, rewind, tag, edit, suspend, or stop command not followed by a ! or a ! command causes the buffer to be written to the current file.
The exit status must be non-zero when an error or warning message is encountered. The error or warning message must be written to stderr.
When the range change count command is issued, ex enters input mode and replaces the first line specified by range and the next count -1 lines with the text entered. The current line is set to the last line entered.
When autowrite is set and the current buffer has been modified, a next, rewind, tag, edit, suspend, or stop command followed by a ! does not cause the buffer to be written to the current file. The command checks if the ! is also given with the next command. If it is, the file should not write into the next file even if "autowrite" is set.
When the range move line command is specified, ex moves the lines specified by range (the default is the current line) to be after line. The current line indicator is set to the first of the moved lines.
When the unnamed buffer contains lines from a previous delete or yank command, line put places the lines in the unnamed buffer after line (the default is the current line) and sets the current line indicator to the first line put back.
When the SHELL environment variable is set to "myshell" and the read !file command is invoked, the command myshell -c file is called and the standard output of this command is placed in the current buffer after the current line.
When beautify or bf is set and a command is given to read a file into the buffer and the file contains non-printable characters other than tab, newline or form-feed, those non-printable characters are discarded from the text read in.
All diagnostic and error messages are written to standard error.
When the edcompatible set option is enabled and a substitute command is entered with either the c or g options, all subsequent substitute commands entered without the specification of the g or c options (respectively) are executed as if the appropriate option had been specified.
When a regular expression contains the character sequence \>, this sequence is matched against the beginning of a word in the lines being matched.
When the range & command is invoked, the substitution pair /pattern/repl/ from the previous substitute is used and the first instance of a string that matches the regular expression pattern is replaced by the string repl on each line specified by range (the default is the current line.)
When a RE is [a-z]*$, ex fails to find the match and does not perform the substitution. This is due to an anchor problem "$".

These changes will make the ex command binary incompatible. However, the incompatible behavior will only be seen when the UNIX95 environment variable is set.

Changes at 10.10 for ex(1):

Option -c has been added. This option is the same as the + option.
Option -s has been added. This option is the same as the - option.

Tag Stacking Feature for 10.0:

The :tag command now includes a tag stacking feature. The new :pop command will remove a tag from the tagstack and position the editor to the previous tag location. Up to 30 tags can be stored in the tagstack.

In vi, the [Ctrl-T] command will pop a tag and go to the previous tag location. It is analogous to the existing [Ctrl-] command, but can be used repeatedly to change tag locations until the tagstack is exhausted.

A new edit option (tagstack, tgst) enables this feature. The default setting is on. If notagstack is selected, the tags feature will behave as it did before 10.0.

Regular Expressions

Before 10.0, ex/vi used its own regular expression handler. It now uses the standard regcomp(3C) and regexec(3C) routines. You will notice the following changes:

The following constructs are now supported.
\{m\} \{m,\} \{m,n\}
There are restrictions affecting beginning-of-word and end-of-word:
- Beginning-of-word can be used only at the beginning of a regular expression, not in the middle. For example,
  :s/\<word/new
  is valid, but
  :s/word1 \<word2/new1 new2
  is not.
- Similarly end-of-word can be used at the end of a regular expression, but not in the middle. For example,
  :s/word\>/new
  is valid, but
  :s/word1\> word2/new1 new2
  is not.
- Beginning and end of word constructs will not recognize an ASCII-multibyte character transition as a word boundary.
  For example, if xx is a multibyte character:
  xxAxx5xxYS
  A, 5, YS, and the three xx characters would each be distinguished as words by vi's w command. But the search
  /\<A
  would not find the word beginning with A because it is not delineated by a multibyte character.

expand(1)

For 10.10:

Now conforms to XPG4 specifications.
The range of tabstop changed from 0 through 256 to 0 through 2147483647.

expr(1)

For 10.10:

Now conforms to XPG4 specifications.
When two strings are given as arguments and do not match, a new line is not output to the standard output.
expr suppresses leading zeros. For example, 000001 is output as 1.
expr supports nesting of parentheses to any depth.

find(1)

For 10.10:

A period (.) in a filename is matched by using a period as the first character or immediately following a slash character in the pattern.

For 10.0:

Recognizes two additional special characters:

\a       write an alert character
\0[num]  write an 8-bit value representing the octal number [num]

Now supports multiple file system types.

Enhanced options:

-fsonly [type]: now works with all supported file system types.
-fstype [type]: now works with all supported file system types.

findmsg(1)

For 10.20:

findmsg(1) supports print specifiers, such as PRI* defines in inttypes.h, as part of a message within a catgets() format. It also supports #ifdefs to select the specific messages from the input file.

For example, the message for

printf(catgets(catd, NL_SETN, mno, "mesg1 " PRIdMAX" \n"));

could be read as

"mesg1 <value_of_PRIdMAX> \n"

Input file(s) will be preprocessed using the C preprocessor (cpp(1)) to achieve the above features. The preprocessor recognizes the following new options:

   -D<sym>    Defines the symbol <sym> for #ifdef.
 
   -U<sym>    Undefine the symbol <sym>
 
   -i         Using this option, you can only extract
              the required messages under #ifdefs.
              That is, -D and -U are also used to select
              the text in the input file.
 
              Without this option, -D and -U options
              are only used to select the print specifiers,
              not the messages from the input file.
 
    -v        This option outputs the errors issued
              by cpp(1). By default, errors issued
              by cpp will not be displayed.

Impact

If more than one string occurs in the message part of the catgets() format (catgets(catd, NL_SETN, msgno, "str1" "str2")), all strings will be concatenated as a single string (catgets(catd, NL_SETN, msgno, "str1str2").

Performance

Input files that do not contain print specifiers are preprocessed even when it is not required. This is an overhead for such files.

ftio(1)

For 10.20:

ftio(1) creates archives that are compatible with cpio(1). Because of industry standards and interoperability goals, cpio(1) does not support the archival of files larger than 2GB. User and group IDs larger than 60K are not supported. Consequently, ftio(1) exhibits the same behavior. Therefore, files larger than 2GB cannot be archived using ftio(1). Files with user/group IDs greater than 60K are archived and restored under the user/group IDs of the current process.

Compatibility

There are no compatibility issues for files less than 2GB in size. There is a new error message if archival is attempted for a file that is greater than 2GB in size.

Alternatives

The fbackup and frecover command set is recommended for backing up files that are larger than 2GB or are owned by user/group IDs that are greater than or equal to 60,000.

For 10.10:

The ftio(1) command can now perform tape copy to a remote tape device. ftio(1) was modified to determine where the rmt command exists on the remote system.

If you encounter this problem, you can, on a 9.x system, copy the file /etc/rmt to /usr/sbin/rmt.

For 10.01:

ftio will provide warning messages whenever extent attributes of a file are lost. You can use the -e option to control what ftio does if it cannot archive extent attributes.

See “cp(1) ” in this section for more information. “cpio(1) ” and “mv(1) ” also support -e.

gencat(1)

New option:

-: specifies stdin or stdout for the source or catalog files, respectively.

getconf(1)

For 10.10:

Now conforms to XPG4 specifications.
Proper parse and evaluation of the expression for the argument variable is performed when necessary.

See the getconf(1) manpage for details.

grep(1), egrep(1), fgrep(1)

For 10.10:

Now conforms to XPG4 specifications.
grep -l with stdin as input will output a message on stdout. This also occurs for -l -m.
A grep on regular expressions prints correct results and returns exit 0 status for a successful grep with -e, -f, -i, -x, and -v options.
Null pattern selects every input line. This also occurs for the -e, -f, and -v options.
Null pattern with the -E option selects every input line.
grep -F and fgrep results match. The results also match using similar valid parameters applied to both.
Using the -q option and the first inaccessible input file results in an exit with zero status.

For 10.01:

The collating order of characters has been changed in some locales. See the "Locale Changes" section in the README for NLS in 10.01.

help(1), sccshelp(1)

The name of the help command has been changed to sccshelp, and the back-end command, help2 (/usr/lib/help/lib/help2), is no longer supported as an independent command: its functions are now part of sccshelp.

The reason for the change is that the command is really part of SCCS (the Source Code Control System) and the help libraries only exist for SCCS commands (admin(1), delta(1), get(1), prs(1), etc.). You do not need to change help libraries that you have created.

iconv(1) and iconv(3)

For 10.20:

The iconv(1) and iconv(3) commands now support the conversion of characters between some of the HP-supported code sets and various forms of the ISO 10646 code set, specifically the UCS forms, UCS-2, and UTF-8.




	WARNING! Do not store UCS-2 data in files. If you do, unexpected results might occur. Only UTF-8 data can be safely stored in files for processing.This is only a conversion feature to facilitate input/output with other systems and for code-internal purposes. No other HP-UX commands, utilities, services, and so on has been converted to support UCS-2 or UTF-8 at this time. Only `iconv` supports this feature.

The following conversions are supported:

 UTF-8, UCS-2 <--> roman8, iso8859-1 for West European languages
        UTF-8, UCS-2 <--> SJIS, eucJP (both including UDC/VDC) for Japanese
 UTF-8, UCS-2 <--> eucKR for Korean
 UTF-8, UCS-2 <--> hp15CN for Simplified Chinese
 UTF-8, UCS-2 <--> roc15, big5, eucTR for Traditional Chines
 UTF-8, UCS-2 <--> thai for Thai
 UTF-8, UCS-2 <--> iso8859-2 for East European
 UTF-8, UCS-2 <--> iso8859-5 for Cyrillic
 UTF-8, UCS-2 <--> iso8859-6 for Arabic
 UTF-8, UCS-2 <--> iso8859-7 for Greek
 UTF-8, UCS-2 <--> iso8859-8 for Hebrew
 UTF-8, UCS-2 <--> iso8859-9 for Turkish
 UTF-8 <--> UCS-2

Impact

Additional tables and methods have been added to support this conversion capability.

No current code or applications are impacted. This feature will enable HP-UX to exchange and interoperate with other systems that support ISO 10646 characters.

For 10.10:

Now conforms to XPG4 specifications.
Increased codeset conversion support.
Warning messages will no longer be printed.
New codeset naming convention, but old convention still supported.
Shift-in characters not added while converting to IBM or JIS codesets, if an ASCII character is the first character of the record.

See the README for NLS in 10.01 and the iconv(1) manpage for details.

id(1)

For 10.10:

Now conforms to XPG4 specifications.
You do not have to be superuser to run id otheruser, where otheruser is another user name with a different user ID.

iostat(1)

For 10.30:

There is a proposed changed for the -C and -N options to be ignored beginning with HP-UX 11.0. The reason is that the dump format changed with 10.10 from a format of a single file, which ipcs understands, to a set of several smaller core files.

For 10.0:

The output format of iostat has been substantially revised to make it more readable. Scripts that depend on the 9.x output format will need to be recoded.

The maps output field always reads 1.0; changes in disk technology have rendered this field meaningless, and it may be removed altogether in a later release.

join(1)

Option no longer supported:

-a without a number will now result in an error. As of 10.0, -a must be followed by 1 or 2.

locale(1)

Changed options:

-a: Lists all available public locales.
-k: Displays the name of the charmap file if charmap is specified. Supports new keywords in the LC_TIME category.
-c: Supports the CHARMAP category.

ksh(1)

For 10.10:

Now conforms to XPG4 specifications.
New signals SIGXCPU and SIGXFSZ are available.

The pre-HP-UX 10.10 history file will be discarded. Users who use multiple versions of HP-UX that NFS mount the same directory that contains the history file (usually the home directory) may want to create a separate history file for each HP-UX version. To do this, set the proper HISTFILE parameter. See the ksh(1) manpage for recommendations about setting the HISTFILE parameter to avoid the history file discard problem.

lex(1)

For 10.10:

Now conforms to XPG4 specifications.
Options -v and -n are mutually exclusive.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
If no file is specified or if the file operand is "-", the standard input should be used.

lp(1), lpadmin(1)

Changes at 10.20 for lp(1):

For 10.20, these model script files are added for new printers:

deskjet850C
deskjet855C
deskjet1600CM

You will be able to select these model scripts for configuring your printers.

The lp(1) command is enhanced to interoperate with the new HP Distributed Print Services (HPDPS), a separate print spooling system. The command can submit jobs to the HPDPS, cancel HPDPS jobs, and list HPDPS printers and jobs.

For 10.0:

New model files:

deskjet500C
deskjet550C
deskjet1200C
laserjet4
laserjet4Si
paintjetXL300

These files will support PCL5 features such as language switching, 600 dpi, tray selection, media type, and page level recovery. A summary of the options will print out on the banner page.

lpstat(1)

For 10.20:

These model script files are added for new printers:

deskjet850C
deskjet855C
deskjet1600CM

You will be able to select these model scripts for configuring your printers.

The lpstat(1) command is enhanced to interoperate with the new HP Distributed Print Services (HPDPS), a separate print spooling system. The command can submit jobs to the HPDPS, cancel HPDPS jobs, and list HPDPS printers and jobs.

For 10.10:

Now conforms to XPG4 specifications.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
The exist status is non-zero whenever an error occurs.

ls(1)

For 10.10:

Now conforms to XPG4 specifications.
The -t option has changed so that comparisons occur between a collating sequence if the operands are equal by modified time.
On output, the first newline character has been removed when the first item is to be written is a directory.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

For 10.01:

ls can now display the extent attributes of a file.

New option:

-e: Displays extent attributes. Must be used with -l; if -l is not specified -e is silently ignored. -e causes ls to open and immediately close each file in the list; this could make the command execute more slowly.

Other commands that have changed to handle extent attributes are cp(1), cpio(1), ftio(1), and mv(1).

m4(1)

For 10.10:

Now conforms to XPG4 specifications.
Fixes were made to the ifdef built-in macro.
Support of multiple occurrences of m4wrap built-in macro.
An error is flagged when a non-numeric argument is passed to the following built-in macros: decr, divert, eval, incr, m4exit, substr, and undivert.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
When an error occurs while processing one of the operands, processing continues with remaining operands and the final exit status is non-zero.
The ifdef macro now makes an additional check to see if the value of its first argument is '0'.
When the m4wrap macro is used multiple times, only the latest m4wrap argument is processed on EOF.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

mail(1)

For 10.10:

Now conforms to XPG4 XBD Utility Syntax Guidelines.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).

make(1)

For 10.10:

Now conforms to XPG4 specifications.
If the target is up-to-date, make prints a message and exits with a zero status.
If the target is not up-to-date and the target rule contains no associated commands, make writes a message to stdout indicating that no action was taken for that target and exits with a zero status.
The command with a as a prerequisite for targets, where a exists and is newer than each existing target, writes a message to stdout indicating that no action was taken and exits with a status of zero.
Precedence of the command-line options over the MAKEFLAGS environment.
MAKEFLAGS in the makefile replaces the MAKEFLAGS environment.
Macros defined on the command line are added to the MAKEFLAGS variable.
Macros defined in the MAKEFLAGS, but without any command line macros, adds the macro to the environment, overwriting any variable of the same name.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

For 10.0:

Now conforms to XPG4 specifications.
Search sequence for the makefile has been extended to include the SCCS directory.
Set the environment variable PROJECTDIR to search for an SCCS subdirectory that is not under the current working directory.
Two new default macros: SCCSFLAGS and SCCSGETFLAGS.
New special macro VPATH enables make to search through a list of paths (separated by colons) looking for prerequisites and dependencies.
Conditional macro definitions supported.
include supported.

man(1)

For 10.01:

man will no longer create cat* subdirectories automatically when run on a diskless client.

The man directories for an NFS Diskless client are under /usr/share/man, which resides on the server in the read-only portion of the file system. This means that the man command, when run from a client, will not install the formatted entry into the cat* directories, because only the server can write to them.

You may want to run catman(1M) on the server to set up the cat directories. Otherwise, users will get the message,

Reformatting entry. Wait

and will have to wait for the manpage to be uncompressed, every time they run man.

See “catman(1M) ” in this section or the catman(1M) manpage for information on running catman(1M) on a server that does not have common manpages with a given client.

On servers and standalone systems, the man command will continue to install a formatted entry in the cat* directory.

mesg(1)

A new option, g, sets access mode to 620.

This is the default and recommended access mode for tty/pty lines, allowing legitimate commands which are secure (e.g., write(1)) to be used by other users for sending messages.

mkdir(1)

On 9.0 Series 800s, mkdir -p could go across a read-only file system and follow a soft link to a read-write file system to make a directory. mkdir -p does not have this capability on any 10.x computers.

mkfifo(1)

For 10.10:

Now conforms to XPG4 specifications.
If the mode specified by the user is +, -, or = without user (u), group (g), other (o), or all (a) specified, the mode bits gets set or cleared for all.
If the mode specified by the user has the operator + with user (u), group (g), other (o), or all (a), the permissions for the newly created directory will be permissions specified after the operator and also the permissions as specified in the umask.
If the mode specified at the command line has the operator with user (u), group (g), other (o), or all (a), the permissions for the newly created directory will be the permissions as per the umask value minus the ones specified.
If the mode specified at the command line has the operator = with user (u), group (g), other (o), or all (a), the permissions for the newly created directory will be the permissions as specified after the = operator for the who and the remaining who retain values as per the umask.
If mkfifo is invoked with the -m option, the umask is not referred for setting the mode permissions if the mode given by you is in octal.
If the mode you provide is in symbolic notation, only the bits given by you are set. The rest of the bits (for which who is not provided), are set as per the value in umask.

mm(1)

mm uses uncompiled macro files only; compiled macro files are no longer supported. The -y option, which specifies uncompiled macro files on 9.x, was not needed as of 10.0.

more(1)

Many new options, and some changed, to comply with XPG4 standards.

Changes include:

Backward scrolling.
Third line of screen is current position for positioning commands.
-e causes exit after last line of last file; automatic exit after last line only if stdout is not a terminal device.
-f and -n imply -c.
Special handling for ^L (form feed) eliminated.
-l option eliminated; this behavior is now default.

See the manpage for details.

mt(1)

The default device file for this command in 9.x and earlier releases was /dev/rmt/0mn. As of 10.0, the default is /dev/rmt/0mnb.

The reason for this is that as of 10.0, /dev/rmt/0mn represents AT&T mode, whereas only raw, no-rewind Berkeley-style devices should be used with mt(1).

On the Series 700, /dev/rmt/0mn used to represent a no-rewind, Berkeley-style device. On 10.x such a device is represented by /dev/rmt/0mnb. On the Series 800, /dev/rmt/0mnb has always represented this type of device and continues to do so.

System       Pre-10.0        10.x
===========================================
Series 700   /dev/rmt/0mn    /dev/rmt/0mnb
Series 800   /dev/rmt/0mnb   /dev/rmt/0mnb

If you have 9.x scripts that use /dev/rmt/0mn with mt(1), you will need to change them to use /dev/rmt/0mnb before running them on a 10.x system.

mv(1)

mv will provide warning messages whenever extent attributes of a file are lost. You can use the -e option to control what mv does if it cannot find extent attributes.

See the entry for “cp(1) ” in this section for more information. See also “cpio(1) ”, “ftio(1) ”, and “ls(1) ” in this section.

nice(1)

For 10.10:

Now conforms to XPG4 specifications.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
New option n with a "numeric option argument".
Changes to usage and error messages.

nl(1)

For 10.10:

Now conforms to XPG4 specifications.
The options can now be intermingled with the optional file operand.
If - is specified as a file name, input will be taken from stdin.
The limit for input lines is increased to 2048 bytes.
If text numbering option is used, the text line will now be numbered only if that line contains graphic characters.
Only one file can now be specified. If multiple files are specified, an error occurs.

nljust(1)

New syntax:

nljust [-acilnt] [-d digits] [-e seq] [-j just] [-m mode]
       [-o order] [-r margin] [-w width] [-x ck] [file...]

New options:

-i: Triggers ISO 8859/6 interpretation of the data.
-d digits: Where digits is h, w, or b. Processes digits for output as Hindi (h), Western (w), or both (b).

These options support the ISO 8859/6 character set (also known as ASMO 708).

nohup(1)

For 10.10:

Now conforms to XPG4 specifications.
If a file is created, the file's permissions bits will be set to S_IRUSR or S_IWUSR.
The following exit values are returned:

126: The command specified by command was found, but could not be invoked.
127: An error occurred in the nohup utility or the specified command could not be found.

Otherwise, the exit status of nohup will be that of the command specified.

"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).

nroff(1)

New option:

-P: directs Asian printers to print two-column-wide characters in boxes 1 1/2 columns wide.

od(1)

For 10.10:

Now conforms to XPG4 specifications.
The output format has been changed. When multiple types are specified using multiple -bcbox options, output lines are written for each type in the order specified.
If multiple files are specified on the command line, the dump is uniformly generated reading the files as if there was one file that was generated by concatenating each file on the command line.

pack(1)

For 10.10:

Now conforms to XPG4 XBD Utility Syntax Guidelines.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
No packing occurs if the file name has more than NAME_MAX -2 characters.

patch(1)

For 10.10:

Reads a patch file containing a difference listing produced by the diff(1) command.
Applies the diff file to an original file, producing a patched file.

See the patch(1) manpage for details.

pathchk(1)

For 10.10:

When the length of a given pathname exceeds the system limit, the command will exit with non-zero value.

passwd (1)

New options:

-m (min): Sets the minimum time between password changes for a given user.
-x (max): Sets the maximum time before the password expires.
-w (warn): Sets the time prior to expiration when users receive warnings to change their password.
-f: Forces the user to change the password at the next login attempt.
-F: Same as the old -f.

The above new password aging options will not work with -F, and they affect only the system's local users.

paste (1)

No longer limits output line to 1023 characters.

pax(1)

For 10.20:

Because of industry standards and interoperability goals, files larger than 2GB cannot be archived using pax(1). You will receive an error message if archival is attempted for a file that is larger than 2GB in size.

User and group IDs larger than 60K are not supported. Files with user/group IDs greater than 60K are archived and restored under the user/group IDs of the current process.

The fbackup and frecover command set is recommended for backing up files that are larger than 2GB or are owned by user/group IDs that are greater than or equal to 60000.

For 10.10:

New option -o provides information to the implementation to modify the algorithm for extracting or writing files that is specific to the file format specified by -x.
MAXLINE has been changed from 1024 to 2048.
pax has been changed to restore the file with its original permissions when the file was backed up.

For 10.0:

Ba,sed on OSF 1.2.
Supports 4-byte EUC
POSIX.2 compliant

New options:

-k: Do not write over existing files.
-X: When traversing the file hierarchy specified by a pathname, do not descend into directories that have a different device ID.

Changed options:

Old            Replaced
option         by            Meaning
===========================================================
-m             -pm           File modification times
                             preserved
-o             -po           File ownership restored from
                             archive
-p             -t            Access times preserved
-t [device]    -f [archive]  Overrides standard default
                             input for -r and standard
                             output for -w.

Option no longer supported:

-H will now result in the general usage message. See “NFS Diskless ” for details.

pr(1)

For 10.10:

A new option -c has been added. This option is equivalent to the existing -k option.
With the -k option, if an invalid option is used, pr does not report an error message.
pr now returns a non-zero exit value for missing option arguments.
If multiple files are specified with pr and the -F option, the "\n" character will be added at the end of output.

prs(1)

For 10.10:

Now conforms to XPG4 XBD Utility Syntax Guidelines.
The -c and -d option arguments are now mandatory.
When "-" is specified as an argument, SCCS directory names given on standard input are processed (they were ignored on earlier releases).
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
If an error occurs when processing one of the files, the processing continues with the next file operand, but exits with a non-zero status.
Unreadable files are now silently ignored.

ps(1)

For 10.10:

Now conforms to XPG4 specifications.
New options have been added that increase the data available from ps and the ability to customize its' output. The options that changed are: -A, -c, -C, -G, -H, -j, -n, -o, -s, and -U. Refer to the manpages for option details.
Specifically, the changes for XPG4 compliance are:
- Addition of the -A option. This option is the same as the existing -e option.
- Addition of the -G grouplist option. This option writes the information for processes whose real group ID numbers are given in grouplist.
- Addition of the -o format option. This option writes information according to the format specification given in format.
- Addition of the -U userlist option. This option writes information for processes whose real user ID numbers or login names are given in userlist.
- Addition of the -n namelist option, which is ignored.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

For 10.0:

Two new options for HP Process Resource Manager (HP PRM)
Modifications to accommodate DTC nailed ports and Streams ptys

New options (for systems configured with HP PRM):

-P: Adds an additional column to ps's output, showing the process resource group ID of each process.
-R: Filters the processes displayed, showing only those that belong to specified process resource groups.

Modifications for DTC nailed ports and Streams ptys:

The manner in which ps searches for terminal device files has been changed to accommodate DTC nailed ports and Streams ptys, which are supported with these restrictions:

All DTC nailed port device files must appear in the directory /dev/telnet.
All Streams ptys must be specified, and will be printed, as pts/NN, where NN is the pty number,

renice(1)

For 10.10:

Arguments are evaluated more strictly.
Error messages have been added:
- One error message asks you to enter an unsigned decimal process/group ID whenever you enter an invalid process/group ID.
- One error message informs you if the process/group ID entered is out of range.

rm(1)

Changed to comply with XPG4.
Will descend to arbitrary depth in file hierarchy without path length limitation.
Now conforms to XPG4 specifications:

Changed options:

Option          Changed Behavior
===========================================================
-f              Any previous occurrence of the -i option
                will be ignored.
-i              Any previous occurrence of the -f option
                will be ignored.
-r, -R          (Minor changes on encountering directories
                without read, write or execute permission.
                See the manpage for details.)

rmdel(1)

For 10.10:

Now conforms to XPG4 specifications.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
Silently ignores unreadable files.
When "-" is specified as an argument, SCCS directory names given on standard input are processed (they were ignored on earlier releases).

rmdir(1)

Changed options:

Option          Changed Behavior
===========================================================
-f              Any previous occurrence of -i option
                will be ignored.
-i              Any previous occurrence of -f option
                will be ignored.

sact(1)

For 10.10:

Now conforms to XPG4 specifications.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
When "-" is specified as an argument, SCCS directory names given on standard input are processed (they were ignored on earlier releases).
Unreadable files are silently ignored.
Input buffers of size BUFSIZ have changed to LINE_MAX.
When more than one file (operand) is given on the command line and an error occurs in one of the files, the utility continues processing the other file and exits with a non-zero exit status.

sar(1)

sar has a new option, -S, to report select calls.

sar -m reports message and semaphore activities. This report includes the number of System V msgrcv() calls per second and the number of System V semop() calls per second. By explicitly specifying the new -S option with -m, you can make sar report the number of System V select() calls per second as well.

The default behavior of sar -m has not changed.

sccs(1)

For 10.10:

Now conforms to XPG4 specifications.
The relative path name can be assigned to the PROJECTDIR environment variable.

For 10.01:

Front end to the programs comprising the Source Code Control System. Provides short cuts to running the SCCS commands directly.

sed(1)

For 10.10:

Now conforms to XPG4 specifications.
Error messages are redirected to stderr.
sed(1) handles eight-character labels.
A call to sed -f script_file accepts a script file consisting of editing commands, one per line.
When the editing command D deletes the whole current pattern space, the next cycle of editing commands is applied to the remaining pattern space.
The editing command H appends to the hold space a newline followed by the contents of the pattern space.
r pathname returns with zero exit status for correct operation.
w pathname returns with zero exit status for correct operation.
The editing command x switches the contents of the pattern and hold spaces.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

For 10.0:

General usage message displayed in response to invalid options.
Improvements to l output.
Invalid regular expressions not processed (for example the expression [x[=] will not be processed as of 10.0).
Only printable multi-byte characters printed; non-printable characters displayed in octal.

sh-posix(1)

For 10.10:

Two new signals, SIGXCPU and SIGXFSZ are available in POSIX sh (/usr/bin/sh and /sbin/sh).
The history file has a new internal magic number that causes a pre-10.10 history file to be discarded. If you use multiple versions of HP-UX that NFS-mount the same directory containing the history file (usually the home directory), you may want to have a separate history file for each HP-UX version by setting the proper HISTFILE parameter. Read the sh-posix(1) manpage WARNING section for more details.
The file descriptors used internally by the POSIX shell are moved to numbers 24 through 30.
The cd built-in command — if the new current directory is found using a non-null pathname from shell parameter CDPATH, an absolute path of the new current directory is written to standard output, regardless of whether the shell is executing a script or non-interactive. In previous releases, the path was written only by interactive shells.
The fc -l built-in command — when using the -l option of the fc built-in command, if the argument last is omitted, the last command listed is the previous command. In previous releases, the last command listed was the fc -l command currently being executed.
The whence -v command — if a whence -v name (or "type name") generates the error "name not found", the message will be displayed to stderr. In previous releases, the message was displayed to stdout.
The getopts built-in command — whenever the shell is invoked, OPTIND will be initialized to 1.
When an I/O redirection error occurs during a call to a function, a non-interactive shell aborts. In previous releases, only the currently executing function was aborted.
The POSIX sh supports the POSIX internationalization module. You have to set the proper LC_* or LANG environment parameters to input and output the proper local languages.

Refer to the sh-posix(1) manpage for details.

sort(1)

New option:

-A: Sorts on a byte-by-byte basis using each character's encoded value. Extended (signed byte) characters will be considered negative values, and sort before ASCII characters. If you are sorting ASCII characters in a non-C/POSIX locale, this flag performs much faster.

Changed options:

Option          Changed Behavior
===========================================================
-f              Supports folding of multibyte characters,
                if folding is possible in the locale.
-t              Supports multibyte characters as field
                delimiters.

Option no longer supported:

-l (previously ignored).

split(1)

For 10.10:

Now conforms to XPG4 specifications.
split -1 returns with status zero when all files have been successfully created and an EOF has occurred in the input file.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

strings(1)

For 10.10:

Now conforms to XPG4 specifications.
strings(1) now exits with a non-zero status on failure.

strip(1)

For 10.10:

Now conforms to XPG4 specifications.
Now returns non-zero status when an error occurs, but continues processing the remaining files.

sum(1)

Change to -p option.

The checksum values provided when you specify -p are generated according to a new algorithm to ensure conformance with the latest POSIX.2 standard.

This means that checksum values will differ between 9.x and 10.x for the same input. If you need to obtain checksum values calculated by the 9.x algorithm, you can use the old version of the command, delivered with 10.x as /usr/old/usr/bin/sum. If you are using these values in a script, use /usr/old/usr/bin/sum to verify them, then update them to the 10.x values using the 10.x command.

-p now also supports piped input.

tar(1)

For 10.20:

Because of industry standards and interoperability goals, files larger than 2GB cannot be archived using tar(1). You will receive an error message if archival is attempted for a file that is larger than 2GB in size.

User and group IDs larger than 60K are not supported. Files with user/group IDs greater than 60K are archived and restored under the user/group IDs of the current process.

The fbackup and frecover command set is recommended for backing up files that are larger than 2GB or are owned by user/group IDs that are greater than or equal to 60000.

For 10.10:

New e option
Can extract multiple archives from one tape using a no-rewind device

New option:

The new option e causes tar to fail whenever extent attributes of a file are lost.

Extracting Multiple Archives

As of 10.0, tar can extract multiple archives from one tape when using no-rewind device files. This requires different steps depending on whether you are using an AT&T-style or Berkeley-style device file.

Using AT&T-style device file with no-rewind:

mt -t /dev/rmt/0mn rew      rewind to beginning of tape
tar -xvf /dev/rmt/0mn       extract first archive
tar -xvf /dev/rmt/0mn       extract second archive
tar -xvf /dev/rmt/0mn       extract third archive

Using a Berkeley-style device file with no-rewind:

mt -t /dev/rmt/0mnb rew     rewind to beginning of tape
tar -xvf /dev/rmt/0mnb      extract first archive
mt -t /dev/rmt/0mnb fsf     position to beginning of second
                            archive
tar -xvf /dev/rmt/0mnb      extract second archive
mt -t /dev/rmt/0mnb fsf     position
to beginning of third
                            archive
tar -xvf /dev/rmt/0mnb      extract third archive

Using a Berkeley-style device file with no-rewind to restore the first and third tar archive:

mt -t /dev/rmt/0mnb rew     rewind to beginning of tape
tar -xvf /dev/rmt/0mnb      extract first archive
mt -t /dev/rmt/0mnb fsf 2   position to beginning of third
                            archive
tar -xvf /dev/rmt/0mnb      extract third archive

time(1)

For 10.10:

Now conforms to XPG4 specifications.
Addition of the option -p, which provides a usage message for time(1).
Context-sensitive error message have been added to reflect the cause of errors in time(1).
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
Exit values of time(1) have changed. If the command to be timed was found, but could not be invoked, the exit value is 126. If the command to be timed could not be found, the exit value is 127.
Exit values of time(1) when a signal occurred has been corrected.

top(1)

For 10.10:

Processes whose size exceeds 99999Kb will have their size reported in megabytes, with an M suffix.
Scripts and programs that parse top output will have to be sensitive to the units in use to properly handle large processes.

tput(1)

For 10.10:

The maximum length for the input line has changed from BUZSIZ to LINE_MAX.

For 10.0:

SVR4-compatible -S option.
Improved performance.
Supports many new terminal capabilities.

New option:

-S: Allows terminal capabilities to be read from stdin.

See the manpage for details.

tr(1)

New, XPG4-compliant syntax
New -A option

New syntax:

tr [-Acs] string1 string2
tr -s [-Ac] string1
tr -d [-Ac] string1
tr -ds [-Ac] string1 string2

New option:

-A: Translates on a byte-by-byte basis. tr with this option does not support extended characters.

Changed options:

Some changes affecting -c, -d, and -s.
If -c and -d are both specified, all characters except those specified by string1 are deleted. The contents of string2 are ignored, unless -s is also specified.
The same string cannot be used for both the -d and the -s flags.
If -d is not specified, each input character or collating element found in the array specified by string1 is replaced by the character or collating element in the same relative position in the array specified by string2.
The abbreviation [.cc.] is no longer supported because multi-character collating elements no longer require special treatment.
Changes affecting the following abbreviations used to introduce ranges of characters or repeated characters into the strings:
- [:class:] or [[:class:]]
  Represents all characters belonging to the defined character class, as defined by the current setting of the LC_CTYPE locale category.
- [=equiv=]
  Can be used for string1 or string2 only in combination with the -d and -s flags.
- [a*n]
  Valid only when it occurs in string2.

tsort(1)

For 10.10:

Now conforms to XPG4 specifications.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).

uncompress(1)

For 10.10:

Now conforms to XPG4 specifications.
Now returns a value of 1 whenever uncompress fails on one of the operands. (In previous releases, a return status of 0 was returned.)
Now if the uncompress command without the -f option executes on an existing file and the file is not altered, uncompress exits with a status of 1. (In previous releases, a return status of 0 was returned.)
The XPG4 behavior is activated if you set the UNIX95 environment variable.

unexpand(1)

For 10.10:

Now conforms to XPG4 specifications.
When an error occurs processing one of the operands, processing continues with the remaining operands and the final exit status is non-zero.

uniq(1)

For 10.10:

Now conforms to XPG4 specifications.
Can now handle a maximum of 2048 characters per line (includes newline).

For 10.0:

The -s option assumes each line in the input is terminated with a new line character for purposes of comparison.

uname(1)

For 10.30:

A Future Consideration

In future releases, the uname(1) command might display an incorrect model. uname(1) is restricted to eight characters for the model number. However, some future machines will have more than eight characters for the model. If the model string is longer than eight characters, uname(1) will truncate the model string to eight characters. Therefore, code that uses uname(1) to obtain the model string should be changed to use the model(1) command.

Compatibility

Backward compatibility is not affected.

unpack(1)

For 10.10:

Now conforms to XPG4 XBD Utility Syntax Guidelines.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
The maximum file name length changed to take NAME_MAX - 2 as the maximum filename length.
The maximum path length has changed to MAXPATHLENGTH.

uucp(1)

For 10.01:

As a consequence of the new NFS file-sharing paradigm, the uucp(1) and cu(1) commands are now supported on client systems.

This change applies to all commands and scripts in the UUCP fileset, as well as to the commands in the SYSCOM fileset:

The files in the UUCP fileset are as follows:

uucp
uux
uulog
uupick
uustat
uuto
uuls
uusnap
uusnaps
mkuupath
uucpd
getx25
SetUp
Uutry
uucheck
uucico
uuclean
uucleanup
uugetty
uuname
uusched
uusub
uuxqt
dialit
remote.unknown
uudemon.admin
uudemon.cleanu
uudemon.hour
uudemon.poll
opx25
clrsvc

The files in the SYSCOM fileset are as follows:

cu
ct
uupath
kermit
umodem
vt
vtdaemon
vtgateway
vtserver

In a 9.x "DUX" cluster, all systems have a shared root and sharing directories. ct and cu can be run only from a root server and therefore can utilize only root server physical ports. If you attempt to run cu on a 9.x cluster client, this message is returned: cu must be run on the root server. UUCP physical connections are restricted to the root server. UUCP can be run from a client, but is actually using root server UUCP configuration, physical ports, and device files.

In 10.01 clusters, all systems have a private root directory, and all other directories are private by default. All systems (standalone, server, clients) are treated identically. UUCP, ct, and cu are supported on any system (standalone, server, or client). There is no distinction between the different system configurations — standalone, server, diskless client, or client with local disk. Consequently, each system has his own private configuration, log files, lock files, spool and work files. The only shared files between server and clients, are the command executables, backend executables, system administration commands, and startup/shutdown scripts. When you execute a command, the command is accessing the physical ports and associated device files on the system where the command was issued (for example, if you run UUCP from a client, you are using the client device files, physical ports and UUCP configuration).




	NOTE: To run UUCP from an NFS client and use the server device files, physical ports, and UUCP configuration (that is, produce 9.0 behavior), `telnet` to the server, and run UUCP.

uuencode(1)

For 10.10:

Now conforms to XPG4 specifications.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).

uulog(1)

For 10.10:

Now conforms to XPG4 specifications.
If a system is not specified as the command argument with the -s option, the exit code is 2. In previous releases, the return value was 0.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

uupick(1)

For 10.10:

Now conforms to XPG4 specifications.
uupick(1) now takes care of invalid parameters such as:
- when the argument to -s is NULL. That is, the system name is not specified.
- when the number of parameters exceeds two.
The error messages are now redirected to stderr.
In case of errors, the utility exits with a non-zero exit value.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

uustat(1)

For 10.10:

Now conforms to XPG4 specifications.
If no system is specified as the command argument with the -s option, error messages are written to stderr with a return value of 1. In previous releases, no error messages were written and the exit status was 0.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

uuto(1)

For 10.10:

Now conforms to XPG4 specifications.
The exit code changed to a non-zero value if there is an invalid filename argument.
The error message is printed to stderr instead of stdout.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
If a FIFO special file is specified as an argument, the command exits with an exit code 2. In previous releases, this was ignored.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

uux(1)

For 10.10:

Now conforms to XPG4 specifications.
Addition of the -p option.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
The XPG4 behavior is activated if you set the UNIX95 environment variable.

val(1)

For 10.10:

Now conforms to XPG4 specifications.
The limit on the number of files that can be specified on the command line has been removed. In previous releases, the number was limited to 50.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).

vi(1)

For 10.20:

vi(1) is XPG4 compatible. This compliance is achieved by incorporating the changes listed below. These changes will occur only if the UNIX95 environment variable is set.

Changes:

The abbreviation or ab command now allows abbreviating recursively.
The size of the tmp files created when vi, with the LANG environment variable set to any language other than C, was previously very large. At 10.20, this is no longer the case.

* The XPG4 changes include the following :

If the implementation supports the ctags utility and when -t tagstring is specified with either the -c command or + command, vi processes -t tagstring first and then executes the command.
When P or p is entered in the command mode and the unnamed buffer does not contain complete lines, vi inserts text from the unnamed buffer before the current cursor position and positions the cursor to the last character of the inserted text.
When x is a lowercase character in the POSIX locale and the buffer referenced by x contains lines from a previous put or yank command, line put places the lines in the buffer referred to by x after line (the default is the current line) and sets the current line indicator to the first of the inserted lines.
All error and warning messages should be written to standard error.
When the warn option is set, a ! command is issued, and the contents of the current buffer is modified, vi writes a warning to standard error before executing the ! command.
When W is entered in command mode and there is no following bigword on the current line, vi moves to the first character of the first bigword on the next line that contains a bigword.
When count e is entered in command mode and the cursor position is at the end of a word, vi moves the cursor to the last character of the count-th following word (the default is the next word).
When U or u is entered in command mode and the autoindent option is not set, vi restores the line to its state before the cursor was last moved and positions the cursor to column position one.
When count { is entered in command mode and there are count paragraphs before the current cursor position, vi moves backward to the beginning of the count-th preceding paragraph, as defined by the ex paragraph option. The current line is set to the line containing the beginning of that paragraph. The current column is set to the first nonblank character of that paragraph.
When control-D is entered in command mode and the line movement would place the current line after the end of the file, the movement does not occur. The terminal is alerted and the current position is not changed.

Impact

The above changes impact the backward compatibility of the vi(1) command. These changes, however, will come into effect only when the UNIX95 environment variable is set.

Compatibility

The changes made will render this command binary incompatible. The incompatible behavior will be seen only when you set the UNIX95 environment variable.

For 10.10:

The addition of the -c option, which is equivalent to the + command.
Now reports an error when the -s option is used.

wc(1)

For 10.10:

Now conforms to XPG4 specifications.
Now accepts vertical tab (\v), form feed (\f), and carriage return (\r) as delimiters for words.
The output of wc is in this format: (Number of lines) (Number of words) (Number of characters) (file name)
This format is independent of:
- The order in which the options are specified. Previously, wc printed in the same order as the options appeared in the command line.
- The number of repeated options specified. Previously, wc printed as many line, word, character, byte counts as the number of options appeared in the command line.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

what(1)

For 10.10:

Now conforms to XPG4 XBD Utility Syntax Guidelines.
"" as an argument indicates the end of options and the beginning of operands. Any arguments following the "" that starts with a "-" are considered to be operands (not options).
Returns an error for invalid options.

who(1)

For 10.10:

Now conforms to XPG4 specifications.
The XPG4 behavior is activated if you set the UNIX95 environment variable.
Changes:
Option
Description
-H
Displays the header if used with the -d,-r and -b options.

Displays the header before data if used with the -a option.

Displays the state of the header if used with the -T option.
-T
Will not display information about the IDLE,PID and COMMENTS fields.

Will not display information about PID and COMMENTS if used with the -u option.

When used with -u options, displays the terminal state.
-s
Is mutually exclusive with the -T,-a and -d options.
-q
If used, other options will be ignored.
who am i
Displays usage if called with option(s).
who am I
Displays usage if called with option(s).

xargs(1)

For 10.10:

Addition of -I, -E, and -L options.
The -i, -e, and -l options have optional arguments.
Exit codes are returned on non-zero failures.
The command can take input arguments up to 2048 (LINE_MAX) characters.
If the utility specified on the command line was found, but could not be invoked, xargs returns an exit code of 126.
The command returns a value of 127 when the utility could not be found.
The exit code of a signal to xargs is within the range of 0 to 127 or -1. In previous releases, the exit code was greater than 128.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

zcat(1)

For 10.10:

Now conforms to XPG4 specifications.
zcat returns a value of 1 whenever it fails on one of the operands. In previous releases, it returned a status of 0.
The XPG4 behavior is activated if you set the UNIX95 environment variable.

Changed Commands in Section 1

Technical documentation

» Table of Contents

» Index

adjust(1)

admin(1)

ar(1)

asa(1)

at(1)

awk(1)

bc(1)

cal(1)

cancel(1)

cat(1)

chown(1), chgrp(1)

cksum(1)

compress (1)

cp(1)

cpio(1)

crontab(1)

csh(1)

ctags(1)

cu(1)

date(1)

dd(1)

diff(1)

doschmod(1), etc.

du(1)

echo(1)

eucset(1)

ex/vi(1)

expand(1)

expr(1)

find(1)

findmsg(1)

Impact

Performance

ftio(1)

Compatibility

Alternatives

gencat(1)

getconf(1)

grep(1), egrep(1), fgrep(1)

help(1), sccshelp(1)

iconv(1) and iconv(3)

Impact

id(1)

iostat(1)

join(1)

locale(1)

ksh(1)

lex(1)

lp(1), lpadmin(1)

lpstat(1)

ls(1)

m4(1)

mail(1)

make(1)

man(1)

mesg(1)

mkdir(1)

mkfifo(1)

mm(1)

more(1)

mt(1)

mv(1)

nice(1)

nl(1)

nljust(1)

nohup(1)

nroff(1)

od(1)

pack(1)

patch(1)

pathchk(1)

passwd (1)

paste (1)

pax(1)

pr(1)

prs(1)