CUI supplies two ways you may enter text commands. One way is activated from the Operations tree and displays in the desktop area. The other way is a fixed display just below the desktop area. Both cases have similar capability and this help applies to both.
An area is available, "Command:", where you may type in a command. This area also has a list available of the most recent commands entered which you may select from to reexecute a command. Whether you type a command or select one from the list, hitting "Enter" will execute the command. The list of commands is remembered across CUI sessions.
Like normal command entry in a terminal session, multiple commands may be entered separated by semicolons (;). Like terminal sessions, the commands are executed sequentially. However only one set of results are displayed to the user which is a combination of the individual results. The maximum error code is returned and the output and error messages are concatenated.
Commands may display different amounts of information depending on your "Output Level:" selection. Once you select a level, it will be remembered, even across CUI sessions.
When running CUI on a running Cyflex system, there is no difference between running a command locally or running it remotely. However when CUI is connected across a network to a Cyflex system this distinction becomes important. In this case, local means running a command on the system where CUI is executing. Remote means running a command on the Cyflex system connected to.
In the event CUI is runnng on the system that it is connected to, no selection is displayed for local or remote execution since they are the same system. However when connected remotely, you have the option of where to execute a command.
For example when running CUI on Windows but connecting to a Cyflex system, you could enter an "ls" command to run the command remotely on the Cyflex system. But you could enter a "dir" command to run the command locally on the Windows system.
If a command fails, there are several things you can do to try to resolve the problem. First be sure the output level is set to "Detailed output" and try the command again. This may display sufficient information for you to resolve the problem. If that doesn't help, open a standard system command window and try typing the command in directly. This may supply more information and perhaps error messages which will help you diagnose the problem.