If you are having queuing or performance problems, you might need to use the monitoring and controlling tools described later in this subsection to identify any transactions that are causing problems, and to clear or remove the problem.
Monitoring External Automatic Entries
Use the following guidelines to monitor your external Automatic Entries:
Use the :HUB and :HUB D Administration commands to identify which external Automatic Entry activity your application is processing, and which applications your application is communicating with, either as a client or as a server.
Use the :HUB I command to monitor for a given period. This command initializes the statistics displayed by the :HUB and :HUB D commands.
Look specifically for applications which are locally disabled, as shown by the :HUB D command.
Use the :HUB Q command if you suspect performance problems. This command shows you the queued times for outgoing transactions.
Look specifically for transactions that have been queued for a long period of time. These are listed first, as the display is in descending order of time queued.
If these methods do not identify a reason for a suspected problem, use the HUB Diagnostic Trace or the AX SYS and AX HOSTS HUBRouter commands.
The HUB Diagnostic Trace tracks your HUB communications through the HUB mechanism. The Trace facility has an effect on performance, therefore it should only be used when potential performance costs are acceptable.
Refer to Communicating With Other Hosts for more information on HUB Diagnostic Trace and HUBRouter commands.
Controlling External Automatic Entries
Use the following guidelines to control the external Automatic Entry (HUB) communications of your application:
When you have identified a suspected problem with a particular application, you should check the status of that application. To do this, use the :HUB command on the suspect system to identify if the HUB mechanism is enabled.
Use the :HUB + command to enable the suspect application it is not already enabled.
To avoid encountering the same problems again, you might choose to amend your logic. Check that Ispecs specifically test the values of Glb.Status and Glb.HubStatus to ensure that problems are identified by the logic, and appropriate messages can be displayed to inform administrators of the need to enable a particular application.
If a particular application is unavailable for a different reason, you might prefer to clear and locally disable that target application. Use the :HUB - key command to both clear and disable a specified application as a valid target.
Use the :HUB + key command to enable access to a disabled application if it becomes available again.
Refer to Administration Commands for more information on these Administration commands.