IC62621: ADMINISTRATION CENTER, "CLIENT NODES" TABLE DISPLAYS "COULD NOT DISPLAY THE PORTLET, THE PORTLET MAY NOT BE STARTED"

APAR status

• Closed as fixed if next.

Error description

• In addition the seeing the message, "Could not display the
  portlet..." in red-font, check the Admin Center's systemOut
  log (under tsmServer, under logs, in the ISCW61 installation
  tree) for the following series of messages:
  
  Nested Exception is java.lang.StringIndexOutOfBoundsException
   at java.lang.String.charAt(String.java:415)
   at com.tivoli.dsm.admcntr.util.qftable.QfTableJavascriptFac
  tory.GetRangeKeys(QfTableJavascriptFactory.java:505)
   at com.tivoli.dsm.admcntr.util.qftable.QfTableJavascriptFac
  tory.getRowsInJavascript(QfTableJavascriptFactory.java:214)
   at com.tivoli.dsm.admcntr.util.qftable.QfTableJavascriptFac
  tory.getRowsInJavascript(QfTableJavascriptFactory.java:394)
   at com.tivoli.dsm.admcntr.comp.nodes.NodesTableJspBean
  .getNodesInJavascript(NodesTableJspBean.java:468)
  
  Please note that the messages listed here must be present in
  the systemOut log for the symptoms of an encountered issue to
  match the problem  described in this APAR.
  

Local fix

• The error is due to the way the list of all clients nodes is
  grouped into pages that appear in the Client Nodes table. The
  error can be circumvented by changing the number of nodes that
  appear on a single page. Registering additional nodes to a TSM
  server will change the groups used to represent a page when
  displaying the Client Nodes table. By changing this page
  grouping used during display, this problem can be circumvented
  because memory use and alignment will be different.   These
  nodes will act as placeholders to shift the point where one
  page is ended and another starts. These nodes must have names
  that place them on a page prior to the page with the error,
  so their names should be near the beginning of the alphabet
  or earlier in sequence than the page that encountered the error.
  
  
  A similar effect can be acheived by deleting nodes that are no
  longer used, if their names appear before the page with the
  error.
  
  To determine the page with the error, it may be helpful to
  turn on Administration Center tracing. Look for the error
  messages listed in the error description.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager Administration    *
  *                 Center users of Version 6.1                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: See error description.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This problem is projected to be fixed in a future version of
  the Tivoli Storage Manager server.  Note that this is subject
  to change at the discretion of IBM.
  Affected platforms:  AIX, HP-UX, Sun Solaris, Linux, and
  Windows.
  

Problem conclusion

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

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP