LOG CONNECTIONS UTILITY Release Level TUE 07/17/90 14:59 PM This application consists of one runfile: LogConn.Run Product Name : Log Connections Supported On : B24, B26, B27, B28, B38, B39, and all SuperGen hardware Supported OS : BTOS II, CTOS I, CTOS II, CTOS III Description : The Log Connections utility filters requests associated with OSI Session (ses), OSI Transport-WAN (trs), OSI Transport-LAN (botl), LAN STI (lansti), and X.25 (x25), and displays on the screen, and optionally to a file, the messages indicating the actions of the various components concerning connections established and broken. This program is very useful in debugging BNet related problems where a connection attempt across the network reports an 8992 error code. Directions/Use : The suggested method for using this utility is to install the Context Manager and run the Log Connections program in one partition. This leaves other partitions free for monitoring utilities or to run other programs. If you run the Log Connections program without using Context Manager, the keyboard and video are not accessible during the logging session. When you are done monitoring connections, type FINISH, which causes the program to close the output file and exit. To run the Log Connections utility execute the /Log Connections command using the parameters which are described and detailed below: [Output file (default screen only)] This field is optional. The default output is to the screen. Enter a file or device name in which to print the program's output. The messages are always written to the screen, with no scrolling control. [Services (default all)] This field is optional. The default is all services. The codes for the services desired (ses, trs, botl, lansti, x25) should be entered on one line, separated by spaces. If left blank, then the program tries to monitor all installed services. [# of requests outstanding (default 200)] This field is optional. Enter the number of requests to monitor, unless you have a very large number of connections active, the default of 200 should be plenty. COMMAND /Log Connections [Output file (default screen only)] [Services (default all)] [# of requests outstanding (default 200)]