Product | Command Type |
---|---|
Attache | command |
Platform |
---|
UNIX |
Windows |
Single-command mode:
Interactive mode:
attcmd>
subcommand [ options/args]
attcmd>
quit
Display version information for Attache:
attcmd is a console version of the Attache command-line interface. It is similar to the command window in the Attache graphical user interface (see the attache_command_line_interface reference page for more information). It is intended primarily for users who want to embed Attache operations in scripts or invoke them from other tools.
attcmd accepts all commands which are valid in the Attache command window, except for these:
NOTE: attcmd is a 32-bit Windows console application and is available on Windows 95 and Windows NT only.
This reference page does not describe the individual attcmd subcommands. For a list of the attcmd subcommands, see the attache_command_line_interface reference page.
You can use attcmd in either single-command mode or interactive mode. A single Attache command can be invoked from the shell using this syntax:
attcmd [ -ws ws-name ] subcommand [ options/args]
If you want to enter a series of subcommands, enter the attcmd command with no subcommand arguments. This places you at the interactive mode prompt:
attcmd>
You can then issue any number of subcommands (called "commands" from now on), ending with quit to return to the shell.
The -ws option can be used to specify which workspace in which to start. If not specified, then the current working directory is used to determine the workspace. If the current working directory is in or under a workspace, that workspace is set. If it is not, no workspace is set on startup and the setws command must be used to set a workspace.
After startup, if the current working directory is within the startup workspace, attcmd attempts to change to that directory after connecting to the workspace helper host. The attempt may fail if the directory does not exist in the view associated with the workspace. In this case, the initial working directory is the root directory.
Command input is read from the standard input, but input redirection generally does not work. Whenever a remote command is executed, any input which occurs during command execution is sent to the remote command process. Therefore, if input were redirected from a file, for example, the first command which caused remote command execution would cause the rest of the input file to be read and sent to the remote process.
If you exit attcmd by entering a quit command in interactive mode, the exit status is 0
(zero). The exit status from single-command mode depends on whether the command succeeded (zero exit status) or generated an error message (nonzero exit status).
attache, attache_command_line_interface
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |