LO88593: DBACCOUNTSCHECK DOES NOT REPAIR ACCOUNTS THAT HAVE THE SAME LOGIN NAME BUT DIFFERENT HASH VALUES B/C OF JVM ENCODING CHANGES
Direct links to fixes
Closed as program error.
For improved Traveler DB performance, Traveler uses a hash of the user's name (normally the canonical name) for SQL operations. This hash is generated using the bytes from the Java String which uses the default encoding specified in the JVM. If this encoding ever changes, the bytes may change which would change the hash value. If the hash value in the DB no longer matches the current hash value, the records will not be cleaned up in the Traveler DB and the user will still be shown by DbAccountsCheck as having duplicate accounts and prevent the index to prevent duplicates accounts in the future from being applied.
If the account hash value was created on Windows for example, then the environment switched to Linux, you could get different hash values due to code page differences. This is not common but could effect any lookup for the user.
The IBM Traveler server was updated to ensure a common code page used for all account Hash actions.
This fix is included in IBM Traveler 184.108.40.206 and will be included in all future releases. For the latest available maintenance information see this technote: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
NoSpecatt / Xsystem
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
LOTUS NOTES TRA
Fixed component ID
Applicable component levels