...
To run UDM in interactive mode, enter the following at the command prompt:
Panel | |
---|---|
Html bobswift | udm
</pre>
|
This starts the UDM Manager. You will be greeted with a start-up message and the UDM prompt:
Panel |
---|
<pre>
UNV2800I Universal Data Mover 6.3.0 Level 0 started.
udm>
</pre>
|
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:
Panel |
---|
<pre>
quit
</pre>
|
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:
Panel | |
---|---|
Html bobswift | udm -script script_filename
</pre>
|
When the script file has finished executing, UDM exits automatically.
...
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. |
...
The following figure illustrates the command line syntax of UDM Manager for UNIX.
Panel | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Html bobswift | udm
[ -allow_repl_on_rename Html bobswift | { <b>yes</b>|<b>no</b>yes|no}] [ -bif_directory
directory Html bobswift | directory [ -ca_certs Html bobswift | file] [ -cert Html bobswift | file] [ -private_key Html bobswift | file [ -private_key_pwd Html bobswift | password] ] [ -proxy_certificates Html bobswift | { <b>yes</b>|<b>no</b>yes|no}] [ -days Html bobswift | number] [ -crl Html bobswift | file] [ -script Html bobswift | ddname] [ -options Html bobswift | options] [ -codepage Html bobswift | codepage] [ -ctl_ssl_cipher_list Html bobswift | list] [ -data_ssl_cipher_list Html bobswift | list] [ -encrypt Html bobswift | { <b>yes</b>|<b>no</b>|<b>cipher</b>yes|no|cipher} ] [ -compress Html bobswift | { <b>yes</b>|<b>no</b>yes|no}[,{<b>zlib</b>|<b>hasp</b> zlib|hasp}] ] [ -delay Html bobswift | seconds] [ -idle_timeout Html bobswift | seconds] [ -keep_alive_interval Html bobswift | seconds] [ -lang Html bobswift | language] [ -level Html bobswift | { <b>trace</b>|<b>audit</b>|<b>info</b>|<b>warn</b>|<b>error</b>trace|audit|info|warn|error}[,{<b>time</b>|<b>notime</b> time|notime}] ] [ -msg_suppression_list Html bobswift | list ] [ -min_ssl_protocol Html bobswift | option] [ -network_fault_tolerant Html bobswift | { <b>yes</b>|<b>no</b>yes|no} [ -frame_interval Html bobswift | number] ] [ -mode_type Html bobswift | { <b>binary</b>|<b>text</b>binary|text}] [ -umask Html bobswift | number] [ -outboundip Html bobswift | host] [ -port Html bobswift | port] [ -recvbuffersize Html bobswift | size] [ -open_retry Html bobswift | { <b>yes</b>|<b>no</b>yes|no}] [ -open_retry_count Html bobswift | number] [ -open_retry_interval Html bobswift | number] [ -retry_count Html bobswift | number] [ -retry_interval Html bobswift | Html bobswift | seconds] [-sendbuffersize size] [-saf_key_ring name] [ -saf_key_ring_label label] [-server_stop_conditions codes] [ -tcp_no_delay Html bobswift | option] [ -tcp_window_size Html bobswift | size] [ -tracefilelines Html bobswift | number] [ -trace_table Html bobswift | size,{<b>error</b>|<b>always</b>|<b>never</b> error|always|never}] [ -verify_host_name Html bobswift | { <b>yes</b>|<b>no</b>yes|no}|<i>host hostrname</i> name] [ -comment Html bobswift | text] udm { -help Html bobswift | | -version Html bobswift | }
</pre>
|