PI63502: USER LOGIN ISSUES DUE TO USER PREFERENCE DATA MIGRATED FROM 2.X OAC AND REFERENCING DB CONNECTIONS NOT ENUMERATED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• 1) Exceptions throw & caught during the bulk of the Login Action
  are not recorded clearly in the WAS logs
  2) User Preference data migrated from a 2.x OAC prevent user
  login
  3) User Preference data that references database connections not
  enumerated for the installation may cause a
  ConcurrentModificationException when the code attempts to
  reconcile the differences.
  4) Invalid database connection XML can also prevent login.
  

Local fix

• Deploy the FTM3 UI with the configuration set to point to all 4
  databases (the configuration which works), but ensure ops users
  to only use it to access Instance 1
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of Financial Transaction Manager   *
  *                 V3.0                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: User preferences data from an FTM 2.x   *
  *                      database is not compatible with FTM 3.0 *
  *                      database configured for multiple        *
  *                      database instances and prevents user    *
  *                      login.                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  User preferences data from an FTM 2.x database is not
  compatible with FTM 3.0 database configured for multiple
  database instances and prevents user login.
  

Problem conclusion

• Financial Transaction Manager has been changed as follows:
  
  The OAC now corrects the user preferences when the instance
  preference data is not found.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PI68334

Modules/Macros

• FXH00088
  

Fix information

• Fixed component name

  FTM FOR Z/OS

• Fixed component ID

  5655FT230

Applicable component levels

• R300 PSY UI40706

     UP16/09/20 P F609

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.