6.4.1 Executable commands
The following types of commands can be executed as automated actions:
- On a Windows host:
-
-
Executable file (.com or .exe)
-
Batch file (.bat)
-
Script file of JP1/Script (.spt) (provided the .spt file extension is associated with JP1/Script so that it can be executed)
-
Data file (including .vbs) that has a file type (extension) associated with an application that can be run as an automated action
-
- On a UNIX host:
-
-
UNIX command
-
Shell script
-
However, the following types of commands cannot be executed:
-
Commands that require interactive operation
-
Commands that display windows
-
Commands that use an escape sequence or control code
-
Non-terminating commands such as daemons
-
Commands (Windows only) that require interaction with the desktop, such as the Windows message structure or DDE
-
Commands that shut down the OS, such as shutdown and halt
- Important
-
In 64-bit editions of Windows, if you execute a command in the %WINDIR%\System32 folder, the WOW64 redirection function redirects the command to a command in the %WINDIR%\SysWow64 folder. If the command is not found in the destination folder, command execution might fail. Therefore, be careful when you specify a command in the %WINDIR%\System32 folder as the execution command.
- Important
-
If a command is executed by an automated action or from a command execution window and the executed command produces child processes, information such as the standard output of the child processes and detection of terminations is also acquired. However, if the executed command terminates before all of its child processes, the standard output of those child processes cannot be acquired. In addition, termination of those child processes cannot be detected correctly. This is because the command execution function manages only those commands that are executed directly. If an executed command produces child processes and grandchild processes, the child and grandchild processes must be managed by the command that is executed.
- Important
-
When a command or automated action executes a Windows PowerShell script, the script might seem to continue running because powershell.exe cannot exit properly. To execute a Windows PowerShell scrip, use the following command line to redirect the script from standard input to nul:
powershell.exe xxx.ps1 < nul