Troubleshooting

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-user-interface 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

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

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

1. You applied the latest PTF 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.

To resolve this error if you have not yet applied the latest PTF, 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 server started task and update the installation path for the BMC AMI Ops User Interface.
2. Run the server started task and make sure it executes with return code 0.
3. Restart the server started task for the BMC AMI Ops User Interface.

• 
  
  • Default started task names by servers
    • AMIAPSRV—for application server
    • AMIDSSRV—for registry service
    • AMIMOSRV—for monitor service

Troubleshooting Java Virtual Machine heap size

Issue

You get the following error when working on a view:

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 AMIMOSRV runs out of memory the error message is displayed. runs out of memory the error message is displayed.

Increase the JVM heap size that is located in the BMCSAMP dataset in MUXMONEV 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 AMIMOSRV started task and restart.
   This restarts the server.

Accessing different components of BMC AMI Ops User Interface components in different environments in the same browser

This topic describes how to move component connection from one BMC AMI Ops User Interface to other BMC AMI Ops User Interface, so that you can view this component in the same browser along with the existing components from the other BMC AMI Ops User Interface.

Connect both the components by using one of the following procedures:

Configuring the components from AMICMNEV member

To connect the component (BMC AMI Ops Monitor or BMC AMI Manager) from one environment (suppose Env#1) to another (suppose Env#2), configure the AMICMNEV member as follows: 

1. Open AMICMNEV member in UBBSAMP in Env#2 for editing.
2. Copy the following values from the UBBSAMP dataset's AMICMNEV member in Env#2 to the AMICMNEV member in Env#1:
   • JWT
   • AMIDSC_PORT
   • AMIDSC_PORT_TYPE

   • AMIDSC_HOST
     

     Important

     If the Discovery server is on a remote system, use the BMC AMI Ops UI Discovery server host name and not the localhost.

   • AMIDSC_SECURED
   • AMIDSC_UNSECURED

Configuring the components from JCL

Configure the component (BMC AMI Ops Monitor or BMC AMI Manager) from Env#2 JCL by pointing it to the common member in Env#1.

For example, change the AMICMNEV member in the BMC AMI Manager JCL in Env#2 UBBSAMP to the one that is used in AMICMNEV member in Env #1 UBBSAMP.

Troubleshooting insufficient authority

When setting up the started tasks required for the BMC AMI Ops User Interface, an error occurs in the started task that disables the permission for the users to change the file attributes. 

To write to the log, a user must have the permission to Write. During installation, all the file systems have Read and Write permissions.

To change the permissions, perform the following steps:

1. Enter tso omvs command on mainframe command prompt.
2. Go to run time file system directory location.
   For example,</u/MAINVIEW/ospui20>
3. Enter chmod 775 <fileName>.
   For more information on chmod, see IBM's chmod - Change the mode of a file or directory topic.