After you run the following command to add apps_1203_cfg to the cfg clause, you can install any applications that are in the depot:

#manage_index -a -f /var/opt/ignite/data/Rel_B.11.11/apps_1203_cfg \ -c "Custom B.11.11 installation using SD"

An example problem

It is often helpful to examine a real life problem. The previous process created a problem by adding the applications configuration file to the same cfg clause as the core operating system (OE) depot. This issue was touched on previously and this section describes it in further detail.

In /var/opt/ignite/data/Rel_B.11.11/core_cfg is the following definition of Perl:

init sw_sel "perl" {

description = "Perl Programming Language" sw_source = "core"

sw_category = "OrderedApps"

sd_software_list = "perl,r=B.5.6.1.F,a=HP-UX_B.11.11_32/64,v=HP" impacts = "/opt" 68657Kb

} = TRUE

In /var/opt/ignite/data/Rel_B.11.11/apps_1203_cfg is this definition of Perl82:

init sw_sel "perl" {

description = "Perl Programming Language"

sw_source = "/var/opt/ignite/depots/Rel_B.11.11/apps_1203" sw_category = "OrderedApps"

sd_software_list = "perl,r=B.5.6.1.F,a=HP-UX_B.11.11_32/64,v=HP" impacts = "/opt" 68657Kb

} = TRUE

The two previous examples have the same sw_sel name so they are the same. When the second perl sw_sel clause is parsed, Ignite-UX assumes that it is an update to the existing definition of Perl already found because the clauses are named identically. The attributes of the sw_sel, such as the sw_source, are updated by the second definition, which replaces the first definition of Perl.

Perl is an always-loaded product; by default, it is marked to be loaded. There is the possibility that this could cause a problem if the application media and the core operating system (OE) media do not have the same release date. If you have newer core operating system (OE) media and a much older application depot being referenced, problems like the following could occur:

∙An older version of Ignite-UX is referenced in the applications depot and it may not support the system being installed. For example, if you create a recovery tape and the installation kernel on the tape does not support the current system it may panic on first boot when you need to recover the system.

∙The kernel drivers in the application depot are also located in the core operating system (OE) depot including SCSI, Fibre Channel, and Gigabit Ethernet drivers. If you are referencing older versions of the drivers and the system is newer, you may have hardware in the system that is not supported by the older drivers and this causes problems.

82Perl is not the only product affected by the issue. There are other products that the core operating system (OE) media and the applications media have in common.

177