Direct links to fixes
APAR status
Closed as program error.
Error description
When upgrading from SSP 3.2 to 3.4.1.0 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.
Local fix
STRRTC - 350386 MB/RJ Circumvention: There is manual work around to run the convertKey.sh script
Problem summary
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.
Problem conclusion
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.
Temporary fix
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.
Comments
APAR Information
APAR number
IC87277
Reported component name
STR SECURE PROX
Reported component ID
5725D0300
Reported release
341
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-10-16
Closed date
2012-11-02
Last modified date
2012-11-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
STR SECURE PROX
Fixed component ID
5725D0300
Applicable component levels
R341 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS6PNW","label":"IBM Sterling Secure Proxy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"341","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
02 November 2012