Troubleshooting the BMC AMI Ops user interface

Troubleshooting data collection configuration

To make sure that BMC AMI Ops User Interface receives expected data, configure the following for BMC AMI Ops User Interface and the BMC AMI Ops products:

• Authorization—The Security-definitions-for-BMC-AMI-Ops-UI branch lists topics about customizing authorization for RACF, ACF2, and Top Secret.
• Alarm manager—Turn on Alarm manager and distribute alarms to be captured for the BMC AMI Ops User Interface dashboards and alarms. For more information about Alarm Management, see Using-Alarm-Management. For information about setting up configuring alarms for distribution, see Working with Alarm Management parameter files.
  
• HFSPATH configuration—Configure the BMC AMI Ops CAS and PAS to point to the correct HFSPATH entries. For more information, see Identifying a file system to a CAS.

Troubleshooting Java configuration

Issue

Your BMC AMI Ops UI job STDOUT log shows the following error message:

Explanation

The error message indicates that the BMC AMI Ops UI environment is not correctly pointing to the Java 8 (31-bit or 64-bit) for one of the following reasons:

1. You applied BP00471 and the IBM SDK Java 8.0 (31-bit or 64-bit) is not in the default /usr/lpp/java/J8.0 directory.
2. Your server is pointing to the correct Java directory, but updates to the Java package changed the Java SDK library location in your mainframe.

Resolution

To resolve this error if you have not yet applied PTF BP00471, apply the PTF and restart the server.

If you still see the error, your server is probably not in the default directory. Perform the following steps:

1. Open the MUXSYMLK job and update the installation path for the BMC AMI Ops UI.
   Use the absolute path to the Java 8 (31-bit or 64-bit) directory in your environment.
2. Run the MUXSYMLK job and make sure it executes with return code 0.
3. Restart the started task for the BMC AMI Ops UI.

Troubleshooting Java Virtual Machine heap size

Issue

You get the following error when working on a view:

Explanation

The parameter for Java Virtual Machine (JVM) heap size is set to a min of 256m and a max of 512m as the default memory. When MUXTC runs out of memory the error message is displayed.

Resolution

Increase the JVM heap size that is located in the BMCSAMP dataset in MUXTCENV member.

1. To increase the JVM heap size, in the following default parameter:

   IJO="$IJO -Xms256m -Xmx512m"

   • Replace -Xms256m with Xms512m
   • Replace -Xmx512m with -Xmx1048m
2. Now stop the MUXTCJCL started task and restart.
   This restarts the server.