swmodify.1m (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

swmodify(1M) swmodify(1M)

NAME

swmodify - modify software products in a target root or depot

SYNOPSIS

swmodify [-d|-r][-p

][-u][-v][-V][-a attribute =[value ]] [

-c catalog ][-C session_ﬁle ]

[

-f software_ﬁle ][

-P pathname_ﬁle ][-s product_speciﬁcation_ﬁle|[

-S session_ﬁle ]

[

-x option=value ][-X option_ﬁle ][software_selections][

@ target_selection]

Remarks

For an overview of all SD commands, see the sd(5) man page by typing

man5sdon the command line.

DESCRIPTION

The

swmodify command modiﬁes the deﬁnitions of software objects installed into a primary or alter-

nate root, or available from a software depot. It supports the following features:

• adding new objects - The user can add new bundles, products, subproducts, ﬁlesets, control ﬁles,

and ﬁles to existing objects (which will contain them).

• deleting existing objects - The user can delete existing bundles, products, subproducts, ﬁlesets,

control ﬁles, and ﬁles from the objects which contain them.

• modifying attribute values - The user can add an attribute, delete an attribute, or change the

existing value of an attribute for any existing object. When adding a new object, the user can at

the same time deﬁne attributes for it.

• committing software patches - The user can remove saved backup ﬁles, committing the software

patch.

With the exception of control ﬁles,

swmodify does not manipulate the actual ﬁles that make up a pro-

duct (ﬁleset). The command manipulates the catalog information which describes the ﬁles. However,

swmodify can replace the contents of control ﬁles.

Common uses of

swmodify include:

• adding ﬁle deﬁnitions to the existing list of ﬁle deﬁnitions in a ﬁleset. Example: If a ﬁleset’s con-

trol scripts add new ﬁles to the installed ﬁle system, the scripts can call

swmodify

to "make a

record" of those new ﬁles.

• changing the values of existing attributes. Example: If a product provides a more complex

conﬁguration process (beyond the SD conﬁgure script), that script can set the ﬁleset’s state to

CONFIGURED upon successful execution.

• deﬁning new objects. Example: to "import" the deﬁnition of an existing application that was not

installed by SD, construct a simple PSF describing the product. Then invoke

swmodify to load

the deﬁnition of the existing application into the IPD.

Options

swmodify supports the following options:

-d Perform modiﬁcations on a depot (not on a primary or alternate root). The given

target_selection must be a depot.

-p Preview a modify session without modifying anything within the target_selection.

-r Performs modiﬁcations on an alternate root directory, which must be speciﬁed in the @

target_selections option. (This option is not required for alternate root operations but is

maintained for backward compatibility. See the Alternate Root Directory and Depot

Directory heading in sd(5) for more information.)

-u If no -a attribute =value options are speciﬁed, then delete the given software_selections

from within the given target_selection. This action deletes the deﬁnitions of the software

objects from the depot catalog or installed products database.

-a attribute options are speciﬁed, then delete these attribute deﬁnitions from the given

software_selections (from within the given target_selection).

-v Turn on verbose output to stdout.

-V List the data model revisions that this command supports.

HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1

Summary of content (10 pages)

PAGE 1
swmodify(1M) swmodify(1M) NAME swmodify - modify software products in a target root or depot SYNOPSIS swmodify [-d|-r] [-p] [-u] [-v] [-V] [-a attribute =[value ]] [-c catalog ] [-C session_file ] [-f software_file ] [-P pathname_file ] [-s product_specification_file | [-S session_file ] [-x option=value ] [-X option_file ] [software_selections] [@ target_selection] Remarks For an overview of all SD commands, see the sd(5) man page by typing man 5 sd on the command line.
PAGE 2
swmodify(1M) swmodify(1M) -a attribute [=value ] Add, modify, or delete the value of the given attribute . If the -u option is specified, then delete the attribute from the given software_selections (or delete the value from the set of values currently defined for the attribute ). Otherwise add/modify the attribute for each software_selection by setting it to the given value . Multiple -a options can be specified. Each attribute modification will be applied to every software_selection.
PAGE 3
swmodify(1M) swmodify(1M) product [.subproduct ][.fileset ][,version ] • You can 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.
PAGE 4
swmodify(1M) swmodify(1M) Values must be specified in the defaults file using this syntax: [command_name .]option =value The optional command_name prefix denotes one of the SD commands. Using the prefix limits the change in the default value to that command. If you leave the prefix off, the change applies to all commands. You can also override default values from the command line with the -x or -X options: command -x option =value command -X option_file The following keywords are supported by swmodify.
PAGE 5
swmodify(1M) swmodify(1M) • INDEX.gz or INFO.gz exist on the source depot. • INDEX.gz or INFO.gz are not older than the corresponding uncompressed INDEX or INFO files. The uncompressed INDEX or INFO file is accessed by the source agent if any problem occurs when accessing, transferring, or uncompressing the INDEX.gz or INFO.gz file. control_files= When adding or deleting control file objects, this option lists the tags of those control files. There is no supplied default.
PAGE 6
swmodify(1M) swmodify(1M) logfile=/var/adm/sw/swmodify.log Defines the default log file for swmodify. loglevel=1 (for direct invocation) loglevel=0 (for invocation by a control script) Controls the log level for the events logged to the swmodify logfile, the target agent logfile, and the source agent logfile. This information is in addition to the detail controlled by the logdetail option. See logdetail for more information. A value of: 0 provides no information to the log files.
PAGE 7
swmodify(1M) swmodify(1M) Targets are usually specified in a target input file, as operands on the command line, or in the GUI. verbose=1 Controls the verbosity of a non-interactive command’s output: 0 disables output to stdout. (Error and warning messages are always written to stderr). 1 enables verbose messaging to stdout. 2 for swmodify, enables very verbose messaging to stdout. Session File Each invocation of the swmodify command defines a modify session.
PAGE 8
swmodify(1M) 1 swmodify(1M) An error occurred during the session (for example, bad syntax in the PSF, invalid software_selection, etc.) Review stderr or the logfile for details. DIAGNOSTICS The swmodify command writes to stdout, stderr, and to specific logfiles. Standard Output In verbose mode, the swmodify command writes messages for significant events. These include: • a begin and end session message, • selection, analysis, and execution task messages.
PAGE 9
swmodify(1M) swmodify(1M) FILES $HOME/.swdefaults Contains the user-specific default values for some or all SD options. $HOME/.sw/sessions/ Contains session files automatically saved by the SD commands, or explicitly saved by the user. /usr/lib/sw/sys.defaults Contains the master list of current SD options (with their default values). /var/adm/sw/ The directory which contains all of the configurable (and non-configurable) data for SD. This directory is also the default location of logfiles.
PAGE 10
(Notes) A (Notes) sA 10 Hewlett-Packard Company −1− HP-UX 11i Version 3: September 2010