Overview

This page provides information on the Universal Data Mover (UDM) Manager, specific to the IBM i operating system. It describes the commands, modes of operation, configuration and configuration options, and command line syntax of UDM Manager for IBM i.

UDM Manager transfers files between any computers running UDM Server. Using a UDM command script, you indicate to the UDM Manager the actions to take. The UDM Manager connects to the UDM Server (or Servers) and processes your request.

Usage

UDM Manager is executed from the command line (interactive mode), a script file, or in batch mode. In interactive mode, commands come from standard input; in batch mode, they come from a script file.

Workload Automation 5 for IBM i Commands

The names of the Workload Automation 5 for IBM i commands that are installed in the IBM i QSYS library are tagged with the Workload Automation 5 for IBM i version / release / modification number, 511.

The names of the commands installed in the Workload Automation 5 for IBM i product library, UNVPRD511, are untagged.

To maintain consistency across releases, you may prefer to use the untagged names in your production environment. The Change Release Tag program, UCHGRLS, lets you change the tagged command names in QSYS to the untagged command names in UNVPRD511.

These pages reference the IBM i commands by their untagged names. If you are using commands with tagged names to run UDM, substitute the tagged names for the untagged names in these references.

Modes of Operation

Under IBM i, UDM can be run either:

• In interactive mode
• From a script file
• In batch mode

Additionally under IBM i, UDM can use either the LIB or HFS file system.

Running UDM in Interactive Mode

To run UDM in interactive mode, enter the following at the command prompt:

This starts the UDM Manager. You will be greeted with a start-up message and the UDM prompt:

UDM now is ready to process commands. At the udm> prompt, you can enter any UDM command.

To exit UDM, enter the following command at the udm> prompt:

Running UDM from a Script

To invoke a UDM script, enter the following on the command line:

This starts the UDM Manager using the script located by library, file, and member.

When the script file has finished executing, UDM exits automatically.

UDM requires the member name (there is no default). This makes script specification under IBM i behave as it does on other platforms. On other systems, there is no default search order as exists under IBM i. However, you can explicitly provide *FILE as a member name to use the IBM i default file search order.

Running UDM in Batch Mode

(When running in batch mode, use a script as shown in #Running UDM from a Script.)

To execute a batch file such as the one below, use SBMDBJOB FILE(LIBNAME/FILENAME) MBR(MBRNAME):

Output is sent to the output queue associated with the batch job. Two spooled files will be sent to the output queue; one file associated with standard out and one file associated with standard error.

Configuration

Configuration consists of:

• Setting default options and preferences for all executions of UDM Manager.
• Setting options and preferences for a single execution of UDM Manager.

Configuration options are read from the following sources:

1. Command line
2. Command file
3. Environment variables
4. Configuration file

The order of precedence is the same as the list above; command line options being the highest and configuration file being the lowest. That is, options specified via the command line override options specified via a command file, and so on.

Detailed information on these methods of configuration can be found in Configuration Management.

Configuration File

The configuration file provides the simplest method of specifying configuration options whose values will not change with each command invocation. These default values are used if the options are not read from one or more other sources.

The installation default for the UDM configuration file is Workload Automation 5 installation library UNVPRD511, file UNVCONF, and member UDM. The configuration file name can be any valid file name. It can be edited manually using an IBM i editor such as SEU, EDTF, or any other installed source file editor, or via the IFS using a text editor. If a text editor is used to edit the file via the IFS, the padded spaced must be removed for lines that exceed the file maximum record length.

Some options only can be specified in the configuration file; they have no corresponding command line equivalent. Other options cannot be specified in the configuration file; they must be specified via one or more other sources for a single execution of UDM Manager.

Configuration Options

The following table describes the configuration options used to execute UDM Manager for IBM i. Each Option Name is a link to detailed information about that configuration option.

Command Line Syntax

The following figure illustrates the command line syntax of UDM Manager for IBM i.

STRUDM
[SCRFILE([library/]filename) [SCRMBR(member) ]
[PLFDIR (directory)]
[OPTIONS(options)]
[CODEPAGE(codepage)]
[CTLCPHRLST(cipherlist)]
[DTACPHRLST(cipherlist)]
[ENCRYPT {*yes|*no|cipher} ]
[COMPRESS(*{yes|no})]
[CMPRSMTH(*{zlib|hasp})]
[DELAY(seconds)]
[IDLTIMOUT(seconds)]
[KEEPALIVE(seconds)]
[MODETYPE (*{bin|binary|text}]
[MSGLANG(language)]
[[MSGLEVEL(*{trace|audit|info|warn|error}) [,*{yes|no}] ]
[MINSSLPROTOCOL(option)]
[NETWORKFT(*{yes|no}) [FRAMEINT(number)]]
[OPENRETRY(*{yes|no} count interval)]
[OUTBOUNDIP(host)]
[PORT(port)]
[PROXYCERT(option)]
[RCVBUFSIZE(size)]
[RETRYCNT(number)]
[RETRYINT(seconds)]
[SNDBUFSIZE(size)]
[TCPNODELAY(*{yes|no})]
[TCPWINSIZE(size)]
[TRCLINES(number)]
[TRCTBL(size,*{error|always|never})]
[CACERTS(file [lib] ) [CACERTSMBR(member)] ]
[CERT(file [lib] ) [CERTMBR(member)]
     [PVTKEYF|PRIVATE_KEY - UDM Manager configuration option](file [lib] ) [PVTKEYFMBR(member)] [PVTKEYPWD(password)] ]
[CRLFILE(file [lib]) [CRLMBR(member)] ]
[COMMENT(user-defined string)]


STRUDM
[VERSION(*{yes|no})]