Ignite-UX Custom Configuration files

manage_index -t -s script

_file_name [-p] [-v] [-i index_filename]

manage_index -w -c cfg

_clause_name [-v] [-i index_filename]

manage_index -x -c cfg

_clause_name [-v] [-i index_filename]

Note:

The examples presented are for illustration purposes only; they show the

intended purpose

of the command and use fictional configuration files,

index files, and scripts.

Although the –p (preview, make no changes) and –v (verbose) options are available to most or all

forms of manage_index, they are not discussed with any of the examples.

Adding a configuration file to a clause or "release"

When you need to add a configuration file to a clause or release you need to use the –a option.

The –i option must be given a fully qualified path if it is used (it cannot be relative).

manage_index -a -f config_filename [-c cfg_clause_name| -r release]

[-p] [-v] [-i

index_filename]

Neither the –c nor –r options are required. If you use the –c option, you can explicitly name the

configuration clause to which to add the configuration file. If you use the –r option to give an

HP-UX release identifier (for example, B.11.23), the configuration file will be added to each

configuration clause that satisfies one of the following conditions:

 One of the configuration files in a cfg clause defines the release keyword with a value that

matches the release identifier given with the –r option.

 One of the configuration files in a cfg clause starts with the path

/var/opt/ignite/data/Rel_, and the value of the release identifier immediately after it

matches the release identifier given with the –r option.

 One of the configuration files in a cfg clause starts with the path /opt/ignite/data/Rel_,

and the value of the release identifier immediately after it matches the release identifier given

with the –r option.

Without the –c or –r option, the value of the release identifier is determined in the same way that

clauses are matched with the –r option. The following, in order, is performed to try to determine

the release identifier that will be used:

 The configuration file defines the release keyword, and the value of the release keyword provides

the value for the release identifier.

 The configuration file starts with the path /var/opt/ignite/data/Rel_, and the value of the

release identifier from this path provides the value for the release identifier.

 The configuration file starts with the path /opt/ignite/data/Rel_, and the value of the

release identifier from this path provides the value for the release identifier.