When Igniting From An Archive, Why Do I Get Numerous Samreg Errors ?

1.	When Igniting From An Archive, Why Do I Get Numerous Samreg Errors ?
Answer» The problem is that the SAM filesets have not been configured when certain PRODUCTS are TRYING to REGISTER themselves with SAM. The WORKAROUND is as follows: Place this configuration stanza in "/var/opt/ignite/config.local" or directly in the configuration file with the core sw_source: sw_source "core" { post_load_cmd += " swconfig -xautoselect_dependencies=false / -xenforce_dependencies=false SystemAdmin.SAM " } The problem is that the SAM filesets have not been configured when certain products are trying to register themselves with SAM. The workaround is as follows: Place this configuration stanza in "/var/opt/ignite/config.local" or directly in the configuration file with the core sw_source: sw_source "core" { post_load_cmd += " swconfig -xautoselect_dependencies=false / -xenforce_dependencies=false SystemAdmin.SAM " }

Answer»

The problem is that the SAM filesets have not been configured when certain PRODUCTS are TRYING to REGISTER themselves with SAM.

The WORKAROUND is as follows:

Place this configuration stanza in "/var/opt/ignite/config.local" or directly in the configuration file with the core

sw_source:
sw_source "core"
{
post_load_cmd += "
swconfig -xautoselect_dependencies=false /
-xenforce_dependencies=false SystemAdmin.SAM "
}

The problem is that the SAM filesets have not been configured when certain products are trying to register themselves with SAM.

The workaround is as follows:

Place this configuration stanza in "/var/opt/ignite/config.local" or directly in the configuration file with the core

sw_source:
sw_source "core"
{
post_load_cmd += "
swconfig -xautoselect_dependencies=false /
-xenforce_dependencies=false SystemAdmin.SAM "
}

Discussion