Closed as program error.
When upgrading from SSP 3.2 to 184.108.40.206 the idmb.enc file is not automatically upgraded to the new idmb2.enc version file, this results in the SSP being unable to start if configured to use an HSM device.
STRRTC - 350386 MB/RJ Circumvention: There is manual work around to run the convertKey.sh script
The new <installdir>/conf/system/idmb2.enc provides a greater encryption level, and without the new file, the system will not start when running an HSM device. Without HSM, the idmb2.enc file is automatically created during the first system startup after the upgrade.
Updated the InstallAnywhere upgrade logic to silently create the idmb2.enc file from the idmb.enc file during an upgrade. If the file is created, it then goes on to update the self-bootstrap file sb.enc with the higher encryption level.
Run the bin/convertKey.sh script to create the idmb2.enc file and update the sb.enc file if it does not happen automatically during the upgrade.
Reported component name
STR SECURE PROX
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
STR SECURE PROX
Fixed component ID
Applicable component levels
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.