Chapter 4 - Configuring the ATE Service
The ATE option uses the ATE service on the server and software on the workstation to perform asynchronous terminal emulation. This chapter describes how to configure the ATE service that runs on your server. To configure this software, you add connections.
A connection represents a physical line from your server to the network. A connection can represent one of the following types of lines:
![]() |
A direct line |
![]() |
A dial-out line |
![]() |
An X.25 line |
A connection can also represent no line at all; server development connections and remote server console connections do not have separate lines. They use the existing network.
Figure 4-1 presents an overview of the steps involved in adding and configuring connections.
For direct, dial-out, and X.29 connections, provide additional information for the connection.
The steps in this figure are described in detail in the following sections.
To add a connection, perform these steps:
1. Run MSERVICE.
2. From the Manage Services menu, choose the ATE service. The Manage a Service menu appears.
3. From the Manage a Service menu, choose CONTROL the Service.
4. From the Control a Service menu, choose CONFIGURE Service. The Configure Asynchronous Connections menu appears.
When you create a new service, there are no connections defined. After you add connections, the connection names will appear on the menu.
5. From the Configure Asynchronous Connections menu, choose ADD a Connection. The procedures for adding a connection are described in the following sections. To cancel the addition at any time, press ESC.
When you choose ADD a Connection, the Name a Connection screen appears. It prompts you for the following information:
Connection name. The name by which users identify the host computer or data service. It appears on the Select a Connection menu and must be unique within the service. The name can be up to 19 characters in length and can contain letters, numbers, spaces, and punctuation marks.
Alternate name. Another name for the connection. The alternate name appears along with the connection name on the Select a Connection menu. The alternate name can be up to 19 characters in length. This entry is optional.
Description. The description line is optional but can be very helpful to you later on. It is a reminder about the connection. It can be up to 40 characters in length.
To provide the naming information, follow these steps:
1. Enter a connection name. Use the backspace, insert, delete, and arrow keys to make corrections as needed.
2. Enter an alternate name if you wish.
3. Enter a description if desired, or press F10.
When you press F10 or press ENTER on the description line, the Select a Terminal Type menu appears. You have identified the connection. You must now identify the terminal type, which is described in "Selecting a Terminal Type," which follows.
After you name a connection, the Select a Terminal Type menu appears. Here you choose a terminal type for a workstation to emulate when using the connection. Banyan ATE supports the following terminal types:
TTY A plain terminal type, also called a glass TTY.
VT100 A DEC VT100 terminal.
VT52 A DEC VT52 terminal.
IBM3101 An IBM 3101 terminal.
Assign the terminal type that is most useful for the host computer. For example, you might need to set up a connection for users to run SNA client programs. For that connection you would choose IBM3101.
If you choose TTY, control characters or escape sequences are not interpreted but are simply passed through. This terminal type is compatible with all host computers. You must select this terminal type if third-party terminal emulation software will use the connection.
Associating a Script File with the Connection
After specifying the terminal type, you are asked if you want a script file to be executed whenever this connection is used. Script files enable you to automate certain or all routine portions of a terminal emulation session. Chapter 10 describes script files in detail.
If you do not want to specify a script file, press ENTER without specifying a filename and proceed to the next section, "Selecting the Connection Type."
To specify a script file, perform these steps:
1. Enter the name (up to 64 characters including a pathname) of the script file. Do not specify a script file if users running third-party terminal emulation software will use the connection.
2. Press ENTER.
Proceed with the next section.
The Select Connection Type menu allows you to choose from the following connection types:
Asynchronous Direct or Dial-out. Use this connection type for either a direct or a dial-out line. A direct line connects the server to a host without an auto-dial modem. A dial-out line uses an auto-dial modem to connect to a host.
Server Console. Use this connection type for a remote server console connection.
X.29 PAD. An X.29 PAD connection uses the X.29 protocol to connect to hosts over an X.25 line.
Server Development Connection. This choice appears only if the Applications Toolkit is installed on the server.
Choose a connection type, then follow the instructions in one of the next four sections according to the connection type you have chosen.
The Add a Direct Line screen, which is described in the following pages, asks you for the following information:
Slot number. The number of the server slot that contains a serial communications card. This number combines with the line number to uniquely identify a direct line to a host computer.
Line number. The number of a line connected to a serial communications card.
Line speed. The transmission speed associated with this line. This speed must be the same one assigned to the line at the server console as described in "Assigning Communications Lines" in Chapter 3 and must be compatible with the host computer. Possible line speeds are 110, 300, 600, 1200, 2400, 4800, 9600, and 19200.
Stop bits. The number of stop bits to be transmitted with each character for this line. Enter 1 or 2. If you do not enter a value, a line speed of 110 or 300 automatically uses 2 bits; all other speeds use 1 bit.
Parity. The parity to be generated for characters transmitted to the host computer. The default value is NONE (no parity). You can use NONE, EVEN, or ODD.
Character size. The number of bits transmitted for each character. The default value is 8; you can change it to 7.
End session on carrier loss. Specifies whether the service terminates the session that uses the direct line when carrier is lost. The default value is N (no). You can change it to Y (yes). If you specify Y and the direct line does not use a modem, the line must support carrier signals, and the host must assert carrier. Otherwise, the session remains in the waiting state when a user attempts to establish it.
Note: All settings except Slot number, Line number, and End Session on Carrier Loss can be changed by parameter files, script files, or from ATE menus.
To configure a direct line connection, perform the following steps:
1. From the Select Connection Type menu, choose Asynchronous Direct or Dial-out.
2. From the Assign Connection Characteristics menu, choose Add Direct Lines. The Add a Direct Line screen appears, as shown in the following illustration.
3. Enter the appropriate information for each field (as described earlier in this section).
4. When finished, press F10 or ENTER from the Character Size field. If you omit the Slot number, Line number, Line speed, or Parity, an error message is displayed.
5. You are asked if you want to add another direct line.
- If you choose YES, another Add a Direct Line screen appears. Repeat steps 1 and 2 until you have no more lines to add.
- If you choose NO, you return to the Assign Connection Characteristics menu.
Your connection is now set up for direct lines. You can now add phone numbers for dial-out or specify the ARL.
- If you are using phone numbers to dial out through this connection, see "Configuring Dial-out Lines," which follows.
- If you want to specify who is allowed to use the connection, see "Specifying Access to Connections" later in this chapter.
- If you want to add the connection without specifying access, press F10 at the Assign Connection Characteristics menu.
6. You are asked to confirm that you want to add this connection.
- If you choose YES, the new connection is added to the currently selected service.
- If you choose NO, the new connection is not added and all the information you entered is discarded.
In either case, you return to the Configure Asynchronous Connections menu.
When a new connection has been added successfully, it appears on the Configure Asynchronous Connections menu.
If the system cannot add the new connection, you return to the Configure Asynchronous Connections menu. An error message appears indicating what caused the problem.
Dial-out lines require phone numbers. You can have more than one phone number for each dial-out line. If you have more than one telephone number for a dial-out line, the ATE service will use the additional numbers if the first number is in use (busy). For example, if the first number is busy, the ATE service will try the second. If that number is busy, the ATE service will try the third, and so on.
The Add a Phone Number screen, which is described in the following pages and which you use to configure a dial-out line connection, asks you for the following information:
Phone number. A phone number that lets users access the appropriate host computer. This entry is required. You can have more than one phone number per dial-out line.
A telephone number can be up to 38 characters. Enter a complete number in the order you would dial it manually.
Valid characters include 0 through 9 and * and # for touch tone (push-button) phones. In some phone systems, you might be instructed to dial a special prefix to disable services which allow incoming calls while you are using that line. For example, you might be told to dial *70 before initiating a call. Put the prefix before the telephone number and use a comma to pause so that the action can take place. For example, T *70, 9, 555-1212.
You can include dashes, spaces, and parentheses for readability; they have no effect on what is dialed. In addition, you can use the characters shown in Table 4-2.
Parity. The parity to be generated for characters transmitted to the host computer. The default value is NONE (no parity). You can use NONE, EVEN, or ODD.
Character size. The number of bits transmitted for each character. The default value is 8; you can change it to 7.
There are also two items on the Add a Phone Number screen that appear in four pairs of fields:
Line speed. You can enter up to four transmission speeds associated with the phone number. These speeds must equal the speeds assigned to dial-out lines at the server console. They must also be compatible with the host computer. The possible line speeds are: 110, 300, 600, 1200, 2400, 4800, and 9600. The default is 1200.
Stop bits. For each line speed you specify, you can enter the number of stop bits to be transmitted with each character. Enter 1 or 2. If you don't enter a value, a line speed of 110 or 300 automatically uses 2 bits; all other speeds use 1 bit.
Note: All settings can be changed by parameter files, script files, or from ATE menus, unless the user is running third-party terminal emulation software. Users can also set up their own parameter files for dial-out, if you give them dial-out access.
To configure a dial-out line connection, perform these steps:
1. From the Select Connection Type menu, choose Asynchronous Direct or Dial-out.
2. From the Assign Connection Characteristics menu, choose Asynchronous Direct or Dial-out.
3. From the Assign Connection Characteristics menu, choose Add Phone Numbers for Dial-out. The Add a Phone Number screen appears, as shown in the following illustration.
4. Enter the appropriate information for the fields on the Add a Phone Number screen. (Each field is described earlier in this section.) You can specify from one to four pairs of line speeds and stop bits.
5. When you have finished, press F10 or ENTER at the fourth field of stop bits. If you omit the phone number or parity, an error message appears.
6. You are asked if you want to add another phone number.
- If you choose YES, another Add a Phone Number screen appears. Repeat steps 4 and 5 for each phone number you want to add.
- If you choose NO, you return to the Assign Connection Characteristics menu.
7. Your connection is now set up with phone numbers for dial-out.
- If you want to specify who can use the connection, see "Specifying Access to Connections" later in this chapter.
- If you want to add the connection without specifying access, press F10 at the Assign Connection Characteristics menu.
8. You are asked to confirm that you want to add this connection.
- If you choose YES, the new connection is added to the currently selected service.
- If you choose NO, the new connection is not added and all the information you entered is discarded.
In either case, you return to the Configure Asynchronous Connections menu.
When a new connection has been added successfully, it appears on the Configure Asynchronous Connections menu.
If the system cannot add the new connection, you return to the Configure Asynchronous Connections menu. An error message appears indicating what caused the problem.
The Assign Connection Characteristics screen, which is described in the following pages and which you use to configure an X.29 PAD connection, asks you for the following information:
Slot number. The number of the server slot that contains a serial communications card. This number combines with the line number to uniquely identify either an X.25 line to a PDN or a dedicated or switched X.25 line to a host computer.
Line number. The number of a line connected to a serial communications card. Combined with the slot number, it uniquely identifies either an X.25 line to a PDN, or a dedicated or switched X.25 line to a host computer. This number cannot be changed by a parameter file, a script file, or ATE menus.
DTE Address. The DTE address of the host computer. If the X.25 line you specified uses an X.25 PDN, obtain the DTE address of the host from the PDN, the host systems programmer, or other qualified source. If the X.25 line you specified is a dedicated or switched line that goes directly to the host, obtain the DTE address from the host systems programmer.
Facilities. If the connection uses an X.25 line to a PDN, you can specify any of the facilities you contracted for with the PDN. The facilities were specified when the line was assigned. If the X.25 line is a dedicated or switched line that goes directly to the host, consult the systems programmer at the host.
Facilities are expressed as hexadecimal 2-character strings from 00 to FF. You can specify the strings together or separate them with a space. For example, if the strings you want to specify are 2d, bc, and 3c, you can enter them as 2dbc3c or 2d bc 3c. The strings are not case-sensitive.
Make sure you enter the correct facilities. The ATE service does not verify their accuracy.
Call User Data. Call user data is exchanged between the Banyan server and the host during the set-up phase of an X.25 call. This data identifies the call as an X.29 connection attempt and can provide other information as well.
If the connection uses an X.25 line to a PDN, consult the PDN. If the connection uses a dedicated or switched line that goes directly to the host, consult the systems programmer at the host.
You can enter up to 16 bytes of information in this field. The first four bytes must be 1000, which is the X.29 protocol identifier. Obtain the remaining bytes from the PDN or systems programmer. For more information on call user data, see the CCITT Recommendation X.29.
PAD Parameters. PAD parameters define certain aspects of how a workstation communicates with the host during a session. You can enter a series of PAD parameters and their associated values. Each parameter identifies a specific aspect of workstation-to-host communication.
For more detailed information on PAD parameters, see "Configuring PAD Parameters," which follows this section.
For an X.29 PAD connection, you must enter information in the following fields to have a functional connection:
![]() |
Slot number |
![]() |
Line number |
![]() |
DTE address |
The other parameters are optional.
To add an X.29 PAD connection, perform the following steps:
1. From the Select Connection Type menu, choose X.29 PAD. The Assign Connection Characteristics menu appears.
2. From the Assign Connection Characteristics menu, choose the Specify Parameters option. The Specify Parameters screen appears, as shown in the following illustration.
3. Enter the appropriate information for each field. For fields in which you don't have to enter any information, press ENTER.
4. When finished, press F10 or ENTER from the PAD Parameters field. If you omit the line number, line speed, or DTE address, an error message is displayed.
5. You are asked to confirm that you want to add this connection.
- If you choose YES, the new connection is added to the currently selected service.
- If you choose NO, the new connection is not added and all the information you entered is discarded.
In either case, you return to the Configure Asynchronous Connections menu.
When a new connection has been added successfully, it appears on the Configure Asynchronous Connections menu.
If the system cannot add the new connection, you are returned to the Configure Asynchronous Connections menu. An error message appears indicating what caused the problem.
If you want to specify who is allowed to use the connection, see "Specifying Access to Connections" later in this chapter.
The ATE option fully supports all values for 12 of the 22 X.3 standard PAD parameters, and supports some values for two of the parameters. Other PAD parameters are not applicable to a Banyan network or are not supported at this time. See the CCITT Recommendation X.3 for descriptions of all the PAD parameters. Table 4-3 lists the support for each parameter.
To configure a PAD parameter, enter a PAD parameter number followed by a comma and a value. Be sure to separate parameter/value pairs by at least one space, as follows:
7,2 8,1
The value you associate with the parameter specifies exactly how that aspect is configured. For example, PAD parameter 7 determines how the service responds when it receives a break signal from the workstation, and a value of 2 indicates that the service should reset the user's session.
"Values for PAD Parameters" describe the parameter values that each of the implemented parameters supports. They also describe any limitations that pertain to the Banyan implementation. All numbers are decimal unless otherwise noted.
Parameter 1, PAD Recall Using a Character - Lets you escape from a data transfer state to issue PAD commands. The Banyan implementation of this parameter supports the values 0 and 1. The other possible values, 32 to 126, are not supported in the Banyan implementation. See Figure 4-6.
For more on the PAD commands you can use with PAD recall, see "Using PAD Commands" in Appendix B.
Parameter 2, Echo - Allows you to specify whether the PAD will echo characters at the terminal as they are typed. See Figure 4-7.
Parameter 3, Selection of Data Forwarding Characters - Allows you to define which character or characters cause the PAD to forward a data packet to the host. All possible values of this parameter are implemented. See Figure 4-8
You can use a combination of these values. For example, a value of 6 combines the effects of value 2 plus value 4, forwarding on receipt of ASCII characters CR, ESC, BEL, ENQ, or ACK. A value of 20 combines the effects of value 4 plus value 16, forwarding on receipt of the ASCII characters ESC, BEL, ENQ, ACK, ETX, or EOT.
Regardless of which character or characters you define, if the PAD buffer is full (1024 characters), the PAD automatically forwards the data packet to the host.
Parameter 4, Idle Timer Delay - Allows you to specify a time-out value between successive characters received by the PAD after which the PAD will forward the data packet to the host. See Figure 4-9.
A value between 1 and 255 indicates both that the time-out is to be used and the delay in twentieths of a second. However, because the ATE service uses the Banyan tasking system, the timer in the Banyan implementation marks time only in seconds. Therefore, a task can be delayed only in intervals of seconds. To enter a value in seconds, choose a value that is a multiple of 20 (20, 40, 60, 80, and so on).
If you set the delay in fractions of a second (by specifying a value that is not a multiple of 20), the timer in the Banyan implementation rounds the fraction down to the nearest whole second. If you set the delay to a value of less than one second (value less than 20), the value is rounded down to 0 (zero). The packet will be forwarded within the second.
When Parameter 15 is set to 1, the value of the idle timer delay is ignored. This follows the X.3 standard.
Parameter 6, Control of PAD Service Signals - Allows you to control whether, and in what format, PAD service signals are transmitted to the terminal.
The Banyan implementation of this parameter supports only decimal values 0 and 1. See Figure 4-10.
Parameter 6 must be set to 1 to use Parameter 16, Character Delete, or Parameter 17, Line Delete.
Other possible values that are not supported in Banyan implementation include value 4 (the prompt PAD service signal is sent in standard format) and values 8 to 15 (PAD service signals are sent in network-dependent format).
Parameter 7, Operation on Break Signal from Terminal - Allows you to specify what will happen when the PAD receives a break signal from the terminal. The Banyan implementation of this parameter supports all possible values. See Figure 4-11.
Note: If you set Parameter 7 to 16, then Parameter 8, Discard Output, is automatically set to 1.
You may also use a combination of these values. For example, a value of 5 combines the effects of value 1 (PAD sends interrupt packet to host) plus value 4 (PAD sends indication of break to host).
Parameter 8, Discard Output - Allows you to specify whether data destined for the terminal is to be delivered to the terminal or if it is to be discarded. The only possible values in the standard are 1 and 0. The Banyan implementation supports both values. See Figure 4-12.
Parameter 13, Line Feed Insertion After CR - Allows you to control if and when the PAD automatically inserts a line feed character in the character stream. See Figure 4-13.
You may also use a combination of these values. For example, a value of 5 produces the effects of 1 (insert line feed after transmission of CR to terminal) plus 4 (insert line feed after echo of carriage return).
This parameter affects the line display you choose using Parameter 18. (See the description for Parameter 18 later in this section for more information.)
Parameter 15, Editing in Data Transfer State - Allows you to specify whether editing is possible while in a data transfer state. The only possible values in the standard are 1 and 0. The Banyan implementation supports a value of 1. See Figure 4-14.
Parameter 16, Character Delete - Allows you to specify which ASCII character (in the range of 0 to 127) is to be used as the character delete character. Upon receipt of this character, the PAD deletes the last character from its editing buffer (as well as this character delete character) and sends an editing service signal to the terminal only if Parameter 6 and Parameter 19 are non-zero. The format of the editing service signal depends on the value of Parameter 19. For more information, see the description of Parameter 19 later in this section. See Figure 4-15.
Parameter 17, Line Delete - Allows you to specify which ASCII character (in the range of 0 to 127) is to be used as the line delete character. Upon receipt of this character, the PAD deletes the entire contents of its editing buffer (including the line delete character) and sends an editing service signal to the terminal, if Parameters 6 and 19 are non-zero. See Figure 4-16.
Parameter 18, Line Display - Allows you to specify which ASCII character (in the range of 0 to 127) is to be used to trigger the display of the PAD's editing buffer. The line display character is removed from the editing buffer and the PAD sends a CR character to the terminal, followed by the current contents of the editing buffer. If Parameter 13 is set to 1 (or some combination with 1), then the PAD also inserts an LF character after the CR. See Figure 4-17.
Parameter 19, Editing PAD Service Signals - Allows you to specify whether editing PAD service signals are transmitted and which format should be used. All possible values for this parameter are supported. See Figure 4-18.
Parameter 20, Echo Mask - Allows you to specify which special characters will not be echoed. This parameter does not take effect unless Parameter 2, Echo, is set to 1. All values of this parameter in the X.3 standard are supported. See Figure 4-19.
You may also use a combination of these values. For example, 3 combines the effects of value 1 (no echo of CR) and value 2 (no echo of LF).
Adding a Remote Server Console Connection
A remote server console connection allows you to gain access to the server console from a workstation. With the remote server console feature, it appears as if you are working at a server console. The remote server console feature provides more than just server console emulation; when you use the remote server console feature, your workstation becomes the server console. Any commands you enter and any screens you display on the remote server console simultaneously appear on the server console.
The remote server console feature is most appropriate for networks where a limited number of people use this feature, or where it is possible to control who can gain access to the actual server console. You can use ARLs (Access Rights Lists) to restrict who can use the remote server console. For more information on ARLs, see Managing VINES Services.
To add a remote server console connection, use one of the methods described in "Adding Connections" earlier in this chapter, to reach the Configure Asynchronous Connections menu, then follow these steps:
1. From the Configure Asynchronous Connections menu, choose ADD a Connection.
2. At the Connection Name field in the Name a Connection menu, enter a name for the connection (for example, Remote or RemoteConsole).
Note: The remote console connection does not need to be called RemoteConsole. However, if you give the connection a name that contains the words "remote console," it will be easier to tell which connection is the remote connection when using the HOSTS command.
3. At the Alternate Name field in the same menu, enter an alternate name (if desired).
4. At the Description field in the same menu, enter a description.
The Connection Name, Alternate Name, and Description fields are described in "Naming a New Connection" earlier in this chapter.
5. From the Select a Terminal Type screen, select VT100 for the type of terminal this connection should emulate by default. Press ENTER. The Associate a Script File screen appears.
6. Press ENTER at the Associate a Script File screen. (Since you do not know which screen the server console is on, you could not really predict what your entry point is. Therefore, writing a script file that would perform the way you wanted it to would be difficult.) The Select Connection Type menu appears.
7. From the Select Connection Type menu, select Server Console. Press ENTER.
8. You are now asked if you want to specify the access rights.
- If you want to specify who is allowed to use the connection, see "Specifying Access to Connections" later in this chapter.
- If you do not want to specify who is allowed to use the connection, choose NO to accept the default access rights. The default is AdminList@servername@Servers, where servername is the name of the server on which the ATE service is running.
9. The Confirmation to Add screen appears, asking if you want to add this connection.
- If you choose YES, the new connection is added to the currently selected service.
- If you choose NO, the new connection is not added and all the information you entered is discarded.
Select YES or NO and press ENTER.
In either case, you now return to the Configure Asynchronous Connections menu.
Adding a Server Development Connection
On native VINES, the server must have both the ATE option and the Applications Toolkit option installed before you can create a server development connection.
To add a server development connection, follow these steps:
1. From the Select Connection Type menu, choose the Server Development Connection option.
2. You are then asked if you want to specify an ARL. Choose YES to specify who is allowed to use the connection, or NO to continue.
- If you choose YES, the new connection is added to the currently selected service. Proceed to "Specifying Access to Connections" later in this chapter.
- If you choose NO, another screen appears asking you if you want to add the connection. If you choose NO again, the new connection is not added and all the information you entered is discarded. In either case, you return to the Configure Asynchronous Connections menu.
When a new connection has been added successfully, it appears on the Configure Asynchronous Connections menu.
If the system cannot add the new connection, you return to the Configure Asynchronous Connections menu. An error message appears indicating what caused the problem.
Your server development connection is now ready for use.
Specifying Access to Connections
You can specify access rights to the connection to restrict the use of the direct lines and phone numbers associated with it. The access rights also protect the lines and phone numbers when a parameter file contains the connection name. You specify the access rights with a StreetTalk name, list, or pattern. Therefore, to use the connection, a user's name must match whatever you specify. If you do not specify access rights to the connection, anyone can access the connection.
To specify access to the connection, perform these steps:
1. From the Assign Connection Characteristics menu, choose Specify ARL.
2. Type in the StreetTalk name, list, or pattern that identifies the users to whom you want to give access. Press ENTER.
If you have not already done so, you can specify any direct lines, dial-out lines, or X.29 parameters you want to be part of the connection. For details, see "Configuring Direct Lines," "Configuring Dial-out Lines," or "X.29 PAD Connections" earlier in this chapter.
Setting Access Rights for Dial-out
You can control who uses the service to dial-out without using configured connections. If you do not specify access rights to the connection, anyone can dial out.
Users can dial out manually or by using parameter files that include a phone number. You control this type of dial-out access by specifying a StreetTalk name, list, or pattern. If you use a list, the user's name must be on the list. If you use a pattern, the user must have a name that fits that pattern. For example, the pattern *@Finance@WCTUS grants access to all users in the group Finance@WCTUS.
To specify the access rights list for dial-out, perform these steps:
1. From the Configure Asynchronous Connections menu, choose SET ARL for Dial-out.
2. Specify the StreetTalk name, list, or pattern that identifies the users to whom you want to give access. Press ENTER.
Note: Once users enter terminal emulation, they can create, edit, and save parameter files from the terminal emulation screen. They can also generate parameter files from ASCII text editors if you provide them with the information from Chapter 5. However, they cannot change the access rights for dial-out.