IJ48958: SOMETIMES WHEN THE RECORD IS UPDATED BY ANOTHER USER, MAXSESSION RECORDS REMAIN IN DATABASE EVEN AFTER A LOGOUT

APAR status

• Closed as program error.

Error description

• PROBLEM DESCRIPTION:
  
  Sometimes when the record is updated by another user, MAXSESSION
  records remain in database even after a logout.
  
  STEPS:
  
  Example:
  
  1.) Login to Maximo.
  2.) Check the MAXSESSION record.
  3.) Logout
  4.) Make sure that the MAXSESSION record is deleted.
  
  System Information:
  Tivoli's process automation engine 7.6.1.2
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Sometimes when the record is updated by another user,        *
  * MAXSESSION records remain in database even after a logout.   *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: Release 9.0
  

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:

Fix information

• Fixed component name

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels