Hello Ayappan,
thanks for the info.
Now the strange thing:
on one of our test systems I wasn't on the newest level for the toolbox rpm's and I could install our Control M package without any error.
I removed Control M again and updated all Toolbox RPM's to the latest level. And now the installation of Contol M fails...
So, I did a downgrade for the rpms I recently updated (one by one) and checked the installation of Control M....
As soon as I downgraded "libiconv" to 1-16-1 the installation for Control M worked fine...
Makes it any sense to you?
best regards,
Joerg
------------------------------
Joerg Kauke
Unix Administrator
COOP Switzerland
------------------------------
Original Message:
Sent: Mon November 07, 2022 08:19 AM
From: Ayappan P
Subject: Problems with installing a RPM with dnf
LIBPATH comes into play when invoked through dnf. LIBPATH will be set to "/usr/opt/rpm/lib:/opt/freeware/lib:/usr/lib:/lib" by dnf.
------------------------------
Ayappan P
Original Message:
Sent: Mon November 07, 2022 07:23 AM
From: Joerg Kauke
Subject: Problems with installing a RPM with dnf
Dear team,
I'm struggling to install a RPM package via dnf.
We build our own package to install the Control M agent on our systems.
With this package we create a filesystem, unpack the tar files to with directory and start the Control M installation script.
If I try to install it with dnf the Control M install-script fails with following message:
*** The operating system is not ready to run Java. ***
*** Please consult your OS documentation and check that all appropriate patches are installed. ***
Control M brings its own java environment within the tar files, but seems not to find the files.
Installing the same package directly with rpm -ihv works well without any error.
[ Starting automated installation ]
[ Starting to unpack ]
[ Processing package: Check pre-requirements for Control-M/Agent ]
[ Processing package: Control-M/Agent files ]
[ Processing package: Control-M/Agent JRE files AIX ]
[ Processing package: Configure Control-M/Agent ]
[ Processing package: Create softlinks for Control-M/Agent ]
[ Processing package: Start and enable Control-M Agent ]
[ Processing package: The installed-versions.txt update. ]
[ Processing package: The installation log file: /opt/ctm/ctmagp/BMCINSTALL/log/BMC_Control-M_AGENT_Install_2022.11.07.13.01.32.log ]
[ Processing package: Write uninstaller ]
[ Unpacking finished ]
[ Automated installation ended successfully ]
Installation has completed successfully.
Is there any environment variable set with dnf that could cause this problem?
Many thanks in advance for your support.
best regards,
Joerg
------------------------------
Joerg Kauke
Unix Administrator
COOP Switzerland
------------------------------