Universal Data Mover Server for z/OS
Overview
This page provides information on the Universal Data Mover (UDM) Server, specific to the z/OS operating system.
Component Definition
All Universal Agent components managed by Universal Broker have a component definition. The component definition is a text file of options containing component-specific information required by Universal Broker. (For details on how Universal Broker manages components, see the Universal Broker 7.3.x Reference Guide.)
The UDM Server for z/OS component definition is located in the component definition library #HLQ.UNV.UNVCOMP allocated to the Universal Broker ddname UNVCOMP. The UDM Server component definition member is UDSCMP00.
The following table identifies all of the options that comprise the UDM Server for z/OS component definition. Each Option Name is a link to detailed information about that component definition option.
Option Name | Description |
|---|---|
Specification for whether or not UDM Server starts automatically when Universal Broker is started. | |
Name by which the clients know the UDM Server. | |
Member name of the UDM Server configuration file in the UNVCONF library allocated to the Broker ddname UNVCONF. | |
Maximum number of UDM Servers that can run simultaneously. | |
Member name of the UDM Server program. | |
HMS directory used as the working directory of the UDM Server. |
Configuration
Universal Data Mover Server configuration consists of defining runtime and default values.
Configuration File
The configuration file provides the simplest method of specifying configuration values that will not change with each command invocation.
The UDM Server configuration file name is specified in the Universal Data Mover Server component definition (see Universal Data Mover Component Definition Options). The default name is UDSCFG00. The name refers to a member in the PDS allocated to the Universal Broker ddname UNVCONF.
Configuration Options
The following table identifies all UDM Server for z/OS command options. Each Option Name is a link to detailed information about that option.
Option | Description |
|---|---|
Specification for whether or not product activity monitoring events are generated. | |
Abnormal disposition of a data set being allocated. | |
Block size used for newly allocated data sets. | |
SMS data class used for newly allocated data sets. | |
Number of directory blocks for newly allocated partitioned data sets. | |
Data set organization used for newly allocated data sets. | |
Status of data sets being allocated for input. | |
Logical record length used for newly allocated data sets. | |
SMS management class used for newly allocated data sets. | |
Normal disposition of a data set being allocated. | |
Status of existing data sets being allocated for output. | |
Primary space allocation used for newly allocated data sets. | |
Record format used for newly allocated data sets. | |
Secondary space allocation used for newly allocated data sets. | |
Space unit in which space is allocated for newly allocated data sets. | |
SMS storage class used for newly allocated data sets. | |
Unit used for newly allocated data sets. | |
Volume serial number used for newly allocated data sets. | |
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. | |
Character code page used to translate text data. | |
Specification for whether or not data is compressed on all standard I/O files. | |
SSL/TLS cipher suites to use for data session between UDM primary and secondary servers. | |
Events to be generated as persistent events. | |
Number of UDM transfer blocks transferred before a frame-sync message is sent with network fault tolerance turned on. | |
Level of messages that UDM will write to the Universal message Catalog (UMC) file. | |
Minimum SSL/TLS protocol level that will be negotiated and used for communications channels. | |
List of message IDs representing Universal messages to be suppressed. | |
Expected network latency (in seconds). | |
Host or IP address that UDM binds to when initiating outgoing connections to another UDM server. | |
Number of attempts that the UDM 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. | |
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 secondary UDM Server that receives a file from a primary Server in a three-party transfer. | |
Directory that UDM Server uses for temporary files. | |
Maximum number of lines to write to the trace file. | |
Size of a wrap-around trace table maintained in memory. | |
File mode creation mask. | |
User security option. | |
User security option. |
Universal Access Control List
UDM Server uses the Universal Access Control List (UACL) file as an extra layer of security. The UACL file contains Universal Data Mover Server entries that contain Access Control List (ACL) rules that permit or deny access to the Server.
UACL Entries
The syntax of a UACL entry file is the same as the UDM configuration file.
The following table identifies all UDM Server for z/OS UACL entries. Each UACL Entry Name is a link to detailed information about that UACL entry.
UACL Entry Name | Description |
|---|---|
Allows or denies access to Universal Data Mover Server services | |
Allows or denies access based on the host name and/or user of the Manager trying to initiate a UDM session. |