swinstall question

[Michael D'Aulerio]

I'm a littled confused by the behavior of swcopy and swinstall on my system and was hoping someone out there could explain it. I'm trying to install patch PHKL_23418 (mount(2) cumulative patch) on a B180 running HP-UX 10.20. When I tried to create a SW depot, I got an error from swcopy that it could not create the depot because the patch PHKL_16750 (SIG_IGN/SIGCLD,LVM,JFS,PCI/SCSI cumulative patch) was not in the depot. PHKL_16750 is already installed on my system but I added it to the depot anyway.

I ran swinstall and marked PHKL_23418 for install and PHKL_16750 was marked also because of dependencies. After PHKL_23418 installed, I checked the swinstall.log and swagent.log. The analysis showed that the install for PHKL_16750 was to be skipped because it was already installed on the system.

Don't swinstall and swcopy check what patches/products are installed on a system before marking products to be installed. Are there any flags I need to set or parameters I must pass to swcopy and swinstall to get them to ignore errors for patches that are already installed. This thing's got me stumped. Thanks for any help.

Mike

[Rick Garland]

The analysis phase determines if a patch has been installed already. This occurs after the patches/products are marked.

[Sridhar Bhaskarla]

Hi Mike,

When you swcopy any depot, you would need to put all the dependencies in that depot. You can overwrite it with swcopy options. Swinstall will give out a warning. This was your first problem.

Secondly, the answer is no. It is done during the analysis phase.

-Sri

[john kingsley · Accepted solution]

swinstall/swcopy don't do any checking until the analysis phase which occurs after the sofware has been marked.

There are are couple of options that you can change:

interactive:
[ ] Enforce dependency analyis errors in agent
[ ] Autoselect dependencies when marking software

command line:
-x enforce_dependencies=false
-x autoselect_dependencies=false

Be very careful when disabling dependency enforcement. SW may not work properly if dependencies have not been resolved when it is installed. However, I typically turn-off the dependency checker when I am copying patches to my patch depot.

[Cheryl Griffin]

swcopy by default will check that dependencies exist in the depot.

You can tell swcopy to ignore dependencies in the case where the dependencies are already installed:
# swcopy -x enforce_dependencies=false ....

The dependencies for PHKL_23418 include
PHCO_18563
PHCO_23844
PHKL_16750
PHKL_16959
PHKL_17857
PHKL_20610
PHKL_21594
PHKL_21660
PHNE_22506

[Michael D'Aulerio]

Thank you all.

I'm going to try the -x enforce_dependencies=false option of swcopy.

I think I'll stay away from -x autoselect_dependencies=false for swinstall for now.

[Prashant Zanwar_4]

I dont see there is any way of skipping the analysis that if the product/patches are already installed on the system.
You can also use swinstall -p -s on the patches you want to install which will tell you clearly the analysis.
You can set the options for installation in /var/adm/sw/defaults file for installation. Before that do not forget to read the patch description at ITRC.
Hope it helps
Thanks and regards
Prashant

[Michael D'Aulerio]

Thanks all. I used the -x enforce_dependencies=false option of swcopy and it works fine.