HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
s
swmodify(1M) swmodify(1M)
-s product_specification_file
The source Product Specification File (PSF) describes the product, subproduct, fileset,
and/or file definitions which will be added, modified, or used as input by swmodify.
The -s and -u options are mutually exclusive, the -s option cannot be specified when
the -u option is specified.
-S session_file
Execute swmodify based on the options and operands saved from a previous session, as
defined in session_file. You can save session information to a file with the -C option.
-x option=value
Set the session option to value and override the default value (or a value in an alternate
options_file specified with the -X option). Multiple -x options can be specified.
-X option_file
Read the session options and behaviors from options_file.
Operands
The swmodify command supports two types of operands: software selections followed by target selec-
tions. These operands are separated by the "@" (at) character. This syntax implies that the command
operates on "software selections at targets".
Software Selections
If a product_specification_file is specified,
swmodify will select the software_selections from the full set
defined within the PSF. The software selected from a PSF is then applied to the target_selection, with the
selected software objects either added to it or modified within it. If a PSF is not specified,
swmodify will
select the software_selections from the software defined in the given (or default) target_selection.
The
swmodify command supports the following syntax for each software_selection:
bundle
[.product[.subproduct][.fileset]][,version]
product[.subproduct][.fileset][,version]
• The = (equals) relational operator lets you specify selections with the following shell wildcard
and pattern-matching notations:
[], *, ?
• Bundles and subproducts are recursive. Bundles can contain other bundles and subproducts can
contain other subproducts.
• The
\* software specification selects all products. Use this specification with caution.
The version component has the form:
[,r <op> revision][,a <op> arch][,v <op> vendor]
[,c
<op> category][,q=qualifier][,l=location]
[,fr
<op> revision][,fa <op> arch]
• location applies only to installed software and refers to software installed to a location other than
the default product directory.
• fr and fa apply only to filesets.
• The <op> (relational operator) component can be of the form:
=, ==, >=, <=, <, >,or!=
which performs individual comparisons on dot-separated fields.
For example, r>=B.10.00 chooses all revisions greater than or equal to B.10.00. The sys-
tem compares each dot-separated field to find matches.
• The = (equals) relational operator lets you specify selections with the shell wildcard and
pattern-matching notations:
[], *, ?, !
For example, the expression r=1[01].* returns any revision in version 10 or version 11.
• All version components are repeatable within a single specification (e.g. r>=A.12, r<A.20
).
If multiple components are used, the selection must match all components.
HP-UX Release 11i: December 2000 − 3 − Section 1M−−907
___
___