Coordinating Client Line Consumption

This topic summarizes several guidelines and a few strategies that may help you prevent conflict in the line consumption of multiple client types. This topic addresses the line consumption of all clients managed by the Workstation in addition to client line consumption of the mvTerm client.

Overview of Client Line Consumption

When you use multiple client types, you may experience unintentional conflict in line availability due to conflicting line-consumption methods between clients. Here are two hypothetical examples:

If a user starts too many mvTerm sessions, they may consume lines specifically allocated to Telnet clients in the mvTelnet Server.
If you temporarily disconnect a printer and a user starts too many Telnet sessions, you may find that one of these Telnet sessions has consumed the printer’s line, and the line is no longer available when you attempt to reconnect that printer on that specific line.

This topic summarizes the three ways in which mvBase clients consume lines. When you understand these concepts, you may be able to plan out a better line consumption strategy that prevents unintentional or unforeseen line consumption.

NOTE	If you initially configure many more processes than lines, you can gradually adjust the quantity of lines as demand requires without having to perform a fileload. A fileload is not required when adjusting the quantity of lines on the Server.

The following topics are presented in this section:

Options for Client Line Consumption

General Methods for Coordinating Line Consumption

Troubleshooting Client Line Consumption