Software Distributor Administrator Guide (September 2010)
The command line is most effective for:
• Quickly executing simple commands
• Executing tasks that take a long time to accomplish
• Creating commands for later execution by scripts
A typical command line might look like this:
Figure 1-15 Sample Command
command
file of
software
selections
location of
software
depot
target host
swinstall -f MySoft -s /mnt/cd @ targetB
The example shows that you have several ways to specify SD-UX behavior including
command-line options (such as -f and -s), input files (mysoft and /mnt/cd), and
target selections.
A complete list of command line components includes:
• Software selections and software selection files ((page 47))
• Target selections and target selection files ((page 49))
• Command-line options ((page 50))
• Session files ((page 52))
Each item on this list is discussed in more detail in the following sections.
1.4.1 Software Selections
Software selections let you specify software in great detail. You can also use an input
file to specify software.
1.4.1.1 Syntax
The software_selections syntax is identical for all SD-UX commands that require
it (bundle[.product[.subproduct][.fileset]][,version] and
product[.subproduct][.fileset][,version]):
• The = (equals) relational operator lets you specify selections with the following
shell wildcard and pattern-matching notations:
[ ] Square brackets—groups an expression
* Asterisk—wildcard for multiple characters
? Question mark—wildcard for a single character
For example, the following expression installs all bundles and products with tags
that end with man:
1.4 Working from the Command Line 47