In circumstances in which you require coordinated line consumption, follow one of these three approaches:
Method 1
Perform these steps to ensure general line availability when you have 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.
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. |
Method 2
Perform these steps in order to implement a more stringent level of security than Method 1 allows.
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
Implement one or more of these measures in order 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 available for connection.
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 by leaving the lowest line number open for wildcard clients.
See Also
Coordinating Client Line Consumption