Expert Functions
Use
These functions are for those users with expert knowledge. The functions are described in the following:
Features
The following submenu appears:
Expert functions
-------------------------------------------------------------------
1 : memory usage
2 : request block
3 : reset error counter
4 : reset all error counter
5 : reset NI buffer
6 : dump NI buffer
7 : reset trace file
8 : activate external program trace
9 : deactivate external program trace
10 : dump connection table
11 : dump system table
12 : dump work process table
13 : dump remote gateway table
14 : dump gateway's release infos
15 : tail trace file
16 : edit trace file
q - quit
m - Menu
-->
Displaying memory usage
The header displays the maximum number of request blocks, the number of request blocks being currently used, and the maximum number of previously used request blocks. The current memory usage is displayed, that is all blocked memory blocks. The number of each request block is displayed, and the process that is currently working on it.
Displaying memory contents
You can display the contents of a request block. To do this, you have to enter its number.
Resetting the IBM error counter
If the gateway is running under IBM, then connections with an error are flagged with an error counter. They are only used again when the counter has been reset to 0. You can reset to 0 with
gwmon , both in dialog, and in the background. In dialog, you have to select the function "reset error count" in the expert menu, you can then specify the number of the connection that you want to reset, or you can specify "all". To reset the error counter for one or all connections in the background, use the calls gwmon -e <nr> pf=... or gwmon -e all pf=.. gwmon then exits.Resetting the NI Buffer
Use this function to reset the NI buffer (it buffers host name and IP addresses and service names. This means that all buffered entries will be deleted from the buffer.
Dumping the NI buffer
You can use this function to write the contents of the NI buffer to the trace file
dev_rd .Resetting the trace file
Use this function to reset the trace file. You need to do this is the file has become very large, for example, because of error analyses.
Activating and deactivating the trace for external programs
You can use this function to trace programs started by the gateway. This is necessary for error analysis. The file
CPICTRC<pid> is generated in the working directory.Dumping the connection table
This function is the same as the Display menu option.
Dumping the system table
This function displays all available information on a system that is logged on to the gateway.
Dumping the work process table
This function displays all available information on the gateway work processes.
Dumping the remote gateway table
This function displays all available information on a remote gateway logged on to this gateway.
Dumping the gateway's release information
This function displays the gateway's release information. The output is the same as the gateway's V option.
Gateway monitor, connected to hs0311 / sapgw53
Gateway's release info
---------------------------------------------------
kernel information
------------------
kernel release = 46A
compiled on = HP-UX B.10.20 E 9000/889
compiled time = Jul 8 1998 22:04:32
patch level = 0
supported environment
---------------------
operating system
HP-UX B.10
Development system build information:
-------------------------------------
Host : hs0055
Srcdir: /bas/BIN/src
Gendir: /sapmnt/hs0055/b/bin/hp/O
Basdir: /bas/BIN/gen/opt/hp
IKVers: 19982700
Displaying the end of the trace file
You can use this function under UNIX only. It display the last two lines of a file.
You can control this function with the following environment variable:
Displaying the trace file in the editor
You can use this function under UNIX only. It displays a file in the editor.
You can control this function with the following environment variable: