Chapter 6 - Using ATE Commands
Table 6-1 lists the ATE commands. Some of these commands, like MASYNCH and SETASYNCH, are commands that usually only an administrator would use. Other commands, like the ASYNCH and BASYNCH commands, are commands that advanced users might use.
With the exception of the EMULATION, MASYNCH, and TASYNCH commands, the following sections describe the commands in Table 6-1 in more detail. Appendix C gives the complete syntax for each command.
If you are an advanced user, you can skip the menus or set up your own parameter files and take advantage of the DOS command line entry to ATE.
The ASYNCH command provides this entry. The ASYNCH command accepts switches that describe what you want and executes differently based on the parameters given with the switches.
Before you can execute the ASYNCH command successfully, your administrator must set up your user profile to access the command. SETASYNCH is the user profile command that sets up user access to an ATE service. Chapter 5 describes the SETASYNCH command in the section on setting up access through user profiles.
Examples of the ASYNCH Command
Here are some examples of ways to use the ASYNCH command. For a complete description of the ASYNCH command and all its switches, see Appendix C.
Example 1
asynch
Presents the Action Menu with no connection defined. You can use the service in only one way - by dialing out manually from Banyan terminal emulation menus. There must be a service set in your user profile.
Example 2
asynch /s:remotevax@finance@homeoffice
Presents the Action Menu using the specified service. No connection is defined. By default, your workstation emulates a VT100 terminal. You can use the service in only one way - by dialing out manually from Banyan ATE menus. No service is needed in your user profile.
Example 3
asynch /c:vaxdirect
Puts you in terminal emulation with an active session, using the specified configured connection. The service must be set in your user profile.
Example 4
asynch /s:vaxhost@finance@homeoffice/c:vaxdirect
Puts you in terminal emulation with an active session, using the specified service and configured connection. No service is needed in your user profile.
Example 5
asynch /s:vaxhost@finance@homeoffice/c:vaxdirect/f:vax1
Puts you in terminal emulation with an active session, using the specified service and configured connection. No service is needed in your user profile. The parameter file vax1 overrides communications settings. If a script file is associated with the connection, the parameter file is ignored.
Example 6
asynch /e:ibm3101
Presents the Action Menu using the specified terminal type. No connection is defined. You can use the service in only one way - by dialing out manually from ATE menus. There must be a service set in your user profile.
asynch /e:vt52/s:remotevax@finance@homeoffice
Presents the Action Menu using the specified terminal type and service. No connection is defined. You can use the service in only one way - by dialing out manually from ATE menus. No service is needed in your user profile.
Example 8
asynch /f:vax2
Puts you in terminal emulation, using settings in the parameter file vax2. If vax2 is a partial file, you enter terminal emulation without an active host session and must dial out manually. Otherwise, the connection or phone number in the file is used to connect to the host. Any settings in the file override those in the connection. The service must be set in your user profile.
Example 9
asynch /f:vax2/s:vaxhost@finance@homeoffice
Puts you in terminal emulation, using the specified service and the settings in the parameter file vax2. If vax2 is a partial file, you enter terminal emulation without an active host session and must dial out manually. Otherwise, the connection or phone number in the file is used to connect to the host. Any settings in the file override those in the connection. No service is needed in your user profile.
Example 10
asynch /c:vax2/s:vaxhost@finance@homeoffice/o:f:\reflect\r2
Puts you in terminal emulation, using the specified service, connection, and third-party software. The third-party software controls how your workstation behaves during your session with the host.
Commands for Third-Party Software
For third-party software that uses the BANV interrupt, you can establish sessions with the host by first issuing the BASYNCH command, and then issuing the command that runs the third-party software. Appendix C describes the BASYNCH command.
Making Terminal Emulation Software Resident
Sometimes you may want to exit from terminal emulation and return to DOS while maintaining your connection to the host. For example, you may want to exit from terminal emulation, perform a few immediate tasks in DOS, and then return to terminal emulation. Or, your site may use programs that run under DOS but communicate with the host through a programmatic interface to terminal emulation.
If you want to exit from and then return to terminal emulation, the terminal emulation software must be resident in the workstation. You use the RASYNCH command to do this.
To use this feature, enter the RASYNCH command from DOS before you enter either Banyan ATE or third-party emulation. Then you can exit from terminal emulation without breaking the connection and return to that same connection.
Note: Most third-party terminal emulation software packages provide capabilities, such as hotkeys, to exit from terminal emulation and return to DOS while maintaining your connection to the host. See your third-party documentation for details.
If Banyan ATE software handles your session with the host, complete the following steps to exit from terminal emulation and maintain the connection:
1. Exit terminal emulation from the Action Menu while in terminal emulation.
2. Enter Y in response to the prompt to suspend your session.
3. Enter ASYNCH at the DOS prompt to return to terminal emulation.
You cannot start a new host session until you end the one you suspended.
You also can use the scripting commands - SUSPEND and XDOS - from the terminal emulation command line to perform this function. See your administrator or refer to Chapter 10 for more information on script commands.
Appendix C describes the RASYNCH command in more detail.
Releasing Terminal Emulation from Memory
To release RASYNCH from memory, enter RELASYNC from DOS. The RELASYNC command can be used only if you have not loaded another program after issuing either the RASYNCH command or the BASYNCH command.
This restriction prevents memory fragmentation and allows DOS to load another program in that area of memory, thereby giving that program free use of the rest of memory.
Appendix C describes the RELASYNC command in more detail.
Using the Emulation Command Line
For advanced users who want to issue scripting commands while in terminal emulation, there is a command line that you can use to enter them.
To access the command line, press the ATTENTION key. This key is defined as SHIFT-TAB by default, but your administrator can redefine it as needed.
The commands you issue perform functions such as changing settings from the menus and also provide ways to exit to DOS and then return to terminal emulation.
The syntax of the commands is similar to that used by Crosstalk software. For information on the commands you can enter, see Chapter 10 or talk with your administrator.
Figure 6-1 shows how the menus, the ASYNCH command, connections, script files, and parameter files work together. The top of the figure shows the actions that a user performs. The lower portion shows the actions of the service.
Note the following information as you examine the figure:
There must be a service name specified either in the user profile or with the ASYNCH command. | |
The terminal type is determined by the last element to specify one, whether from the command line, a connection, a parameter file, a script file, or a terminal emulation screen. |