swinstall to alternate directory

[nancy rippey]

I need to install MQSeries 6.0 and do not want to install over the old version. The MQinstall installs to /opt/mqm and /var/mqm. I want to change the install directory to /software/mqm_6.0 but I am having problems with my swinstall.
swinstall -x autoreboot=true -x patch_match_target=true \ -s /usr/mqm/p000-L050519.v11 @/software/mqm
The errors are
ERROR: Could not apply the software selection "-s"; it is not
available from depot or root "omhq1a65:/var/spool/sw".
* Software selection failed for "omhq1a65:/var/spool/sw".
ERROR: Could not apply the software selection
"/usr/mqm/p000-L050519.v11"; it is not available from depot or
root "omhq1a65:/var/spool/sw".
* Software selection failed for "omhq1a65:/var/spool/sw".
ERROR: Could not access remote file "GLOBAL_INDEX" in software item
"". The file could not be found on the remote system.
ERROR: There is currently no installed software on host "omhq1a65" at
location "/software/mqm". (Note that you need to use "swcopy"
to manage depot software).
* Source selection failed for "omhq1a65:/software/mqm".
ERROR: Error code -1 returned from procedure CLUI_PatchMatchTarget().
ERROR: No software has been selected.
NOTE: Cannot continue the "swinstall" task.

When I run swinstall and select the depot /usr/mqm/p000-L050519.v11 it is valid and I can install

Thanks in advance.
nancy

[Steven E. Protter]

Shalom,

Back up the old installation before trying anything.

rename /usr/mqm to /usr/mqm.old

Do a normal installation.

See if both work afterwards.

You might check the documentation of the manufacturer and see if the new version will even overwrite the old or its possible to run multiple versions on the same system. Its probably true but is not a universal fact.

SEP

[nancy rippey]

They want both versions on the server at the same time. The new version install overlays the old version that's why I want the new version somewhere different.

[Alzhy]

Then why not just run "swinstall" interactively?

swinstall -x autoreboot=true -x patch_match_target=true \ -s /usr/mqm/p000-L050519.v11 @/software/mqm

is syntactically incorrect.

If the Software Depot does not offer any relocation of the destination/install directory - then you're stuck with it..

Always a good idea to back up your existing software tree or your OS first...

Note: mqm creates/installs to various directories so be extra carefull!

[spex]

Nancy,

Your syntax is off.

swinstall [XToolkit Options] [-i] [-p] [-r] [-v] [-c catalog]
[-C session_file] [-f software_file] [-J jobid] [-Q date] [-s
source] [-S session_file] [-t target_file] [-x option=value] [-X
option_file] [software_selections] [@ target_selections]

For example, to install all selections from gcc-4.1.2-hppa-11.11.depot:
# swinstall -s /path/to/gcc-4.1.2-hppa-11.11.depot \*

I am not aware of a way to change the destination. Perhaps you could roll your own depot, but that would probably violate the software terms of use, and most likely wouldn't work in the end.

The safest thing would be to back up the affected filesystems before attempting installation. Next rename /opt/mqm and /var/mqm, which will break the old version. Then install the new version. See if the new version works, then rename the new directories, restore the old directories, and see if the old version still works.

If you need to revert, you have the backup.

If your software vendor supports multiple versions on the same system, they most likely have a guide for accomplishing this.

PCS

[Bill Hassell]

Rather than experiment extensively, I would check with IBM first. There may be a number of very important reasons why multiple versions cannot exist, not the least of which is that MQseries does not properly isolate all files and directories to handle multiple versions. Although the app may "install" in /opt, you can run a simple tar -tvf on the depot file and look at all the pathnames. There are likely several that are not in /opt (ie, /var, /etc) and this will cause both versions to fail. And even if the tar list comes up clean, starting MQseries may create files and directories which cannot control.

[Dennis Handly]

The @ syntax installs to an alternate root.
The v=...,l= installs to an alternate directory. Note not all software will support either.

But your main problem is that extraneous "\".
Also these are useless for alternate roots:
-x autoreboot=true -x patch_match_target=true

The former because a reboot will be confused. The latter because nothing gets matched at all on alternate root installs, even if you ask nicely. ;-)