Use
With program msmon you can monitor the message server at operating system level.
Integration
Program msmon offers the same functions at operating system level as the Message Server Monitor in the SAP System (transaction SMMS).
Prerequisites
You have access to the host on which the message server of your SAP System is running and you can log on there with user
Features
The call of the message server monitor without arguments displays the permitted arguments and options:
Usage msmon
pf=
name=
[-mshost mshost] : msg server host
[-msserv msserv] : msg server services
[-customer] : enable customer mode
Under this:
q - quit
m – menue
->
As a rule you use q to quit the message server monitor and m to get to the menu (next level up).
After you have called msmon with the system ID, the profile or the host/port of the message server, you will get a list of the application servers logged on to the message server (see the example in section Monitoring Program msprot).
If you then enter m and select Return, you will get to the main menu:
Main Menu
Menu Entry | Meaning |
1 : display client list | Displays the list of logged on application servers – as on the initial screen. |
2 : display hardware id | Displays the Hardware Keys of the host. |
3 : security menu | Jumps to a security sub-menu. Each application server has a security name that it sends to the message server at the start. You can find out this name from the server name (1) or from the IP address and port number (2). |
4 : statistics menu | Here you can activate, display, deactivate, or reset message server statistics. See also Message Server Monitor. |
5 : server parameter | The most important profile parameters of the message server are displayed (see Message Server Parameters) |
6 : server release information | Displays the release details of the message server, see Message Server Monitor. |
7 : expert menue | Jumps to the expert menu, see Message Server Monitor. |
8 : connect to server | Here you can directly establish or cancel the connection of msmon to the message server. |
9 : disconnect from server | |
11 : display logon group list | Displays the configured logon groups, see Test Program lgtst. |
12 : display logon group list with snc | Displays the configured logon groups with SNC, see Test Program lgtst. |
13 : group logon data | Displays data of a logon group. |
14 : group logon data with SNC | Displays data of a logon group with SNC. |
15 : group logon data with LB | Displays data of a logon group: IP address, port, release, and whether RFC load balancing is activated for this group, see Test Program lgtst |
16 : group logon data with LB and SNC | Same as for groups with SNC. |
17 : free memory of logon data | The allocated memory for this logon group is released (expert function). |
18 : force reread of logon data | The logon data is checked by the message server at regular intervals. With this you can force a new import. |
19 : counter menu | Counter menu (expert function). |
+ : increase trace | Increase trace level (see Message Server Monitor) |
- : decrease trace | Decrease trace level (see Message Server Monitor) |
If you are using the option –customer when you call msmon, a different menu will appear.
Customer Menu
Menu Entry | Meaning |
1 : display client list | See above |
2 : display hardware id | See above |
3 : display server parameter | See point 5. |
4 : change server parameter | You can change parameters online (provided they are set up as dynamically modifiable).
Note that the changes are lost when you call the program again. You have to make permanent changes in the profile file. |
5 : display server release information | See point 6 above. |
6 : display logon group list | See point 11 above. |
7 : display logon group list with snc | See point 12 above. |
8 : dump network buffer | Writes the host name buffer to the trace file dev_ms (see Message Server Monitor, expert functions) |
9 : reset network buffer | Reset host name buffer |
10 : reset trace file | Reset trace file dev_ms |
+ : increase trace | See above |
- : decrease trace | See above |
No comments:
Post a Comment