If one or more clients of any type cannot connect via their intended line(s), there may be one of four likely causes.
More wildcard clients than anticipated may be connected. For example, a user of a wildcard mvTerm or Telnet client may open more instances or sessions than the administrator planned, prematurely consuming low line numbers.
Clients intended to connect as non-wildcard clients may be connected as wildcard clients, prematurely consuming low line numbers.
The Disconnect on Logoff option in the Ports tab may not be selected when it needs to be. This possibility pertains to configuration of clients connecting via a COM port. Access the Ports tab via the Configure button on the Workstation tab.
Additional lines and/or licenses may be required. Additional lines may be added without performing a required fileload. Contact your local Rocket representative for licensing options.
Overview of AUTO-DISCONNECT and AUTO-LOGOFF
Two TCL commands offer additional help in coordinating the line consumption of mvBase clients. These commands are AUTO-DISCONNECT and AUTO-LOGOFF.
AUTO-DISCONNECT |
Allows certain mvBase clients the capability to disconnect from the mvBase Server with a custom delay. The delay you define with AUTO-DISCONNECT allows those clients who wish to reserve their connection (line) to do so while logged off. In addition, delayed disconnect makes the license available to other clients, allowing a larger number of users to connect to an mvBase Server over a period of time than are licensed. |
AUTO-LOGOFF |
Automatically logs off a specified process after either a designated period of inactivity or the loss of an incoming DTR signal. An unattended terminal can be a security problem; the AUTO-LOGOFF command can reduce this risk on a system-wide or an account-by-account basis. |
See Using the SYSPROG Account and Commands in the Guide to mvBase Files and Accounts for additional information about these commands.
See Also
Coordinating Client Line Consumption