Problem determination

This topic describes components and methods that you can use to help determine what is causing your problem.

Server status

The AGENTS screen contains configuration and connectivity status of the server's components:

Download server logs

The Download Server Logs button downloads a zip file containing the compressed server logs, including:

The catalina, localhost, manager, and hostmanager logs, which are different tomcat components
The model9* logs, containing the server application's log

Sync with storage

When deleting archived, backed up, and imported data sets by using life cycle management or a CLI command, the data set might still be visible in the web UI. To update the web UI, the management server performs an automatic synchronization with the storage device every 5 minutes. Use the Sync With Storage button in the AGENTS screen to initiate the process on demand. This action requires admin permissions. A message is displayed in the AGENTS screen when the action is completed.

Output DD description

DD Card	Description
SYSOUT	JZOS related information during startup
STDOUT	Agent—All messages, according to the debug level defined in the relevant logging.properties configuration file The default level is INFO. Life cycle management—BMC AMI Cloud messages
UTILMSGS	Life cycle management: utility messages

Where to look for error messages

Operation	Where to look	Notes
Automatic recall	Agent’s STDOUT DD	When automatic recall is initiated, the requesting address space waits for up to 25 seconds (can be configured) for the recall to complete. If the recall does not complete within this time limit, a message is issued and the request is cancelled. The messages in the agent’s log specify the reason for failure.
CLI	Agent’s STDOUT DD	When encountering a problem in the CLI, full error messages appear in the agent’s log.
Backup/archive/ restore/recall	UI Backup Log	The backup log contains the original output of the utilities invoked by BMC AMI Cloud.
Server issues including policy run	Policy Run LogServer’s logAgent’s STDOUT	The policy run log is accessible from the UI. The server’s logs can be downloaded from the AGENTS screen, see Server Statusfor more details.
Agent startup	SYSOUT DD STDOUT DD	If the agent ends with RC=102, it might suggest an issue with the model9-stdenv.sh file. Add the LOGLVL='+T' parameter to the agent PROC, restart the agent, and search for errors under the JVMJZBL1005I message in the SYSOUT DD.