IJ33436: PRESENTATION CACHE RELOAD DURING ADMIN MODE PREVENTS JVM FROM EXITING ADMIN MODE

APAR status

• Closed as program error.

Error description

• Description
  Admin mode will get stuck under certain circumstances when
  specific series of steps takes place.
  A user making a screen change in Application Designer may
  prevent Admin Mode (either going in or out of admin mode) from
  working.
  
  STEPS TO REPRODUCE:
  initially this was thought to require a cluster configuration ,
  however the developer has advised it can be created in a single
  jvm environment.  Below are steps for both:
  
  Cluster:
  1) Have a cluster (at least 2 JVMs).
  2) Login to the app on each JVM.
  3) On one JVM, go to Database Configuration. Open the Manage
  Admin Mode dialog, but don't turn it on yet.
  On the other JVM go to Application Designer and open the Asset
  application. Open the properties dialog of an attribute on the
  list tab (such as Description) and provide a label (say Test).
  Do not save yet
  4) Turn on admin mode in Database Configuration.
  
  5) Continue refreshing this until you see Admin Mode on
  completed
  6) Quickly jump to your application design window and save your
  application designer changes.
  
  7) Admin mode on the app designer jvm will never get ON and you
  won't be able to turn Off admin mode on the other jvm  You can
  verify this by running sql against the serversession table
  >> SELECT serverhost, servername, active, reloadcache, adminmode
  FROM serversession
  
  When this occurs, the JVM where the user was in application
  designer will not enter admin mode no matter how long you wait.
  You have to restart for it to take effect.
  
  Single JVM:
  1) Go to Aplication Designer, bring up an app, bring up
  Properties for any field, change the label but do not save
  2) Using a sql tool, simulate ADMINMODE(ON) being set by another
  JVM:
  >> update serversession set reloadcache='ADMINMODE(ON)';
  
  commit;
  
  3) Back to the Application Designer, save the label change.
  
  4) You will observe that the SERVERSESSION.RELOADCACHE is set
  to null, and admin mode will never be turned on.
  
  RESULTS:
  Admin mode will not come on.
  
  EXPECTED RESULTS:
  
  Admin mode should get enabled
  
  PRODUCT VERSION:
  7.6.1.1
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * PRESENTATION CACHE RELOAD WIPED OUT DURING ADMIN MODE        *
  * PREVENTS JVM FROM EXITING ADMIN MODE                         *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: release\fix pack for Release 7.6.1.3 Product
  

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

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels

• R761 PSY

     UP