...
The primer discussions are from the perspective of the initiating system where the Universal Command (UCMD) Manager component is executed via the Universal Data Mover (UDM) exec command.
The primer examples assume that Universal Data Mover is installed with default configuration values to help keep the examples consistent and clear. UCMD components must be installed both on the local system from which the UCMD Manager is executed as well as the remote system where UCMD Server is executed.
The primer examples demonstrate how to execute a command on a remote system using the UDMD Manager component via the UDM Manager component using the UDM exec command. All examples use the same set of parameters.
...
This page illustrates the minimum set of parameters required to execute a remote process via the Universal Data Mover (UDM) exec command using UDM scripting language syntax.
The platform-independent nature of the UDM scripting language means that the format of exec is the same regardless of the UDM Manager's host platform. See the Universal Data Mover 7.6.x Reference Guide for platform-specific information on executing UDM Manager, using UDM script files, and invoking exec.
exec instructs UDM to spawn a Universal Command (UCMD) Manager process. The Universal Command 7.6.x Reference Guide contains platform-specific information for invoking UCMD Manager. A UCMD Server installed on the remote system receives the command specified by exec's cmd parameter and executes it.
If security is enabled in the remote UCMD Server's configuration, exec must provide user account information. To establish a secure execution environment, the UCMD Server requires a user account ID, which exec specifies via the user parameter. The UCMD Server may also require a password (pwd) to authenticate the user account, depending on the remote operating system and Universal Agent configuration.
For information on securing access to Universal Agent components, see Universal Agent Security.
Executing the Examples
To execute the following examples in your environment, simply make these changes to the values specified in the command's parameters:
...
In each of these examples, the UCMD Manager establishes a network connection to the UCMD Server installed on the remote system (dallas). The UCMD Manager passes exec parameters to the UCMD Server over this connection. UCMD Server then executes the command as local user named joe.
...
When the remote command completes, the UCMD Server retrieves the process' exit code and status and forwards them to the local UCMD Manager, which exits with that same value. The UDM Manager stores this exit code in its built-in _execrc variable.
Remote Execution Requirements for z/OS
These examples illustrate how to execute a process on a remote z/OS system using the UDM exec command. Each example lists the contents of the /u/joe directory in the z/OS UNIX file system.
...
To execute a command on a remote system using an active UDM transfer session, follow the example shown in #Remote z/OS Execution Using a UDM Logical Session Name.
The exec command initiates UCMD Manager using the UCMDPRC JCL procedure installed in the SUNVSAMP library.
| Anchor | ||||
|---|---|---|---|---|
|
| Panel |
|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Panel |
|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Panel |
|---|
|
...
These examples illustrate how to execute a process on a remote Windows system using the UDM exec command. Each example lists the contents of the root directory on the c: drive.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Panel |
|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Panel |
|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Panel |
|---|
open rmtsys=dallas user=joe pwd= abcdefg exec rmtsys cmd="dir c:\" |
Remote Execution Requirements for UNIX
These examples illustrate how to execute a process on a remote UNIX system using the UDM exec command. Each example lists the contents of the home directory for the user account named joe.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Panel |
|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Panel |
|---|
exec dallas cmd="ls -al /home/joe" user=joe pwd=abcdefg |
| Anchor | ||||
|---|---|---|---|---|
|
| Panel |
|---|
open rmtsys=dallas user=joe pwd= abcdefg exec rmtsys cmd="ls -al /home/joe" |
...
These examples illustrate how to execute a process on a remote IBM i system using the UDM exec command. Each example lists the contents of the library joelib.
...
To execute a command on a remote system using an active UDM transfer session, follow the example shown in #Remote IBM i Execution Using a UDM Logical Session Name.
The exec command initiates UCMD Manager via runtime linkage on IBM i. Stonebranch only supports runtime linkage to the UCMD Manager using the exec command.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Panel |
|---|
exec 192.168.10.111 cmd="dsplib joelib" user=joe pwd=abcdefg |
| Anchor | ||||
|---|---|---|---|---|
|
| Panel |
|---|
exec dallas cmd="dsplib joelib" user=joe pwd=abcdefg |
| Anchor | ||||
|---|---|---|---|---|
|
| Panel |
|---|
open rmtsys=dallas user=joe pwd= abcdefg exec rmtsys cmd=" dsplib joelib" |
...