Coordinating Line Consumption by mvBase Clients

When you use multiple client types, you may experience unintentional conflict in line availability. Here are two hypothetical examples:

• If a user starts too many mv.TERM sessions, they may consume lines specifically allocated to Telnet clients in the mv.TELNET server.
• If you temporarily disconnect a printer and a user starts too many Telnet sessions, you may find that the line is no longer available when you attempt to reconnect that printer.

mvBase clients consume mvBase lines in the following three ways:

This table below summarizes line-consumption methods for each standard mvBase client:

In circumstances in which you requite highly-controlled line consumption, follow one of these three approaches:

• Method 1:
  To ensure general line availability with less concern about security:
  • Configure the server with a high number of processes.
  • Start with a lesser number of lines, and gradually increase the number of lines as client demand requires.
  • Once you have defined the number of processes, a fileload is not required merely to increase (or decrease) the number of lines.
• Method 2:
  To implement a more stringent level of security:
  • Use no wildcard clients.
  • Allocate specific line numbers exclusively to non-wildcard clients.
  • Limit tightly the quantity of extra lines or phantom lines.
  • Closely monitor line-consumption (e.g., issue LISTLINES at TCL).
• Method 3:
  To implement the highest level of security in line consumption:
  • Keep each client (of any type) continually connected via its intended line.
  • Limit tightly the quantity of extra lines or phantom lines.
  • Closely monitor line-consumption (e.g., issue LISTLINES at TCL).

In most cases, such rigid control may not be required, but when combining wildcard clients with non-wildcard clients, you may wish to safeguard line availability for both. Click here to implement a coordinated line-consumption strategy.

mv·TELNET Considerations

When configuring multiple mv·TELNET servers, each of which uses a single dedicated line and TCP port,we recommend using a consecutive sequence of lines and TCP ports. Customary TCP ports are ports 23, and 1024-5000. To reduce the likelihood of encountering a previously consumed port when configuring the sequence, we recommend starting with port 2000. Line configuration should follow the recommendations made earlier. mv·TELNET servers are configured with the Telnet Servers tab of the mvBase workstation.

Note, however, that this approach cannot guarantee resolved conflict with other line or TCP port consumption.

Configuring Line Consumption for Multiple Client Types

This procedure configures coordinated line consumption when multiple client types are used. This requires familiarity with multiple configuration instructions in the mvBase 1.2 Installation Guide.

1. Configure known printer(s) to take the highest line number(s). Printer line requirements and usage are unlikely to change frequently, but it is important to safeguard line availability for printers even when they are not connected.
2. Configure all line-specific and/or line-pooling clients to take the next lower series of line numbers.
3. Leave the lowest line numbers open for any required wildcard clients.

Troubleshooting Line Consumption

If you have implemented coordinated configuration of line consumption and 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 mv.TERM 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. Click here to change the number of mvBase lines. Contact your local representative for licensing options.