Hello,
@Martin Balaz, completely correct.
For this fix you have to remove indeed first the old fix with emgr -r -L 993015sa
The new fix wil NOT remove the this fix automatically.
addition: if you like to verify that your efix is not tampered or corrupted after downloading it. Then you can download the efix + the .sig file.
Instead of using emgr you can use emgr_sec /path/efixname.Z
In the same directory you have to store the .sig file together with the efix.
If you like check or "see" what is installed / replaced by emgr or emgr_sec
You can use emgr -lv3
Greetings Christian Sonnemans
------------------------------
Christian Sonnemans
Tactical Unix system engineer
ASN Bank
Den Bosch
------------------------------
Original Message:
Sent: Tue July 15, 2025 08:41 AM
From: Martin Balaz
Subject: How can we install same kind of efix if one already installed without removing the previous one
Hi, if you install an efix using emgr you can see if this efix is enabled to be automatically removed. If you want to see that before doing the install you can also use:
emgr -e >ifix> -p ( aka preview)
Among the (long) output you will see "efix enabled for automatic removal or not enabled". You have to look up all ines and you will find it.
This will als hold true if you are (trying to) installing a Service Pack level or an TL that contains locked files. if enabled install will run through otherwise you will have to remove efix first.
rgds
Martin
------------------------------
Martin Balaz
Original Message:
Sent: Wed July 09, 2025 06:16 AM
From: Manoj Kumar
Subject: How can we install same kind of efix if one already installed without removing the previous one
And will that be IBM who will generate the efix in that way so that it can remove automatically and installed the new one? I think for other such fixes we have that functionality but in case of openssl/openssh we have to do it manually removed.
------------------------------
Manoj Kumar
Original Message:
Sent: Wed July 09, 2025 03:20 AM
From: Srikanth Thanneeru
Subject: How can we install same kind of efix if one already installed without removing the previous one
The previous efix locks certain binaries/files, so it must be removed before installing the latest one. To simplify this process, the latest efix can be generated by referencing the previous efix in its table. This ensures the old efix is automatically removed during installation of the new one.
------------------------------
Srikanth Thanneeru
Original Message:
Sent: Tue July 08, 2025 08:01 AM
From: Manoj Kumar
Subject: How can we install same kind of efix if one already installed without removing the previous one
Hi Team,
How can we install same kind of efix if one already installed without removing the previous one which is already installed.
Like we already have openssh efix 993015sa and there is new release of this efix 3272899ma. So to install the 3272899ma we have to remove the previously installed efix which is 993015sa. Is there any way we can install the new one without removing the other. This situation happen frequently specially for openssh/openssl efixes.
Any thought suggestion please.
------------------------------
Manoj Kumar
------------------------------