Execution mode details
The Execution mode menu selects how the command is executed. The command may be executed directly or within a shell. The command may also be executed as the user that started server or as the System Command user. The execution mode determines the execution syntax, or how the command is executed; the execution syntax wraps the specified command with appropriate shell or user options.
The following table summarizes the options for execution mode. Here, {command} is the text in the Command field, {user} is the System Command user specified in pfserv config, and {password} is the System Command password specified in pfserv config.
Execution mode | Execution syntax | Description |
---|---|---|
run program directly | {command} | Runs an executable program directly, with no shell. Shell options such as output redirection will not work in this mode. |
run shell | sh –c {command} | Runs the command within an sh POSIX shell. On Windows, sh is part of MKS Toolkit. |
run Korn shell | ksh –c {command} | Runs the command within a ksh Korn shell. On Windows, ksh is part of MKS Toolkit. |
run shell as System Command user (Unix only) |
Runs the command in a sh or ksh shell as the System Command user on Unix via the su (substitute user) command. System Command username is configured using the tool, pfserv config. System Command password is not used. Note:
The server must run as root to use this option. |
|
run shell as System Command user with password (Windows only) | No longer supported |
No longer supported execution modes. If the Unix utilities available to your Windows system support the "su" command, you might be able to run a revised command using a different execution mode and including within the command the syntax related to "su" to achieve the same results. When constructing the command, you can use **Username** and **Password** in the command syntax to reference the username and password values on the related System Command Connection Configuration. These markers will be resolved to those username and password values at run time. If you are working with a flow that was converted from Infor ProcessFlow and that used these parameters, download and read the Lawson Knowledge Base article "System Command Activity Node: Converting from ProcessFlow to Infor Process Automation" for more information. |
run shell as System Command user with password (Windows only) | su –p {password} {username} –c {command} | |
run cmd.exe (Windows only) | cmd.exe /C {command} | Runs the command in the Windows command interpreter (cmd.exe). |
run cmd.exe as System Command user with password (Windows only) | su –p {password} {username} –c cmd.exe /C {command} | Obsolete parameter. If you are working with a flow that was converted from Infor ProcessFlow and that used this parameter, download and read the Lawson Knowledge Base article "System Command Activity Node: Converting from ProcessFlow to Infor Process Automation." |