Overview
This page provides information on the Universal Data Mover (UDM) Manager, specific to the UNIX operating system.
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) or a script (batch mode). In interactive mode, commands come from standard input; in batch mode, they come from a script file.
This section describes the modes of operation, configuration and configuration options, and command line syntax of UDM Manager for UNIX.
Modes of Operation
Under UNIX, UDM can be run either in:
- Interactive mode
- Batch mode
Running UDM in Interactive Mode
To run UDM in interactive mode, enter the following at the command prompt:
udm
This starts the UDM Manager. You will be greeted with a start-up message and the UDM prompt:
UNV2800I Universal Data Mover 6.3.0 Level 0 started. udm>
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:
quit
Running UDM in Batch Mode
To run UDM in batch mode, enter udm on the command line and specify a script file via the SCRIPT_FILE option.
For example:
udm -script script_filename
When the script file has finished executing, UDM exits automatically.
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:
- Command line
- Command file
- Environment variables
- 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.
See Configuration Management for detailed information on these methods of configuration.
Configuration File
The configuration file, udm.conf, 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. (See the Universal Agent 7.6.x Installation, Upgrade, and Applying Maintenance to determine the directory in which it is located.)
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 UNIX. Each Option Name is a link to detailed information about that configuration option.
Option Name | Description |
Specification for whether or not product activity monitoring events are generated. | |
Specification for whether or not the UDM rename command will succeed if the new file name provided in that command matches the name of an existing file. | |
Broker Interface File directory where the Universal Broker interface file is located. | |
File name / ddname of the PEM-formatted trusted CA X.509 certificates. | |
File name / ddname of UDM Manager's PEM-formatted X.509 certificate. | |
Number of days prior to certificate expiration to begin issuing informational messages about the expiration. | |
File name / ddname of the PEM-formatted CRL. | |
Character code page used to translate text data received and transmitted over the network. | |
User-defined string. | |
Acceptable and preferred SSL/TLS cipher suites to use for the control session between UDM components. | |
Specification for whether or not data is compressed on all standard I/O files. | |
Acceptable and preferred SSL/TLS cipher suites to use for the data session on which file data is transferred between UDM primary and secondary servers. | |
Encryption method to be used in a UDM transfer session if one is not specified by an encrypt parameter in the UDM open command. | |
Events to be generated as persistent events. | |
Number of UDM transfer blocks transferred before a frame-sync message is sent when UDM is operating with network fault tolerance turned on. | |
Writes a description of the command options and their format. | |
Number of seconds of inactivity in an interactive UDM session after which the manager will close the session. | |
Directory on which UDM Manager is installed. | |
Default interval at which a keep alive message is sent from the manager to the transfer server(s). | |
Specification for whether or not to merge standard out and standard error output streams from a remote command to the UDM transaction log. | |
Universal Message Catalog (UMC) file used to write messages. | |
Level of messages to write. | |
Minimum SSL/TLS protocol level that will be negotiated and used for communications channels. | |
Default transfer mode type for UDM sessions. | |
List of message IDs representing Universal messages to be suppressed. | |
Expected network latency. | |
Specification for whether or not UDM transfer sessions are network fault tolerant by default. | |
Directory where the UDM Manager message catalog and code page tables are located. | |
Level of fault tolerance for the open command. | |
Maximum number of attempts that will be made to establish a session by the open command. | |
Number of seconds that UDM will wait between each open retry attempt. | |
Host or IP address that UDM binds to when initiating outgoing connections to another UDM server. | |
Program Lock File directory that specifies the location of the UDM Manager program lock file. | |
ddname of Manager's PEM formatted RSA private key. | |
Password for the Manager's PRIVATE_KEY. | |
Specification for whether or not UDM will use proxy certificates in three-party transfer sessions if a certificate is supplied to the UDM Manager. | |
Number of attempts the manager will make to re-establish a transfer session when a network fault occurs. | |
Number of seconds that UDM will wait between each successive attempt to re-establish a transfer session when a network fault occurs. | |
Size (in bytes) of the application's incoming buffer for UDM. | |
TCP port number on the remote computer used for invoking UDM Server instances. | |
Script file containing UDM commands to execute. | |
Options to pass to the script command file. | |
Size (in bytes) of the application's outgoing buffer for UDM. | |
Specification for whether or not to use TCP packet coalescing. | |
TCP/IP buffer size of a UDM Server on the receiving end of a two-party transfer. | |
Maximum number of lines to write to the trace file. | |
Size of a wrap-around trace table maintained in memory. | |
Sets the complete path to UCMD for calls by the exec command. | |
File mode creation mask. | |
Sets the complete path to USAP for calls by the execsap command. | |
Specification for whether or not the Universal Broker's X.509 certificate identity is verified. | |
Writes the program version information and copyright. |
Command Line Syntax
The following figure illustrates the command line syntax of UDM Manager for UNIX.
udm [-allow_repl_on_rename {yes|no}] [-bif_directory directory
[-plf_directory directory [-ca_certs file] [-cert file] [-private_key file [-private_key_pwd password] ] [-proxy_certificates {yes|no}] [-days number] [-crl file] [-script ddname] [-options options] [-codepage codepage] [-ctl_ssl_cipher_list list] [-data_ssl_cipher_list list] [-encrypt {yes|no|cipher} ] [-compress {yes|no}[,{zlib|hasp}] ] [-delay seconds] [-idle_timeout seconds] [-keep_alive_interval seconds] [-lang language] [-level {trace|audit|info|warn|error}[,{time|notime}] ] [-msg_suppression_list list ] [-min_ssl_protocol option] [-network_fault_tolerant {yes|no} [-frame_interval number] ] [-mode_type {binary|text}] [-umask number] [-outboundip host] [-port port] [-recvbuffersize size] [-open_retry {yes|no}] [-open_retry_count number] [-open_retry_interval number] [-retry_count number] [-retry_interval seconds] [-sendbuffersize size] [-saf_key_ring name] [-saf_key_ring_label label] [-server_stop_conditions codes] [-tcp_no_delay option] [-tcp_window_size size] [-tracefilelines number] [-trace_table size,{error|always|never}] [-verify_host_name {yes|no}|host name] [-comment text] udm { -help | -version }