Home

Universal Data Mover 3.2.0 User Guide

1. MESSAGE_LANGUAGE Universal Message Catalog UMC file used to write messages MESSAGE_LEVEL Level of messages to write MODE_TYPE Default transfer mode type for UDM sessions NETWORK_DELAY Expected network latency NETWORK_FAULT_TOLERANT Specification for whether or not UDM transfer sessions are network fault tolerant by default OPEN_RETRY Level of fault tolerance for the open command udm user 3207 Confidential amp Proprietary 127 Usage Universal Data Mover Manager for OS 400 OPEN_RETRY_COUNT OPEN_RETRY_INTERVAL 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 OUTBOUND_ IP Host or IP address that UDM binds to when initiating outgoing connections to another UDM server PLF_DIRECTORY Program Lock File directory that specifies the location of the UDM Manager program lock file PRIVATE_KEY Location of Manager s PEM formatted RSA private key PRIVATE_KEY_PWD Password for the Manager s PRIVATE_KEY PROXY_CERTIFICATES Specification for whether or not UDM will use proxy certificates in three party sessions if a certificate is supplied to the UDM Manager RECONNECT_RETRY_COUNT Number of attempts the manager will make to re establish a transfer session when a network fault occurs RECONNECT_RETRY_INTERVAL Number of seconds that UDM will
2. 56 244 Modifying Entering Data vos siccsas sa rs A Siaee nied 56 Rules for Modifying Entering Data 0 2 eee ee 56 245 SAVING Data circa dee aa i E aa Bead 57 2 4 6 Accessing Help Information 0 0 00 c eee eee 57 2 4 7 Universal Data Mover Installed Components 505 58 Universal Data Mover Manager 0 002 e ee ees 58 Universal Data Mover Server 0 000 ee 59 2 5 Network Data Transmission 0 0 0 ee 60 2 5 1 Secure Socket Layer Protocol 000 cece eee ees 60 Data Privacy and Integrity lt icccs ewes Mee naw e A Aa 61 Peer Authentication scaricare a t 62 2 5 2 Universal Products Protocol oooo0ooooooooomrarnoros 63 Data Privacy and Integrity ocoooooooooorcrrocrrncan es 63 2 5 3 Universal Products Application Protocol oooooooooo o 64 Low Overhead umi cala dd A Aaa sd 64 SOOUIE estr AE RRE a ARA 64 Extensible peet ii rd da dada 65 2 5 4 Configurable Attributes ooooooccrrrnrrr es 66 2 6 Fault Tolerance lt cciccendnon ne RRE Fak Se een ne eeak eae E 70 2 6 1 Network Fault Tolerance ooooooocrcrrrcrrar ee 70 202 Open REY a cise e Ria ri Mea eo Mee oe ees 71 2 6 3 Component Management ocooooocrrnnncr 72 2 7 z OS CANCEL Command Support 0000 cece eee 73 LA EXIPCOAOS da a Da Maratea ney Ata p RANS 73 udm user 3207 Confidential amp Proprietary 14 Contents
3. 0 000 000 eee 182 11 6 7 Variable Attributes 0 0 00 eee 183 exists Attribute o oo oo oo coco 183 length Attribute candace cepa iketeehed sc ee Ree Ree ee KORE 183 11 6 8 Built in Variables 0 0 000000 cee 184 date aee Sy O O Ree eccrine 185 SOCIO hee ti rss ri a tada 185 JOXBCIC voaat ri A A bi a fous E 185 MM A A RA AA A RASE 186 ANAON Sae a as E E et Saeed mere eta 187 _keepalive 2 0 2 een eens 187 ASIS estare AA a nex eakeneem ead t 187 ASIC fi ty ia Sak Hees yn ener ee kee Gente wh E ene eee a a 188 A ahs tesa nt toscana a E teacnten E AN ane A Gat pce tenet A eat 189 pathi id da adan site 189 TOS Darro Doro o ERA a e e 189 AING ic a A Ca bee A Ed A ee eS 190 Aud il aa a ai ead oat 190 11 6 9 Logical Name Built In Variables ooooooocccccoooo 191 EXaMpl S sion a ca a e a aca A Racal aL e od een A 191 11 0 Statement aras ada daa eta ai 192 11 7 1 Comparison Operations ooocoooooooorr ee 192 Comparators ac csi weak RR a ee kone ala na aed Komal E 192 EQSIEQUal sucias aesae a PP Ah eee aa ee a 193 udm user 3207 Confidential amp Proprietary 19 Contents NE NOtEQUAl ies cies a fared eee a a de Face eres 193 LT Less Than 0 ccc eee eee eens 194 GT Greater Than 2 0 194 LE Less Than or Equal 0 0000 c cece eee es 194 GE Greater Than or Equal 0000 es 195 11 7 2 Adding an Alternate Path with else Stateme
4. 00 0 ce eee eee eee 114 Figure 5 1 UDM Manager for UNIX Command Line Syntax s 119 Chapter 6 Universal Data Mover Manager for OS 400 o ooooocooooommmmmmmoo 122 Figure 6 1 UDM Manager for OS 400 Command Line Syntax ees 129 Chapter 8 Universal Data Mover Server for Windows 000 cee eee eens 140 udm user 3207 Confidential amp Proprietary 25 List of Figures Figure 8 1 Universal Configuration Manager Component Definitions 141 Figure 8 2 Universal Configuration Manager Universal Data Mover Server ACCESS ML ios EEA 147 Chapter 13 Transfer Operations z OS Specific ooooooooommmmmmmmmm oo 235 Figure 13 1 Load Module Transfer Script Example o o ooooccccccncccccccnnonononnninnninnnoss 251 Figure 13 2 Load Module Transfer Script Output oooooooococccccccnnccnnconnconcnnnncnoncnnness 251 udm user 3207 Confidential amp Proprietary 26 List of Tables Preface A E NAO 30 Table P 4 Command Line Syntax mspeiocinasica fla tind cilantro careta btencedemsudinn aici dotengst 31 Chapter 2 Features 1000 a 38 Table 2 1 UNIX Configuration File Directory Search ooooocccccnnninocccccnnncccnnncannccncnnnnnns 46 Table 2 2 Supported SSL cipher Suites ooonccccncncccnconoonnnononnnnnononononononennnnnonononananens 62 Table 2 3 Component Communication States ooconcnncncnnnncccncononcnonnnnnnnononanenenens 72 Table 24 Certificate Ma
5. Open Retry is used during the establishment phase of a session UDM tries to establish a session when the open command is issued If the OPEN_RETRY option value is yes and UDM fails to establish the session due to a network error timeout or the inability to start a transfer server it will retry the open command based on the settings of the OPEN_RETRY_COUNT and OPEN_RETRY_INTERVAL options udm user 3207 Confidential amp Proprietary 71 Fault Tolerance Features 2 6 3 Component Management In order to fully understand Universal Data Mover fault tolerant features some understanding of how the Universal Broker manages components is necessary Universal Broker manages component startup execution and termination The broker and its components have the ability to communicate service requests and status information between each other The Broker maintains a database of components that are active or have completed and waiting for restart or reconnection The component information maintained by the broker determines the current state of the component This state information is required by the broker to determine if a restart or reconnect request from a manager is acceptable or not The broker s component information can be viewed with the Universal Query program One piece of component information maintained by the broker is the component s communication state The communication state primarily determines what state the Universal Da
6. mark 11 3 2 Sample UDM Script The following is a sample UDM script Open a transfer session open src dst ntmachine Copy command using line continuation copy src test txt dst test txt if 8 EQ _lastrc print msg The last command resulted in an error end Close the transfer session and exit UDM quit udm user 3207 Confidential amp Proprietary 166 UDM Command Format UDM Scripting Language 11 3 3 Expressions The following basic rules apply to expressions in UDM commands Appearance An expression can appear either as a parameter or its value It must comprise the entire parameter or value in which it appears not just part of it For example in the following command lt 2 2 gt is not an expression echo 2 2 lt 2 2 gt It is merely part of the quoted string and the output would be 2 2 lt 2 2 gt In order to treat lt 2 2 gt as an expression the command must be echo 2 2 lt 2 2 gt The output of this command is 2 2 4 Integer Only Although floating point number are allowed in expressions everything is evaluated as an integer The only exception is that the EQ Equal and NE Not Equal comparators can be used to compare strings as well as numbers Delimiters All expressions must be bound by left angle lt and right angle gt brackets For example set value lt 2 2 gt Operand Operator Delimiters Operands and operators in an e
7. udm user 3207 Confidential amp Proprietary 124 Usage Universal Data Mover Manager for OS 400 Running UDM in Batch Mode UDM also can be run in batch mode When running in batch mode use a script as shown in Section Running UDM from a Script To execute a batch file such as the one below use SBMDBJOB FILE LIBNAME FILENAME MBR MBRNAME BCHJOB JOB MYUDMJOB ENDSEV 10 STRUDM MYLIB QSCRSRC UDM817 ENDBCHJOB 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 udm user 3207 Confidential amp Proprietary 125 Usage Universal Data Mover Manager for OS 400 6 2 3 Configuration Configuration consists of e Setting default options and preferences for all executions of UDM Manager e 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 The configuration file provides the simplest method of specifying configuration options whose values will not change with each
8. udm user 3207 Confidential amp Proprietary 278 Chapter 15 Remote Execution 15 1 Overview This chapter provides information on Universal Data Mover UDM remote execution UDM provide two commands for remote execution exec Command execsap Command udm user 3207 Confidential amp Proprietary 279 exec Command Remote Execution 15 2 exec Command 15 2 1 Executing Remote Commands within UDM If you have a licensed version of the Universal Command UCMD Manager version 3 1 1 or later on the same system with the UDM Manager you can execute system commands on remote machines using the exec command The exec command has the following format exec ogical name host name cmd cmdref stc command user userid pwd password port port codepage codepage file f7 ename xfile 777ename key key option opt7on mergelog yes no trace yes no input data e ement svropt server options stdout data element stderr data element The first parameter of the exec command is either e Logical name logical name of a transfer server valid only if a transfer session has been established Host name host name of the machine on which you want to execute the command Note You must have the UCMD Server and Universal Broker installed on the machine on which the command is to be executed The second parameter is the command type which is either cmd command cmdref command reference e stc started t
9. 2 7 2 Security Token conoser o a da 74 2 8 Universal Access Control List 000 0c eee 75 2 8 1 UACL Configuration sxc accice Sesh RR Rak een ad ae eee AR ER 76 2 8 2 UACL Entries so ceccar saetas e aE EDE ete 77 Client Identification 0 0 0 0000s 77 Certificate Based and Non Certificate Based UACL Entries 81 2 8 3 Types of UACL RUGS cocinas wees e ls AA 82 UAM ACCESS ici a A a aa iaa 82 UM MgriaccessS vna ad dio 82 udm_cert_aCCe SS o 82 2 8 4 Proxy Certificates 2 ctiad kan rene RRA ra E AREA 83 2 9 Message and Audit Facilities oooooooooooocooommoo ro ooo 84 2 9 1 Message Types cod heehee a rola a ad A pee 84 2 9 2 Message ID cicccdance tae KRG Ree RES EA OR anra ERE 85 2 9 3 Message Levels cei ses coctel 85 2 9 4 Message Destinations 022 es 86 2 10 X 509 Certificates 0 0 02 eee 88 2 10 1 Sample Certificate Directory 00 0c ee 89 2 10 2 Sample X 509 Certificate 0 0 es 90 Certificate FieldS 0 0 0 0 eee 91 2 10 3 SSL Peer Authentication 00 00 es 92 Certificate Verification 00 0 0 92 Certificate Revocation o oo oo oooo cocer 92 Certificate Identification 00 eee 93 Certificate Support o 93 Chapter 3 Universal Data Mover Manager for z OS 0 0000 e eee eee 94 3 1 OVEIVIOW iso cen Baa en ee ea a a oe a Re 94 32 Usage PP RN 95 3 2 1 JOL Procedure wiii idos ici a eae dk
10. Table 10 1 UDM Server for OS 400 Component Definition Options udm user 3207 Confidential amp Proprietary 156 Configuration Universal Data Mover Server for OS 400 10 3 Configuration UDM Server configuration consists of defining runtime and default values This section describes the Server configuration options See Section 2 2 1 Configuration Methods for details on Universal Products configuration methods 10 3 1 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 UDM Server component definition see Section 10 2 Component Definition The default name is UNVPRD320 UNVCONF UDMS This file can be edited manually with any text editor udm user 3207 Confidential amp Proprietary 157 Configuration Universal Data Mover Server for OS 400 10 3 2 Configuration Options Table 10 2 identifies all Universal Data Mover Server for OS 400 configuration options Each Option Name is a link to detailed information about that configuration option in the Universal Data Mover 3 2 0 Reference Guide ACTIVITY_MONITORING Specification for whether or not product activity monitoring events are generated CODE_PAGE Character code page used to translate text data CODEPAGE_TO_CCSID_MAP Specification to use either the interna
11. udm ca_certs f7 e cert file private_key file private_key_pwd password proxy_certificates yes no crl file script f7 ename options options codepage codepage ctl_ssl_cipher_list 77st data_ssl_cipher_list 77st compress yes no zlib hasp delay seconds idle_timeout seconds keep_alive_interval seconds lang anguage level trace audit info warn error time notime network_fault_tolerant yes no frame_interval number mode_type binary text umask number outboundip host port port recvbuffersize s7ze open_retry yes no open_retry_count number open_retry_interval number retry_count number retry_interval seconds sendbuffersize size tcp_no_delay option tracefilelines number trace_table s7ze error always never comment text udm help version Figure 4 1 UDM Manager for Windows Command Line Syntax udm user 3207 Confidential amp Proprietary 112 Examples of UDM Manager for Windows Universal Data Mover Manager for Windows 4 3 Examples of UDM Manager for Windows Appendix A Examples provides operating system specific examples that demonstrate the use of Universal Data Mover Included in this appendix are the following examples that demonstrate the use of Universal Data Mover Manager for Windows and UNIX e Simple File Copy to the Manager e Simple File Copy to the Server e
12. 0 cee 211 12 2 3 Closing a Session 3 6 2 dsoceds cee ects wee ee a Mee eee eee ees 212 12 3 File Systems cours ERA a A eas 213 12 3 1 File System Overview ori a e eee SEE es 213 12 3 2 Changing the Current File System 000 ee eee eee 214 12 4 UDM Common File System 0000 ee ee 215 12 4 1 Common File System Terminology 00 eee eee eee ee 215 12 5 z OS File System anaaa anaana aana 217 12 6 OS 400 File Systems xc pag teak oat ae dal aa Gd See a ees 219 120 HFS ria Snes nett cin s 219 12 02 LB seai ri ida pics int ded se bio ed Fa E E 220 udm user 3207 Confidential amp Proprietary 20 Contents 12 7 Transfer Modes and Attributes 2 0 00 cee 221 12 7 1 Setting the Transfer Type 00 0c eee eee 221 12 7 2 Transfer Attributes 0 0000s 222 12 7 3 End of Line Sequence 2000 000 eee 223 eol Attribute faci ees Oe aaa Ok CAD Dew e ee Oe do 224 12 7 4 Line Length and Line Operations ooooooocnnmoo 225 12 8 Copying Files with UDM a c 08 coves Pe eee eG dees deenenehe dae GES ks 226 12 8 1 Simple Copy Operation 0 00000 0c eee 226 Examples sr caer nd a tise A A oe ea 226 12 8 2 Move Operation 00 000s 227 12 8 3 Copying Multiple Files Using Wildcards ooooo o 228 12 8 4 File Extension Attributes 0 00000 002 eee 229 12 8 5 File Creation Options 0 0000 000s 22
13. 0 000 cece eee eens 170 11 3 5 Examples of Expressions 0000000 eee eee 171 11 4 SCripl FIleS s 4200 40200 Gidbe44 delta dda dbnsietddaidae beeen eas 172 11 4 1 Invoking UDM in Batch Mode with Commands from a Script File 172 11 4 2 Invoking UDM Interactively with Commands from a Script File 173 udm user 3207 Confidential amp Proprietary 18 Contents 11 4 3 Invoking Scripts from within Scripts 0 00000 eee eee 174 11 4 4 Parameter Processing 0 20 e ec eee eee eee 174 11 5 Subroutines 0 0 ete eeee 175 11 51 1 ck id cctesenees GOR RTS p i eee aa ea eed daal eta ees 175 Defining a Subroutine eh pn eos Weed a Sew hee Pee eee Nee eee 175 INVOKING a Subroutine sica Souda eee eee ee eee oe ee eee es 175 Sequence of Defining Invoking a Subroutine 0055 176 Nesting Recursion of Subroutines 0 000 cee ees 176 11 02 Example vu dadas tad de 177 OUUU rosa a ea rape a aci 177 11 6 UDM Variables o ooooocooocoocc ete 178 11 6 1 Variable Types 2osurprrarodi abandonaba ia a ed a 178 Variable Names 2 0 0 cc ete eens 178 11 6 2 Variable Reference 000 000 ee 178 11 6 3 Script Variables 0 0 0 eee 179 11 6 4 Global Variables 0 0000 0000s 179 11 6 5 Scope of Script and Global Variables ooooooo 180 Variable Scope Scripts oooooooooooo eee 181 11 6 6 User Defined Variables
14. 5 4 Security Universal Data Mover is designed to be a secure system As the level of security rises so does the administrative complexity of the system Universal Data Mover has balanced the two to avoid the administrative complexity with a minimum sacrifice to security Universal Data Mover security concerns are Access to Universal Data Mover files and directories Access to Universal Data Mover configuration files Universal Data Mover user account Privacy and integrity of transmitted network data User authentication 2 0 NS 5 4 1 File Permissions Only trusted user accounts should have permission to write to the Universal Data Mover installation directory and subdirectories and all files within those directories 5 4 2 Configuration Files Only trusted user accounts should have write permission to the Universal Data Mover configuration files and add and delete access to the directories in which they reside udm user 3207 Confidential amp Proprietary 121 Chapter 6 Universal Data Mover Manager for 0S 400 6 1 Overview This chapter provides information on the Universal Data Mover UDM Manager specific to the OS 400 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 udm user 3207 Confidential amp Proprietary
15. ADDENVVAR ENVVAR UDMLEVEL VALUECINFO udm user 3207 Confidential amp Proprietary 44 Configuration Features 2 2 5 Configuration File Configuration files are used to specify system wide configuration values They are last in precedence order for specifying configuration options see Section 2 2 1 Configuration Methods For most Universal Products some options can be specified only in a configuration file while other options can be overridden by individual command executions The Stonebranch Inc documentation for each product identifies these options If an option is specified more than once in a configuration file the last option specified is used All configuration files on a system are maintained by the local Universal Broker The Universal Broker serves the configuration data to other Universal Products running on the local system The one exception is Universal Enterprise Controller UEC UEC directly reads its own configuration files The Universal Broker reads the configuration files when it first starts or when it receives a REFRESH command from Universal Control or Universal Enterprise Controller Any changes made to a configuration file are not in effect until the Broker is recycled or receives a REFRESH command Universal Product components do not read the configuration files themselves When a component starts it first registers with the locally running Universal Broker As part of the registratio
16. Command Reference Transfer Operations OS 400 Specific 14 4 7 rename Rename Command The rename Rename command in the UDM for OS 400 LIB file system takes the following form RENAME logical name old name new name rename Command Requirements The rename command has the following requirements e Libraries cannot be renamed Asingle object level file or member can be renamed only with a single call The name of a file and one of its members cannot be renamed with a single call All other cases result in a failure e Wild cards are not allowed It can be used only at the file and member level it cannot be used to rename libraries However rename can be used to move existing files to existing libraries e It cannot be used to move a member from one file to another since the destination file may not have the same attributes for example record length as the source file This could result in corrupt or seemingly corrupt data It cannot be used to move a file from one library to another because it should not be used to create new libraries udm user 3207 Confidential amp Proprietary 277 Command Reference Transfer Operations OS 400 Specific rename Command Forms RENAME logical name LIBRARY FILE LIBRARY FILE Renames the file in the old portion with file name in the new portion The library in the new name portion of the rename must match the library name in the old name portion RENAME logic
17. ST mebrancA Universal Data Mover User Guide Universal Products Version 3 2 0 udm user 3207 Universal Data Mover User Guide Universal Products 3 2 0 Universal Data Mover Manager lt lt lt lt lt lt lt lt Universal Data Mover Server udm user 3207 Confidential amp Proprietary 3 Stonebranch Documentation Policy This document contains proprietary information that is protected by copyright All rights reserved No part of this publication may be reproduced transmitted or translated in any form or language or by any means electronic or mechanical including photocopy recording or any information storage and retrieval system without permission in writing from the publisher Requests for permission to make copies of any part of this publication should be mailed to Stonebranch Inc 950 North Point Parkway Suite 200 Alpharetta GA 30005 USA Tel 678 366 7887 Fax 678 366 7717 Stonebranch Inc makes no warranty express or implied of any kind whatsoever including any warranty of merchantability or fitness for a particular purpose or use The information in this documentation is subject to change without notice Stonebranch shall not be liable for any errors contained herein or for incidental or consequential damages in connection with the furnishing performance or use of this document All products mentioned herein are or may be trademarks of their re
18. alloc_abnormal_disp keep delete catlg uncatlg alloc_blksize s7ze alloc_dataclas c ass alloc_dir_blocks number alloc_dsorg po ps alloc_input_status old shr alloc_lrecl ength alloc_mgmtclas class alloc_normal_disp keep delete catlg uncatlg alloc_output_status old shr alloc_prim_space space alloc_recfm format alloc_sec_space space alloc_space_unit cyl trk aumber alloc_storclas class alloc_unit un7t alloc_volser number system_id ID ssl_implementation f openss1 system ca_certs ddname cert ddname private_key ddname private_key_pwd password proxy_certificates yes no crl ddname script ddname options options codepage codepage ctl_ssl_cipher_list 7st data_ssl_cipher_list 77st compress yes no zliblhasp delay seconds idle_timeout seconds keep_alive_interval seconds lang anguage level trace audit info warn error time notime Figure 3 3 UDM Manager for z OS Command Line Syntax 1 of 2 udm user 3207 Confidential amp Proprietary 103 Usage Universal Data Mover Manager for z OS network_fault_tolerant fyes noj 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_int
19. filename Stoneman s Tip a en length Attribute The length attribute expands to the length of the variable s value If the length attribute is used for a variable that does not exist an error is issued You can use the length attribute in combination with the if statement to decide if a file name is too long to copy to a remote system if Cfilename length LE 8 copy src filename end Stoneman s Tip udm user 3207 Confidential amp Proprietary 183 UDM Variables UDM Scripting Language 11 6 8 Built in Variables UDM provides built in variables that are used to make available some of its internal values to UDM commands Depending on the variable their values are provided by UDM and or defined via the set command Note All built in variables are preceded by an underscore _ to indicate that they are built in variables reserved by UDM Version 1 1 0 of UDM had four built in variables echo halton lines and rc The names of these variables were not preceded with an _ as they are in version 3 1 0 and later For the purpose of backward compatibility these variables can be referenced by their 1 1 0 names as well Stoneman s Tip Table 11 3 lists all of the UDM built in variables and provides a link to detailed information about them in this section _date Displays the current date in the format appropriate for the system s locale 18
20. COMMUNION ss reos nde IIA NR 116 5 2 3 Configuration Options asko RRA A Re wE 117 5 2 4 Command Line Syntax oooococcrccaro or eee be Eee we 119 5 3 Examples of UDM Manager for UNIX 00002 ee 120 IA SECUI O Bh Smee Tate a cle eS ae ecw ca ald een 121 5 4 1 PUP EMnSsiOns cicistvauvetteweseerevibhed e a 121 5 4 2 Configuration Files 1 bch venwsne nis bh cee A eee ph dwees 121 Chapter 6 Universal Data Mover Manager for OS 400 2 0 0 ce eee 122 6 1 OVES W crisps tot oes Reade is bok ee een E 122 02 USAS dere gts bee aren eee aa as dira ee laa een 123 6 2 1 Universal Products for OS 400 Commands 00 0005 123 6 2 2 Modes of Operation 0 0000 cee 124 Running UDM Interactively 0 00 2 eee 124 Running UDM from a Script i tecser ceceidadbaxiddericaieaaebdaks 124 Running UDM in Batch Mode 0 0c ee 125 6 2 3 Configuration 2erciglr ocre RRA RAR EEE 126 6 2 4 Configuration Options 2 lt v2 0 bnaeeeweedew edseedews be a ee we 127 6 2 5 Command Line Syntax anaa aaa 129 6 3 Examples of UDM Manager for OS 400 20 0 ee 130 6 4 Security escoria ees RANA ROAM ES A RRR eT ARERR ee ee RE 131 6 4 1 Object Permissions c206 eis See ee duke SeGGb se eeecee war ee ee rks 131 Chapter 7 Universal Data Mover Server for Z OS 0 0 ccc es 132 Lal AVERSA be eee cae be eee ewe ee ce ee ee 132 udm user 3207 Confidential amp Proprietary 16 Contents 7 2 Compo
21. Confidential amp Proprietary 73 z OS CANCEL Command Support Features The Universal Broker then compares this exit code with the list of exit codes provided by SERVER_STOP_CONDITIONS If a match is found and network fault tolerance is enabled the Universal Broker will execute a uctl command to STOP the running Universal Data Mover Server component 2 7 2 Security Token For security purposes Universal Products pass around a security token that is used by the locally running Universal Broker to STOP associated Universal Data Mover Server process This security token is generated on a component by component basis by the Universal Broker process that starts the Universal Data Mover Server Upon generation this token is returned to the Universal Data Mover Manager which in turn updates its locally running Universal Broker with this token The locally running Universal Broker then uses this token with the issued STOP command to cancel the running Universal Data Mover Server process When this token is received by the Universal Broker processes with the request to STOP the server component the Broker authenticates the received token with the stored token for the running Universal Data Mover Server process When the token is authenticated the Universal Data Mover Server process is STOPPED udm user 3207 Confidential amp Proprietary 74 Universal Access Control List Features 2 8 Universal Access Control List Many Unive
22. NLS directory or library New code pages may be created and added to the NLS directory or library The CODE_PAGE option value is simply the name of the code page file without any file name extension if present CTL_SSL_CIPHER_LIST The CTL_SSL_CIPHER_LIST option specifies one or more SSL cipher suites that are acceptable to use for network communications on the control session which is used for component internal communication The SSL protocol uses cipher suites to specify the combination of encryption and message digest algorithms used for a session An ordered list of acceptable cipher suites can be specified in a most to least order of preference An example cipher suite list is RC4 MD5 RC4 SHA AES128 SHA The RC4 MD5 cipher suite is the most preferred and AES128 SHA is the least preferred When a manager and server first connect they perform an SSL handshake The handshake negotiates the cipher suite used for the session The manager and server each have a cipher suite list and the first one in common is used for the session Why is a list of cipher suites helpful A distributed software solution may cross many organizational and application boundaries each with their own security requirements Instead of having to choose one cipher suite for all distributed components the software components can be configured with their own list of acceptable cipher suites based on their local security requirements When a high level of security is r
23. Privacy and integrity of transmitted network data User authentication MASAS 9 4 1 File Permissions Only trusted user accounts should have write permission to the Universal Data Mover Server installation directory and subdirectories and all of the files within them 9 4 2 Configuration Files Only trusted user accounts should have write permission to the Universal Data Mover Server configuration files and add and delete access to the directories in which they reside 9 4 3 Universal Data Mover Server User ID Universal Data Mover Server requires read access to its installation directory and its working directory defined in the component definition If user security is activated the Server requires root access to create processes that execute with another user s identity The Server security identity is inherited from the Broker If the Broker is running with a non root user ID then the Server program must have the set user ID on execution permission set and root as owner udm user 3207 Confidential amp Proprietary 152 Security Universal Data Mover Server for UNIX 9 4 4 User Authentication User authentication is the process of verifying that a user is known and valid to the system The process used by UDM Server requires the user to provide a user name ID and a password The UDM Server passes the name ID and password to the operating system for verification this is referred to as logging on the user For
24. access from host 10 20 30 40 to user TS1004 on that host No host can execute commands as local user root User TS1004 on host 10 20 30 40 can execute commands as local user tsup1004 without providing the password Users TS1004 from host 10 20 30 40 can execute commands as any local user by providing the local user password udm_access 10 20 30 40 TS1004 tsup1004 allow noauth udm_access 10 20 30 40 1TS1004 allow auth udm_access 10 20 30 40 deny auth udm_access ALL root deny auth udm user 3207 Confidential amp Proprietary 161 Chapter 11 UDM Scripting Language 11 1 Overview This chapter provides information on the Universal Data Mover UDM scripting language UDM has an easy to learn scripting language that can be used to give instructions to UDM in both interactive and batch mode While simple to use UDM s scripting language has some powerful features such as the ability to nest script file calls up to ten levels deep and parameters udm user 3207 Confidential amp Proprietary 162 UDM Commands UDM Scripting Language 11 2 UDM Commands The UDM Manager processes commands using UDM s scripting language Table 11 1 below identifies all of the UDM commands Each Command Name is a link to detailed information about that command in the Universal Data Mover 3 2 0 Reference Guide appenddata Appends a line of text to the end of an existing data element or creates a new data element
25. and the destination filename that will be used The third message produced indicates that the file was transferred successfully This message contains the source and destination filenames and host names The UDM Manager also can produce these messages when it is involved in a two party transfer session though much of the information will be redundant with its standard information messages by setting its message level to audit The manager s audit messages are written to stderr sysout under z OS udm user 3207 Confidential amp Proprietary 233 Auditing Transfer Operations UDM Transfer Operations 12 9 2 Reporting Transfer Progress For long transfer operations it is often useful to see periodic indications of the operation s progress You can get this information by turning on progress reporting using the report command report progress yes This will cause the UDM manager to issue periodic updates regarding the progress of a file being transferred The interval these updates are given is the same as the keep alive interval Progress messages look as follows 1024000 bytes processed udm user 3207 Confidential amp Proprietary 234 Chapter 13 Transfer Operations z OS Specific 13 1 Overview This chapter provides information on Universal Data Mover UDM transfer operations that are specific to the z OS operating system z OS I O UDM Commands under z OS Copying Load Modules udm user 3207 Confidential am
26. containing that line of text attrib Sets the file system attributes that govern the transfer operations on the host with the specified logical name break Stops iterating through a for files loop and picks up execution at the script line immediately following the end statement marking the end of the forfiles loop call Loads and executes a command script cd Changes the working directory on UNIX Windows OS 400 and file system HFS or if z OS the current data set qualifiers for DSN and DD file systems on the specified logical machine to the specified path close Closes the current transfer session closelog Closes the open log file compare Compares two strings of data copy Initiates a copy operation copydir Initiates a copy operation that recurses into subdirectories data Defines an in stream data element that can be passed as input for other commands debug Turns debug information on and off delete Deletes a file or series of files if file spec contains any wildcards from the transfer server with the corresponding logical name deletestring Removes a substring from an existing string echo Sends text to standard out stdout echolog Sends text to an open log file exec Executes system commands on remote machines execsap Executes SAP events exit Exits the UDM Manager same as the quit command filesys Sets the file system with which the
27. copy unix txt quit ND UN PWN pp udm user 3207 Confidential amp Proprietary 300 UDM Manager for OS 400 Examples Examples A 4 UDM Manager for OS 400 Examples This section describes how to use UDM in the OS 400 environment It provides specific examples for the following topics which explain how to use UDM ina two party mode between OS 400 and UNIX e Copy a File to an Existing OS 400 File e Copy an OS 400 Data Physical File to a File e Copy a Set of Files to an Existing Data Physical File e Copy a File to a New OS 400 Data Physical File Copy a File to a New OS 400 Source Physical File e Copy a Set of Files to a New Data Physical File on OS 400 e Copy Different Types of OS 400 Files using forfiles and _file type e Invoke a Script from a Batch Job Note These examples apply equally as well to the Windows operating system with appropriate changes for the file system syntactical differences Each topic provides an example for the LIB file system The first topic Copy a File to an Existing OS 400 File also provides an example specific to the HFS file system For other examples similar to those used in the HFS file system see Section UDM Manager for UNIX and Windows Examples udm user 3207 Confidential amp Proprietary 301 UDM Manager for OS 400 Examples Examples A 4 1 Copy a File to an Existing OS 400 File These examples copy in text mode one sequential file to another This is th
28. does the administrative complexity of the system Universal Data Mover has balanced the two to avoid the administrative complexity with a minimum sacrifice to security Universal Data Mover security concerns are 1 Access to Universal Data Mover files 2 Privacy and integrity of transmitted network data 3 4 1 Data Set Permissions Only trusted user accounts should have write access to the Universal Data Mover installation files Eligible users of Universal Data Mover require read access to the national language support library SUNVNLS the configuration file UNVCONF and the load library SUNVLOAD udm user 3207 Confidential amp Proprietary 106 Chapter 4 Universal Data Mover Manager for Windows 4 1 Overview This chapter provides information on the Universal Data Mover UDM Manager specific to the Windows 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 udm user 3207 Confidential amp Proprietary 107 Usage Universal Data Mover Manager for Windows 4 2 Usage The UDM Manager command is executed from the command line or a script After it has been initiated UDM is ready to process commands The commands can come from standard input or a script file This section describes the modes of operation configu
29. private keys and CA lists Universal Products support X 509 version 1 and version 3 certificates Although implementing a full featured PKI infrastructure is beyond the scope of Universal Products and this documentation some assistance is provided using the OpenSSL toolkit http www openssl org Universal Products on most of the supported platforms utilize the OpenSSL toolkit for its SSL and certificate implementation OpenSSL is delivered on most UNIX distributions and Windows distributions are available on the OpenSSL web site Universal Products supports z OS System SSL on the IBM z OS operating system as well as OpenSSL System SSL interfaces directly with the RACF security product for certificate access All certificates CA and user certificates and private keys must be stored in the RACF database to use System SSL The Universal Product suite includes an X 509 certificate utility Universal Certificate to create certificates for use in the Universal Product suite See the Universal Certificate chapter in the Universal Products Utilities 3 2 0 User Guide for details udm user 3207 Confidential amp Proprietary 93 Chapter 3 Universal Data Mover Manager for z OS 3 1 Overview This chapter provides information on the Universal Data Mover UDM Manager specific to the z OS operating system UDM Manager transfers files between any computers running UDM Server Using a UDM command script you indicate to the UDM Manag
30. process associated with the stopped ended manager process In the case of a Universal Data Mover three party transfer both the primary and secondary servers need to be cancelled The Universal Broker running locally with the cancelled Universal Data Mover Manager process will send a STOP command to the primary server This primary server will in turn forward the STOP command to the secondary server thus cancelling both servers of the three party transfer 2 1 1 Exit Codes Through the use of the SERVER_STOP_CONDITIONS configuration option the Universal Data Mover Manager process notifies the locally running Universal Broker of the exit codes that should cause it to terminate the running Server process With this option the user can specify a list of exit codes that should trigger the locally running Universal Broker to issue the STOP command to the manager s Universal Data Mover server side process SERVER_STOP_CONDITIONS can specify a single exit code or a comma separated list of exit codes These stop conditions are passed from the manager to the locally running Universal Broker which store this and other component specific data about the executing manager component When this executing Universal Data Mover Manager process is cancelled or stopped the locally running Universal Broker detects the ending of the manager process and retrieves its process completion information which includes the exit code of the manager udm user 3207
31. the Universal Configuration Manager application accessible via the Control Panel is the recommended way to set configuration options The Universal Configuration Manager provides a graphical interface and context sensitive help and helps protect the integrity of the configuration file by validating all changes to configuration option values see Section 2 4 Universal Configuration Manager OS 400 The configuration files on OS 400 are stored in a source physical file named UNVCONF in the UNVPRD320 library The files can be edited with a text editor See Section 2 2 6 Configuration File Syntax for the configuration file syntax udm user 3207 Confidential amp Proprietary 46 Configuration Features 2 2 6 Configuration File Syntax Configuration files are text files that can be edited with any available text editor The following rules apply for configuration file syntax Options are specified in a keyword value format Keywords can start in any column Keywords must be separated from values by at least one space or tab character Keywords are not case sensitive Keywords cannot contain spaces or tabs Values can contain spaces and tabs but if they do they must be enclosed in single or double quotation marks Repeat the enclosing characters to include them as part of the value Values case sensitivity depends on the value being specified For example e Directory and file names are case sensitiv
32. the fully qualified file name udm user 3207 Confidential amp Proprietary 246 UDM Commands under z OS Transfer Operations z OS Specific Partitioned Data Sets A file is considered partitioned if it has a data set organization of Partitioned Organization PO or a system managed type of Partitioned Data Set Extended PDSE A file is referenced directly as a fully qualified name enclosed in apostrophes or as a relative name composed of one or more qualifiers concatenated to the current working directory value to form a fully qualified name The qualifiers and that are used in the cd command do not have any special meaning in a file specification and will most likely result in an invalid fully qualified data set name A partitioned data set member requires an additional member name as part of the file specification The member name is enclosed within parenthesis as in APP PDS DATA1 where APP PDS is the partitioned data set name and DATA1 is the member name Table 13 4 provides some examples of copy command destination file specifications for partitioned data sets The examples assume that the fully qualified names are PDS s and a UDM logical name of SRV TOM123 copy local appl srv data TOM123 DATACAPP1 TOM123 DATA copy local appl TOM123 DATACAPP1 TOM123 DATA copy local appl GAM789 APP2 DATACAPP1 srv GAM789 APP2 DATA TOM123 DATA copy local app1 srv PDS PRO1 TOM123 DATA PDS PRO1 Table
33. 12 8 5 File Creation Options The createop attribute determines how the destination file is created By default it has a value of new which means that a file with the destination filename either implicitly or explicitly specified must not exist for it to be successfully written by UDM If a file with that name does exist when UDM begins a copy operation an error is issued If the value of the createop attribute is replace the destination file is created if the destination file does not already exist If it does exist it is overwritten with the transferred data If the value of createop is append and the file already exists the data transferred is appended to the end of the data already in the existing file If the file does not exist a new file is created udm user 3207 Confidential amp Proprietary 229 Copying Files with UDM UDM Transfer Operations 12 8 6 File Permission Attribute Under the UNIX operating system the mode attribute specifies the mode in UNIX parlance or file permissions of a file created by UDM in a copy operation Existing files do not have their modes modified by UDM They retain the file mode that they had before the copy operation was initiated Note The mode attribute is not to be confused with the mode command which is used to set the type of file transferred and trim option The mode attribute is set using the attrib command The value of mode is either a set of three numbers or nothing
34. 13 4 copy Command Destination File Specifications for Partitioned Data Sets Table 13 5 provides some examples of copy command source file specifications for partitioned data sets The examples assume that the fully qualified names are PDS s and a UDM logical name of SRV TOM123 copy srv data app1 local appl txt TOM123 DATACAPP1 TOM123 DATA copy srv appl local appl txt TOM123 DATACAPP1 TOM123 DATA copy srv GAM789 DATACAPP1 GAM789 DATACAPP1 local appl txt Table 13 5 copy Command Source File Specifications for Partitioned Data Sets Note Member names are restricted to ISPF member naming conventions e The createop attribute values REPLACE and NEW apply to the member names and not to the partitioned data set udm user 3207 Confidential amp Proprietary 247 UDM Commands under z OS Transfer Operations z OS Specific DD File System The semantics of a file specification is determined primarily by whether the ddname being referenced has a sequential or a partitioned data set allocated A ddname allocating a sequential data set is referred to as a sequential ddname and a ddname allocating a partitioned data set is referred to as a partitioned ddname in the following text for purposes of brevity Sequential ddnames A ddname is considered sequential if it allocates a data set with an organization of Physical Sequential PS A ddname reference is always a fully qualified name A ddname must not
35. 5 File Specification Rules 0 0 c cc eee 269 Source File Specification Rules 0 0 0 ccc nes 270 Destination File Specification Rules 0000 c cece eens 271 14 4 6 delete Delete Command 0 0 cee ee ee 276 delete Command Requirements 276 delete Command Forms 276 14 4 7 rename Rename Command 00 eee ee eee 277 rename Command Requirements 000 cece eee eee ences 277 rename Command Forms 00 0c cece eee eee eee eens 278 Chapter 15 Remote Execution ooooooororrrrrr eee 279 15 1 OVEIVIOW eiii a Ae aad alae ae ea MA a ea Awe a ee a 279 15 2 exec Command cd 280 15 2 1 Executing Remote Commands within UDM 280 15 2 2 Return Values 0 0200000 eee 282 15 2 3 exec Command Examples 200000 eee eee eee 282 15 3 execsap Command 0 eens 283 15 3 1 Triggering SAP Events within UDM 0 000 283 15 3 2 execsap Command Example 20000 0c eee eee eee 284 Chapter 16 Return Code Processing cece eects 285 16 1 Overview 2 eee eens 285 16 1 1 UDM Return Codes 0 0000 eee 285 16 2 Return Codes in UDM Built In Variables ooooocccocoo 286 slastre Variable 10 eerie neetan e bd a ee eae a 286 tc Variable 2 2 eens 286 _halton Variable ssis rasana Ean ene 286 16 3 Setting Return Codes voici ciaciacede bathe stated sideven
36. Copy a Set of Files Each example illustrates a procedure that occurs under the operating system s default file system See Section A 2 UDM Manager for z OS Examples in Appendix A Examples for z OS examples that apply equally as well to the Windows operating systems udm user 3207 Confidential amp Proprietary 113 Chapter 5 Universal Data Mover Manager for UNIX 5 1 Overview This chapter 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 udm user 3207 Confidential amp Proprietary 114 Usage Universal Data Mover Manager for UNIX 9 2 Usage The UDM Manager command is executed from the command line or a script After it has been initiated UDM is ready to process commands The commands can come from standard input or a script file This section describes the modes of operation configuration and configuration options and command line syntax of UDM Manager for UNIX Section 5 3 Examples of UDM Manager for UNIX provides examples demonstrating the flexibility of Universal Data Mover 5 2 1 Modes of Operation Under UNIX UDM can be run either in e Interactive mode e Batch mode Running UDM in Interactive Mode To invoke U
37. Each number in the set corresponds to one or more individuals for whom access is granted for the file First number Owner of the file e Second number Users in the group assigned to the file e Third number Everyone else The value of each number is the sum of values representing file permissions e 0 No permissions 1 Permission to execute the file e 2 Permission to write to the file 4 Permission to read from the file Thus a value of 7 for the first number would provide the file owner with permission to read write and execute a file A value of 6 for the second number would provide users in the group assigned to the file with permission to read from the file and write to the file but not to execute the file A value of O for the third number would provide everyone else with no permissions for the file By default the mode attribute is not set The default mode of a newly created file by UDM is dependent upon the user s umask or the mode of the source file in a UDM transfer Examples The following example provides the owner group and everyone else permission to read write and execute the file attrib local mode 777 The following example provides the owner permission to read write and execute the file members of the file s group permission to read and execute the file and everyone else no permissions attrib local mode 750 The following example provides the owner permission to read and write the file an
38. Examples DSN file system S1 EXEC UDMPRC UNVSCR DD NY DON DOU hu NN pp set _echo yes set _halton warn open unix sol9 user top098 pwd p100m cd unix opt app data mode type text attrib local createop replace copy unix datal0 txt local app data daily quit The DSN file system example is basically the same as the DD file system example with these changes Removal of the filesys command line 4 in the DD file system example since the default file system for the z OS manager is DSN Addition of the line 6 which sets the local attribute createop The createop attribute controls how a file is created By default its value is new indicating that only new files are created and existing files are not written over replaced In this example the value is being set to replace which specifies that if the file exists it should be replaced otherwise it is created udm user 3207 Confidential amp Proprietary 291 UDM Manager for z OS Examples Examples A 2 2 Copy a z OS Sequential Data Set to a File These examples copy in text mode a sequential data set on z OS to a remote UNIX system Note A text transfer by default does not trim spaces from the end of a record If the data set being copied is a fixed record format each record is padded with spaces so that the record length equals the logical record length of the data set If you do not want the trailing spaces copied they must be
39. Matches the user name with which the remote user is executing as on the remote system The REMOTE_USER value has the following syntax An asterisk matches 0 or more characters and a question mark matches one character For example AB M matches ABCDM and ABM AB M matches ABCM but not ABCDM e Control code c switches off case sensitivity and C switches on case sensitivity matching The default is on For example cABC matches abc ca Cbc matches Abc but not ABC e Pattern matching characters such as the asterisk and question mark are included in the text to be matched by prefixing them with a forward slash character For example A B matches A B A B matches A B Table 2 6 Client IP Address Matching Criteria udm user 3207 Confidential amp Proprietary 80 Universal Access Control List Features Certificate Based and Non Certificate Based UACL Entries Universal Products components that support X 509 certificates define their UACL entries in two varieties 1 Certificate based entries 2 Non certificate based entries The two entry types are distinguished by their name For example cmd_cert_access is the certificate based form of the entry and ucmd_access is a non certificate based entry All entries follow the same format Certificate based UACL entries are searched under the following conditions e Client provides an X 509 certificate that matches a certificate map entry Non certif
40. Operations z OS Specific Partitioned ddnames A ddname is considered partitioned if it allocates a data set with an organization of Partition Organization PO or a system managed type of Partitioned Data Set Extended PDSE A ddname reference is always a fully qualified name A ddname must not be enclosed in apostrophes A partitioned data set member requires an additional member name as part of the file specification The member name is enclosed within parenthesis as in APPDD DATA1 where APPDD is the ddname and DATA1 is the member name There are three possible partitioned ddname destination file specifications 1 Name of the ddname defined by a JCL DD statement followed by a member name enclosed in parenthesis 2 Current working directory value set to the name of a ddname defined by a JCL DD statement and a member name specified as the destination file specification 3 Current working directory value set to the name of a ddname defined by a JCL DD statement and a member name specified by the source file specification if no destination file specification is provided There are two possible partitioned ddname source file specification 1 Complete name of the ddname defined by a JCL DD statement followed by a member name enclosed in parenthesis Current working directory value set to the name of a ddname defined by a JCL DD statement and a member name specified as the source file name N Table 13 8 provides som
41. Proprietary 269 Command Reference Transfer Operations OS 400 Specific Source File Specification Rules The following rules apply to file specifications that are in the source position in a copy command In all examples CURLIB is the current library 1 Ifthe file specification contains only the file portion the current library is pre pended to the name to refer directly to a file with no member component Example COPY SRC MYFILE The absolute path derived would be CURLIB MYFILE 2 If the file specification contains only file and member portions the current library is pre pended to the name to refer to a specific member in a file Example COPY SRC MYFILE MYMBR The absolute path derived would be CURLIB MYFILE MYMBR 3 If the file specification contains only library and file portions an absolute path without a member component is used Example COPY SRC MYLIB MYFILE The absolute path would be exactly as given MYLIB MYFILE 4 Ifa file specification contains library file and member portions all of those components are used explicitly in the absolute path Example COPY SRC MYLIB MYFILE MYMBR The absolute path would be MYLIB MYFILE MYMBR udm user 3207 Confidential amp Proprietary 270 Command Reference Transfer Operations OS 400 Specific Destination File Specification Rules Destination path names follow many of the same rules as source path names with one big exception all or pa
42. Set e Cluster Alternate Index VSAM Path Alias User Catalog Connector e Tape Volume Catalog Library e Tape Volume Catalog Volume 13 2 4 Allocation Data set allocation is the process of obtaining access to the data set If the data set already exists it resides on a device such as a tape or more likely a disk In order to allocate an existing data set the device must be known A volume serial name or number and a unit name or number represents an I O device in z OS The unit and volume serial number volser can be specified explicitly or specified implicitly with a catalog entry Allocation can be performed with JCL or dynamically Dynamic allocation requires allocation attributes to be specified by the user UDM dynamic allocation of a data set that has been migrated by HSM or similar three party product will result in the data set being recalled UDM will wait until the recall is complete and then continue processing udm user 3207 Confidential amp Proprietary 239 UDM Commands under z OS Transfer Operations z OS Specific 13 3 UDM Commands under z OS This section describes the behavior of UDM commands when working with z OS data sets and ddnames 13 3 1 attrib Attribute Command z OS data sets can be allocated statically with JCL DD statements or dynamically with the z OS Dynamic Allocation service aka SVC 99 Table 13 1 below lists the dynamic allocation attributes that can be spec
43. UNIX user authentication is optional However if security is enabled a user name ID and password are required in order to verify the user s credentials With security enabled you transfer files using a specific user s security context Universal Data Mover can use three different types of user authentication methods 1 Default authentication uses the UNIX traditional password comparison method 2 PAM authentication uses the PAM API to authenticate users The PAM modules which authenticate and account are called This option is available only for certain UNIX platforms 3 HP UX Trusted Security uses HP UX Trust Security APIs to authenticate users This is available only on Hewlett Packard HP UX platforms 9 4 5 Universal Access Control List UDM Server uses the Universal Access Control List UACL file as an extra layer of security The UACL file contains UDM Server entries that contain Access Control List ACL rules that permit or deny access to the UDM Server See Section 2 8 Universal Access Control List for details on the Universal Access Control List feature UACL Entries The syntax of a UACL entry file is the same as the UDM configuration file See Section 2 2 6 Configuration File Syntax for detailed syntax information Table 9 3 identifies all UDM Server for UNIX UACL entries Each UACL Entry Name is a link to detailed information about that UACL entry in the Universal Data Mover 3 2 0 Reference Guide UDM_ACCESS Al
44. USESRCSEQ with values of YES or NO governs whether or not the sequence number and modification date are included in the source record when transferring a source physical file How this happens depends on the mode type of the transfer By default this value is set to NO meaning sequence numbers and modification dates are to be stripped When writing a source physical file the USESRCSEQ attribute specifies whether or not source sequence information is expected to be included in the source data If the value is set to NO UDM generates sequence number and modification date information Otherwise the first 12 bytes of each source record contain that information This value is sent as a source attribute in OS 400 to OS 400 copies so unless it is overridden it automatically will tell the destination side if the sequence numbers are in the data Allowing this option to be set permits the effective copying of source physical files from non 400 systems that already contain sequence number information When creating UDM sequence data two additional destination side attributes are used SEQSTART specifies the starting sequence number of the first record written and range from 0000 01 to 9999 99 The default is 0001 00 SEQINCR indicates how much the sequence number is incremented from record to record Valid values are 00 01 to 99 99 The default value is 01 00 SEQSTART and SEQINCR are sent as source attributes but used on the destination side
45. a model for creating UCMD and RECFM F FB V FB USAP trace files when they are called by UDM using the exec and execsap commands SYSPRINT DSORG PS output Standard output file for the UDM program RECFM F FB V VB SYSOUT DSORG PS output Standard error file for the UDM program RECFM F FB V VB SYSIN DSORG PS input Standard input file for the UDM program UDM reads RECFM F FB V VB its command options from SYSIN UNVSCR DSORG PS input UDM command script UDM executes the script allocated to this ddname The C runtime library determines the default DCB attributes Refer to the IBM manual OS 390 C C Programming Guide for details on default DCB attributes for stream I O Table 3 1 UDM Manager for z OS DD Statements in JCL udm user 3207 Confidential amp Proprietary 97 Usage Universal Data Mover Manager for z OS 3 2 3 JCL Figure 3 2 below illustrates the Universal Data Mover for z OS JCL using the UDMPRC procedure illustrated in Figure 3 1 jobname JOB CLASS A MSGCLASS X STEPL EXEC UDMPRC UNVSCR DD open srv sol7 user id001 pwd pwd001 copy local uid data srv data quit Figure 3 2 UDM Manager for z OS JCL Job step STEP1 executes the procedure UDMPRC The UDM script commands are specified on the UNVSCR DD udm user 3207 Confidential amp Proprietary 98 Usage Universal Data Mover Manager for z OS 3 2 4 Configuration Configuration consists
46. and transmitted over the network COMMENT User defined string CTL_SSL_CIPHER_LIST Acceptable and preferred SSL cipher suites to use for the control session between UDM components DATA_COMPRESSION Specification for whether or not data is compressed on all standard 1 O files DATA_SSL_CIPHER_LIST EVENT_GENERATION Acceptable and preferred SSL cipher suites to use for the data session on which file data is transferred between UDM primary and secondary servers Events to be generated as persistent events FRAME_INTERVAL Number of UDM transfer blocks transferred before a frame sync message is sent when UDM is operating with network fault tolerance turned on HELP Writes a description of the command options and their format IDLE_TIMEOUT Number of seconds of inactivity in an interactive UDM session after which the manager will close the session INSTALLATION_DIRECTORY Directory in which Universal Data Mover is installed KEEP_ALIVE_INTERVAL Default interval at which a keep alive message is sent from the manager to the transfer server s MERGE_LOG Specification for whether or not to merge standard out and standard error output streams from a remote command to the UDM transaction log MESSAGE_LANGUAGE Universal Message Catalog UMC file used to write messages MESSAGE_LEVEL MODE_TYPE Level of messages to write Default transfer mode type for UDM session
47. created when v PROD TEST PROD LIB creating a library LVLCHK Record format level check v YES NO NULL YES PF MAXMBRS Maximum number of members v integer NOMAX NULL 1 for PF PF SP NOMAX for SP MAXRCDS Maximum number of records 1 2146762800 NULL SAVF NOMAX OPTION Source listing options SRC NOSRC empty string PF SOURCE NOSOURCE LIST NOLIST SECLVL NOSECLVL EVENTF NOEVENTF up to four repetitions RCDLEN Record length if no DDS is v integer 92 PF SP used REUSEDLT Reuse deleted records v YES NO NULL NO PF SEQSTART Beginning sequence number v 0000 01 9999 99 1 00 SP used when writing to a source physical file SEQINCR Amount to increment v 00 01 99 99 1 00 SP sequence number by when writing a record to a source physical file SHARE Share open data path v YES NO NULL NO PF SP SAVF udm user 3207 Confidential amp Proprietary 265 Command Reference Transfer Operations OS 400 Specific SIZE Member size v e Single values size_attrib 10000 1000 PF SP NOMAX configuration 3 for PF e Other values file entry if 10000 1000 Comma separa provided 499 for SP ted element list otherwise Element 1 empty string Initial number of records 1 2147483646 Element 2 Increment number of records Integer Element 3 Maximum increments Integer EX 10000 1000 3 USESRCSEQ Sequence number and v YES NO NO SP modification date information On Source side retain this
48. destination When UDM has finished executing the copyfiles udm it will terminate udm user 3207 Confidential amp Proprietary 172 Script Files UDM Scripting Language The following example shows the same options for a batch execution in z OS jobname JOB CLASS A MSGCLASS X STEP1 EXEC UDMPRC UNVSCR1 DD udm commands SYSIN DD s UNVSCR1 o file source c source dest c destination JF For OS 400 examples see Sections Running UDM from a Script and Running UDM in Batch Mode 11 4 2 Invoking UDM Interactively with Commands from a Script File You also can invoke scripts directly from the UDM prompt in interactive mode or as part of a script file itself using the ca11 command Any parameters to the ca11 command are passed on to the script being called The following example illustrates the ca11 command executing the copyfiles udm script as identified in the previous example UDM UDM gt ca11 copyfiles udm file source c source dest c destination UDM gt UDM gt quit Unlike executing a script from the command line UDM will not exit automatically when it finishes processing a script invoked using the ca11 command If you are passing a large number of parameters to a script you may want to break up the ca11 command into multiple lines You can do this by putting a at the end of each line break except for the last line However this method cannot be used for inv
49. following tables e Chapter 3 Universal Data Mover Manager for z OS e Chapter 4 Universal Data Mover Manager for Windows e Chapter 5 Universal Data Mover Manager for UNIX e Chapter 7 Universal Data Mover Server for z OS e Chapter 8 Universal Data Mover Server for Windows e Chapter 9 Universal Data Mover Server for UNIX Added the following commands in Table 11 1 UDM Commands appenddata e closelog echolog logdata move openlog e savedata Added Table 11 4 _ file Built in Variable Special Attributes Added the following built in variables to Section 11 6 8 Built in Variables uuid e _lastmsg Added sortby parameter information in Section 11 10 forfiles Statement e Added _file Variable Attributes section in Section 11 10 1 forfiles Built In Variables Added Section12 8 2 Move Operation Added the following parameters in Section 15 2 exec Command e stdout e stderr Changes for Universal Data Mover 3 2 0 User Guide udm ref 3203 December 17 2008 Added Updating the Universal Data Mover Server ACL Entries in Section 8 4 5 Universal Access Control List of Chapter 8 Universal Data Mover Server for Windows udm user 3207 Confidential amp Proprietary 7 Summary of Changes Changes for Universal Data Mover 3 2 0 User Guide udm ref 3202 October 17 2008 e Changed JCL SNTYPE value to type for the dsntype attribute in Table 13 1 attrib Command Dynamic Allocation Attributes Changes for Uni
50. for only seconds or days The manager will attempt server reconnection for a limited amount of time That amount of time is configured with the RECONNECT_RETRY_COUNT and RECONNECT_RETRY_INTERVAL options These two options determine respectively how many reconnect attempts are made and how often they are made After all attempts have failed the manager ends with an error udm user 3207 Confidential amp Proprietary 70 Fault Tolerance Features When a network connection terminates the server enters a disconnected state and waits for the manager to reconnect The user process continues running however if the user process attempts any I O on the standard files it will block The server waits for the manager to reconnect for a period of time defined by the manager s RECONNECT_RETRY_COUNT and RECONNECT_RETRY_INTERVAL Once that time has expired the server terminates the user process and exits UDM can request the use of the network fault tolerant protocol If the server does not support the protocol or is not configured to accept the protocol the Manager continues without using the protocol The NETWORK_FAULT_TOLERANT option is used to request the protocol 2 6 2 Open Retry Open Retry is a type of fault tolerance used at the session establishment level Network fault tolerance as described in Section 2 6 1 Network Fault Tolerance is used from the time that a session has been fully established until the session has terminated
51. forfiles nt C Example print msg Filename _file Abs Path _path end Executing this would build a file list containing the files file1 txt file2 txt and file3 txt Since there are three files in the list that was built UDM would iterate through the loop three times 1 During the first iteration through the loop the _file variable would contain file1 txt and the _path variable would contain C Example file1 txt 2 During the second iteration the _file variable would contain file2 txt and the _path variable would contain C Example file2 txt 3 During the third and final iteration the _file variable would contain file3 txt and the _path variable would contain C Example file3 txt This script segment would result in the following output Filename file1 txt Abs Path C Example file1 txt Filename file2 txt Abs Path C Example file2 txt Filename file3 txt Abs Path C Example file3 txt udm user 3207 Confidential amp Proprietary 203 forfiles Statement UDM Scripting Language _file Variable Attributes The _file variable also has special attributes that further define a file see Table 11 4 _file Built in Variable Special Attributes For efficiency reasons all of these attributes other than name and type are retrieved only as requested You can request to retrieve the file attributes by adding fileattrib yes to the end of the forfiles call For example forfiles src txt fil
52. information when copying a source physical file On Destination side Record data includes this information WAITFILE Maximum file wait time integer IMMED NULL 30 for PF PF SP CLS IMMED for SAVF SP SAVF NOMAX With CCSID set to CODEPAGE when the UDM CCSID attribute is not set either explicitly or implicitly via an OS 400 to OS 400 file transfer the CCSID associated with the code page via the code page to CCSID mapping tables gets used as the CCSID attribute value One implication is that by default files may be created with the CCSID associated with the codepage option Table 14 2 0S 400 Specific LIB File Attributes for Creating New Files HFS Attributes Table 14 3 identifies attributes that are unique to the HFS file system Currently there is only one HFS unique attribute CCSID CCSID CCSID of the file EBCDIC and ASCII CODEPAGE AA a CCSIDs Table 14 3 0S 400 Specific HFS File Attributes for Creating New Files udm user 3207 Confidential amp Proprietary 266 Command Reference Transfer Operations OS 400 Specific 14 4 2 call Call Command To invoke a script the member name is required and can be FILE call mylib myfile myscript Specifying FILE invokes the normal default OS 400 file search order To invoke a script included as an inline file in a database job the call must specify FIRST as the database member name The following example illustrates both e In
53. line sequence set for the destination side of the transfer is appended to the end of each line of data UDM also does this for record oriented file systems as well By managing the end of line sequence this way UDM easily can be used to translate end of line characters across platforms such as a transfer from UNIX to Windows strip end of line characters from the data completely or even add a completely new end of line sequence for use by other applications For most operations though the end of line sequence will not need to be changed udm user 3207 Confidential amp Proprietary 223 Transfer Modes and Attributes UDM Transfer Operations eol Attribute The end of line sequence is set with the eo1 attribute The default value for eo1 depends on the platform and file system selected For Windows based platforms the default value is r n For UNIX platforms and the HFS file system under USS the default value is n e For the HFS file system under OS 400 the default is FILE which makes end of line terminator consistent with file CCSID e For record oriented file systems z OS s dd and dsn and OS 400 s LIB the value for eol is not set To provide consistent eo1 definitions under the OS 400 HFS file system specific ASCII and EBCDIC values are defined for the symbolic values e AsASCIl n x0A r x0D t x09 and Y x0A As EBCDIC n x15 r xOD t x05 and Y x25 By default the file CCSID deter
54. local UDM Manager and a remote UDM server running on host so19 The host so19 is given the a logical name of unix The open command also provides user credentials for the UDM server to verify and if success verified specifies the user ID with which the UDM server executes 4 Line 4 changes the current directory of the UDM server unix running on host so19 5 Line 5 changes the transfer mode type from binary the default to text Text mode transfers will translate between code pages and process the end of line characters 6 Line 6 is the copy command that actually moves the data between systems It copies file data1 txt in the root directory on drive C of the Windows machine to the UNIX Server as data10 txt 7 Line 7 executes the quit command which closes all sessions and exits UDM with the highest exit code set udm user 3207 Confidential amp Proprietary 299 UDM Manager for UNIX and Windows Examples Examples A 3 3 Copy a Set of Files This example copies in text mode multiple files with one copy This example assumes that the remote UNIX directory opt app data contains the following list of files e data001 txt e data002 txt e data003 txt e data004 pr e data005 pr The following files will be created on the destination machine e data001 txt e data002 txt e data003 txt set _echo yes _halton warn open unix sol9 user top098 pwd p100m cd unix opt app data mode type text attrib local truncext yes
55. lt _lastrc message EQ MATCH gt echo echo Data contains an exit command echo end set i lt i 1 gt end If a data element called mydata txt contained the following contents cd Is al exit Running this script against the contents of mydata would produce the following results 1 cd 2 Is al 3 exit Data contains an exit command udm user 3207 Confidential amp Proprietary 201 forfiles Statement UDM Scripting Language 11 10 forfiles Statement UDM provides a powerful iterative loop structure forfiles that iterates through a series of statements for each file found that matches a file specification The syntax of the forfiles statement is forfiles Jogical_name file_spec sortby attr bute name ascending descending UDM commands end log cal_name is the logical name of a transfer server f le_specis the file specification used to select files for the iteration see Section 11 10 2 forfiles File Specification From the specified transfer server UDM builds a list of files that match the file specification UDM then executes all of the commands listed between the forfiles statement and the end statement once for each file in the list The optional sortby parameter specifies the name of a special attribute attribute name of the _file built in variable see Table 11 4 _ file Built in Variable Special Attributes The list of files that match F77e_spec will be sorted bas
56. o aaa ee bw ele 96 3 2 2 DD Statements inJCL o o ooooccccccoccoccor es 97 SA A aa eae be aad 98 2424 Config ratlion urraca SO ea Milt ON e eid Me s CR OR Rte 99 3 2 5 Configuration Options brete ran Ped beans Rea Rees 100 3 2 6 Command Line Syntax carr youre eo ieee oun eee Ea 103 3 3 Examples of UDM Manager for z OS 0 0 0 ee 105 O A tee ats cae de Scr ace Beene 106 3 4 1 Data Set Permissions 0 0 00 cc cee tte 106 Chapter 4 Universal Data Mover Manager for Windows 000 essen ee eee eens 107 4 1 OVIE W ivi a a ake ae do bade edhe ats 107 udm user 3207 Confidential amp Proprietary 15 Contents 42 WEAde secucnebeca canst edurad basses Shoe e alce ad eee ee 108 4 2 1 Modes of Operation 0 0 0 2 108 Running UDM in Interactive Mode 2 0 0 ee 108 Running UDM in Batch Mode v c20ns2 een cneoes errata e 108 4 2 2 Configuration 2 cinares kee Pen Rese a Oe AR A 109 4 2 3 Configuration Options sii ia a ia a a 110 4 2 4 Command Line Syntax 0 002 ee 112 4 3 Examples of UDM Manager for Windows 000s eee eee eee 113 Chapter 5 Universal Data Mover Manager for UNIX 0 0 ce eee eee eee eee 114 A A a ee ee Bate Otek E 114 D2 USADO ikke seared stian sean AE EA MOREA Se Meee ee Be 115 5 2 1 Modes of Operation 0 0000 tte 115 Running UDM in Interactive Mode 0 0 00 c eee ee 115 Running UDM in Batch Mode 0 0000 eee ee 115 S22
57. of e Setting default options and preferences for all executions of UDM Manager e Setting options and preferences for a single execution of UDM Manager Configuration options are read from the following sources 1 PARM keyword 2 SYSIN ddname 3 Configuration file The order of precedence is the same as the list above PARM keyword options being the highest and configuration file being the lowest That is options specified via a PARM keyword override options specified via a SYSIN ddname and so on 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 ifthe options are not read from one or more other sources 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 See Section2 2 1 Configuration Methods for details on Universal Products configuration methods udm user 3207 Confidential amp Proprietary 99 Universal Data Mover Manager for z OS 3 2 5 Configuration Options Table 3 2 below describes the configuration options used to execute UDM Manager for z OS Each Option Name is a link to detailed information about that configuration option in the Universal Data Mover 3 2 0 Reference Guid
58. on how to select managed mode udm user 3207 Confidential amp Proprietary 49 Remote Configuration Features Figure 2 1 below illustrates remote configuration for one Universal Agent in managed mode and one Universal Agent in unmanaged mode Universal Agent Universal Agent Unmanaged Mode Managed Mode F Configuration Configuration Configuration Configuration Files Spool Files Spool Universal Universal Broker Broker Configuration Query Configuration Update Y A Universal Universal Enterprise Management Controller Console Figure 2 1 Remote Configuration Unmanaged and Managed Modes of Operation udm user 3207 Confidential amp Proprietary 50 Remote Configuration Features 2 3 3 Universal Broker Startup At Universal Broker start up in both managed and unmanaged modes the Universal Broker configuration file always is read Unmanaged Mode At Universal Broker start up in unmanaged mode Universal Broker reads the configuration files of all Universal Products components into its memory The Universal Broker configuration file is used to define the Universal Broker configuration just as all configuration files are used in unmanaged mode Universal Broker updates its memory from the configuration files whenever Universal Control issues a REFRESH request Managed Mode At Universal Broker start up in managed mode the Universal Broker configuration file points Universal Broker to the l
59. or not UDM will use proxy certificates in three party transfer sessions if a certificate is supplied to the UDM Manager RECONNECT_RETRY_COUNT Number of attempts the manager will make to re establish a transfer session when a network fault occurs RECONNECT_RETRY_INTERVAL Number of seconds that UDM will wait between each successive attempt to re establish a transfer session when a network fault occurs RECV_BUFFER_SIZE Size of the TCP receive buffer for UDM REMOTE_PORT TCP port number on the remote computer used for invoking UDM Server instances SCRIPT_FILE Script file containing UDM commands to execute SCRIPT_OPTIONS Options to pass to the script command file SEND_BUFFER_SIZE Size of the TCP send buffer for UDM TCP_NO_DELAY Specification for whether or not to use TCP packet coalescing TRACE_FILE_LINES Maximum number of lines to write to the trace file TRACE_TABLE Size of a wrap around trace table maintained in memory UCMD_PATH Sets the complete path to UCMD for calls by the exec command UMASK File mode creation mask VERSION Writes the program version information and copyright Table 4 1 UDM Manager for Windows Configuration Options Confidential amp Proprietary 111 Usage Universal Data Mover Manager for Windows 4 2 4 Command Line Syntax Figure 4 1 below illustrates the command line syntax of UDM Manager for Windows
60. parameter of the execsap command is either e Host parameter with an SAP destination entry Name of a destination in your SAP RFC file The type parameter specifies the type of action being performed A specified type of event requires that an SAP event ID be specified with the eventid parameter Note For version 3 2 0 the only valid type is event which triggers an SAP event An event parameter can be passed to the SAP event using the parm parameter The client parameter specifies the SAP client UDM must authenticate a user SAP in order to execute an SAP action The user ID and password can be specified with the user and pwd parameters respectively The codepage is inherited from the UDM Manager s configuration file unless explicitly overridden in the call to the execsap command The codepage specifies to which codepage the output of the remote command is translated udm user 3207 Confidential amp Proprietary 283 execsap Command Remote Execution The user pwd and codepage parameters can be stored in an external file instead of being specified explicitly in the execsap command syntax e Ifa plain text file is used the file parameter specifies the name of this file Ifthe file was encrypted with Universal Encrypt the xfile parameter specifies the name of this file If an encryption key was used other than Universal Encrypt s default that key can be specified with the key parameter This options and the format of the
61. read for non VSAM catalog entries The following organizations are supported Physical Sequential e Partitioned Organization e Partitioned Data Set Extended e Generation Data Set The following organizations are not supported e Indexed sequential e Direct e Unmovable e VSAM Any organization not listed is undetermined Record Format The following record formats are supported e Fixed length e Variable length e Undefined length e Blocked e Fixed length standard e Variable length spanned ISO ANSI control character e Machine control character Block Size There are three different types of block sizes 1 User specified block size that cannot exceed 32 760 2 System determined block size that cannot exceed 32 760 3 Block sizes supported by the Large Block Interface LBI that permits sizes up to 2G LBI is supported by DFP on tape devices only at this time udm user 3207 Confidential amp Proprietary 237 z OS I O Transfer Operations z OS Specific 13 2 2 Generation Data Group and Generation Data Sets A Generation Data Group GDG is a catalog entry used to maintain a group of Generation Data Sets GDS GDS s are referred to with absolute names or relative names Absolute name has the form of GDG G0000V00 e Relative name has the form of GDG n where e n 0 forthe current GDS e n 1 for the previous GDS e n 1foranew GDS Allocation Allocation attributes fora GDS are obtained diff
62. sae a a 287 16 3 1 Return Codes in set Set Command 200005 287 issuing the set Command 23 sc1800icecneetdinadwa a aa 287 16 3 2 Return Codes in return Return Command 0000e 287 Appendix A ExampleS eae ee ee eee eee iia 288 A 1 Overview ooo 288 A 2 UDM Manager for z OS Examples 00000 cece eee eens 289 A 2 1 Copy a File to an Existing z OS Sequential Data Set 290 DD file system ciuccacdtouecs doe rara bageneadh oe news 290 DONS systemi rra ae Stok wees ee ee ee a eee 291 A 2 2 Copy a z OS Sequential Data Set to a File 292 udm user 3207 Confidential amp Proprietary 23 Contents DD file system crema nee a oa Bio ea beca a 292 DIS SISI a ted tes ia RA Fan pl sii ld 292 A 2 3 Copy a Set of Files to an Existing z OS Partitioned Data Set 293 DD TGSYSICN ensucia RAS AS is AA ERE WA 294 DSN file system auxoziosrorstrerara al ERA ERA 294 A 2 4 Copy a File to a New z OS Sequential Data Set 295 DSI Sy SUI iiri ae aai Gene a aE AGTA ae tea wie Brae AE Ee pro 295 A 2 5 Copy a Set of Files to a New z OS Partitioned Data Set 296 DSN filesystem dps sil o E a da ees 296 A 3 UDM Manager for UNIX and Windows Examples 297 A 3 1 Simple File Copy to the Manager 000 eee eee 298 A 3 2 Simple File Copy to the Server 2 0000000 ce eee eee 299 A 3 3 Copy a Set of Files s
63. situation if you want to exit from UDM altogether However if you only want to exit the current script you can couple the return command with an if statement and the _lastrc built in variable Stoneman s Tip if C_lastrc NE 0 return _lastrc end udm user 3207 Confidential amp Proprietary 199 while Statement UDM Scripting Language 11 8 while Statement The while statement implements a simple while loop The syntax of the while statement is while expression end In this case the loop iterates executing the commands between the while and end statements as long as the expression evaluates to a value that is not zero If the expression evaluates to a value of zero code execution picks up at the point immediately following the end of the while loop For example set n 1 while lt n LE 10 gt echo n set n lt n 1 gt end udm user 3207 Confidential amp Proprietary 200 fordata Statement UDM Scripting Language 11 9 fordata Statement The fordata statement iterates through a data element once for each line For each iteration a variable provided by the user is set to hold the contents of the line in the data element corresponding to the current iteration The syntax of the fordata statement is fordata variable name data element end Example set i 1 loaddata mydata mydata txt fordata line mydata echo i line compare line exit case yes if
64. the data set is allocated Equivalent to the JCL UNIT parameter UNIT unit Default is SYSALLDA it can be set with UDM configuration option ALLOC_UNIT unitcnt Number of units to allocate for a multi volume data set e Equivalent to the unit count sub parameter JCL UNIT parameter UNIT unitcnt No default or UDM configuration option volcnt Number of volumes to allocate for a multi volume data set Equivalent to the volume count sub parameter JCL VOL parameter VOL volcnt No default or UDM configuration option volseq e Volume sequence number on which a multi volume data set starts Equivalent to the volume sequence number sub parameter JCL VOL parameter VOL volseq No default or UDM configuration option volser e Volume serial number on which the data set is allocated Equivalent to the SER sub parameter of the JCL VOL parameter VOL SER volser No default default value can be set with UDM configuration option ALLOC_VOLSER Table 13 1 attrib Command Dynamic Allocation Attributes udm user 3207 Confidential amp Proprietary 243 UDM Commands under z OS Transfer Operations z OS Specific 13 3 2 cd Change Directory Command The cd Change Directory command moves the current position within a file system Position means different things depending on the file system This section describes the behavior of the cd command for each file system DS
65. the data stream being sent to the file has an associated CCSID and the file itself has an associated CCSID In this way the operating system knows how to provide the translation between data to be written to a file and the data that is physically on the disk file OS 400 For UDM on OS 400 the data stream CCSID is established via the code page to CCSID mapping file which is controlled by the UDM Manager CODEPAGE_TO_CCSID_MAP configuration file option and the UDM Server CODEPAGE_TO_CCSID_MAP configuration file option Of course the translation also works the other way around when data is read from a disk it is translated from the physical disk back to the data stream One special CCSID is 65535 which indicates that no translation is to take place When transferring data between computer systems UDM allows the specification of a code page for each system For example open source winsys45 user id1 pwd mypwd codepage is08859 1 destination 0s400trex user id2 pwd newpwd codepage 1BM037 This tells UDM that the two code pages iso8859 1 and IBM037 are to be used for mapping data between the two systems Very often the numeric portion of a code page also is a CCSID to which the code page relates In this case the numeric representations represented by the code page are the same as those represented by the CCSID One example of this common identification is the code page IBM037 and the CCSID 037 This code page and CCSID represent the native nu
66. the primary server s 12 2 2 Session Options The examples given thus far show the simplest versions of the open command Additional options can follow each server name such as the port on which the Universal Broker is listening the codepage that the server uses for text translation authentication information and references for a file from which these options are read this file may be encrypted if desired At the end of the open command are optional parameters that specify the type of encryption and compression used for the data transfer operations See Chapter 6 UDM Commands in the Universal Data Mover 3 2 0 Reference Guide for detailed information on these parameters Unless otherwise specified UDM transfers file data using the SSL protocol and the NULL MD5 cipher suite If you do not want to take the performance hit of SSL and authentication of the transferred data is not required you may want encrypt NULL NULL specified as a session option However the NULL NULL cipher suite must be in the cipher list for all UDM servers involved in the transfer Stoneman s Tip udm user 3207 Confidential amp Proprietary 211 Transfer Sessions UDM Transfer Operations 12 2 3 Closing a Session When all transfer operations have concluded you can close a transfer session by issuing a close command At this point UDM is ready to initiate another transfer session Alternatively if you want to exit
67. time stamp and the program s process ID SYSTEM Messages are written to the syslog daemon Not all programs provide this destination Universal programs that execute as daemons write to the syslog s daemon facility All messages include the programs process ID If an error occurs writing to the syslog the message is written to the system console udm user 3207 Confidential amp Proprietary 86 Message and Audit Facilities Features Message destinations are listed in the table below STDERR Messages are written to standard error This destination is most useful for console commands LOGFILE Messages are written to a log file Not all programs provide this destination Log files are written to product specific log directories which can be modified with the LOG_DIRECTORY option All messages written to log files include a date and time stamp and the program s process ID SYSTEM Messages are written to the Windows Application Event Log OS 400 Message destinations are listed in the table below STDERR Messages are written to standard error A batch job s standard error file is allocated to the print file QPRINT LOGFILE Messages are written to the job s job log SYSTEM Messages are written to the system operator message queue QSYSOPR udm user 3207 Confidential amp Proprietary 87 X 509 Certificates Features 2 10 X 509 Certificates A certificate is an e
68. to OS 400 copy on the destination side unless the DDSFILE DDSLIB and or DDSMBR attributes are overridden on the destination side to indicate a different DDS or no DDS is to be used The DDS itself is not copied so it must reside on the destination side There is one exception if the source side is a file created via FTP the created file has an associated DDS file The associated DDS specifies a single field and DDS source identified by the file is deleted following completion of the job under which the file was created When UDM identifies a file created by FTP it ignores the DDS and copies the file as though no DDS exists When copying any file to a destination data physical file with the DDSFILE DDSLIB and DDSMBR attributes set to point to the file library and member of an existing DDS that DDS is attached to the destination file In either case whether from the source or explicitly on the destination side if a DDS is used on the destination side the resulting file s CCSID is determined by the DDS or by the job CCSID settings if not provided by the DDS If the source file has no DDS or if the destination attributes specify no DDS or are overridden to do so to prevent the source attributes used in an OS 400 to OS 400 copy the destination data physical file is created with a CCSID of 65535 meaning no translation UDM will issue an informational message if you try to transfer a source file that has a DDS in text mode that te
69. to verify and if success verified specifies the user ID with which the UDM Server executes Line 4 changes the current directory of the UDM server unix running on host so19 Line 5 changes the transfer mode type from binary the default to text Text mode transfers will translate between code pages and process the end of line characters 6 Line 6 is the copy command that actually moves the data between systems It copies file data10 txt on server unix to the local UDM Manager as data10 txt Line 7 executes the quit command which closes all sessions and exits UDM with the highest exit code set a En udm user 3207 Confidential amp Proprietary 298 UDM Manager for UNIX and Windows Examples Examples A 3 2 Simple File Copy to the Server This example copies in text mode a sequential data set on the UDM Manager machine to a remote UNIX system 1 set _echo yes 2 set _halton warn 3 open unix sol9 user top098 pwd p100m 4 cd unix opt app data 5 mode type text 6 copy local c datal0 txt 7 quit For this UNIX and Windows example the following is a line by line explanation 1 Line 1 turns on command echo which results in each command being sent to stdout prior to processing 2 Line 2 sets error condition value on which script process halts Any error equal to or greater than 4 halts script processing A value of 4 effectively means halt on any error or warning 3 Line 3 opens a session between the
70. transfer server with the specified logical name return Stops executing the current script immediately and returns execution to the calling script immediately after the cal 1 command used to invoke the current script reverse Reverses the order of all characters in the string of a specified existing variable or element savedata Writes each line of a data element to a file on disk set Sets the UDM Manager s built in and global variable values status Displays the current connection status strip Strips occurrences of a sequence from a string substring Finds a substring in an existing string and stores it in a variable truncate Truncates a string to a specific length upper Forces all alpha characters in a given variable or list element to upper case Table 11 1 UDM Commands udm user 3207 Confidential amp Proprietary 164 UDM Command Format UDM Scripting Language 11 3 UDM Command Format All UDM commands conform to the following format command parameter_1 value_1 parameter_n value_n 11 3 1 Basic Rules The following basic rules apply to all UDM commands Parameters Each command can have zero or more parameters Each parameter can have a value which immediately must follow an equal sign Spaces A space must precede each parameter or parameter and value Value names such as a filename with a long path under Windows can include spaces To indicate such values use quotation marks
71. user 3207 Confidential amp Proprietary 40 Configuration Features UNIX and Windows UNIX and Windows command line options are prefixed with a dash character and alternatively on Windows the slash character For many options there are two different forms in which they can be specified Short form one case sensitive character Long form two or more case insensitive characters The parameter and value must be separated by at least one space or tab character Example command line options follow Short form 1 info G yes Long form level info login yes LEVEL info LoGiN YES OS 400 OS 400 command line options use the native conventions for Command Language CL commands The option name is specified as a CL parameter with its value enclosed in parentheses Example command line options follow Command line options MSGLEVEL info COMPRESS yes All of the Stonebranch Inc Universal Products provide OS 400 style command panels The panels are accessed by entering the command name on the command line and pressing the F4 PROMPT key udm user 3207 Confidential amp Proprietary 41 Configuration Features 2 2 3 Command Line File The command line file contains command line options specified in a file The command line file enables you to save common command line options in permanent storage and reference them as needed The command line file is the
72. user s security context 8 4 5 Universal Access Control List UDM Server uses the Universal Access Control List UACL file as an extra layer of security The UACL file contains UDM Server entries that contain Access Control List ACL rules that permit or deny access to the UDM Server See Section 2 8 Universal Access Control List for details on the Universal Access Control List feature UACL Entries The syntax of a UACL entry file is the same as the UDM configuration file See Section 2 2 6 Configuration File Syntax for detailed syntax information Table 8 3 identifies all Universal Data Mover Server for Windows UACL entries Each UACL Entry Name is a link to detailed information about that UACL entry in the Universal Data Mover 3 2 0 Reference Guide UDM_ACCESS Allows or denies access to Universal Data Mover Server services UDM_MGR_ACCESS Allows or denies access based on the host name and or user of the Manager trying to initiate a UDM session Table 8 3 UDM Server for Windows UACL Entries udm user 3207 Confidential amp Proprietary 146 Security Universal Data Mover Server for Windows Updating the Universal Data Mover Server ACL Entries Although UACL files can be edited with any text editor for example Notepad the Universal Configuration Manager application accessible via the Control Panel is the recommended way to update UACL entries see Section 2 4 Universal Configuration Manager From
73. value is considered a decimal format For example the value 0x016A392E7F would be considered a hexadecimal format An example SERIALNUMBER value is e serialnumber 0x7a2d52cbae Table 2 4 Certificate Map Matching Criteria If a certificate map rule is found that matches the client certificate the rule s identifier is assigned to the client s request The certificate identifier is then used in matching certificate based UACL entries Table 2 5 below defines the certificate identifier field as used in UACL entries CERTID Matches the certificate identifier defined by the certificate map entry The CERTID value has the following syntax An asterisk matches O or more characters and a question mark matches one character For example AB M matches ABCDM and ABM AB M matches ABCM but not ABCDM The comparison is case insensitive e Pattern matching characters such as the asterisk and question mark are included in the text to be matched by prefixing them with a forward slash character For example A B matches A B A B matches A B Table 2 5 Certificate Identifier Field udm user 3207 Confidential amp Proprietary 79 Universal Access Control List Features Client IP Address Identification TCP IP provides a method to obtain a client s IP address The IP address typically identifies the host computer on which the client is executing There are exceptions to this though Networks can be
74. wait between each successive attempt to re establish a transfer session when a network fault occurs RECV_BUFFER_SIZE Size of the TCP receive buffer for UDM REMOTE_PORT TCP port number on the remote computer used for invoking UDM Server instances SCRIPT_FILE Script file containing UDM commands to execute SCRIPT_OPTIONS Parameters to pass to the script file SEND_BUFFER_SIZE Size of the TCP send buffer for UDM SIZE_ATTRIB Default file creation size for physical files of both data and source file types TRACE_FILE_LINES Maximum number of lines to write to the trace file TRACE_TABLE Size of a wrap around trace table maintained in memory UMASK File mode creation mask VERSION Writes the program version information and copyright Table 6 1 UDM Manager for OS 400 Configuration Options udm user 3207 Confidential amp Proprietary 128 Usage Universal Data Mover Manager for OS 400 6 2 5 Command Line Syntax Figure 6 1 below illustrates the command line syntax of UDM Manager for OS 400 STRUDM SCRFILEC 7brary filename SCRMBR member PLFDIR d7rectory OPTIONSCopt7ons CODEPAGE codepage 1 CTLCPHRLST c7pher 7st DTACPHRLSTCc7pher 7st COMPRESS yes no CMPRSMTHC zlib hasp DELAY seconds IDLTIMOUT seconds KEEPALIVE seconds MODETYPE bin binary text MSGLANG anguag
75. written see Section 2 9 3 Message Levels udm user 3207 Confidential amp Proprietary 84 Message and Audit Facilities Features 2 9 2 Message ID Each message is prefixed with a message ID that identifies the message The message ID format is UNVnnnn1 where nnnn is the message number 1 is the message severity level e A Audit e I Informational W Warning E Error e T alerT e D Diagnostic Note The Universal Products 3 2 0 Messages and Codes document identifies all messages numerically by product using the nnnn message number 2 9 3 Message Levels Each Universal Product includes a MESSAGE_LEVEL configuration option that lets you select which levels that is severity levels of messages are to be written Audit specifies that all audit informational warning and error messages are to be written Informational specifies that all informational warning and error messages are to be written Warning specifies that all warning and error messages are to be written Error specifies that all error messages are to be written Trace specifies that a trace file is created to which data used for program analysis will be written The trace file name and location are Universal Product dependent see the appropriate Universal Product documentation for details Trace should be used only at the request of Stonebranch Inc Customer Support Note Diagnostic and Alert messages always are writt
76. 122 Usage Universal Data Mover Manager for OS 400 6 2 Usage The UDM Manager command is invoked from a command line or a batch job After it has been initiated UDM is ready to process commands The commands can come from Standard input or a script file in interactive mode Script file in batch mode This section describes the modes of operation configuration and configuration options and command line syntax of UDM Manager for UNIX Section 6 3 Examples of UDM Manager for OS 400 provides examples demonstrating the flexibility of Universal Data Mover 6 2 1 Universal Products for OS 400 Commands The names of the Universal Products for OS 400 commands that are installed in the OS 400 QSYS library are tagged with the Universal Products for OS 400 version release modification number 320 The names of the commands installed in the Universal Products for OS 400 product library UNVPRD320 are untagged To maintain consistency across releases you may prefer to use the untagged names in your production environment The UCHGRLS Change Release Tag program lets you change the tagged command names in QSYS to the untagged command names in UNVPRD320 See the Universal Products 3 2 0 for OS 400 Installation Guide for detailed information on UCHGRLS This chapter references the OS 400 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
77. 136 Table 7 3 UDM Server for z OS UACL Entries occccccccccccccccnocenicenininininininicininen 138 udm user 3207 Confidential amp Proprietary 27 List of Tables Chapter 8 Universal Data Mover Server for Windows 00 000 cece eee ees 140 Table 8 1 UDM Server for Windows Component Definition Options 142 Table 8 2 UDM Server for Windows Configuration Options 0 0 0 0 eeeeeeeeeeeees 144 Table 8 3 UDM Server for Windows UACL Entries ooccccccccccccccccncccncinicinininininns 146 Chapter 9 Universal Data Mover Server for UNIX 2 0 00 cece eee 148 Table 91 UDM Server for UNIX Component Definition Options ee 149 Table 9 2 UDM Server for UNIX Configuration Options s 151 Table 9 3 UDM Server for UNIX UACL Entries occccccccccccccconiconineninininininininininos 153 Chapter 10 Universal Data Mover Server for OS 400 00 02 ccc es 155 Table 10 1 UDM Server for OS 400 Component Definition Options 156 Table 10 2 UDM Server for OS 400 Configuration Options 158 Table 10 3 UDMr Server for OS 400 UACL Entries ccccccccciccciccciciniciniceninininininnn 160 Chapter 11 UDM Scripting Language 2 cece eee eee eee eee eens 162 Table 11 1 UDM Commands oocccccccnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnennnneninenine 164 Table 11 2 UDM Command Expressions Operators occccccccccccccccccccnncnnncinc
78. 16 fatal Fatal error has occurred The value of _halton can be set using the set command You also can use the convenience values of none warn error and fatal indicating 0 4 8 and 16 respectively to set the value of _halton set _halton error _keepalive When a UDM session is established the UDM Manager periodically sends a keep alive message to the transfer servers to which the transfer servers respond in order to make sure the session is still established The _keepal ive built in variable contains the interval in seconds at which these messages are sent If it has a value of 0 no keep alive messages are sent You can change this interval by setting the _keepalive variable using the set command before a session is established set _keepalive 60 _lastmsg The _lastmsg built in variable is a data element that is a simple array that contains all of the messages written in the transaction log for the last network or file oriented command that was issued open close attrib cd copy copydir delete or rename Whenever a new network or file oriented command is issued the contents of _lastmsg is cleared before the command is processed so that _lastmsg will contain only messages relating to that command If UDM encounters a print command while processing a network or file oriented command the value of the msg parameter in that command is appended to _lastmsg as a new line The contents of _lastmsg can be l
79. 40 13 3 1 attrib Attribute Command 00 cee ee 240 13 3 2 cd Change Directory Command 0 00 eee eee 244 DSN data set name File System ooooooooooommmmm o 244 EXAMPIES sci cca cake ra ee beak a a a a a ele 244 udm user 3207 Confidential amp Proprietary 21 Contents DD ddname File System 1 ee 245 13 3 3 copy Copy Command iia caoba al ook wares 246 DSNFIGSYSIGN scosossriasisiri da ai 246 Sequential Data Sets o ooooocococoocooc eee 246 Partitioned Data Sets 0 0c eee 247 DE File Systemi 24c8d iettecdcdeves i davdetdetecs shh tasendadans 248 Sequential ddnames 0 00 ce eens 248 Partitioned ddnamesS 1 eens 249 13 4 Copying Load Modules 0 0 02 cece ees 250 13 4 1 Example 251 13 4 2 Error Reporting lt a1 lt cnccenpedieh piven ene ners en sed een ea ees amp 252 13 4 3 Special Attributes 0 0002 252 Chapter 14 Transfer Operations OS 400 Specific 00 cee ee 253 14 1 Overview o o o oooooo eee eee eens 253 14 2 OSMOOWO p43 ceuw be ra e eRe ed HEREC A EADS PENAY RAE OK 254 14 2 1 File Systems arrasar rr ee RoR eR eee DER Re Ree ee RR aE 254 14 2 2 HFS for OS 400 File System 00000000 0000s 254 14 2 3 LIB File System oe ee ee ee ee 254 File TYDOS raras dee gaa ken kes babes ke Pease kos Me Ree RGM Rex eae 254 14 2 4 Data Physical Files Support 22 02 2000 0c ee e
80. 5 _echo Specification for whether or not a command is echoes prior to processing 185 _execrc Holds the value of the process executed by the last exec command issued 185 _file Name of the file for the current iteration in a forfiles loop 186 _halton Return code value that causes UDM to terminate if it is greater than 0 and is 187 equalled or exceeded by the return code value in the _rc variable _keepalive Interval at which keepalive messages are sent form the UDM Manager to 187 transfer servers _lastmsg Contains all of the messages written in the transaction log for the last network 187 or file oriented command issued _lastre Holds the return code of the last command issued and optionally an indication 188 of what happened with the last executed statement _lines Specification for whether or not the line number is printed with the error if a 189 command cannot be parsed or is malformed _path Absolute path of the file for the current iteration in a forfiles loop 189 re Current UDM return code 189 _time Current time 190 _uuid Generates a UUID 190 Table 11 3 Built In Variables udm user 3207 Confidential amp Proprietary 184 UDM Variables UDM Scripting Language _date The _date built in variable displays the current date in the format appropriate for the system s locale _date has several additional variable attributes e day resolves to the day of the week e month resolves to the curren
81. 7 Confidential amp Proprietary 75 Universal Access Control List Features 2 8 1 UACL Configuration The method used to configure UACL rules is platform dependent The following sections discuss each of the methods All UACL rules are defined in library UNVCONF member ACLCFG00 The Universal Broker allocates the UACL configuration data set to ddname UNVACL The UACL file syntax is the same as all other Universal Products z OS configuration files See Section 2 2 6 Configuration File Syntax for details UNIX All UACL rules are defined in one file uacl conf This file is required for products utilizing UACL rules otherwise the product will not start The configuration file consists of zero or more UACL entries The UACL file syntax is the same as all other Universal UNIX configuration files See Section 2 2 6 Configuration File Syntax for details All UACL rules are stored in the configuration file uacl conf UACL entries for each component are maintained using the Universal Configuration Manager see Section 2 4 Universal Configuration Manager OS 400 All UACL rules are defined in file unvconf and member uac1 This file is required for products utilizing UACL rules else the product will not start The configuration file consists of zero or more UACL entries The UACL file is searched for in the same manner as all other product configuration files See Section 2 2 5 Configuration File for information on how configur
82. 7st data_ssl_cipher_list 77st compress yes no zlib hasp delay seconds idle_timeout seconds keep_alive_interval seconds lang anguage level trace audit infolwarn error time notime network_fault_tolerant fyes no frame_interval number mode_type binary text umask number outboundip host port port recvbuffersize s7ze open_retry yes no open_retry_count number open_retry_interval number retry_count number retry_interval seconds sendbuffersize s7ze tcp_no_delay option tracefilelines number trace_table s7ze error always never comment text udm help version Figure 5 1 UDM Manager for UNIX Command Line Syntax udm user 3207 Confidential amp Proprietary 119 Examples of UDM Manager for UNIX Universal Data Mover Manager for UNIX 9 3 Examples of UDM Manager for UNIX Appendix A Examples provides operating system specific examples that demonstrate the use of Universal Data Mover Included in this appendix are the following examples that demonstrate the use of Universal Data Mover Manager for Windows and UNIX e Simple File Copy to the Manager Simple File Copy to the Server e Copy a Set of Files Each example illustrates a procedure that occurs under the operating system s default file system udm user 3207 Confidential amp Proprietary 120 Security Universal Data Mover Manager for UNIX
83. 9 12 8 6 File Permission Attribute 0 000000 00 eee 230 Examples escaun 6 pa ia God ninos Pepe aie ae ee eee 230 DefaullS iuris ken dea aia dd a E A a al ee a 231 12 8 7 Destination umask 0 000 0000 cee 231 12 8 8 Transaction Oriented Transfers 200000 2c ee ee eens 231 12 8 9 Changing the Current Directory in UDM 00000 232 12 9 Auditing Transfer Operations 0200 c eee es 233 12 9 1 Logging File Transfer Operations 00 0 e eee eee 233 12 9 2 Reporting Transfer Progress ooooeooconoommnrarnos 234 Chapter 13 Transfer Operations z OS Specific ooooooommmmrmmmmmmmmmo 235 13 1 OVENVICW ciu ica a A E EE RR 235 19 2 AUSWO pocovass bicis pb as ke aaa 236 13 21 DataSets enminda rn aa ae ri edad e eae 236 Data Set Names ococcccoccocccoo eens 236 Data Set Organization sis nessa elsa 237 Record Format ooccooo tee e ete 237 Block SIZE arica nina ciara ica gE aac ao aa aaa ken aed Hea aaa cal a E 237 13 2 2 Generation Data Group and Generation Data Sets 238 PAO GALOIS att ao arte BARR cer aan ania aie nd lag me Es 238 13 23 Catalogs lt tesitctatvattupussiatesaet ea seats taeda a E aes 239 Symbolic Mames suicidas ee Se ewes peers bak aes eeu aE a i 239 Catalog Entry Types Loxa ane dea be he Bee ee Wee wae ee 239 132 4 Allocation aida brasa we Dee dba ida 239 13 3 UDM Commands under Z OS o o occcococococcoc 2
84. AB relative path Data set name without one or more leading qualifiers The name is relative to the current directory Examples PHONE DATA DATA PDS name without its high level or mid level qualifiers and a member name enclosed in parenthesis or just a member name The name is relative to the current directory Examples e JCL CNTL JOBAB CNTL JOBAB lt JOBAB file Same as path data set name It may be absolute or relative Member name only Example JOBAB udm user 3207 Confidential amp Proprietary 217 z OS File System UDM Transfer Operations directory N A PDS name without the member name The directory name may be relative or absolute Examples JCL CNTL e MYUID JCL CNTL current directory Current leading qualifiers Note It may be more than one qualifier long Examples MYUID MYUID DATA Current leading qualifiers Note It may be more than one qualifier long or even the full PDS name Examples MYUID MYUIDJCL MYUID JCL CNTL Table 12 2 CFS Terminology Associated with z OS Data Sets UDM is capable of running as a JES batch job In a batch environment data sets may be allocated dynamically by UDM or UDM may use data sets pre allocated with JCL DD statements The JCL DD statement allocates the data set and defines its to the batch job environment as a ddname that the program us
85. ALLOC_NORMAL_DISP udm user 3207 Confidential amp Proprietary 241 UDM Commands under z OS Transfer Operations z OS Specific password Password for password protected data sets No JCL equivalent primspace e Primary amount of space to allocate for the data set e Equivalent to the first positional parameter of the second positional parameter of the JCL SPACE parameter SPACE primspace Default is 15 it can be set with the UDM configuration option ALLOC_PRIM_SPACE pwdprotect Specification for whether or not the data set is password protected Equivalent to the PASSWORD or NOPWREAD sub parameters of the JCL LABEL parameter LABEL PASSWORD NOPWREAD Value must be either PASSWORD or NOPWREAD recfm e Record format with which the data set is allocated Equivalent to the JCL RECFM parameter RECFM fmt e Default is VB it can be set with the UDM configuration option ALLOC_RECFM refdd ddname from which to copy SMS data set attributes Equivalent to the JCL REFDD parameter REFDD ddname e No default or configuration option retpd e Retention period of the data set e Equivalent to the JCL RETPD parameter RETPD date e No default or configuration option rise e Specification for whether or not to release unused space when the data set is unallocated Equivalent to the sub parameter RLSE of the JCL SPACE parameter SPACE RLSE Defaul
86. C PGM UDM REGION 256M PARM ENVAR TZ EST5EDT amp UPARM STEPLIB DD DISP SHR DSN amp UNVPRE SUNVLOAD SUNVNLS UNVCONF amp USPRFC SUNVSAMP MDL UDM command options UDM script Figure 3 1 UDM Manager for z OS JCL Procedure For this JCL procedure UPARM parameter is used to specify EXEC PARM keyword values UNVPRE parameter specifies the data set name prefix of Universal Products installation data sets UNVPRD parameter specifies the data set name prefix of Universal Products production data sets udm user 3207 Confidential amp Proprietary 96 Usage Universal Data Mover Manager for z OS 3 2 2 DD Statements in JCL Table 3 1 below describes the DD statements used in the Universal Data Mover for z OS JCL illustrated in Figure 3 1 RECFM F FB V VB STEPLIB DSORG PO RECFM U input Universal Products load library containing the program being executed UNVNLS DSORG PO input Universal Products national language support RECFM F FB V VB library Contains message catalogs and code page translation tables UNVUSRC DSORG PS input Universal SAP connector RFC member RECFM F FB V VB UNVCLIB DSORG PO input UDM call library UDM searches for script files RECFM F FB V VB specified on the call command in this library UNVTRACE DSORG PS Output UDM trace output RECFM F FB V VB UNVTRMDL DSORG PS input Data set used as
87. C_OUTPUT_STATUS Status of existing data sets being allocated for output ALLOC_PRIM_SPACE Primary space allocation used for newly allocated data sets ALLOC_RECFM Record format used for newly allocated data sets ALLOC_SEC_SPACE Secondary space allocation used for newly allocated data sets ALLOC_SPACE_UNIT Space unit in which space is allocated for newly allocated data sets ALLOC_STORCLAS SMS storage class used for newly allocated data sets ALLOC_UNIT Unit used for newly allocated data sets ALLOC_VOLSER Volume serial number used for newly allocated data sets CODE_PAGE Character code page used to translate text data DATA_COMPRESSION Specification for whether or not data is compressed on all standard I O files DATA_SSL_CIPHER_LIST SSL cipher suites to use for data session between UDM primary and secondary servers EVENT_GENERATION Events to be generated as persistent events FRAME_INTERVAL Number of UDM transfer blocks transferred before a frame sync message is sent with network fault tolerance turned on MESSAGE_LEVEL Level of messages that UDM will write to the Universal message Catalog UMC file NETWORK_DELAY Expected network latency in seconds OUTBOUND_IP RECONNECT_RETRY_COUNT 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 t
88. D Figure 13 1 Load Module Transfer Script Example This simple script will copy all of the load modules from a PDS E on the source system named MYHLQ UDM TESTLM to a newly created PDS E on the destination system named YOURHLQ TEST LOAD Figure 13 2 below illustrates an example of the output that is received when running a script such as that illustrated in Figure 13 1 Data session established using cipher NULL MD5 Two party session established with 2 component 1208550125 Transfer mode settings type binary trim no Session options Keep Alive Interval 120 Network Fault Tolerant yes src Packaging up the following files in MYHLQ UDMTMP STCO7047 R2EED53 NO000000 src LML src LM2 src tmp src MYHLQ UDMTMP STCO7047 R2EED53 NO000000 is being transferred in binary mode src YOURHLQ UDMTMP JOB07063 RD36420 NO000000 will be used as the destination filname dst Unpacking from YOURHLQ UDMTMP J0B07063 RD36420 N0000000 src MYHLQ UDMTMP STCO7047 R2EED53 N0000000 transfered successfully in 0 01 55 src 10566891 bytes read 10566891 bytes written src Transfer operation complete 1 file s copied in 0 01 55 448 src 10566891 bytes transferred 91529 44 bytes per second Figure 13 2 Load Module Transfer Script Output udm user 3207 Confidential amp Proprietary 251 Copying Load Modules Transfer Operations z OS Specific At the beginning of the copy operation the sou
89. DELAY The NETWORK_DELAY option provides the ability to fine tune Universal product s network protocol When a data packet is sent over a TCP IP network the time it takes to reach the other end depends on many factors such as network congestion network bandwidth and the network media type If the packet is lost before reaching the other end the other end may wait indefinitely for the expected data In order to prevent this situation Universal Products time out waiting for a packet to arrive in a specified period of time The delay option specifies this period of time NETWORK_DELAY specifies the maximum acceptable delay in transmitting data between two programs Should a data transmission take longer than the specified delay the operation ends with a time out error Universal Products will consider a time out error as a network fault The default NETWORK_DELAY value is 120 seconds This value is reasonable for most networks and operational characteristics If the value is too small false network time outs could occur If the value is too large programs will wait a long period of time before reporting a time out problem udm user 3207 Confidential amp Proprietary 68 Network Data Transmission Features SIO_MODE The SIO_MODE option specifies whether the data transmitted over the network is processed as text data or binary data Text data is translated between the remote and local code pages Additionally end of line repres
90. DM in interactive mode enter the following at the command prompt udm This will start the UDM Manager You will be greeted with a start up message and the UDM prompt similar to this UNV2800I Universal Data Mover 3 2 0 Level 0 started udm gt At the udm gt prompt you can enter ny UDM command To exit UDM enter the following command at the udm gt prompt quit Running UDM in Batch Mode UDM also can be run in batch mode When running in batch mode UDM processes a script file When the script file has finished executing UDM will exit automatically udm s script_filename udm user 3207 Confidential amp Proprietary 115 Usage Universal Data Mover Manager for UNIX 5 2 2 Configuration Configuration consists of e Setting default options and preferences for all executions of UDM Manager e 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 The configuration file udm conf provides the simplest method of specifying configuration options whose values will not change with each command invocation These default v
91. File mode creation mask USER_SECURITY User security option Table 10 2 UDM Server for OS 400 Configuration Options udm user 3207 Confidential amp Proprietary 158 Security Universal Data Mover Server for OS 400 10 4 Security Universal Data Mover Server is designed to be a secure system As the level of security rises so does the administrative complexity of the system Universal Data Mover Server has balanced the two to avoid the administrative complexity with a minimum sacrifice to security Universal Data Mover security concerns are Access to Universal Data Mover files and libraries Access to Universal Data Mover configuration file Universal Data Mover user account Privacy and integrity of transmitted network data User authentication MASAS 10 4 1 Object Permissions Only administrator accounts should have write permission to the following Universal Products libraries and all objects within these libraries e Installation library UNVPRD320 by default e Product temporary library UNVTMP320 Universal spool library UNVSPL320 For maximum security only trusted accounts administrators and the UNVUBR320 user profile should have management existence alter add update or delete authority to these objects As a reminder the system value QCRTAUT controls public access authority to created objects unless overridden by specific commands 10 4 2 Universal Data Mover Server User Profile If us
92. Files using forfiles and _file type e Invoke a Script from a Batch Job Note These examples apply equally as well to the Windows operating system with appropriate changes for the file system syntactical differences Each topic provides an example for the LIB file system The first topic Copy a File to an Existing OS 400 File also provides an example specific to the HFS file system For other examples similar to those used in the HFS file system see Section A 3 UDM Manager for UNIX and Windows Examples in Appendix A Examples These examples reference the OS 400 commands by their untagged names If you are using commands with tagged names to run UDM substitute the tagged names for the untagged names See Section 6 2 1 Universal Products for OS 400 Commands for further information udm user 3207 Confidential amp Proprietary 130 Security Universal Data Mover Manager for OS 400 6 4 Security Universal Data Mover is designed to be a secure system As the level of security rises so does the administrative complexity of the system Universal Data Mover has balanced the two to avoid the administrative complexity with a minimum sacrifice to security Universal Data Mover security concerns are 1 Access to Universal Data Mover files and libraries 2 Access to the Universal Data Mover configuration file 3 Privacy and integrity of transmitted network data 6 4 1 Object Permissions Only administrator accounts shou
93. For detailed information on defining script variables see Section 11 4 Script Files 11 6 4 Global Variables Global variables are variables that are visible at all script levels There are two types of global variables 1 User defined see Section 11 6 6 User Defined Variables 2 Built in see Section 11 6 8 Built in Variables Global variables are permanent in scope and once defined last until the UDM Manager is terminated Once defined a global variable cannot be undefined but its value can be changed by issuing another set command Issuing the set command by itself with no arguments displays all user defined and built in variables Each global variable includes the following information 1 Name identifies a variable as either a UDM pre defined built in variable see 11 6 8 Built in Variables or a user defined variable A variable is referenced in a script by this name 2 Attribute optional entry that can be included in a variable reference It provides additional information about a variable see 11 6 7 Variable Attributes 3 Value assigned by the user and or provided by UDM depending on the variable Built in variables have pre defined and or user defined values All user defined variables have user defined values udm user 3207 Confidential amp Proprietary 179 UDM Variables UDM Scripting Language 11 6 5 Scope of Script and Global Variables A variable s scope is its visibility throughout the scrip
94. For example copy src c program files somefile txt dst test txt Escape Sequences Double Quote Marks To include quotation marks as part of the token use two quotation marks in a row gt echo This word is This word is quoted quoted Other Printable Characters When processing tokens that are inside quotation marks all other printable characters except variable references are ignored as being part of the language If you want to assign a variable to have a value of a language symbol such as an equal sign you must enclose it in quotation marks gt set myvar gt echo myvar udm user 3207 Confidential amp Proprietary 165 UDM Command Format UDM Scripting Language Line Continuation If a command is too long for a single line it can be continued on one or more following lines by placing either of the following characters as the last character in each line break e Plus sign Retains leading white space on the next line when assembling the finished line e Minus sign Trims the leading white space For example This is a test Yields the following line This is a test This is a test Yields the following line This is a test Comments A script also can have comments lines of user specified text indicating information about the script and the operations taking place Comment lines begin with the hash mark White space characters can precede the hash
95. Format ISO 8601 is yyyy mm dd modt ime Time when the file was last modified referenced for z OS Format ISO 8601 is hh mm ss modtimestamp Combination of moddate and modtime yyyy mm dd hh mm ss If the file does not have a modification time but does have a modification date 00 00 00 is used for the time portion name Name of the file same as referencing _fi1e itself without any attributes size Size of the file in bytes type Type of file Values are e file e directory also used for PDSs under z OS unknown type has meaning in a forfiles statement under OS 400 in the LIB file system e Ifthe value of _file type is directory the file type is a Physical file e Ifthe value of _file type is file the file type is a Save file Table 11 4 _file Built in Variable Special Attributes _file cannot be set using the set command udm user 3207 Confidential amp Proprietary 186 UDM Variables UDM Scripting Language _halton The _halton built in variable specifies a return code value that causes UDM to terminate if that value is e Greater than 0 Equaled or exceeded by the return code value in the _rc variable Note If the _halton value is 0 and the return code in _rc is 0 UDM will not terminate Each UDM command has a return code indicating its level of success or failure e 0 none Success or no error 4 warn Warning has been issued 8 error Error has occurred e
96. IVAL SP ALWDLT Allow delete operation v YES NO NULL YES PF SP ALWUPD Allow update operation v YES NO NULL YES PF SP ASPDEV ASP device ASP ASPGRPPRI NULL ASP LIB SYSTEM device name ASPNUM ASP number LIBASP 1 32 NULL LIBASP LIB ASPDEV for SAVF SAVF 1 for LIB AUT Authority LIBCRTAUT ALL NULL LIBCRTAUT LIB PF CHANGE for SP SAVF EXCLUDE USE LIB PF SP 2 EXCLUDE for SAVF CCSID CCSID of the file Source v EBCDIC CCSIDs CODEPAGE SP physical files only For data physical files the DDS if one is given determines its CCSID if no DDS is given the value is 65535 udm user 3207 Confidential amp Proprietary 264 Command Reference Transfer Operations OS 400 Specific CRTAUT Create authority SYSVAL ALL NULL LIB CHANGE EXCLUDE USE authority name DDSLIB Library of the DDS used to v empty string PF describe the file DDSFILE File of the DDS used to v empty string PF describe the file DDSMBR Member of the DDS used to v empty string PF describe the file DLTPCT Maximum percentage of 1 100 NONE NULL NONE PF deleted records allowed EXPDATE Expiration date for member v date NONE NULL NONE PF SP FILETYPE Type of file to create when v DATA SRC SAVF DATA PF SP creating a new file SAVF FRCRATIO Records to a force write integer NONE NULL NONE PF SP GENLVL Generation severity level 0 30 NULL 20 PF LIBTYPE Type of library
97. In this example if the command executed before the first if statement resulted in an error the output would have been as follows Last command was not successful Last command was successful This is because the _lastrc variable holds the value of the last command executed by UDM In the example given the command executed before the first if statement resulted in an error for example result code 8 and would result in the first if statement evaluating to true udm user 3207 Confidential amp Proprietary 196 if Statement UDM Scripting Language However the successful execution of the print command inside the first if statement would result in _1astre being set to 0 which would in turn mean the second if statement would evaluate to true thus printing the second message This would not have been what was intended In this contrived example it is rather easy to see what went wrong and come up with a workaround in this case creating a new global variable into which to save the value of _lastrc for example set newvar _lastrc and using the new variable in the comparison operations instead of _lastrc as its value would not be overwritten For longer and more complex scripts however this may not be the case Alternate Path with else Statement UDM offers an easy solution with the else statement As part of the if statement the else statement can be used to provide an alternative path to take if the comparison evalu
98. It could be specified as YES Yes or yes However if a value specifies a directory name or file name it would be case sensitive if the operating system s file system is case sensitive If an option is specified more than once on the command line the last instance of the option specified is used z OS command line options are specified in the JCL EXEC statement PARM keyword or on the SYSIN ddname The PARM keyword is used to pass command line options to the program being executed with the EXEC statement Command line options are prefixed with a dash character For many options there are two different forms in which they can be specified Short form one case sensitive character e Long form two or more case insensitive characters The parameter and value must be separated by at least one space Example command line options specified in the PARM value follow Short form PARM 1 INFO G yes Long form PARM LEVEL INFO LOGIN YES As noted above z OS command line options also can be specified on the SYSIN ddname This is the easiest and least restrictive place to specify options since the PARM values are limited in length The options specified in the SYSIN ddname have the same syntax Options can be specified on one line or multiple lines The data set or inline data allocated to the SYSIN ddname cannot have line numbers in the last 8 columns that is all columns of the records are used as input udm
99. LATION_DIRECTORY Directory on which UDM Manager is installed KEEP_ALIVE_INTERVAL Default interval at which a keep alive message is sent from the manager to the transfer server s MERGE_LOG Specification for whether or not to merge standard out and standard error output streams from a remote command to the UDM transaction log MESSAGE_LANGUAGE Universal Message Catalog UMC file used to write messages MESSAGE_LEVEL Level of messages to write MODE_TYPE Default transfer mode type for UDM sessions NETWORK_DELAY Expected network latency NETWORK_FAULT_TOLERANT Specification for whether or not UDM transfer sessions are network fault tolerant by default udm user 3207 Confidential amp Proprietary 110 Universal Data Mover Manager for Windows NLS_DIRECTORY OPEN_RETRY Directory where the UDM Manager message catalog and code page tables are located Level of fault tolerance for the open command OPEN_RETRY_COUNT Maximum number of attempts that will be made to establish a session by the open command OPEN_RETRY_INTERVAL Number of seconds that UDM will wait between each open retry attempt OUTBOUND_IP Host or IP address that UDM binds to when initiating outgoing connections to another UDM server PRIVATE_KEY ddname of Manager s PEM formatted RSA private key PRIVATE_KEY_PWD Password for the Manager s PRIVATE_KEY PROXY_CERTIFICATES Specification for whether
100. N data set name File System The DSN data set name file system has no directories The cd command treats each data set qualifier as a directory in regards to traversing and positioning within the data set name space UDM initializes the current directory to a high level qualifier equal to the user identifier with which UDM executes A cd value can be enclosed in apostrophes One or more qualifiers enclosed in apostrophes replaces the current directory value A cd value not enclosed in apostrophes is concatenated to the current directory value separated by a period effectively moving up in the hierarchy There are two special directory qualifier names 1 Current directory represented by a single period Directory name makes no change 2 Previous directory represented by two periods Directory name moves back one qualifier Examples Table 13 2 below provides examples of positioning within the data set file system using the cd command The examples assume the following User ID of TOM123 UDM logical name SRV TOM123 cd srv data TOM123 DATA TOM123 DATA cd srv appl jcl TOM123 DATA APP1 JCL TOM123 DATA APP1 JCL cd srv TOM123 DATA APP1 TOM123 DATA APP1 cd srv GAM789 DATA GAM789 DATA GAM789 DATA cd srv GAM789 GAM789 cd srv GAM789 Table 13 2 cd Command in DSN File System udm user 3207 Confidential amp Proprietary 244 UDM Commands under z OS Transfer Ope
101. NNING_MAXIMUM Maximum number of UDM Servers that can run simultaneously START_COMMAND Full path name of the UDM Server program WORKING_DIRECTORY Full path name of the UDM Server working directory Table 8 1 UDM Server for Windows Component Definition Options udm user 3207 Confidential amp Proprietary 142 Configuration Universal Data Mover Server for Windows 8 3 Configuration Universal Data Mover Server configuration consists of defining runtime and default values This section describes the UDM Server configuration options See Section 2 2 1 Configuration Methods for details on Universal Products configuration methods 8 3 1 Configuration File The configuration file provides a method of specifying configuration values that will not change with each command invocation The Universal Data Mover Server configuration file name and directory is specified in the Universal Data Mover Server component definition see Chapter 4 Universal Data Mover Component Definition Options in the Universal Data Mover 3 2 0 Reference Guide The default configuration file name is udms conf Although configuration files can be edited manually with any text editor for example Notepad the Universal Configuration Manager application is the recommended way to set configuration options in the configuration file The Universal Configuration Manager provides a graphical interface and context sensitive help and helps protect the
102. S 400 IBM iSeries and IBM System i systems Note These names do not imply software support in any manner For a detailed list of supported operating systems see the Universal Products 3 2 0 Installation Guide udm user 3207 Confidential amp Proprietary 32 Preface Document Organization Overview Chapter 1 General architectural and functional overview of Universal Data Mover Features Chapter 2 Description of Universsal Data Mover features including configuration methods and network protocols Universal Data Mover Manager for z OS Chapter 3 Description of Universal Data Mover Manager specific to the z OS operating system Universal Data Mover Manager for Windows Chapter 4 Description of Universal Data Mover Manager specific to the Windows operating system Universal Data Mover Manager for UNIX Chapter 5 Description of Universal Data Mover Manager specific to the UNIX operating system Universal Data Mover Manager for OS 400 Chapter 6 Description of Universal Data Mover Manager specific to the OS 400 operating system Universal Data Mover Server for z OS Chapter 7 Description of Universal Data Mover Server specific to the z OS operating system Universal Data Mover Server for Windows Chapter 8 Description of Universal Data Mover Server specific to the Windows operating system Universal Data Mover Server for UNIX Chapter 9 Description of Universal Data Mover Server specific to the UNIX opera
103. Section 6 2 4 Configuration Options of Chapter 6 Universal Data Mover Manager for OS 400 e ACTIVITY_MONITORING CA_CERTIFICATES CERTIFICATE CERTIFICATE REVOCATION LIST CODEPAGE_TO_CCSID_MAP COMMENT EVENT_GENERATION OPEN_RETRY e OPEN_RETRY_COUNT e OPEN_RETRY_INTERVAL PLF_DIRECTORY e PRIVATE_KEY e PRIVATE_KEY_PWD PROXY_CERTIFICATES Added the following STRUDM parameters in Figure 6 1 UDM Manager for OS 400 Command Line Syntax e CTLCPHRLST e DTACPHRLST FRAMEINT MODETYPE e MSGLEVEL time values OUTBOUNDIP Added an Invoke a Script from a Batch Job example in Appendix A 4 UDM Manager for OS 400 Examples Added the following configuration options in Section 10 3 2 Configuration Options of Chapter 10 Universal Data Mover Server for OS 400 ACTIVITY_MONITORING CODEPAGE_TO_CCSID_MAP EVENT_GENERATION TMP_DIRECTORY Modified Section 14 4 2 call Call Command in Chapter 14 Transfer Operations OS 400 Specific Added Caution about Text Mode Transfer of Files with DDS in subsection 14 2 4 Data Physical Files Support of Section 14 2 OS 400 I O udm user 3207 Confidential amp Proprietary 6 Summary of Changes Changes for Universal Data Mover 3 2 0 User Guide udm user 3204 April 1 2009 e Moved the Licenses and Copyrights appendix to the Universal Products 3 2 0 Installation Guide Universal Data Mover 3 2 0 3 Added the TCP_NO_DELAYconfiguration option to the
104. T YOURLIB YOURLIB MYFILE MYFILE is used as the destination name if the destination file type is a physical file or YOURLIB MYFILE if the destination file type is a save file If the destination file specification contains only library and file portions an absolute path of YOURLIB YOURFILE is derived if a save file is wanted If an absolute path of YOURLIB YOURFILE MYFILE is used if a physical file is wanted Example COPY SRC MYFILE DST YOURLIB YOURFILE YOURLIB YOURFILE MYFILE is the destination name if a physical file is wanted and YOURLIB YOURFILE is used if a save file is wanted If the destination file specification contains library and file portions as well as an empty member portion the result is exactly the same as when the specification contains only a library and file portions Example COPY SRC MYFILE DST YOURLIB YOURFILE YOURLIB YOURFILE MYFILE is the destination name if a physical file is wanted If the destination file specification contains a complete absolute path library file and member portions the source file name has no effect on the destination path in any way In this case if the destination file type is a physical file YOURLIB YOURFILE YOURMBR is used Example COPY SRC MYFILE DST YOURLIB YOURFILE YOURMBR YOURLIB YOURFILE YOURMBR is the destination if the destination file type is a physical file In cases where a member is specified explicitly in the destination file name and the destination f
105. TES File name of the PEM formatted trusted CA X 509 certificates CERTIFICATE File name of UDM Manager s PEM formatted X 509 certificate CERTIFICATE_REVOCATION_LIST File name of the PEM formatted CRL CODE_PAGE Character code page used to translate text data received and transmitted over the network CODEPAGE_TO_CCSID_MAP Specification to use either the internal or external table for code page to CCSID mapping COMMENT User defined string CTL_SSL_CIPHER_LIST Acceptable and preferred SSL cipher suites to use for the control session between UDM components DATA_COMPRESSION Specification for whether or not data is compressed on all standard 1 O files DATA_SSL_CIPHER_LIST Acceptable and preferred SSL cipher suites to use for the data session on which file data is transferred between UDM primary and secondary servers EVENT_GENERATION Events to be generated as persistent events FRAME_INTERVAL Number of UDM transfer blocks transferred before a frame sync message is sent when UDM is operating with network fault tolerance turned on IDLE_TIMEOUT Number of seconds of inactivity in an interactive UDM session after which the manager will close the session KEEP_ALIVE_INTERVAL Default interval at which a keep alive message is sent from the manager to the transfer server s MERGE_LOG Specification for whether or not to merge standard out and standard error output streams from a remote command to the UDM transaction log
106. The DEFAULT_CIPHER option specifies the SSL cipher suite to use since SSL protocol requires a cipher suite if the DATA_ENCRYPTION option is set to NO The default DEFAULT_CIPHER is NULL MD5 no encryption MD5 message digest All SSL cipher suites have a message digest for good reasons The message digest ensures that the data sent are the data received Without a message digest it is possible for bits of the data packet to get changed without being noticed KEEPALIVE_INTERVAL The KEEPALIVE_INTERVAL option specifies how often in seconds a keepalive message also commonly known as a heartbeat message is sent between a manager and server A keepalive message ensures that the network and both programs are operating normally Without a keepalive message error conditions can arise that place one or both programs in an infinite wait A keepalive message is sent from the server to the manager If the server does not receive a keepalive acknowledgement from the manager in a certain period of time calculated as the maximum of 2 x NETWORK_DELAY or the KEEPALIVE_INTERVAL the server considers the manager or network as unusable How the server processes a keepalive time out depends on what fault tolerant features are being used If no fault tolerant features are being used the server ends with an error The manager expects to receive a keepalive message in a certain period of time calculated as the KEEPALIVE_INTERVAL 2 x NETWORK_DELAY NETWORK_
107. The truncext attribute is used to instruct UDM to remove file name extensions from the source file prior to using the name as the destination member name This example assumes that the remote UNIX directory opt app data contains the following list of files e data001 txt e data002 txt e data003 txt e data004 pr e data005 pr The result of the copy operation will create the following members in PDS APP DATA PDS e DATA001 e DATA002 e DATA003 udm user 3207 Confidential amp Proprietary 293 UDM Manager for z OS Examples Examples DD file system S1 EXEC UDMPRC APOUT DD DSN APP DATA PDS DISP SHR UNVSCR DD NON OU bh uN PH set _echo yes _halton warn open unix sol9 user top098 pwd p100m filesys local dd cd unix opt app data mode type text attrib local truncext yes copy unix txt local apout quit DSN file system S1 EXEC UDMPRC UNVSCR DD NN OW PWN BP set _echo yes _halton warn open unix sol9 user top098 pwd p100m cd unix opt app data mode type text attrib local truncext yes copy unix txt local app data daily quit udm user 3207 Confidential amp Proprietary 294 UDM Manager for z OS Examples Examples A 2 4 Copy a File to a New z OS Sequential Data Set This example copies in text mode a file from a remote UNIX system to a sequential data set on z OS The data set does not exist on z OS UDM is instructed to create it The
108. Transfer server with the logical name dst would change its directory to c destination 3 All files in the c 1source directory then would be copied from the first transfer server over to the second udm user 3207 Confidential amp Proprietary 174 Subroutines UDM Scripting Language 11 5 Subroutines UDM s scripting language provides support for subroutines Subroutines are portions of the script code that can be called by name at any point This provides a convenient way to reuse common script code 11 5 1 Usage There are two parts to a subroutine 1 Definition Names the subroutine and defines the script code that becomes associated with that subroutine name 2 Invocation Carries out the work of lines of script associated with a subroutine Defining a Subroutine subroutine name script line 1 script line n endsub Invoking a Subroutine callsub name udm user 3207 Confidential amp Proprietary 175 Subroutines UDM Scripting Language Sequence of Defining Invoking a Subroutine A subroutine must be physically defined before the ca11sub to the routine is used For example the following subroutine will function correctly subroutine test echo This is subroutine test echo _halton endsub echo This is main callsub test However this subroutine will fail echo This is main callsub test subroutine test echo This is subroutine test echo _halton endsu
109. UDM you can issue a quit command which closes the transfer session and exits the UDM Manager udm user 3207 Confidential amp Proprietary 212 File Systems UDM Transfer Operations 12 3 File Systems 12 3 1 File System Overview Platforms can support one or more file systems or file access methods e UNIX and Windows support a single hierarchical file system e z OS support three file systems or file access methods under UDM 1 DSN data set name the default when UDM is running under z OS 2 DD ddname defined by a JCL DD statement 3 HFS the hierarchical file system supported by USS See Section 12 5 z OS File System for detailed information on z OS file systems e 08 400 supports two file systems under UDM 1 LIB the default file system 2 HFS limited to the root and QOpenSys file systems under IFS See Section 14 2 OS 400 I O for detailed information on OS 400 file systems All transfer operations on a given server will take place in the server s current file system Both servers in a transfer session do not have to be in the same file system UDM is capable of reformatting data between different file systems The default file system under z OS is DSN even if the UDM Manager is executed from USS UNIX System Services Stoneman s Tip udm user 3207 Confidential amp Proprietary 213 File Systems UDM Transfer Operations 12 3 2 Changing the Current File System Changing the
110. URLIB MYFILE MYMBR if the destination file type is a physical file COPY SRC MYLIB MYFILE DST YOURLIB The result is a destination name of YOURLIB MYFILE if the destination file type is a save file If the destination file specification contains only library and file portions an absolute path of YOURLIB YOURFILE is derived if a save file is wanted If a physical file is wanted YOURLIB YOURFILE MYMBR is used Examples COPY SRC MYLIB MYFILE MYMBR DST YOURLIB YOURFILE The result is a destination name of YOURLIB YOURFILE MYMBR if the destination file type is a physical file COPY SRC MYLIB MYFILE DST YOURLIB YOURFILE The result is a destination name of YOURLIB YOURFILE if the destination file type is a save file If the destination file specification contains library and file portions as well as an empty member name the result is exactly the same as when the file specification contains only library and file portions Example COPY SRC MYLIB MYFILE MYMBR DST YOURLIB YOURFILE The result is a destination name of YOURLIB YOURFILE MYMBR if the destination file type is a physical file udm user 3207 Confidential amp Proprietary 272 Command Reference Transfer Operations OS 400 Specific 8 If the destination file specification contains a complete absolute path library file and member portions the source file name has no effect on the destination path in any way In this case if the destination file type i
111. a O Stonebranch Inc OU Sales CN Joe Black A certificate is composed of many fields and possible extensions Many of the most popular fields are specified as X 500 DN values udm user 3207 Confidential amp Proprietary 89 X 509 Certificates Features 2 10 2 Sample X 509 Certificate Figure 2 8 below illustrates a sample X 509 version 3 certificate for Joe Buck at the Acme corporation Certificate Data Version 3 0x2 Serial Number 01 02 03 04 05 06 07 08 Signature Algorithm md5withRSAEncryption Issuer C US ST Florida O Acme Inc OU Security CN CA Authority emai lAddress ca acme com Validity Not Before Aug 20 12 59 55 2004 GMT Not After Aug 20 12 59 55 2005 GMT Subject C US ST Florida O Acme Inc OU Sales CN Joe Buck Subject Public Key Info Public Key Algorithm rsaEncryption RSA Public Key 1024 bit Modulus 1024 bit 00 be 5e 6e f8 2c c7 8c 07 7e f0 ab a5 12 db fc 5a le 27 ba 49 b0 2c e1 cb 4b 05 f2 23 09 77 13 75 57 08 29 45 29 d0 db 8c 06 4b c3 10 88 el ba 5e 6f 1e c0 2e 42 82 2b e4 fa ba bc 45 e9 98 f8 e9 00 84 60 53 a6 11 2e 18 39 6e ad 76 3e 75 8d 1e b1 b2 1e 07 97 7f 49 31 35 25 55 0a 28 11 20 a6 7d 85 76 f7 9f c4 66 90 e6 2d ce 73 45 66 be 56 aa ee 93 ae 10 f9 ba 24 fe 38 d0 f0 23 d7 a1 3b Exponent 65537 0x10001 x509v3 extensions X509v3 Basic Constraints CA FALSE X509v3 Subject Alternative Name email joe buck acme com Signature Algorithm md5withRSAEnc
112. a match is found The certificate map defines a set of X 509 certificate fields that may be used as matching criteria Table 2 4 below defines the certificate map matching criteria SUBJECT Matches the X 509 subject field The subject field is formatted as an X 501 Distinguished Name DN A DN is a hierarchical list of attributes referred to as Relative Distinguished Names RDNs RDNs are separated with a comma by default If a different separator is required perhaps one of the RDN values uses a comma start the DN with the different separator character Valid separators are slash comma and period Many RDN values can be used in a DN Some of the most common values are e C Country name e CN Common name e L Locality e 0 Organization OU Organizational Unit e ST State The RDN attributes must be listed in the same order as they are defined in the certificate to be considered matched A partial DN can be specified All certificates that have a subject name that matches up to the last RDN are considered a match This permits a group of certificates to be matched The RDN attribute values can include pattern matching characters An asterisk matches 0 or more characters and a question mark matches one character Some example of SUBJECT values are subject C US ST Georgia 0 Acme CN Road Runner e subject C US ST Georgia 0 Acme CN Road e subject C US ST Georgia 0 Acme CN Road unn
113. a tee deada rd deca 35 1 2 2 Primary Server oros Paco edt WO Sale ee eae oats se Ree aos 35 1 2 3 Secondary Server cn cca cat eek peewee deca tan pea Pee eee Re ee Re kes 35 1 3 Transfer Sessions 00 0 cette eee 36 1 3 1 Logical Names 20 gane pace iaa de ile a iii ab jasa 36 1 3 2 Two Party Transfer Sessions 0 e eee es 36 1 3 3 Three Party Transfer Sessions 0 000 c eee eee ees 36 udm user 3207 Confidential amp Proprietary 13 Contents Chapter 2 Features 2 end dic sia ii a a e s 38 2 1 OVEIVIEW eite a ca agen dade Vata aaa Pee ade dea Lae ae E 38 22 OI QUISO ens o ata sie e oe oa reo S 39 2 2 1 Configuration Methods ecommerce ra a 39 2 2 2 Command Line ccccoccococccc eee tees 40 2 2 3 Command Line File escri A A 42 2 2 4 Environment Variables os e a e di 43 2 2 5 Configuration File ios a e le eee A ia 45 2 2 6 Configuration File Syntax scort rata dear a ke nice 47 2 3 Remote Configuration sosocsarsricida rar as 48 2 3 1 Unmanaged Mode cota E DA a GR 48 2 3 2 Managed Mode 22iccaxkitad ERA EARARE sea Reread aekas 49 Selecting Managed Mode 2 200 cece ee eee 49 2 3 3 Universal Broker Startup sssaaa anaana 51 2 4 Universal Configuration Manager 0 ce eee ee 52 E cot eeesGen enh bewate seeedmen laced ones ered eyneves 52 2 4 2 Accessing the Universal Configuration Manager 54 2 4 3 Navigating through Universal Configuration Manager
114. able 2 3 Component Communication States udm user 3207 Confidential amp Proprietary 72 z OS CANCEL Command Support Features 2 7 z OS CANCEL Command Support Universal Products provide network fault tolerance see Section 2 6 Fault Tolerance and in some cases manager fault tolerance These features provide users with the ability to execute jobs that will continue to run when the network is down and when a manager is terminated However there are scenarios in which the user may want to cancel an executing job that supports manager and or network fault tolerance and have both the manager and server processes terminate immediately Because of fault tolerance when the manager is terminated the server side would begin a connection reestablishment protocol and continue to execute This would allow the started user job to continue running In particular z OS supports a CANCEL command that will terminate a job executing on the z OS operating system When a Universal Data Mover job is cancelled via the z OS CANCEL command the job terminates with either of these exit codes Exit code 122 if it is cancelled with a dump Exit code S222 if it is cancelled without a dump Part of the responsibility of a Universal Broker executing on a particular host is to monitor the status of all locally running manager processes on that machine So when instructed that Universal Broker could issue a STOP command to the Universal Data Mover Server
115. aces so that the record length equals the logical record length of the data set If you do not want the trailing spaces copied they must be trimmed LIB file system set _echo yes set _halton warn open unix sol9 user top098 pwd p100m cd unix opt app data mode type text trim yes copy local MYLIB APPDATA DAILY unix datal0 txt quit N DW bh WUNA udm user 3207 Confidential amp Proprietary 304 UDM Manager for OS 400 Examples Examples A 4 3 Copy a Set of Files to an Existing Data Physical File This example copies in text mode multiple files with one copy command to an already allocated Data Physical File on an OS 400 system The file names used to create the member names in the destination Data Physical File are the source file names However note that file names on UNIX and Windows file systems often have a file extension as part of their name A file extension is a suffix separated from the file s base name with a period for example BASE TXT Member names are limited to 10 characters on the OS 400 system so UDM must be instructed to remove the file extensions before copying them into the PDS The truncext attribute is used to instruct UDM to remove file name extensions from the source file prior to using the name as the destination member name This example assumes that the remote UNIX directory opt app data contains the following list of files e data001 txt e data002 txt e data003 txt e d
116. al Broker stores the information in a database file located within its specified spool directory The information can be modified only via Universal Management Console UMC From this point on Universal Broker uses the database file not the configuration files to access configuration information Any configuration changes made to the components via UMC are placed in the database file Therefore as long as Universal Broker stays in managed mode the configuration files may no longer contain current or valid configuration information If managed mode is de selected for the Universal Broker it reads the database file where it stored the configuration information Universal Broker uses this information to create and or update configuration files for the components e Ifa configuration file exists in the configuration directory it is overwritten e Ifa configuration file does not exist it is created Note Because of remote configuration and the desire to be able to lock down all product configurations Universal Broker and all Universal Products servers no longer support the command line and environmental variables methods of specifying configuration options Selecting Managed Mode The managed mode of operations for Universal Broker is selected via the Universal Enterprise Controller Administration client application See the Universal Enterprise Controller 3 2 0 Client Applications guide for specific information
117. al Products TLSv1 is more commonly referred to simply as SSL and the term SSL is used throughout the rest of this documentation to mean TLSv1 unless otherwise noted The SSL protocol addresses the major challenges of communicating securely over a potentially insecure data network The following sections discuss the issue of data privacy and integrity and peer authentication udm user 3207 Confidential amp Proprietary 60 Network Data Transmission Features Data Privacy and Integrity People with sufficient technical knowledge and access to network resources can watch or capture data transmitting across the network What they do with the data is up to them Data sent over the network that should remain private must be encrypted in a manner that unauthorized persons cannot determine what the original data contained regardless of their level of expertise access to network resources amount of data captured and amount of time they have The only party that should be able to read the data is the intended recipient As data is transmitted over the network it passes through media and hardware of unknown quality that may erroneously change bits of data without warning Additionally although data may be encrypted there is nothing stopping a malicious person from changing the data while it is transmitted over the network The changed data may or may not be detected by the recipient depending on what changed and how it is processed It may
118. al name FILE FILE Renames the file in the current library in the old portion with the new file name in the current directory library RENAME logical name FILE LIBRARY FILE Renames the file in the current directory with the file name in the new portion The library in the old name portion must be the current library RENAME logical name LIBRARY FILE FILE Renames the file in the given library with the name of the file in the new portion if the library name in the old portion is the same as the current library RENAME logical name LIBRARY FILE MEMBER LIBRARY FILE MEMBER Renames the old member name with the new member name Both the library and file name portions in the old and new member names must match RENAME logical name FILE MEMBER FILE MEMBER Renames the member in the old name with the name of the member in the new name The FILE portion of each name must be the same RENAME logical name FILE MEMBER LIBRARY FILE MEMBER Renames the member in the old name with the name of the member in the new name if the library specified in the old name is the same as the current library and both file name portions match RENAME logical name LIBRARY FILE MEMBER FILE MEMBER Renames the member in the old name with the name of the member in the new name if the library specified in the new name is the same as the current library and both file name portions match Table 14 5 rename Command Forms
119. aluation of a conditional Using this technique with nested conditionals provides an easy way to tell at which level each of the commands belong In addition leaving a blank line before and after a conditional Stoneman s Tip not required by UDM provides a way to visually indicate a block of related script commands This improves the readability and maintainability of scripts in the future udm user 3207 Confidential amp Proprietary 198 if Statement UDM Scripting Language 11 7 4 Returning Early Using the return Command At times it is useful to be able to exit from processing a single script file in the middle of that script file if certain processing conditions are not correct For this UDM provides the return command which takes the following format return value The return command stops processing of the current script and returns control to the calling script at the point immediately following the script call just as if the script had executed completely without calling the return command If there was not a calling script and UDM is not running interactively UDM will exit The return command also can be followed by an optional value If this is the case UDM s return code held by the _re built in variable is set to this value upon executing the return command One common use of the return command is to exit from a script if the previous operation failed The _halton variable can be used for this
120. alues are used if the options are not read from one or more other sources See the Universal Products 3 2 0 Installation Guide 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 See Section 2 2 1 Configuration Methods for details on Universal Products configuration methods udm user 3207 Confidential amp Proprietary 116 Usage Universal Data Mover Manager for UNIX 5 2 3 Configuration Options Table 5 1 below describes the configuration options used to execute UDM Manager for UNIX Each Option Name is a link to detailed information about that configuration option in the Universal Data Mover 3 2 0 Reference Guide ACTIVITY_MONITORING Specification for whether or not product activity monitoring events are generated BIF_DIRECTORY Broker Interface File directory where the Universal Broker interface file is located CA_CERTIFICATES File name ddname of the PEM formatted trusted CA X 509 certificates CERTIFICATE File name ddname of UDM Manager s PEM formatted X 509 certificate CERTIFICATE_REVOCATION_LIST File name ddname of the PEM formatted CRL CODE_PAGE Character code page used to translate text data received
121. ame ddname of the PEM formatted trusted CA X 509 certificates CERTIFICATE File name ddname of UDM Manager s PEM formatted X 509 certificate CERTIFICATE_REVOCATION_LIST File name ddname of the PEM formatted CRL CODE_PAGE Character code page used to translate text data received and transmitted over the network COMMENT User defined string CTL_SSL_CIPHER_LIST Acceptable and preferred SSL cipher suites to use for the control session between UDM components DATA_COMPRESSION Specification for whether or not data is compressed on all standard 1l O files Confidential amp Proprietary 100 Universal Data Mover Manager for z OS DATA_SSL_CIPHER_LIST Acceptable and preferred SSL cipher suites to use for the data session on which file data is transferred between UDM primary and secondary servers EVENT_GENERATION Events to be generated as persistent events FRAME_INTERVAL Number of UDM transfer blocks transferred before a frame sync message is sent when UDM is operating with network fault tolerance turned on HELP Writes a description of the command options and their format IDLE_TIMEOUT Number of seconds of inactivity in an interactive UDM session after which the manager will close the session KEEP_ALIVE_INTERVAL Default interval at which a keep alive message is sent from the manager to the transfer server s MERGE_LOG Specifi
122. an readable string indicating what happened with the last executed statement _rc Variable The _rc built in variable holds the highest numbered return code that UDM has received and placed in the _lastrc built in variable from all processed commands during the current session _rc also can be set via the set command see 16 3 Setting Return Codes _halton Variable The _hal ton built in variable specifies a return code that if equaled or exceeded by the return code in _rc causes UDM to exit Otherwise when UDM exits it returns the highest numbered return code that it received to the UDM Manager _halton only can be set via the set command see 16 3 Setting Return Codes For detailed information on these variable see Chapter 11 UDM Scripting Language udm user 3207 Confidential amp Proprietary 286 Setting Return Codes Return Code Processing 16 3 Setting Return Codes 16 3 1 Return Codes in set Set Command You can use the set command to manage UDM s return code and UDM s action based on this return code The set command lets you set any of the following return code values integer or convenient in both the _halton variable and the _rc variable e 0 none 4 warn e 8 error 16 fatal The following example sets the value of _rc to 0 and the _halton condition to error set _rc 0 _halton error Issuing the set command by itself with no parameters will display the values of all of the UDM Ma
123. ananena 146 8 4 5 Universal Access Control List 0000 ccc eee 146 WACL ENICS 2424 ndiuae Wied aie dae acai ead SoA baad ane kates 146 Updating the Universal Data Mover Server ACL Entries 147 Chapter 9 Universal Data Mover Server for UNIX o o o o o 148 9 1 OVEIVIEW anorisid ir ds eee ial aia 148 9 2 Component Definition 0 0000 eee 149 89 CONMGUIAUON dedica a wade eh wad oe hard ap Mae ee Rea ee Be eee aU Be 150 9 3 1 Configuration File css ars a AER aad 150 9 3 2 Configuration Options e cece ehiber did bedeseea e 151 JA eC ado eo e ne eet eens to 152 9 4 1 File Permissions o oo o oooooooooo ee eee eee eee 152 9 4 2 Configuration Files 0vadd 08 srt 152 9 4 3 Universal Data Mover Server User ID 20000000 152 9 4 4 User Authentication annann aana 153 9 4 5 Universal Access Control List anaana aaae 153 UACL ENIES oc 64 hace be nee aed Gea ERRARE aes aaa aa 153 udm user 3207 Confidential amp Proprietary 17 Contents WACL Examples icc ore eg la ge alee koe ay eek weld dace bares 154 Chapter 10 Universal Data Mover Server for OS 400 0 0 0 cece ees 155 10 1 OVENVIGW gece dis dine ida etd wrth ad hand adie a aed eared ean 155 10 2 Component Definition 0 0 0 eee 156 10 3 C nfig rati n era milf eth Ge Sod serie Mo deans KEE ae KSA a a EO oc ik aio 157 10 3 1 Configuration File 2acccdicrcidababda
124. and The data command can be used to define in stream data elements that can be passed as input for other commands such as the exec command The syntax for the data command is as follows data NAME print NAME resolve a11 defined no end ENDSEQUENCE DATA end ENDSEQUENCE 11 11 1 Creating an In Stream Data Element An in stream data element has four parts 1 Name 2 Optional variable resolution method 3 In stream data itself 4 End of data marker or end sequence The name uniquely identifies the data element and is used to refer to the data element The optional variable resolution method tells UDM whether to resolve variables wrapped in the sequence when the data element is referred to e If the resolution method is a11 default all variables are resolved and an error is issued if the variable is not defined in UDM e Ifthe resolution method is defined only references to variables defined in UDM are resolved and all other references are left as is in the data element e If the resolution method is no UDM does not try to resolve any variable references in the data when the data element is used The data portion of the data element is the actual data that will be used by the command that is referencing that data element Note The data is used as entered including any leading spaces or tabs no trimming is done The end of data marker or end sequence marks the end of the data By default this is simply
125. are not hierarchical Table 12 1 below lists CFS terminology for hierarchical file systems like UNIX Windows and HFS path Name of a file which may or may not include a directory A path is either an absolute path or a relative path Examples home homer phone txt e phone txt e homer phone txt absolute path Full path name of a file starting at the root directory network point or drive letter Examples home homer phone txt FILESERVER homer phone txt e C program filesiphone txt relative path Path name of a file that is relative to the current working directory Examples e phone txt e phone txt phone txt myfiles phone txt homer phone txt udm user 3207 Confidential amp Proprietary 215 UDM Common File System UDM Transfer Operations file Name of a file All files are located in a directory The name does not include a directory name Examples e phone txt e editor exe directory Name of a directory The name does not include a file It can be absolute or relative Examples home homer e C program files current directory Every program that runs on a hierarchical file system has a current directory also known as the working directory For most programs this is the directory from which it was invoked Table 12 1 CFS Terminology for Hierarchical File Systems udm user 3207 Confidential amp Pro
126. as a fully qualified name enclosed in apostrophes or as a relative name composed of one or more qualifiers concatenated to the current working directory value to form a fully qualified name The qualifiers and which are used in the cd command do not have any special meaning in a file specification They most likely will result in an invalid fully qualified data set name Included in the sequential category are generation data sets A data set is considered a generation data set if it had a generation data group catalog entry and the data set name includes a generation relative number for example 0 1 1 Table 13 3 below provides some examples of copy command file specifications for sequential data sets The examples assume a UDM logical name of SRV TOM123 copy srv data TOM123 DATA TOM123 copy srv appl jcl TOM123 APP1 JCL TOM123 copy srv GAM789 APP2 DATA GAM789 APP2 DATA Table 13 3 copy Command File Specifications for Sequential Data Sets Note In the case of a destination file specification if no destination file is specified and the attribute usefqn is set to no default for the source dsn transfer server only the part of the data set name matching the source mask in the copy operation is used as the destination file name If the attribute userfqn is set to yes on the source the destination data set name is composed of the source current working directory concatenated with the source file name
127. ask For any of these three types the value command is the remote command to be executed See the Universal Command 3 2 0 User Guide for more information about command types UDM must authenticate a user on the remote machine in order to execute a command e Ifa logical name is specified in the first parameter the user and pwd values are inherited from the same options specified in the open command for that logical name These inherited values can be overridden by specifying them explicitly in the exec command Ifa hostname is specified in the first parameter the user and pwd values must be specified explicitly in the exec command The port and codepage values are inherited from the UDM Manager s configuration file unless overridden explicitly in the call to the exec command e port specifies which port the Universal Broker is listening on for the remote machine e codepage specifies to which codepage the output of the remote command is translated udm user 3207 Confidential amp Proprietary 280 exec Command Remote Execution The user pwd port and codepage parameters can be stored in an external file instead of being specified explicitly in the exec command e Ifa plain text file is used use the file parameter to specify the name of this file Ifthe file was encrypted with Universal Encrypt use the xfile parameter to specify the name of this file If an encryption key other than the Universal Encrypt defau
128. at have elapsed since the last second You only can reference _time in your scripts it cannot be set using the set command You can use the _ time variable in combination with the print command to display custom time information in UDM s transaction log print msg It is now _time hh _time mm Produces the following output Today is now 23 31 Stoneman s Tip _uuid The _uuid built in variable when referenced generates a UUID For example echo _uuid 1732fd12 7b07 4791 a28a 4cf0776db4f7 udm user 3207 Confidential amp Proprietary 190 UDM Variables UDM Scripting Language 11 6 9 Logical Name Built In Variables When a session is established built in variables are created for each transfer server and contain information about each server The names of these variables are based on the logical name of the transfer server preceded by an underscore If the primary transfer server is not specified implying a two party transfer session its built in variable will have the name _1ocal These logical name built in variables persist only for the duration of the session They have three attributes 1 host contains the host name of the transfer server 2 port holds the port used to connect to the transfer server over 3 user contains the userid used to sign into the transfer server Examples The following shows how these built in variables can be used open remote mymachine port 10000 u
129. ata Mover 3 2 0 Reference Guide UDM_ACCESS Allows or denies access to Universal Data Mover Server services UDM_MGR_ACCESS Allows or denies access based on the host name and or user of the Manager trying to initiate a UDM session Table 7 3 UDM Server for z OS UACL Entries udm user 3207 Confidential amp Proprietary 138 Security Universal Data Mover Server for z OS UACL Examples The following set of rules permit services for the subnet 10 20 30 and denies all other connections udm_access 10 20 30 allow auth udm_access ALL deny auth The following set of rules effectively permit connections from any host but has limited access from host 10 20 30 40 to user TS1004 on that host No host can execute commands as local user root User TS1004 on host 10 20 30 40 can execute commands as local user tsup1004 without providing the password Users TS1004 from host 10 20 30 40 can execute commands as any local user by providing the local user password udm_access 10 20 30 40 TS1004 tsup1004 allow noauth udm_access 10 20 30 40 TS1004 allow auth udm_access 10 20 30 40 deny auth udm_access ALL root deny auth udm user 3207 Confidential amp Proprietary 139 Chapter 8 Universal Data Mover Server for Windows 8 1 Overview This chapter provides the following information on the Universal Data Mover UDM Server specific to the Windows operating system e Compo
130. ata004 pr e data005 pr The result of the copy operation will create the following members in Data Physical File APPDATA e DATA001 e DATA002 e DATA003 LIB file system set _echo yes _halton warn open unix sol9 user top098 pwd p100m cd unix opt app data mode type text attrib local truncext yes copy unix txt 1ocal MYLIB APPDATA quit ND WwW BP UU NN pp udm user 3207 Confidential amp Proprietary 305 UDM Manager for OS 400 Examples Examples A 4 4 Copy a File to a New OS 400 Data Physical File This example copies in text mode a file from a remote UNIX system to a data physical file on OS 400 The Data Physical File does not exist on OS 400 UDM is instructed to create it The file type created defaults to a Data Physical File The Data Physical File is allocated based on the local UDM allocation attributes UDM provides default attributes that can be changed to meet local requirements The UDM defaults as delivered create a Data Physical File with a logical record length of 92 and maximum members of 1 This example changes the record length to 80 and the maximum members to unlimited nomax in order to demonstrate how to set allocation attributes LIB file system set _echo yes _halton warn open unix sol9 user top098 pwd p100m cd unix opt app data mode type text attrib local rcdlen 80 maxmbrs nomax copy unix datal0 txt local MYLIB APPDATA DAILY quit NOM PWN pp Alm
131. ates to false The general format of an if statement when an else statement is used with it is if expression else end In this if statement the parameter for the statement is an expression If the expression evaluates to a value that is not equal to zero the positive branch is taken otherwise the negative else branch is taken if one exists Examples if lt _rc EQ 0 gt echo Everything worked okay else echo Something went wrong end if myvar exists EQ yes gt echo The variable myvar has been defined end Note The previous style of UDM if statements shown in the following example still is valid if lt _lastrc GE 8 gt print msg The last command was not successful else print msg The last command was successful end udm user 3207 Confidential amp Proprietary 197 if Statement UDM Scripting Language 11 7 3 Nested Conditionals For complex and powerful operations if statements can be nested inside of each other For example copy src filename if _lastrc EQ 0 delete src filename if _lastrc NE 0 print msg The source file could not be deleted end else print msg The copy operation failed end print msg The operation completed with a return code of _rc Indenting lines underneath conditionals by putting spaces at the front of them although not necessary provides a visual cue that those lines are to be executed due to the ev
132. ation files are located The UACL file syntax is the same as all other Universal Products for OS 400 configuration files See Section 2 2 6 Configuration File Syntax for details udm user 3207 Confidential amp Proprietary 76 Universal Access Control List Features 2 8 2 UACL Entries UACL entries are composed of two parts type and rule e Type identifies the Universal Products component for which the rule applies For example the Universal Broker product utilizes UACL rules of type ubroker_access Rule defines the client s identity and the client s request for which the entry pertains and the security attributes it enforces UACL configuration file syntax is the same as all other configuration files where the configuration file keyword corresponds to the UACL type part and the configuration file value corresponds to the UACL rule part The entire rule part of the UACL entry must be enclosed in quotation characters not just a sub field of the rule if a space or tab is part of the value The correct syntax would be as follows ucmd_request prod host name MVS USER user cmd DSPLIB QGPL al low auth For each client that connects and sends a request Broker and Server components search UACL entries to find the best match for the client identity and the client request Entries are searched in the order they are listed The first entry found stops the search Note There is no limit to the number of UACL entries tha
133. b Nesting Recursion of Subroutines UDM allows subroutine nesting one subroutine calls another subroutine and recursion a subroutine calls itself For example the following illustrates subroutine nesting subroutine a echo Beginning subroutine A callsub b echo Ending subroutine A endsub subroutine b echo Beginning subroutine B echo Ending subroutine B endsub callsub a udm user 3207 Confidential amp Proprietary 176 Subroutines UDM Scripting Language 11 5 2 Example subroutine loop_increment echo inside loop_increment LOOP set LOOP lt LOOP 1 gt endsub echo Starting Loop set LOOP 0 if lt LOOP LT 1 gt callsub loop_increment end if lt LOOP LT 2 gt callsub loop_increment end if lt LOOP EQ 2 gt callsub loop_increment end echo Final Value of LOOP LOOP Output Starting Loop inside loop_increment 0 inside loop_increment 1 inside loop_increment 2 Final Value of LOOP 3 udm user 3207 Confidential amp Proprietary 177 UDM Variables UDM Scripting Language 11 6 UDM Variables Variables are integral data storage objects in the Universal Scripting Engine This section provides information on e Variable types e Variable scope e Variable reference e Variable attributes 11 6 1 Variable Types There are two types of variables 1 Script 2 Global user defined and built in Variable Names There are no restricti
134. be accepted as valid data but the information it represents is now erroneous Data integrity must be protected from errors in transmission and malicious users Data integrity checks insures that what was sent is exactly what is received by the recipient Without integrity checks there is no guarantee Encryption algorithms are used to encrypt data into an unreadable format The encryption process is computationally expensive There are a variety of encryption algorithms some of which perform better than others Some algorithms offer a higher level of security than others Typically the higher level of security requires more computational resources Message digest algorithms are used to produce a Message Authentication Code MAC that uniquely identifies a block of data The sender computes a MAC for the data being sent based on a shared secret key the sender and receiver hold The sender sends the data and the MAC to the receiver The receiver computes a new MAC for the received data based on the shared secret key If the two MAC s are the same data integrity is maintained else the data is rejected as it has been modified Message digest algorithms are often referred to as MAC s and can be used synonymously in most contexts The SSL standard defines a set of encryption and message digest algorithms referred to cipher suites that insure data privacy and data integrity Cipher suites pair encryption algorithms with appropriate message digest algorit
135. be enclosed in apostrophes There are three possible sequential ddname destination file specifications 1 Name of the ddname defined by a JCL DD statement 2 Current working directory value which is set to the name of a ddname and no destination file specification Source file specification if the current working directory value set to blanks and no destination file specification is provided wo There is one possible sequential ddname source file specification 1 Name of the ddname defined by a JCL DD statement Table 13 6 provides some examples of copy command destination file specifications for sequential ddnames The examples assume that ddname APPDD 1 is defined with a JCL DD statement and a UDM logical name of SRV copy local app1 txt srv appddl APPDD1 APPDD1 copy local appl txt APPDD1 copy local appl APP1 Table 13 6 copy Command Destination File Specifications for Sequential ddnames Table 13 7 provides an example of copy command source file specifications for sequential ddnames The examples assume that ddname APPDD 1 is defined with a JCL DD statement and a UDM logical name of SRV copy srv appdd1 local appl txt APPDD1 Table 13 7 copy Command Source File Specification for Sequential ddnames Note The createop attribute values REPLACE and NEW are not applicable to the sequential ddname file system udm user 3207 Confidential amp Proprietary 248 UDM Commands under z OS Transfer
136. c operator AND Results in a value of 1 if both the left value and right value are not 0 otherwise it results in 0 OR Results in a value of 1 if either the left value or the right value are not 0 otherwise it results in 0 XOR Results in a value of 1 if either the left or the right values are not 0 but not both If both the left and right values are 0 then the result of the XOR operator is 0 NOT Unlike all of the operators the NOT operator has only one operand that appears to the right of the NOT operator This operation evaluates to one if the operand is zero and zero if the operand is non zero Result is the sum of the left and right values Result is subtracting the right value from the left value Result is the product of the left and right values Result is the left value divided by the right value Assuming integer only math the remainder is discarded Result is the remainder of the left value divided by the right value Table 11 2 UDM Command Expressions Operators udm user 3207 Confidential amp Proprietary 169 UDM Command Format UDM Scripting Language 11 3 4 Strings in Expressions You can use strings as operators in EQ and NE expressions However to avoid ambiguity strings must be quoted explicitly even if they are contained in a variable reference otherwise an error is generated The following expression correctly compares strings
137. categories Success 0 none All commands completed successfully Warning 4 warn Non critical error in operation Error 8 error UDM command failed to execute because it was e inappropriately issued for example a copy command was issued before a transfer session had been established Malformed that is grammatically correct but either e Missing required parameters e Containing invalid parameters Fatal 16 fatal Fatal error has occurred UDM cannot continue and must exit A fatal error is one that prevents UDM from running e Failure to allocate memory e Failure to initialize portions of the UDM application e Parser errors grammatically incorrect scripting language Table 16 1 UDM Return Codes Each return code category has an integer value and a convenient value Processed commands return only integers as return code values The convenient values can be used when setting return codes in the _rc and or _hal ton variables via the set command see Section 16 3 1 Return Codes in set Set Command udm user 3207 Confidential amp Proprietary 285 Return Codes in UDM Built In Variables Return Code Processing 16 2 Return Codes in UDM Built In Variables During processing UDM keeps track of the return codes from processed commands _lastrc Variable The _lastre built in variable holds the return code of the last command issued It also has a special attribute message that contains a hum
138. cation States ORPHANED udm user 3207 Confidential amp Proprietary 8 Summary of Changes PENDING e RESTARTING Added Chapter 2 Features including e Section 2 4 Universal Configuration Manager e Section 2 6 2 Open Retry e Section 2 7 z OS CANCEL Command Support e Section 2 8 3 Types of UACL Rules e Section 2 8 4 Proxy Certificates Added the following UDM Manager configuration options for the z OS Windows and UNIX operating systems ACTIVITY MONITORING BIF_DIRECTORY UNIX only e CA_CERTIFICATES e CERTIFICATE e CERTIFICATE _REVOCATION_LIST e COMMENT EVENT_GENERATION e OPEN_RETRY_COUNT OPEN_RETRY_INTERVAL e PLF_DIRECTORY UNIX only e PRIVATE_KEY e PRIVATE_KEY_PASSWORD e PROXY_CERTIFICATES e SAF_KEY_RING z OS only e SAF_KEY_RING_LABEL z OS only e SERVER_STOP_CONDITIONS z OS only e SSL_IMPLEMENTATION z OS only e SYSTEM_ID z OS only e UCMD_PATH UNIX and Windows only Added UDM_MGR_ACCESS UACL entry for the z OS Windows and UNIX operating systems Added the following UDM Server configuration options for the z OS Windows and UNIX operating systems ACTIVITY MONITORING EVENT _GENERATION TMP_DIRECTORY Added Nesting Recursion of Subroutines in Section 11 5 Subroutines of Chapter 11 UDM Scripting Language Changed the _result variable to an attribute of the _lastrc variable in Section 11 6 8 Built in Variables of Chapter 11 UDM Scripting Language Ad
139. cation for whether or not to merge standard out and standard error output streams from a remote command to the UDM transaction log MESSAGE_LANGUAGE Universal Message Catalog UMC file used to write messages MESSAGE_LEVEL Level of messages to write MODE_TYPE Default transfer mode type for UDM sessions NETWORK_DELAY Expected network latency NETWORK_FAULT_TOLERANT Specification for whether or not UDM transfer sessions are network fault tolerant by default OPEN_RETRY Level of fault tolerance for the open command OPEN_RETRY_COUNT Maximum number of attempts that will be made to establish a session by the open command OPEN_RETRY_INTERVAL Number of seconds that UDM will wait between each open retry attempt OUTBOUND_IP Host or IP address that UDM binds to when initiating outgoing connections to another UDM server PRIVATE_KEY ddname of Manager s PEM formatted RSA private key PRIVATE_KEY_PWD Password for the Manager s PRIVATE_KEY PROXY_CERTIFICATES Specification for whether or not UDM will use proxy certificates in three party transfer sessions if a certificate is supplied to the UDM Manager RECONNECT_RETRY_COUNT Number of attempts the manager will make to re establish a transfer session when a network fault occurs RECONNECT_RETRY_INTERVAL Number of seconds that UDM will wait between each successive attempt to re establish a transfer session
140. cess ACL Figure 2 6 Universal Configuration Manager UDM Server udm user 3207 Confidential amp Proprietary 59 Network Data Transmission Features 2 5 Network Data Transmission Distributed systems such as Universal Data Mover communicate over data networks All Stonebranch products communicate using the TCP IP protocol The UDP protocol is not used for any product data communication over a network The Universal Products suite can utilize one of two network protocols 1 Secure Socket Layer version 3 SSLv3 provides the highest level of security available SSL is a widely used and accepted network protocol for distributed software applications that are required to address all aspects of secure data transfer on private and public networks 2 Universal Products version 2 UNVv2 legacy protocol is provided for backward compatibility with previous versions of Universal Products The following sections discuss each of the protocols In addition to the network protocol used to transmit data Universal Products application protocol is discussed as well 2 5 1 Secure Socket Layer Protocol Universal Products implement the SSL protocol using either e OpenSSL library IBM z OS System SSL library available on the z OS operating system The most recent SSL standard is version3 A subsequent version was produced changing the name to Transport Layer Security version 1 TLSv1 TLSv1 is the actual protocol used by Univers
141. cifications for Partitioned GONAMES adds 249 Table 13 9 copy Command Source File Specifications for Sequential ddnames 249 Chapter 14 Transfer Operations 0S 400 SpecifiC oooooooooororormomoo 253 Table 14 1 CCSID Mappings ccccccccccccnnncnnnnnnnnnnnennnennnennnnnnnnnnnnnennnnnnnnnnnnnnnennnnnnineninnns 262 Table 14 2 OS 400 Specific LIB File Attributes for Creating New Files 266 Table 14 3 0S 400 Specific HFS File Attributes for Creating New Files 266 Table 14 4 delete Command Forms with UDM under OS 400 oooccicccnccccnccnnicicicaninno 276 udm user 3207 Confidential amp Proprietary 28 List of Tables Table 14 5 rename Command Forms ccccsecesecccecceceeeecaeceaeccceceeeeeceseeeseeeeeseneeenens 278 Chapter 16 Return Code Processing cece eee eee eee eee eee 285 Table 16 1 UDM Return Codes ccooccnccnnccnnccnnccnncconcnoncconononcnnnnrnnnnnnnnnnnonnronarnnnennnccnncns 285 udm user 3207 Confidential amp Proprietary 29 Preface Document Structure This document is written using specific conventions for text formatting and according to a specific document structure in order to make it as useful as possible for the largest audience The following sections describe the document formatting conventions and organization Format Starting with the Universal Products 3 2 0 release the Universal Data Mover User Guide has been reformatted and re
142. command behavior when working with the LIB and HFS file systems 14 4 1 attrib Attribute Command UDM provides three attribute levels In order of precedence from lowest to highest they are 1 Default lowest priority 2 Source 3 Override highest priority When a user sets an attribute the override attribute level is being set Default attributes are those set by UDM at startup Source attributes are attributes that UDM obtains from the source file and uses for the destination file For example when transferring a file one OS 400 LIB location to another UDM reads the record length of the source file and uses the source file record length to create the destination file If the source file is on UNIX or in the HFS file system record length has no meaning and the source attribute is not set In addition to the standard UDM file attributes CREATEOP EOL LINELEN LINEOP PADLINE and TRUNCEXT OS 400 specific file attributes are required in order to create new files in the LIB and HFS file systems However not all attributes are required for all file types For information on which attributes can be used with each file type refer to OS 400 online documentation File Attributes The following file attributes tables Table 14 2 and Table 14 3 provides the following information about OS 400 specific file attributes and the file types for which they are required Name Name of the attribute to be used in the LIB file system D
143. 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 Universal Products installation library UNVPRD320 file UNVCONF and member UDM The configuration file name can be any valid file name It can be edited manually using an OS 400 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 See Section 2 2 1 Configuration Methods for details on Universal Products configuration methods udm user 3207 Confidential amp Proprietary 126 Usage Universal Data Mover Manager for OS 400 6 2 4 Configuration Options Table 6 1 below describes the configuration options used to execute UDM Manager for OS 400 Each Option Name is a link to detailed information about that configuration option in the Universal Data Mover 3 2 0 Reference Guide ACTIVITY_MONITORING Specification for whether or not product activity monitoring events are generated CA_CERTIFICA
144. compression methods e ZLIB method offers the highest compression ratios with highest CPU utilization HASP method offers the lowest compression ratios with lowest CPU utilization Note Control data is not compressed Compression options are available for application data only Secure The protocol is secure All control data exchanged between Universal Products components are encrypted with a unique session key and contain a MAC The encryption prevents anyone from analyzing the message data and attempting to circumvent product and customer policies Each session uses a different encryption key to prevent play back types of network attacks where messages captured from a previous session are replayed in a new session This applies to both network protocols SSL and UNVv2 The security features used in the control messages are not optional They cannot be turned off The security features are optional for application data sent over the network The data encryption options affect the application data being sent over the network Special fields such as passwords are always encrypted The encryption option cannot be turned off for such data udm user 3207 Confidential amp Proprietary 64 Network Data Transmission Features Extensible The message protocol used between the Universal Products components is extensible New message fields can be added with each new release without creating product component incompatibilities T
145. configured with Network Address Translation NAT systems between the client and the Broker that hides the client s IP address In addition to the client IP address Universal Products clients provide a user account name with which they are executing that is used to further refine the client s identity UACL entries are searched matching the client s IP address and user account to each entry until a match is found Table 2 6 below defined possible matching criteria for IP address and user account client identification HOST Matches the TCP IP address of the remote user The HOST value has the following syntax Dotted numeric form of an IP address For example 10 20 30 40 Dotted numeric prefix of the IP addresses For example 10 20 30 matches all IP addresses starting with 10 20 30 The last dot is required Anet mask expression For example 131 155 72 0 255 255 254 0 matches IP address range 131 155 72 0 through 131 155 73 255 The mask and the host value are AND ed together The result must match net Note Contact your network administrator for calculation of the correct net mask expression Host name for an IP address For example sysa abc com Host name suffix for a range of IP addresses For example abc com matches all host names ending with abc com such as sysa abc com The first dot is required A value of ALL matches all IP addresses The value must be uppercase REMOTE_USER
146. ction 4 Configuring UDM under z OS e 6 1 Invoking the UDM Manager under Windows and UNIX of Section 6 UDM Manager Invocation e 6 2 Invoking the UDM Manager Under z OS of Section 6 UDM Manager Invocation Added default value to USER_SECURITY in Section 3 2 2 2 Configuration Options Reference Added an If statement to the sample UDM script in Section 7 2 UDM Command Format e Redefined Section 7 3 Script Files and renamed and redefined Sections 7 3 1 Invoking UDM in Batch with Commands from a Script File and 7 3 2 Invoking UDM Interactively with Commands from a Script File Added LIB as a value for the filesys command and Indicated availability of filesys value of DD in the following sections e Section 8 2 2 Changing the Current File System of Section 8 UDM Transfer Operations e Section 13 13 filesys of Section 13 Command Reference Added information about EOL attribute in HFS file system in Section 8 6 3 End of Line Sequence Added note in Section 8 7 6 Transaction Oriented Transfers about non support in UDM OS 400 LIB file system Added Syntax Description and Parameters for Section 13 11 execsap in Section 13 Command Reference e Added default value for logical name parameter in Section 13 13 filesys e Modified example in Section 14 1 5 Copy a Set of Files to a New z OS Partitioned Data Set Added Section 14 3 OS 400 Examples to Section 14 Samples Changes for UDM Release 3 1 1 0 April 30 2005 Ad
147. current file system on a server is a simple matter of executing the filesys command which has the following format filesys logical_name dd dsn hfs 1ib In this format the logical name refers to the logical name of the transfer server to send the filesys command An optional file system for example z OS s DD DSN or HFS can be specified after the logical name to change the current file system on that server Sending a filesys command with just a logical name returns the current file system of the server Note A filesys value of dd is available only on z OS manager for two party transfer udm user 3207 Confidential amp Proprietary 214 UDM Common File System UDM Transfer Operations 12 4 UDM Common File System UDM provides a set of consistent capabilities for a diverse set of file systems on many different operating systems UDM commands attempt to behave in a consistent and predictable manner regardless of the file system or operating system on which UDM is running In order to do so UDM behavior is based on a Common File System CFS model CFS is biased towards the hierarchical file systems found on UNIX Windows or HFS z OS or OS 400 CFS terminology and commands then are applied to each of the UDM supported file systems on different operating systems 12 4 1 Common File System Terminology UDM attempts to make consist use of file system terminology so that it can be applied consistently to file systems that
148. cuting the following forfiles local mydir file print msg _file end Will result in the following output filet file2 The forfiles file specification can contain wildcards for any UDM files system Under z OS however the wildcards only can be used to reference a member of a PDS or PDS E and not a data set name Stoneman s Tip udm user 3207 Confidential amp Proprietary 205 forfiles Statement UDM Scripting Language 11 10 3 Breaking Out Using the break Command The break command is a powerful command that can be issued from inside of a forfiles loop It causes UDM to stop iterating through the forfiles loop and resume execution at the command immediately following the end statement marking the end of the loop One use for the forfiles statement is to try and copy a series of files deleting the source file if the copy operation was successful The following is a sample that accomplishes this task exiting from the loop if a file cannot be copied or if after copying a file it cannot be deleted forfiles local copy local _file Stoneman s Tip if Clastrc NE O print msg Could not copy _path break end delete local _fi le if Clastrc NE O print msg Could not delete _path break end end udm user 3207 Confidential amp Proprietary 206 Creating In Stream Data with the data Command UDM Scripting Language 11 11 Creating In Stream Data with the data Comm
149. d be DSTLIB YOURFILE If the destination file is to be a physical file the absolute path would be DSTLIB YOURFILE MYFILE Example COPY SRC MYFILE DST YOURFILE DSTLIB YOURFILE MYFILE will be used as the destination name if the destination file type is a physical file and DSTLIB YOURFILE will be used if the destination file type is a save file 3 If the destination file specification contains only a file portion and an empty member portion the result is exactly the same as when the file specification contains only file portion Example COPY SRC MYFILE DST YOURFILE DSTLIB YOURFILE MYFILE will be used as the destination name if the destination file type is a physical file udm user 3207 Confidential amp Proprietary 274 Command Reference Transfer Operations OS 400 Specific If the destination file specification contains only file and member portions the resulting absolute path is DSTLIB YOURFILE YOURMBR if a physical file is wanted Example COPY SRC MYFILE DST YOURFILE YOURMBR DSTLIB YOURFILE YOURMBR will be used as the destination name if the destination file type is a physical file If the destination file specification contains only a library portion that library is used instead of the current library In this case an absolute path of YOURLIB MYFILE is used if a save file is wanted If a physical file is wanted an absolute path of YOURLIB MYFILE MYFILE is used Example COPY SRC MYFILE DS
150. d into script2 script2 udm print msg The value of varl is varl print msg The value of var2 is var2 print msg The value of var3 is var3 call script3 udm varl passed into script3 script3 udm print msg The value of varl is varl print msg The value of var2 is var2 print msg The value of var3 is var3 Running UDM and calling script1 udm produces the following results Processing script scriptl1 udm The value of varl is a global variable The value of var2 is a global variable The value of var3 is a global variable Processing script script2 udm The value of varl is passed into script2 The value of var2 is passed into script2 The value of var3 is a global variable Processing script script3 udm The value of varl is passed into script3 The value of var2 is passed into script2 The value of var3 is a global variable Finished processing script script3 udm Finished processing script script2 udm Finished processing script scriptl udm udm user 3207 Confidential amp Proprietary 181 UDM Variables UDM Scripting Language 11 6 6 User Defined Variables User defined variables are defined using the set command They can have any name except that they cannot begin with an underscore _ character and any value A user defined variable can be called within any script or in an interactive session set variable_name variable_value The following example creates a user defined variable call
151. d no permissions to the file s group and everyone else attrib local mode 600 udm user 3207 Confidential amp Proprietary 230 Copying Files with UDM UDM Transfer Operations Defaults By default the mode attribute is not set The default mode of a newly created file by UDM is dependent upon either User s umask attribute Mode of the source file in a UDM transfer The latter case comes into play if both the source and destination instances of UDM are e Version 3 2 or greater Running under some form of the UNIX operating system or its derivatives such as Linux The umask attribute is used in specifying the mode if a UDM version prior to 3 2 0 is involved in the transfer Version 3 2 0 and greater versions can be changed to behave this way as well by setting the mode attribute to 0 on the destination side of the transfer For example attrib dest_logical_name mode 0 12 8 7 Destination umask Under UNIX platforms and the HFS file system under z OS USS the umask attribute can be used to define the file s permissions in accordance to UNIX standards see Defaults in Section 12 8 6 File Permission Attribute above See Table 7 2 Common File System Attributes in the Universal Data Mover 3 2 0 Reference Guide for a detailed description of umask 12 8 8 Transaction Oriented Transfers A transaction oriented transfer is a file transfer where the destination file is written using a temporary filename Once t
152. data set is dynamically allocated based on the local UDM dynamic allocation attributes UDM provides default attributes that can be changed to meet local requirements The UDM defaults as they are delivered create a sequential variable block record data set with a logical record length of 1024 The sample below changes the record length to 256 in order to demonstrate how to set dynamic allocation attributes A DD file system sample is not provided since creating a new data set with JCL is the same in UDM as it is in any batch application There are no UDM specific requirements DSN file system S1 EXEC UDMPRC UNVSCR DD 1 set _echo yes _halton warn open unix sol9 user top098 pwd p100m cd unix opt app data mode type text attrib local Trecl 256 copy datal0 txt local app data daily quit NN OW PWN Note All file names in the UNIX system must be within the eight character range to be transferred successfully Almost all data set allocation attributes can be specified as UDM attributes providing you with the ability to dynamically allocate any supported data set Care should be taken that conflicting allocation attributes are not specified The results of the allocation should be check to verify they meet your intentions Although UDM checks attribute values some values are provided by the system from sources that UDM cannot verify and can result in invalid or unintentional attribute combinations udm us
153. ded information about the EXEC command e Added information about the EXECSAP command udm user 3207 Confidential amp Proprietary 11 Summary of Changes Added information about support for wildcards in data set names for the DSN file system Added information about the DATA command for in stream data Added the RENAME command Added information about source allocation attributes being used in MVS to MVS copy operations Added information about the _DATE and _ TIME built in variables Added documentation of the on the fly logical name built in variables Documentation for the new TYPE variable attribute for the _FILE built in variable Updated information on configuration options Added information about the REPORT command Added information about transfer operation auditing Added information about monitoring transfer operation progress Changes for UDM Release 3 1 0 October 31 2004 Removed section on the control session cipher list configuration as this information now comes from the version 3 1 of the Universal Broker Added information about keep alive support Added information about console idle timeout Added information about network fault tolerance support in UDM Added information on nested script parameter scope Added z OS UDM Server Added commands break copydir and delete Added scripting features of IF logic and forfiles Added section on available built in variables and reserved variable
154. ded information to Chapter 11 UDM Scripting Language Added and modified information in Chapter 16 Return Code Processing Added Section 12 8 6 File Permission Attribute Added Section 13 4 Copying Load Modules udm user 3207 Confidential amp Proprietary 9 Summary of Changes Consolidated UDM Manager Configuration chapters and UDM Manager Invocation chapters Changes for Universal Data Mover 3 1 1 User Guide udm user 31111 February 28 2007 Added customer support telephone number for Europe to Appendix B Customer Support Universal Data Mover 3 1 1 7 Added svropt option to the following sections Section 11 1 exec Command in Section 11 Remote Execution e Section 13 10 exec in Section 13 Command Reference Added paragraph about HSM data migration to Section 9 1 4 Allocation of Section 9 z OS Specific Transfer Operations Added ASPDEV value for ASPNUM attribute in Table 10 OS 400 Specific LIB File Attributes for Creating New Files in Section 10 2 1 attrib Attribute Command of Section 10 OS 400 Specific Transfer Operations Updated network fault tolerance information for the NETWORK_FAULT_TOLERANT option in the following sections e Section 3 1 Configuring the UDM Manager of Section 3 Configuring UDM under UNIX Section 4 1 Configuring UDM Manager of Section 4 Configuring UDM under z OS Section 5 1 Configuring UDM Manager of Section 5 Configuring UDM under OS 400 e Section 6 1 Invoking UDM Manager unde
155. directory library Example DATA NAMES A name without a library The name is relative to the current directory library Example BACKUP file Same a path It may be relative or absolute Same as path It may be relative or absolute directory N A N A current directory Name of the current library in which you are working Example e MYLIB Name of the current library in which you are working Example e MYLIB Table 12 4 CFS Terminology Associated with LIB File Types udm user 3207 Confidential amp Proprietary 220 Transfer Modes and Attributes UDM Transfer Operations 12 7 Transfer Modes and Attributes 12 7 1 Setting the Transfer Type There are two basic types of file transfers Binary Binary transfers move the data as it is without any translation e Text Text transfers translate the data from the source server s code page to the destination server s code page as it is transferred from one server to another The default transfer type for UDM is binary To set the transfer type use the mode command To set up UDM for text transfers issue the following command mode type text e To set up UDM for binary transfers issue the following command mode type binary Issuing the mode command by itself displays the current transfer mode The mode command also can be used tell UDM to trim trailing spaces at the end of each line or
156. dm user 3207 Confidential amp Proprietary 308 UDM Manager for OS 400 Examples Examples A 4 7 Copy Different Types of OS 400 Files using forfiles and _file type Physical files are considered directories in UDM because they contain 1 member Save files are considered files because they do not contain any members The forfiles statement and the variable _file type allow you to do a wildcard copy on both save and physical files in the LIB file system This example copies a mix of files Save and Physical from an OS 400 system in a single operation using the forfiles statement and the _file type variable attribute forfiles src MYLIB if C_file type EQ directory copy src _path else copy src _path end end udm user 3207 Confidential amp Proprietary 309 UDM Manager for OS 400 Examples Examples A 4 8 Invoke a Script from a Batch Job To invoke a script included as an inline file in a database job the call must specify FIRST as the database member name The following example illustrates both e Invocation of an inline script CALLME using the STRUDM command from a database job e Invocation of an inline script CALL1 using the CALL command from a database job LIB file system BCHJOB JOB testcal1 ENDSEV 10 OUTQ mytest UDMOUTQ LOGCLPGM YES LOG 2 20 SECLVL MSGQ USRPRF DATA FILECCALL1 ENDCHARCENDDATAFILE print msg I made it to call1 an inlin
157. dm user 3207 Confidential amp Proprietary 155 Component Definition Universal Data Mover Server for OS 400 10 2 Component Definition All Universal Products 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 3 2 0 User Guide The syntax of a component definition file is the same as a configuration file See Section 2 2 6 Configuration File Syntax for detailed syntax information The UDM Server for OS 400 component definition is located in the component definition directory of the Universal Broker Table 10 1 below identifies all of the options that comprise the UDM Server for OS 400 component definition Each Option Name is a link to detailed information about that component definition option in the Universal Data Mover 3 2 0 Reference Guide AUTOMATICALLY_START Specification for whether or not UDM Server starts automatically when Universal Broker is started COMPONENT_NAME Name by which the clients know the UDM Server CONFIGURATION_FILE Full path name of the UDM Server configuration file RUNNING_MAXIMUM Maximum number of UDM Servers that can run simultaneously START_COMMAND Full path name of the UDM Server program WORKING_DIRECTORY Full path name of the UDM Server working directory
158. e MSGLEVEL ftrace audit infolwarn errorj fyes noj NETWORKFT yes no FRAMEINTC number OPENRETRY yes no count interval OUTBOUNDIP host PORT port PROXYCERTCoption RCVBUFSIZE s7ze RETRYCNT number RETRYINT seconds SNDBUFSIZE s7ze TRCLINES number TRCTBL size error always never CACERTSCF77e 17b Y CACERTSMBR member CERTCF71e 1ib CERTMBR member PVTKEYFCf77e 776 PVTKEYFMBR member PVTKEYPWD password CRLFILE file lib CRLMBR member COMMENT user defined string STRUDM VERSION yes no Figure 6 1 UDM Manager for OS 400 Command Line Syntax udm user 3207 Confidential amp Proprietary 129 Examples of UDM Manager for OS 400 Universal Data Mover Manager for OS 400 6 3 Examples of UDM Manager for OS 400 Appendix A Examples provides operating system specific examples that demonstrate the use of Universal Data Mover Included in this appendix are the following examples that demonstrate the use of Universal Data Mover Manager in a two party mode between OS 400 and UNIX e Copy a File to an Existing OS 400 File e Copy an OS 400 Data Physical File to a File e Copy a Set of Files to an Existing Data Physical File Copy a File to a New OS 400 Data Physical File e Copy a File to a New OS 400 Source Physical File e Copy a Set of Files to a New Data Physical File on OS 400 e Copy Different Types of OS 400
159. e ACTIVITY_MONITORING Specification for whether or not product activity monitoring events are generated ALLOC_ABNORMAL_DISP ALLOC_BLKSIZE Abnormal disposition of a data set being allocated Block size used for newly allocated data sets ALLOC_DATACLAS SMS data class used for newly allocated data sets ALLOC_DIR_BLOCKS Number of directory blocks for newly allocated partitioned data sets ALLOC_DSORG Data set organization used for newly allocated data sets ALLOC_INPUT_STATUS Status of data sets being allocated for input ALLOC_LRECL Logical record length used for newly allocated data sets ALLOC_MGMTCLAS SMS management class used for newly allocated data sets ALLOC_NORMAL_DISP Normal disposition of a data set being allocated ALLOC_OUTPUT_STATUS Status of existing data sets being allocated for output ALLOC_PRIM_SPACE Primary space allocation used for newly allocated data sets ALLOC_RECFM Record format used for newly allocated data sets ALLOC_SEC_SPACE Secondary space allocation used for newly allocated data sets ALLOC_SPACE_UNIT Space unit in which space is allocated for newly allocated data sets ALLOC_STORCLAS SMS storage class used for newly allocated data sets ALLOC_UNIT Unit used for newly allocated data sets ALLOC_VOLSER Volume serial number used for newly allocated data sets CA_CERTIFICATES File n
160. e e Pre defined values such as yes and no are not case sensitive Each keyword value pair must be on one line Characters after the value are ignored Newline characters are not permitted in a value Values can be continued from one line to the next either by ending the line with a e Plus character to remove all intervening spaces e Minus character to preserve all intervening spaces between the end of the line being continued and the beginning of the continuing line Ensure that the line continuation character is the last character on a line Comment lines start with a hash character Blank lines are ignored Note If an option is specified more than once in a configuration file the last option specified is used udm user 3207 Confidential amp Proprietary 47 Remote Configuration Features 2 3 Remote Configuration Universal Products can be configured remotely by Universal Enterprise Controller using the Universal Management Console UMC client application UMC instructs the Universal Broker of a remote Universal Agent to modify the configurations of the Universal Products components managed by that Broker Universal Broker supports remote configuration in either of two modes 1 Unmanaged Mode 2 Managed Mode 2 3 1 Unmanaged Mode Unmanaged mode is the default mode of operations for Universal Broker It allows a Universal Broker and the Universal Products managed by that Universal B
161. e examples of copy command destination file specifications for partitioned ddnames The examples assume that ddname APPDDY1 is defined with a JCL DD statement and a UDM logical name of SRV copy local app1 txt srv appddl datal APPDD1 DATA1 APPDD1 copy local app1 txt srv datal APPDD1 DATA1 APPDD1 copy local appl APPDD1 APP1 Table 13 8 copy Command Destination File Specifications for Partitioned ddnames Table 13 9 provides an example of copy command source file specifications for sequential ddnames The examples assume that ddname APPDD 1 is defined with a JCL DD statement and a UDM logical name of SRV copy srv appddi datal local appl1 txt APPDD1 DATA1 APPDD1 copy srv datal local appl txt APPDD1 DATA1 Table 13 9 copy Command Source File Specifications for Sequential ddnames Note The createop attribute values REPLACE and NEW are applicable to members of a partitioned ddname udm user 3207 Confidential amp Proprietary 249 Copying Load Modules Transfer Operations z OS Specific 13 4 Copying Load Modules UDM for z OS provides the ability to copy load modules Note Version 3 2 0 or greater of UDM must be used on both the source and destination sides of the transfer operation for a load module to be properly copied and usable The syntax for copying load modules is the same as any copy operation involving PDS Es However there are some differences in how the copy operation takes place
162. e file ENDDATAFILE DATA FILECCALLME ENDCHARCENDDATAFILE OPEN S AS400V5 USER qatest PWD PORT 4311 CALL CALL1 FIRST CLOSE ENDDATAFILE STRUDM SCRFILE CALLME ENDBCHJOB udm user 3207 Confidential amp Proprietary 310 Appendix B Customer Support Stonebranch Inc provides customer support via telephone and e mail for Universal Data Mover and all Universal Products TELEPHONE E MAIL Customer support via telephone is available 24 hours per day 7 days per week North America 1 678 366 7887 extension 6 1 877 366 7887 extension 6 toll free Europe 49 0 700 5566 7887 All Locations support stonebranch com Customer support contact via e mail also can be made via the Stonebranch website www stonebranch com udm user 3207 Confidential amp Proprietary 311 sT mebrancA 950 North Point Parkway Suite 200 Alpharetta Georgia 30005 U S A
163. e host name somentmachine with the logical name machine2 An alternate method of establishing a two party transfer is simply to give the secondary server as a parameter to the open command open machine2 somentmachine In this example a two party transfer session is implied In such cases the logical name of the UDM Manager primary server side of the transfer session always will be local udm user 3207 Confidential amp Proprietary 210 Transfer Sessions UDM Transfer Operations Opening a Three Party Transfer Session A three party transfer session can be opened using the same syntax as a two party transfer session However both the primary and secondary servers must be specified explicitly and the host name of the primary server must be a valid IP or host address open machine1 somemvsmachine machine2 somentmachine In this example a three party transfer session is established between a machine with the host name somemvsmachine given the logical name machine and a machine with the host name somentmachine given the logical name machine2 It is important to keep in mind that the host name of the secondary transfer server should be specified from the point of view of the primary server since it will be making the connection to the secondary server Depending on your network configuration the host name for the secondary server f might be different from the UDM Manager s perspective Stoneman s Tip than that of
164. e simplest form of data transfer LIB file system 1 set _echo yes 2 set _halton warn 3 open unix sol9 user top098 pwd p100m 4 cd unix opt app data 5 mode type text 6 copy unix datal0 txt local MYLIB APPDATA DAILY 7 quit For this first OS 400 example the following is a line by line explanation 1 Line 1 turns on command echo which results in each command being sent to stdout prior to processing 2 Line 2 sets the error condition value on which script processing halts Any error greater than or equal to warn halts script processing 3 Line 3 opens a session between the local UDM Manager and a remote UDM server running on host so19 The host so19 is given the logical name of unix The open command also provides user credentials for the UDM server to verify and if successfully verified specifies the user ID with which the UDM server executes 4 Line 4 changes the current directory of the UDM server unix running on host sol9 5 Line 5 changes the transfer mode type from binary the default to text Text mode transfers will translate between code pages for example ASCII and EBCDIC and process the end of line characters 6 Line 6 is the copy command that actually moves the data between systems It copies file data10 txt on server unix to the local UDM Manager library MYLIB Data Physical File APPDATA member DAILY 7 Line 7 executes the quit command which closes all sessions and exits UDM with the highest ex
165. e to be the same as the 1rec1 allocation option for new data sets or the LRECL DCB attribute of existing data sets if the value of 1inelen is zero UDM also will set the 1ineop attribute to a value appropriate for the transfer type and destination allocation attributes if 1ineop has previous not be set udm user 3207 Confidential amp Proprietary 225 Copying Files with UDM UDM Transfer Operations 12 8 Copying Files with UDM 12 8 1 Simple Copy Operation At its core UDM is meant to copy files from one system to another This is done with the copy command The basic format of the copy command is copy sourcelname filespec destlname filespec The copy command copies the file specified on the server with the logical name corresponding to sourcelname to the server with the logical name corresponding to dest1name If no destination file name is given the source file name is used absent the directory name regardless of whether or not it was explicitly specified as part of the source file specification Likewise if only a directory is given for the destination file specification the source file name is appended to the directory when writing the file If a destination file name or complete file name and directory are given for the destination file specification that information is used in writing the destination file regardless of the source file name Examples The following example copies the file test txt from a mach
166. eattrib yes echo _file is _file size bytes in size end If the information for an attribute cannot be obtained its value is set to an empty string z OS datasets store only createdate and accessdate There is no time createtime and accesstime associated with these dates nor do z OS datasets store moddate or modt ime udm user 3207 Confidential amp Proprietary 204 forfiles Statement UDM Scripting Language 11 10 2 forfiles File Specification The file specification portion of the forfiles statement file_spec tells UDM how to build its list of files It takes the same format as the copy command file specification and can contain wildcards To list all of the members in a PDS on a z OS system you can issue the following commands forfiles zos MYHLQ MYPDS print msg _file end This would print the name of each member in a PDS called MYHLQ MYPDS For Windows UNIX and OS 400 systems as well as the HFS file system under z OS you can list all of the files in the current directory with the following UDM commands forfiles local print msg _file end To find all of the files ending in txt in a particular directory mydir in this example issue the following forfiles statement forfiles local mydir txt print msg _file end A question mark can be used as a wildcard for a single character In the previous example lets assume mydir contains the files file file1 file2 and file3 txt Exe
167. echo lt 5 5 2 gt 20 gt echo lt 2 4 2 7 2 gt 26 gt echo lt 2 4 2 7 2 gt 24 udm user 3207 Confidential amp Proprietary 168 UDM Command Format UDM Scripting Language Operations All operations take the following form left value operator right value The left value and right value can be Strings EQ and NE only Numbers Variable references Other operations Table 11 2 identifies and describes all of the operators for UDM command expressions EQ Compares the value on the left to the value on the right If the two are equal the result is 1 otherwise it is 0 Both the left an right values can be strings or numbers If they are strings the comparison is case insensitive NE Works like the equal operator except that it results in 1 if the left and right value are not equal and 0 if they are equal LT Results in a value of 1 if the left value is less than the right value otherwise it results in 0 This is a numeric operator GT Results in a value of 1 if the left value is greater than the right value otherwise it results in 0 This is a numeric operator LE Results in a value of 1 if the left value is less than or equal to the right value otherwise it results in O This is a numeric operator GE Results in a value of 1 if the left value is greater than or equal to the right value otherwise it results in O This is a numeri
168. ed on the value of attribute name ascending and descending specify whether the matching files are listed in ascending or descending order If neither is specified the list is sorted in ascending order Since having a sortby attribute in the forfiles loop implies that the file attributes will be used the file attributes will be retrieved regardless of whether or not fileattrib yes is present Examples To obtain a file list sorted by creation date earliest to latest forfiles src txt sortby createdate Do some stuff end Top obtain a file list ordered by file size from largest to smallest forfiles src exe sortby size descending Do some more stuff end An error would be produced if sortby was present without a value or if it referred to an attribute that does not exist for the _ file variable udm user 3207 Confidential amp Proprietary 202 forfiles Statement UDM Scripting Language 11 10 1 forfiles Built In Variables The forfiles statement utilizes two built in variables _ file and _path These variables are set by UDM to contain the file name and absolute path of each file in the list for each iteration For an example assume the following e Windows machine with logical name nt e Directory C Example on the Windows machine e Three files file1 txt file2 txt and file3 txt in the directory The following script segment prints the file name and absolute path of each file in the directory
169. ed test set test This is a test Multiple user defined variables can be set with a single call to the set command listing each variable s name value pair in succession separated by spaces set varname1 value1 varname2 value2 varname3 value3 To assign a value to a variable that has one or more spaces in it the value must be quoted set lonvar This variable has a rather long value udm user 3207 Confidential amp Proprietary 182 UDM Variables UDM Scripting Language 11 6 7 Variable Attributes In addition to accessing the value of a variable you can access information about that variable through its attributes A variable attribute is referenced by putting a dot after the variable name in a variable reference For example name attribute There are two variable attributes that can be used for any variable 1 exists 2 length Note Some built in variables have attributes specific to those variables exists Attribute The exists attribute expands to yes if a variable with that name exists at any scope it expands to no if no variable with that name exists Note Unlike when referencing a variable s value an error is not issued if the exists attribute is used for a variable name that does not exist You can use the exists attribute in combination with the if statement to determine if a variable exists and take the appropriate action if it does if filename exists EQ yes copy src
170. eference Guide AUTOMATICALLY_START Specification for whether or not UDM Server starts automatically when Universal Broker is started COMPONENT_NAME Name by which the clients know the UDM Server CONFIGURATION_FILE Full path name of the UDM Server configuration file RUNNING_MAXIMUM Maximum number of UDM Servers that can run simultaneously START_COMMAND Full path name of the UDM Server program WORKING_DIRECTORY Full path name of the UDM Server working directory Table 9 1 UDM Server for UNIX Component Definition Options udm user 3207 Confidential amp Proprietary 149 Configuration Universal Data Mover Server for UNIX 9 3 Configuration Universal Data Mover Server configuration consists of defining runtime and default values This section describes the UDM Server configuration options See Section 2 2 1 Configuration Methods for details on Universal Products configuration methods 9 3 1 Configuration File The configuration file provides the simplest method of specifying configuration values that will not change with each command invocation The Universal Data Mover Server configuration file name and directory is specified in the Universal Data Mover Server component definition see Chapter 4 Universal Data Mover Component Definition Options in the Universal Data Mover 3 2 0 Reference Guide The default configuration file name is udms conf This file can be edited manually with an
171. em to another Stoneman s Tip udm user 3207 Confidential amp Proprietary 222 Transfer Modes and Attributes UDM Transfer Operations 12 7 3 End of Line Sequence Text mode transfers have the concept of a line in UDM For record oriented file systems such as z OS s DD and DSN and OS 400 s LIB each line is a single record However for UNIX Windows and the HFS file system under USS and OS 400 there is no inherent structure imposed by the operating system on file data To determine what constitutes a line in the data for these types of files UDM looks for an end of line sequence on the source side of a transfer This can be any sequence of characters including a zero length sequence in which case the entire file is considered to be a single line UDM determines when it has read a complete line of data when this sequence is encountered In addition to the normal printable character sets on each platform an end of line sequence also can be e r character sequence to denote a carriage return character 1 sequence to denote a line feed n sequence to indicate a new line character When UDM transfers a line of text data from one server to another it does not transfer the end of line sequence Instead UDM transfers all of the data in each line up to the end of line sequence Stoneman s Tip The end of line sequence also is used on the destination side of a text transfer The end of
172. en regardless of the level selected in the MESSAGE_LEVEL option udm user 3207 Confidential amp Proprietary 85 Message and Audit Facilities Features 2 9 4 Message Destinations The location to which messages are written is the message destination Some Universal Products have a MESSAGE_DESTINATION configuration option that specifies the message destination If a program is used only from the command line or batch job it may have only one message destination such as standard error Valid destination values will depend on the host operating system z OS Universal Products on z OS run as batch jobs or started tasks Batch jobs do not provide the MESSAGE_DESTINATION option All messages are written to the SYSOUT ddname Started task message destinations are listed in the table below LOGFILE Messages are written to ddname UNVLOG All messages written to log files include a date and time stamp and the program s USS process ID SYSTEM Messages are written to the console log as WTO messages UNIX Message destinations are listed in the table below STDERR Messages are written to standard error This destination is most useful for console commands LOGFILE Messages are written to a log file Not all programs provide this destination The recommended directory for log files is var opt universal 1og This can be changed with the LOG_DIRECTORY option All messages written to log files include a date and
173. ens 255 Caution about Text Mode Transfer of Files with DDS 255 14 2 5 Source Physical Files Support 02202000000005 256 14 2 6 Copying Source Physical Files oooo lt oooooooo 257 Like Copies of Source Physical File Data ooooooooooooo 257 Non Source Physical to Source Physical Copies 257 Source Physical to Non Source Physical Copies 257 14 2 7 Save Files Support oo 258 SAVF to SAVF Transfers o oo oocoocoocoo E RETRE EREE NEKE RE 258 Non SAVF to SAVF Transfers 0000 cece eee tees 258 SAVF to Non SAVF Transfers 00000 0c eee eee eee 258 14 2 8 File Specifications 0 0 00000 eee 259 14 2 9 Wild Cards a6558 24 corr aKa ROKER AE AER AAA 259 Examples suscrita ee ai das 259 14 3 Codepage CCSID Mappings occccccoccococcccn es 260 14 3 1 CCSID Mapping xsara alias Re BA ER RRR A A 261 14 4 Command Reference oocccccoccoococ eee 263 14 4 1 attrib Attribute Command o oocccocccoccco ee 263 File Attributes 2 0 0 eee eens 263 LIB File System Attributes 0 0 00 eee eee 264 HFS Attributes 2 2 eens 266 14 4 2 call Call Command 224264224 eoR ceed ene a KEE ERE CRE Ow REE 267 udm user 3207 Confidential amp Proprietary 22 Contents 14 4 3 cd Change Directory Command sssaaa anaa 00 cee eee 268 14 4 4 copy Copy Command 1 eee 269 14 4
174. entations are converted Text translation operates in two modes direct and UCS The default is direct The direct translation mode exchanges code pages between Universal Products components to build direct translation tables Direct translation is the fastest translation method when a significant amount greater then 10K of text data is transmitted The code page exchange increases the amount of data sent over the network as part of the network connection negotiation UCS translation does not require the exchange of code pages For transactions that have little text data transmission this is the fastest Binary data is transmitted without any data translation udm user 3207 Confidential amp Proprietary 69 Fault Tolerance Features 2 6 Fault Tolerance Fault tolerant features address Universal Product capabilities to recover or restart from an array of error conditions that occur in any large IT organization Errors occur as a result of human software or hardware conditions The more resilient a product is to errors the greater value it offers 2 6 1 Network Fault Tolerance UDM uses the TCP IP protocol for communications over a data network The TCP IP protocol is a mature robust protocol capable of re sending packets and rerouting packets when network errors occur However data networks do have problems significant enough to prevent the TCP IP protocol from recovering As a result the TCP IP protocol terminates the connect
175. ential amp Proprietary 195 if Statement UDM Scripting Language 11 7 2 Adding an Alternate Path with else Statement Alternate Path without else Statement Often there are occasions where you may want to take one branch if some condition is true and another branch if that condition is false instead of merely picking up execution after the end statement Those lines would be executed if the condition was true as well only after executing the statements inside the if end pair This could be accomplished by two well phrased if statements one following the other as in this example if lt _rc GE 8 gt echo There has been an error end if lt _rc LT 8 gt echo There has not been an error end Flaws in this Methodology However while this is a perfectly valid method it suffers from two potential flaws First and foremost people may find such logic difficult to read thus making your UDM scripts more difficult to maintain especially by those who had not written them in the first place Second if the comparison operation contains a variable and evaluates to true for the first comparison it is possible something occurs in the statements inside the if end pair that changes the value of the variable and makes the second comparison evaluate to true as well For example if lt _lastrc GE 8 gt echo The last command was not successful end if lt _lastrc LT 8 gt echo The last command was successful end
176. equired the higher CPU consuming cipher suite is justified When lower level of security is acceptable a lower CPU consuming cipher suite may be used As long as the manager has both cipher suites in its list it can negotiate either cipher suite with servers of different security levels udm user 3207 Confidential amp Proprietary 66 Network Data Transmission Features DATA_AUTHENTICATION The DATA_AUTHENTICATION option specifies whether or not the network data is authenticated Data authentication verifies that the data did not change from the point it was sent to the point it was received Data authentication also is referred to as a data integrity in this document Data authentication occurs for each message sent over the network If a message fails authentication the network session is terminated and both programs end with an error The DATA_AUTHENTICATION option is applicable to the UNVv2 protocol only SSL always performs authentication DATA_COMPRESSION The DATA_COMPRESSION option specifies that network data should be compressed Compression attempts to reduce the amount of data to a form that can be decompressed to its original form The compression ratio is the original size divided by the compressed size The compression ratio value will depend on the type of data Some data compress better than others Two methods of compression are available ZLIB method provides the highest compression ratio with the high
177. er Whether an RDN value is case sensitive or not depends on the format in which the value is stored The certificate creator has some control over which format is used All formats except for printableString are case sensitive udm user 3207 Confidential amp Proprietary 78 Universal Access Control List Features EMAIL Matches the X 509 emailAddress attribute of the subject field and rfc822Name of the subjectAl tName extension value Both fields format the email address as an RFC 822 addr spec in the form of identifieredomain The attribute values may include pattern matching characters An asterisk matches 0 or more characters and a question mark matches one character Some example EMAIL values are e email usertifacme com email acme com email user acme com RFC 822 names are not case sensitive HOSTNAME Matches the following X 509 fields in the order listed 1 dNSName of the subjectAl1 tName extension value 2 commonName CN RDN attribute of the subject field s DN value Some example HOSTNAME values are hostname bigfish acme com hostname acme com The values are not case sensitive IP Matches the X 509 iPAddress field of the subj ectAl tName extension value ADDRESS An example IPADDRESS value is e ipaddress 10 20 30 40 SERIAL Matches the X 509 serialNumber value NUMBER The value can be specified in a hexadecimal format by prefixing the value with Ox or 0X otherwise the
178. er UDM Transfer Operations See Chapter 13 Transfer Operations z OS Specific and Chapter 14 Transfer Operations OS 400 Specific for transfer information specific to those operating systems udm user 3207 Confidential amp Proprietary 209 Transfer Sessions UDM Transfer Operations 12 2 Transfer Sessions 12 2 1 Opening a Transfer Session UDM transfer operations all occur within the context of a transfer session This section details how to open a UDM session Opening a Two Party Transfer Session All sessions are established using the open command At its simplest the open command specifies the primary and secondary servers for the session open logical1 hostname logical2 hostname In this example logical1 and logical2 are the user assigned logical names of the primary and secondary servers respectively Each of these parameters is set to the host name or IP address of the corresponding server For two party transfer sessions where the UDM Manager acts as the primary server hostname is not the host address of the local machine this would initiate a three party transfer with the primary server running on the local machine Instead the host address is either the name local or the asterisk character open machine1 machine2 somentmachine In this example a two party transfer session is established between the UDM Manager acting as the primary server with the logical name machine1 and another machine with th
179. er 3207 Confidential amp Proprietary 295 UDM Manager for z OS Examples Examples A 2 5 Copy a Set of Files to a New z OS Partitioned Data Set This example copies in text mode a set of files from a remote UNIX system to a partitioned data set on z OS The data set does not exist on z OS UDM is instructed to create it The data set is dynamically allocated based on the local UDM dynamic allocation attributes UDM provides default attributes that can be changed to meet local requirements The UDM defaults as they are delivered create a sequential variable block record data set with a logical record length of 1024 This example changes the data set organization from sequential PS to partitioned PO and adjusts the data set s space allocation to space units of cylinders primary space to 1 secondary space to 2 and directory blocks to 10 DSN file system S1 EXEC UDMPRC UNVSCR DD set _echo yes _halton warn open unix sol9 user top098 pwd p100m cd unix opt app data mode type text attrib local dsorg po spaceunit cyl primspace 1 secspace 2 dirblocks 10 truncext yes copy unix txt local app data pds quit SN 0 Nu un jp Note Line 5 is continued onto line 6 with the line continuation character udm user 3207 Confidential amp Proprietary 296 UDM Manager for UNIX and Windows Examples Examples A 3 UDM Manager for UNIX and Windows Examples This section describes how to use UDM in
180. er security is activated the UDM Server requires by default ALLOBJ authority to switch user profiles As described in Chapter 6 Universal Broker for OS 400 of the Universal Broker 3 2 0 User Guide this ALLOBJ authority requirement may be removed The UDM Server initially inherits authority from the UNVUBR320 user profile Following the switch to the user profile the UDM Server runs under the authority of the user initiating the data transfer The UNVUBR320 user profile requires SPLCTL authority in order to provide Universal Submit Job with job logs in specific limited situations See Chapter 6 Universal Broker for OS 400 in the Universal Broker 3 2 0 User Guide for information on how to remove the SPLCTLauthority Removing SPLCTL from the UNVUBR320 user profile may prevent the job log processing in limited situations udm user 3207 Confidential amp Proprietary 159 Security Universal Data Mover Server for OS 400 10 4 3 User Authentication User authentication is the process of verifying that a user is known and valid to the system The process used by UDM Server requires the user to provide a user name ID and a password The UDM Server passes the name ID and password to the operating system for verification this is referred to as logging on the user For OS 400 user authentication is optional However if security is enabled a user name ID and password are required in order to verify the user s credentials With secur
181. er the actions to take The UDM Manager connects to the UDM Server or Servers and processes your request The z OS Batch Manager provides a batch job interface to remote computers running the UDM Server component udm user 3207 Confidential amp Proprietary 94 Usage Universal Data Mover Manager for z OS 3 2 Usage UDM Manager for z OS executes as a batch job This section describes the JCL configuration and configuration options and command line syntax of UDM Manager for z OS Section3 3 Examples of UDM Manager for z OS provides examples demonstrating the flexibility of Universal Data Mover udm user 3207 Confidential amp Proprietary 95 Usage Universal Data Mover Manager for z OS 3 2 1 JCL Procedure Figure 3 1 below illustrates the Universal Data Mover for z OS JCL procedure UDMPRC located in the SUNVSAMP library that is provided to simplify the execution JCL and future maintenance ff UNVNLS DD UNVUSRC DD UNVCLIB DD if UNVTRACE DD UNVTRMDL DD JAS SYSPRINT DD SYSOUT DD CEEDUMP DD SYSUDUMP DD i SYSIN DD UNVSCR DD UDMPRC PROC UPARM DISP SHR DSN amp UNVPRE DISP SHR DSN amp UNVPRD DISP SHR DSN amp UNVPRE SYSOUT DISP SHR DSN amp UNVPRD SYSOUT SYSOUT SYSOUT SYSOUT DUMMY DUMMY UDM options USPRFC USPRFCOO USAP SAP RFC member UNVPRE SHLQ UNV UNVPRD PHLQ UNV if PS1 EXE
182. erently depending on whether the data set name is an absolute or relative form Absolute Name Allocation attributes for an absolute name are provided like any other data set through JCL keywords or allocation options Relative Name Allocation attributes for relative names are provided with one of the following methods 1 By referring to a cataloged data set from which attributes are copied a DCB dsname b LIKE dsname c REFDD ddname 2 By referring to a model Data Set Control Block DSCB on the volume on which the GDG is cataloged This cannot be used for SMS managed data sets a DCB modeldsname yourattributes 3 By using the DATACLAS and LIKE allocation keywords 4 Through the assignment of a DATACLAS by a data class ACS routine udm user 3207 Confidential amp Proprietary 238 z OS I O Transfer Operations z OS Specific 13 2 3 Catalogs There are two types of catalogs 1 Integrated Catalog Facility ICF 2 VSAM Catalogs Note IBM has dropped support for VSAM Catalogs as of January 1 2000 UDM does not support them Symbolic Names A catalog entry can be defined with symbolic names for the volume serial number UDM does resolve the symbolic names when they are found for the volume serial number Catalog Entry Types A catalog entry is defined as a specific type UDM only supports the non VSAM type entry A catalog entry type can by any one of the following Non VSAM Data Set e Generation Data
183. erval seconds sendbuffersize s7ze saf_key_ring name saf_key_ring_label 7abel server_stop_conditions codes tcp_no_delay option tracefilelines number trace_table s7ze error always never comment text udm help version Figure 3 4 UDM Manager for z OS Command Line Syntax 2 of 2 udm user 3207 Confidential amp Proprietary 104 Examples of UDM Manager for z OS Universal Data Mover Manager for z OS 3 3 Examples of UDM Manager for z OS Appendix A Examples provides operating system specific examples that demonstrate the use of Universal Data Mover Included in this appendix are the following examples that demonstrate the use of Universal Data Mover Manager for z OS Copy a File to an Existing z OS Sequential Data Set Copy az OS Sequential Data Set to a File e Copy a Set of Files to an Existing z OS Partitioned Data Set Copy a File to a New z OS Sequential Data Set Copy a Set of Files to a New z OS Partitioned Data Set For each topic there is an example as appropriate for both the DSN and DD file systems Note These z OS examples apply equally as well to the Windows operating systems with appropriate changes for the file system syntactical differences udm user 3207 Confidential amp Proprietary 105 Security Universal Data Mover Manager for z OS 3 4 Security Universal Data Mover is designed to be a secure system As the level of security rises so
184. es Although ddnames are not a different file system they do have their own naming conventions and behavior relative to UDM s CFS Table 12 3 below associates CFS terminology with z OS partitioned and sequential data sets allocated to ddnames path ddname defined with a JCL DD statement Examples DD1 PHONE ddname with a member name enclosed in parenthesis or just the member name Examples INDD JOBAB MYDATA PHONE PHONE absolute path There is only one type of path and that is absolute Refer to path above DD1 ddname and member name enclosed in parenthesis Refer to path above relative path N A Member name only The path is relative to the current directory file Same as path the ddname Member name only Example Example DD JOBAB directory N A ddname with which a PDS is allocated current N A Current ddname with which a PDS is directory allocated Examples INDD e OUTDD Table 12 3 CFS Terminology Associated with z OS ddnames udm user 3207 Confidential amp Proprietary 218 OS 400 File Systems UDM Transfer Operations 12 6 OS 400 File Systems Universal Data Mover for OS 400 supports two types of file systems LIB library file system supports the original native database file system e HFS file system supports the root and QOpenSys file systems under IFS Although UDM can access other IFS file systems only ro
185. escription Description of the attribute Source Indication of whether or not the attribute is a source attribute A source attribute is one whose destination side value is taken from its source side unless the user explicitly has overridden the destination side value Source attributes are used only when both of the these conditions apply Copying from one OS 400 system to another Both source and destination are in the LIB file systems udm user 3207 Confidential amp Proprietary 263 Command Reference Transfer Operations OS 400 Specific Value Values that can be assigned to the attribute UDM Default UDM default value that is assigned to an attribute if a value is not otherwise assigned A UDM default of NULL identifies the attribute as available to be set but not set initially If the attribute value is NULL or empty string the system default is used System Default OS 400 system default value that is assigned to an attribute if its UDM default is NULL or empty string An attribute can have different system defaults for different file types File Type Types of files in the LIB and HFS file systems to which an attribute applies LIBLibrary e PF Data physical file SP Source physical file e SAVFSave file e Stream LIB File System Attributes Table 14 2 identifies attributes that are unique to the LIB file system ACCPTH Access path type ARRIVAL KEYED NULL ARR
186. est use of CPU HASP method provides the lowest compression ratio with the lowest use of CPU Whether or not compression is used and which compression method is used depends on several items e Network bandwidth If network bandwidth is small compression may be worth the cost in CPU e CPU resources If CPU is limited the CPU cost may not be worth the reduced bandwidth usage Data compression ratio If the data does not compress well it is probably not worth CPU cost If the data ratio is high the CPU cost may be justified DATA_ENCRYPTION The DATA_ENCRYPTION option specifies whether or not network data is encrypted Encryption translates data into a format that prevents the original data from being determined Decryption translates encrypted data back into its original form The type of encryption performed depends on the network protocol being used SSL or UNVv2 Data encryption does increase CPU usage Whether or not encryption is used depends on the sensitivity of the data and the security of the two host systems and the data network between the hosts udm user 3207 Confidential amp Proprietary 67 Network Data Transmission Features DATA_SSL_CIPHER_LIST The DATA_SSL_CIPHER LIST option specifies one or more SSL cipher suites that are acceptable to use for network communications on the data session which is used for standard I O file transmission See CTL_SSL_CIPHER_LIST in this section DEFAULT_CIPHER
187. etenrbtdnadsimedgeesDelaiatons 37 Chapter 2 Features e oasis a iaa 38 Figure 2 1 Remote Configuration Unmanaged and Managed Modes of Opera cateaieg ieee tia Fa sdueedean Diaeeateiatcs eters 50 Figure 2 2 Universal Configuration Manager Error dialog Windows Vista 52 Figure 2 3 Windows Vista Program Compatibility Assistant oonnmoniccinnnnnnnn 53 Figure 2 4 Universal Configuration Manager oooooccccccccnnnnoconcccccccnnnnnannnnnnnnnnnnannnnannnnns 55 Figure 2 5 Universal Configuration Manager UDM Manager seese 58 Figure 2 6 Universal Configuration Manager UDM Server secese 59 Figure 2 7 X 500 Directory Sample icons iii cate 89 Figure 2 8 X 509 Version 3 Certificate Sample cooommicoonicinnnnnanasiscorcrorranannnanrnnnnos 90 Chapter 3 Universal Data Mover Manager for z OS 0 0 e ee eee eee eee 94 Figure 3 1 UDM Manager for z OS JCL Procedure ooooccccnnncccnccnnnnncccnanannnnnanannnnnnas 96 Figure 3 2 UDM Manager for Z OS SCL ocoooonnccccocononiniccocconcnrnonannnna narrar 98 Figure 3 3 UDM Manager for z OS Command Line Syntax 1 of 2 oo 103 Figure 3 4 UDM Manager for z OS Command Line Syntax 2 of 2 104 Chapter 4 Universal Data Mover Manager for Windows 0 000s ee eee eens 107 Figure 4 1 UDM Manager for Windows Command Line Syntax ee 112 Chapter 5 Universal Data Mover Manager for UNIX
188. file containing the options work exactly like the corresponding option in the open command Two streams of data come back from the SAP execution By default output from standard out and standard error is written to standard out and standard error by the UDM Manager SYSPRINT and SYSOUT respectively under z OS The mergelog option can be set to yes if you want both output streams written to the UDM transaction log standard out under UNIX Windows and OS 400 SYSPRINT under z OS By default if the UDM Manager is invoked with tracing turned on tracing will be turned on in Universal Connector USAP when UDM invokes it via the execsap command Likewise if trace is turned off in the UDM Manager USAP is invoked with tracing turned off You can override this behavior for the USAP invocation by setting the trace parameter in the call to the execsap command 15 3 2 execsap Command Example The following is an example of executing an SAP event using the execsap command execsap sapdest type event eventid MYEVENT parm MYPARM user me pwd mypwd udm user 3207 Confidential amp Proprietary 284 Chapter 16 Return Code Processing 16 1 Overview Universal Data Mover UDM return codes particularly for batch operations are used to gauge the degree of success of a job Each job generates a return code that indicates the status of the job when it ended 16 1 1 UDM Return Codes Table 16 1 below organizes UDM return codes into four
189. file system it will not traverse the directory tree and copy files from directories at a lower level than the current directory or the directory explicitly specified in the source file specification Wildcards should appear only in the filename portion of the file specification and not as part of the directory itself Stoneman s Tip udm user 3207 Confidential amp Proprietary 228 Copying Files with UDM UDM Transfer Operations 12 8 4 File Extension Attributes File extension attributes only come into play when a destination filename is not specified UDM considers a file extension to be the character sequence followed by the last period in the filename not including a dot character appearing as the first character in the filename The character sequence specified by defaul text is appended verbatim Stoneman s Tip A dot is not implied at the beginning of this sequence and must be explicitly included if it is desired in the destination filename Some file systems support file extensions In the case where the source filename is used as the destination filename UDM can either add an extension or truncate a file s extension If the trunctext attribute is set to yes the extension of the source filename is truncated when writing the destination file If the defaultext attribute is set to any value that value is appended to the end of the source filename when writing the destination file
190. guration is performed by one or more methods These configuration methods in their order of precedence are 1 Command Line 2 Command Line File 3 Environment Variables 4 Configuration File This order of precedence means that a command option specified on the command line overrides the same option specified in a command file which overrides the same option specified with an environment variable which overrides the same option specified with a configuration file keyword Note For security reasons not all options can be overridden udm user 3207 Confidential amp Proprietary 39 Configuration Features 2 2 2 Command Line Command line options affect one instance of a program execution Each time that you execute a program command line options let you tailor the behavior of the program to meet the specific needs for that execution Command line options are the highest in order of precedence of all the configuration methods see Section 2 2 1 Configuration Methods They override the options specified using all other configuration methods except where indicated Command line options consist of Parameter name of the option e Value pre defined or user defined value of the option The command line syntax depends in part on the operating system as noted below An value may or may not be case sensitive depending on what it is specifying For example if a value is either yes or no it is not case sensitive
191. h in the name for example ISO8859 1 an underscore _ must replace the when the code page is used in a UDM script 1BM037 037 v v IBM273 273 v v IBM277 277 vV v IBM278 278 v v IBM280 280 vV v IBM284 284 v v IBM500 500 vV v IBM1047 IBM1140 1140 vV v IBM1141 1141 v v IBM1142 1142 v v IBM1143 1143 vV v IBM1144 1144 v v IBM1145 1145 vV v IBM1146 1146 vV v 1BM1147 1147 v v IBM1148 1148 vV v udm user 3207 Confidential amp Proprietary 261 Codepage CCSID Mappings Transfer Operations OS 400 Specific 1508859 1 819 vV 1508859 2 912 v 1508859 4 914 vV 1508859 5 915 vV 1508859 6 1089 vV 1508859 7 813 vV 1508859 8 916 vV 1508859 9 920 vV 1508859 13 921 vV 1508859 15 923 vV PC437 437 v PC737 737 v PC775 775 vV PC850 850 vV PC852 852 V PC855 855 vV PC857 857 Vv PC860 860 vV PC861 861 Vv PC862 862 Vv PC863 863 vV PC864 864 vV PC865 865 vV PC866 866 vV PC869 869 vV PC874 874 vV WIN1250 1250 vV WIN1251 1251 vV WIN1252 1252 vV WIN1253 1253 vV WIN1254 1254 vV WIN1255 1255 vV WIN1256 1256 vV WIN1257 1257 vV WIN1258 1258 vV Table 14 1 CCSID Mappings udm user 3207 Confidential amp Proprietary 262 Command Reference Transfer Operations OS 400 Specific 14 4 Command Reference This section describes UDM
192. h it occurred is printed with the error if the command cannot be parsed or is malformed It has a value of yes or no e Ifthe value is yes the line number is printed e Ifthe value is no the line number is not printed _lines can be set using the set command set _lines yes _path The _path built in variable contains the absolute path of the file for the current iteration in a forfiles loop see Section 11 10 forfiles Statement path cannot be set using the set command C The _rc built in variable holds the current UDM return code a numeric value that indicates the highest return code received from processing all UDM commands up to that point The value of _rc is the return code that the UDM Manager returns when it exits As with the _halton variable _rc can be set via the set command to either of the following integers or convenience values 0 none Success or no error 4 warn Warning has been issued 8 error Error has occurred e 16 fatal error Fatal error has occurred For example set _rc warn udm user 3207 Confidential amp Proprietary 189 UDM Variables UDM Scripting Language _time The _time built in variable displays the current time It has several variable attributes hh resolves to the two digit hour 24 hour time mm resolves to the two digit minute ss the number of seconds that have elapsed since the current minute hs resolves to the number of hundredths of a second th
193. he 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 Table 7 1 below 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 in the Universal Data Mover 3 2 0 Reference Guide AUTOMATICALLY_START Specification for whether or not UDM Server starts automatically when Universal Broker is started COMPONENT_NAME Name by which the clients know the UDM Server CONFIGURATION_FILE Member name of the UDM Server configuration file in the UNVCONF library allocated to the Broker ddname UNVCONF RUNNING_MAXIMUM Maximum number of UDM Servers that can run simultaneously START_COMMAND Member name of the UDM Server program WORKING_DIRECTORY HMS directory used as the working directory of the UDM Server Table 7 1 UDM Server for z OS Component Definition Options udm user 3207 Confidential amp Proprietary 133 Configuration Universal Data Mover Server for z OS 7 3 Configuration Universal Data Mover Server configuration consists of defining runtime and default values See Section 2 2 1 Configuration Methods for details on Universal Products configuration methods 7 3 1 Configuration File The configuration file provides the simp
194. he file transfer has been completed the file is renamed to the appropriate destination filename To turn on transaction oriented transfers set the trans attribute for the server on the destination side of the transfer to yes Note UDM for OS 400 LIB file system does not support transaction oriented transfers udm user 3207 Confidential amp Proprietary 231 Copying Files with UDM UDM Transfer Operations 12 8 9 Changing the Current Directory in UDM The cd command is an easy way to change the current directory in the UDM Common File System discussed earlier in this section By default when the manager is involved in a two party transfer the current directory for primary server is the path in which the manager was launched under Under z OS this would be the high level qualifier for the user id the manager is running as The secondary server as well as the primary server in a three party transfer has a default path of the authenticated user s home directory for hierarchical file systems and a high level qualifier corresponding to the authenticated user for dd and dsn file systems A user can change the current path for a specific server by issuing a cd command cd Iname current directory In this example e Iname is the logical name of the transfer server to change its default path e current directory is the new current directory to set If the cd command is issued with only a logical name UDM displays the current director
195. he primary server This also is true for the secondary server Even if the secondary server when looking up the manager would produce a different IP address than the primary server the ACL rule is based on the address as seen from the primary server udm_cert_access udm_cert_ access works just like the Universal Command ucmd_cert_access rule In the top section of the UACL configuration file you describe a certificate in detail and give it an alias A udm_cert_access rule describes whether access is allowed or denied to a connecting UDM manager or server based on whether or not its certificate matches the one to which the alias in the rule refers For detailed information on these UACL rules see Chapter 5 Universal Data Mover UACL Entries in the Universal Data Mover 3 2 0 Reference Guide udm user 3207 Confidential amp Proprietary 82 Universal Access Control List Features 2 8 4 Proxy Certificates For two party transfer sessions certificates work exactly as they do with Universal Command the manager presents its certificate when trying to establish a session with the server If the access rules allow a connection using that certificate and if they certificate is properly validated a session is established For three party transfer sessions the manager as it does in a two party transfer session presents its certificate to the primary when trying to establish a session The udm_cert_access rules if there are a
196. hich include one or more of the following e Configuration options e Access control lists e Licensing information e Other component specific information 2 Right side of the screen displays information for the selected component page By default Universal Configuration Manager displays the first property page of the first component in the Installed Components tree udm user 3207 Confidential amp Proprietary 55 Universal Configuration Manager Features 2 4 3 Navigating through Universal Configuration Manager To display general information about a component click the component name in the Installed Components list To display the list of property pages for a component click the icon next to the component name in the Installed Components list To display a property page click the name of that page in the Installed Components list If a property page has one or more of its own pages a icon displays next to the name of that property page in the Installed Components list Click that icon to display a list of those pages In Figure 2 4 for example e List of property pages is displayed for Universal Broker e Message Options property page has been selected and information for that property is displayed on the right side of the page No icons next to any of the property pages indicates that they do not have one or more of their own property pages 2 4 4 Modifying Entering Data On the property page
197. 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 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 Although configuration files can be edited with any text editor for example Notepad the Universal Configuration Manager application accessible via the Control Panel is the recommended way to set configuration options The Universal Configuration Manager provides a graphical interface and context sensitive help and helps protect the integrity of the configuration file by validating all changes to configuration option values see Section 2 4 Universal Configuration Manager 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 See Section 2 2 1 Configuration Methods for details on Universal Products configuration methods udm user 3207 Confidential amp Proprietary 109 Usage Universal Data Mover Manager for Windows 4 2 3 Configuration Options Table 4 1 below describes the configuration options used to execute UDM Manager for Wind
198. his permits different component versions to communication with each other with no problems This is a very important feature for distributed systems since it is near impossible to upgrade hundreds of servers simultaneously New encryption and compression algorithms can be added in future releases without loosing backward compatibility with older releases After a network connection is made connection options are negotiated between the two Universal Products programs The options negotiated include which encryption and compression algorithms are used for the session Only algorithms that both programs implement are chosen in the negotiation process The negotiation process permits two different program versions to communicate udm user 3207 Confidential amp Proprietary 65 Network Data Transmission Features 2 0 4 Configurable Attributes The network protocol can be configured in ways that effect compress encryption code pages and network delays The following configuration options are available on many of the Universal Products CODE_PAGE The CODE_PAGE option specifies the code page translation table used to translate network data from and to the local code page for the system on which the program is executing A codepage table is a text file that contains a two column table The table maps local single byte character codes to two byte UNICODE character codes Code pages are located in the product National Language Support
199. hms The two algorithms cannot be specified individually Universal Products supports a subset of the complete SSL cipher suites defined by the standard The cipher suite name is formatted as an encryption algorithm abbreviation followed by the message digest algorithm abbreviation udm user 3207 Confidential amp Proprietary 61 Network Data Transmission Features Table 2 2 below identifies the supported cipher suites RC4 SHA 128 bit RC4 encryption with SHA 1 message digest RC4 MD5 128 bit RC4 encryption with MD5 message digest AES256 SHA 256 bit AES encryption with SHA 1 message digest AES128 SHA 128 bit AES encryption with SHA 1 message digest DES CBC3 SHA 128 bit Triple DES encryption with SHA 1 message digest DES CBC SHA 128 bit DES encryption with SHA 1 message digest NULL SHA No encryption with SHA 1 message digest NULL MD5 No encryption with MD5 message digest Table 2 2 Supported SSL cipher suites Universal Products support one additional cipher suite name that is not part of the SSL protocol The NULL NULL cipher suite turns SSL off completely and instead uses the Universal Products Protocol UNVv2 see Section 2 5 2 Universal Products Protocol To turn off SSL specify NULL NULL for the data cipher list for all UDM servers used for the session and for the encrypt parameter on the open command Peer Authentication When communicating with a party across a data network how do you insu
200. ial amp Proprietary 192 if Statement UDM Scripting Language EQ Equal The equal comparator EQ evaluates to true if both the left and right hand values are equal to each other If one or more of the values contains alpha characters non numeric the comparison is case insensitive That is a word that is all lower case would be equal to the same word if it were all upper case for example dog would be equal to DOG Here are some examples of some if statements using the equal comparator if filename EQ myfile txt print msg The name of the file is myfile txt end if 8 EQ _lastrc print msg The last command resulted in an error end if filename exists EQ yes print msg The filename variable exists end NE Not Equal The not equal comparator NE evaluates to true if the left hand value is not the same as the right hand value As with the equal comparator alpha character comparisons are case insensitive The following are some examples of the not equal comparator if C Program Files Universal NE mydir print msg This is not the Stonebranch application directory end if 8 NE 0 print msg This will always print as 8 is not equal to 0 end if filename exists NE no print msg The filename variable exists end udm user 3207 Confidential amp Proprietary 193 if Statement UDM Scripting Language LT Less Than The less than comparator LT evaluates to true if the left hand va
201. icate based UACL entries are searched under the following conditions e Client provides an X 509 certificate and no certificate map entry matches e Client does not provide an X 509 certificate Either the certificate based UACL entries or the non certificate based UACL entries are searched but not both udm user 3207 Confidential amp Proprietary 81 Universal Access Control List Features 2 8 3 Types of UACL Rules There are three types of ACL rules in the UACL configuration file used by UDM e udm_access e udm_cert_access udm_mgr_access All of them are access rules That is they are used to either allow or deny access the right to establish a connection from a remote system The udm_access and udm_mgr_access rules are similar to the Universal Command ucmd_access rule in that they allow or deny access depending on a remote host IP address and remote user udm_access udm_access takes the same form as the ucmd_access rule The remote host and remote user refer to the host IP of the machine connecting to the UDM Server and the user of the remote system udm_mgr_access udm_mgr_access differs slightly from ucmd_access in that instead of the remote IP and remote user udm_mgr_access refers to the IP address and user of the manager Note Ina three party transfer session the manager s host IP is from the perspective of the primary transfer server the IP address given if you look up the manager s IP address on t
202. ificate ACL Add Edit Delete A Delete Universal Enterorise Con to El TE Wise Dons Cancel Figure 8 2 Universal Configuration Manager Universal Data Mover Server Access ACL udm user 3207 Confidential amp Proprietary 147 Chapter 9 Universal Data Mover Server for UNIX 9 1 Overview This chapter provides the following information on Universal Data Mover UDM Server specific to the UNIX operating system e Component Definition e Configuration e Security udm user 3207 Confidential amp Proprietary 148 Component Definition Universal Data Mover Server for UNIX 9 2 Component Definition All Universal Products 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 3 2 0 User Guide The syntax of a component definition file is the same as a configuration file See Section 2 2 6 Configuration File Syntax for detailed syntax information The UDM Server for UNIX component definition is located in the component definition directory of the Universal Broker Table 9 1 below identifies all of the options that comprise the UDM Server for UNIX component definition Each Option Name is a link to detailed information about that component definition option in the Universal Data Mover 3 2 0 R
203. ified via the attrib Attribute command For complete details on an allocation attribute refer to the IBM JCL Reference Note When performing a z OS to z OS copy and the destination file system is DSN UDM uses the following allocation attributes obtained from the source file assuming the file system is DD or DSN blksize dirblocks dsorg Irecl primspace secspace and spaceunit If you do not want to use the source files values for these allocation attributes you can override them by issuing an attrib command with the attributes that you want to change before the copy operation abnormaldisp e Disposition of a data set after the job ends abnormally Equivalent to the third position sub parameter of the JCL DISP parameter DISP status normaldisp abnormaldisp Default is DELETE it can be set with the UDM configuration option ALLOC_ABNORMAL_DISP avgrec e Indication that the unit of allocation space specified with the spaceunit attribute is records and that the primary space and secondary space values are in units of 1 s K s or M s Equivalent to the JCL AVGREC parameter AVGREC size e No default or configuration option blksize Block size with which the data set is allocated e Equivalent to the JCL BLKSIZE parameter BLKSIZE size Default is 27998 it can be set with the UDM configuration option ALLOC_BLKSIZE blkszlim Block size limit when there is not block size specified from any source Equivale
204. ile type is a save file an error is issued udm user 3207 Confidential amp Proprietary 275 Command Reference Transfer Operations OS 400 Specific 14 4 6 delete Delete Command The delete Delete command in the UDM for OS 400 LIB file system takes the following form DELETE logical name file mask delete Command Requirements The delete command has the following requirements It can be used to remove files and members but not libraries Note For the protection of the file system UDM for OS 400 does not allow users to delete libraries delete Command Forms With UDM for OS 400 the file mask which can contain wild cards in any portion library file and member takes one of the following forms DELETE logical name LIBRARY FILE Deletes any files including Save files in the libraries that match the mask DELETE logical name FILE Deletes any files including Save files in the current directory library that match the mask DELETE logical name LIBRARY FILE MEMBER Deletes any members where the library file and member portions of their fully qualified names match the appropriate elements of the mask DELETE logical name FILE MEMBER Deletes any members in the current directory whose file and member portions of their fully qualified names match the appropriate elements of the mask Table 14 4 delete Command Forms with UDM under OS 400 udm user 3207 Confidential amp Proprietary 276
205. ils In order for this to work you must first clear the destination current library by issuing the following command CD DST udm user 3207 Confidential amp Proprietary 268 Command Reference Transfer Operations OS 400 Specific 14 4 4 copy Copy Command In both the HFS and LIB file systems if a file with multi byte characters including DBCS Double Byte Character Set is transferred using UDM in text mode data loss or corruption can occur This is because UDM is basically SBCS Single Byte Character Set in nature If an SBCS code page is used for the data transfer in text mode some data can be translated into characters that do not translate back to the same data when written to the target file To transfer these type of files users normally should use binary mode and should be very careful if they find it necessary to use text mode 14 4 5 File Specification Rules File specifications can appear in a variety of UDM commands from copy to forfiles On OS 400 a simple set of rules governs how the full file specification used in an operation is constructed Since there are still subtle differences between source and destination side file specifications in terms of how they are derived separate rules are provided for each type of specification e Source File Specification e Destination File Specification Source and Destination in LIB e Destination only in LIB udm user 3207 Confidential amp
206. in all Universal Products that utilize certificates udm user 3207 Confidential amp Proprietary 92 X 509 Certificates Features Certificate Identification When a certificate has been validated as being issued by a trusted CA and not revoked by the CA the next step is to check that it identifies the intended peer A Universal Product Manager validates a Broker certificate by the Broker host name or IP address or the certificate serial number The VERIFY_HOST_NAME configuration option is used to specify the host name or IP address that is identified in the Broker certificate Each certificate signed by a CA must have a unique serial number for that CA The VERIFY_SERIAL_NUMBER option is used to specify the serial number in the Broker certificate Should certificate identification fail the session is immediately terminated Universal Brokers work differently than the Managers A Broker maps a peer certificate to a certificate ID The certificate map definitions are part of the Universal Access Control List UACL definitions At that point the certificate ID is used by UACL definitions to control access to Broker and Server services Certificate Support Many certificate authority applications also known as Public Key Infrastructure PKI applications are available Universal Products should be able to utilize any certificate in a PEM format file PEM Privacy Enhanced Mail is a common text file format used for certificates
207. ine with the logical name src to a file called test txt on the machine with the logical name dst copy src test txt dst The following example copies the test txt file residing in c files from a machine with the logical name src to a file called test txt on the machine with the logical name dst copy src c files test txt dst The following example copies test txt from src to the root of drive C on dst The destination file is also called test txt copy src test txt dst c The following example copies the file test txt from src to a file called test bak in the root of drive C on dst copy src test txt dst c test bak udm user 3207 Confidential amp Proprietary 226 Copying Files with UDM UDM Transfer Operations If you want the destination file name to be the same as that of the source file name you do not have to specify the destination system in the copy command The destination will be implied based on the logical name of the source if the source is the primary server l E the destination is assumed to be the secondary server Stoneman s Tip and vice versa 12 8 2 Move Operation A UDM move operation using the move command is similar to a copy operation The only difference between using a move command and a copy command is that after you move a file it is deleted from the source server from which it was moved udm user 3207 Confidential amp Proprietary 227 Copying Files wi
208. integrity of the configuration file by validating all changes to configuration option values see Section 2 4 Universal Configuration Manager udm user 3207 Confidential amp Proprietary 143 Universal Data Mover Server for Windows 8 3 2 Configuration Options Table 8 2 identifies all Universal Data Mover Server for Windows configuration options Each Option Name is a link to detailed information about that configuration option in the Universal Data Mover 3 2 0 Reference Guide ACTIVITY_MONITORING Specification for whether or not product activity monitoring events are generated CODE_PAGE Character code page used to translate text data DATA_COMPRESSION Specification for whether or not data is compressed on all standard I O files DATA_SSL_CIPHER_LIST SSL cipher suites to use for data session between UDM primary and secondary servers EVENT_GENERATION Events to be generated as persistent events FRAME_INTERVAL Number of UDM transfer blocks transferred before a frame sync message is sent with network fault tolerance turned on INSTALLATION_DIRECTORY Directory on which UDM Server is installed LOGON_METHOD Specification for how users are logged onto the system MESSAGE_LEVEL Level of messages that UDM will write to the Universal message Catalog UMC file NETWORK_DELAY Expected network latency in seconds NLS_DIRECTORY Directory where the UDM Manage
209. ion 1 2 Line 1 turns on command echo which results in each command being printed out prior to processing Line 2 sets the error condition value on which script processing halts Any error greater than or equal to warn halts script processing Line 3 opens a session between the local UDM Manager and a remote UDM server running on host so19 The host so19 is given the logical name of unix The open command also provides user credentials for the UDM server to verify and if successfully verified specifies the user ID with which the UDM server executes Line 4 changes the local file system from the default of DSN to DD The file system type dictates the syntax and semantics of file specifications such as in the copy command Line 5 changes the current directory of the UDM server unix running on host so19 Line 6 changes the transfer mode type from binary the default to text Text mode transfers will translate between code pages for example ASCII and EBCDIC and process the end of line characters Line 7 is the copy command that actually moves the data between systems It copies file data10 txt on server unix to the local UDM Manager ddname APOUT Recall that line 4 sets the local file system type to DD hence APOUT is referencing a ddname Line 8 executes the quit command which closes all sessions and exits UDM with the highest exit code set udm user 3207 Confidential amp Proprietary 290 UDM Manager for z OS Examples
210. ion between the application programs Like any application using TCP IP UDM is subject to these network errors Should they occur a product can no longer communicate and must shutdown or restart These types of errors normally show themselves as premature closes connection resets time outs or broken pipe errors UDM provides the ability to circumvent these types of errors with its Network Fault Tolerant protocol By using the network fault tolerant protocol UDM traps the connection termination caused by the network error and it reestablishes the network connections Once connections are reestablished processing automatically resumes from the location of the last successful message exchange No program restarts are required and no data are lost The network fault tolerant protocol acknowledges and checkpoints successfully received and sent messages respectively The network fault tolerant protocol does reduce data throughput Consequentially the use of network fault tolerance should be carefully weighed in terms of increased execution time versus the probability of network errors and cost of such errors For example it may be easier to restart a program then to incur increased execution time When a network connection terminates the manager will enter a network reconnect phase In the reconnect phase the manager attempts to connect to the server and reestablish its network connections The condition that caused the network error may persist
211. ions category If you have trouble locating the Universal Configuration Manager icon simply switch to the Classic View to display all Control Panel icons at the same time 64 bit Windows Editions The Windows Control Panel places icons for all 32 bit applets under the View x86 Control Panel Icons or on newer versions the View 32 bit Control Panel Icons category even when the Classic View is enabled When using the Category View look for the 32 bit Control Panel applet icons in the Additional Options category udm user 3207 Confidential amp Proprietary 54 Universal Configuration Manager Features EJ Universal Configuration Manager Universal Application Container Ser E E E E E E E E E E E E ge Options i Event Subsystem Options i License Information Universal Broker Universal Command Manager Universal Command Server Universal Control Manager Universal Control Server Universal Data Mover Manager Universal Data Mover Server Universal Enterprise Controller Universal Event Log Dump Universal Event Monitor Manager Universal Event Monitor Server Universal Query Figure 2 4 Universal Configuration Manager Each Universal Configuration Manager screen contains two sections 1 Left side of the screen displays the Installed Components tree which lists e Universal Products components currently installed on your system e Property pages available for each component as selected w
212. ir Gls dae RR Be aaa 300 A 4 UDM Manager for OS 400 Examples 00000 e cece 301 A 4 1 Copy a File to an Existing OS 400 File oooooooooooo 302 LIB filesystem irira be cues eek E ee a Pe ee SOE eee 302 MPSTIGSYSIEMN 2c2dcccccccatadiehatsebhaoddieeadesas aes caae Shs 303 A 4 2 Copy an OS 400 Data Physical File to a File 304 LIB file system escocia Ree eh kee taa ke Soak SS CARRERE OR ERR RRS 304 A 4 3 Copy a Set of Files to an Existing Data Physical File 305 RIB file SISI sra he eo ak le ea area a des Be ena ee See a ie 305 A 4 4 Copy a File to a New OS 400 Data Physical File 306 LIB file system ccc ncceceetawh deat hen Magee dee ee a Sede AR 306 A 4 5 Copy a File to a New OS 400 Source Physical File 307 LIB file System cierres ais baii 307 A 4 6 Copy a Set of Files to a New Data Physical File on OS 400 308 A saad ee nad as eee eee deb Sienennanx hake 308 A 4 7 Copy Different Types of OS 400 Files using forfiles and _file type 309 A 4 8 Invoke a Script from a Batch Job ooooooooooooooooooo 310 LIB file system esc ner raro ead ke Shakes ach heed on bee eee 310 Appendix B Customer Support 00000 ee ee ee ee 311 udm user 3207 Confidential amp Proprietary 24 List of Figures Chapter 1 Overview sica e a a wlan wet we Al wen ee 34 Figure 1 1 UDM Transfer Sessions s sscucagcendicahincides cecapadeensscnsea
213. isted at any time by issuing the following command data print _lastmsg udm user 3207 Confidential amp Proprietary 187 UDM Variables UDM Scripting Language _lastre The _lastrc built in variable holds the return code of the last command issued _lastrc also has two special attributes message and result message contains a human readable string indicating what happened with the last executed statement f acommand could not be executed or had improper values the value of _Tastrc message is ERROR Ifa command successfully executed the value of _lastrc message is either SUCCESS or some other message depending upon the command result holds an integer value that indicates the result of the last command executed The meaning of this value depends on the command Unless otherwise stated e 1 indicates failure e O ora positive value indicates success This value does not affect the value of _rc and _lastrc _lastrc cannot be set using the set command Stoneman s Tip You can use the _lastrc variable in combination with the if statement to take action based on the return value of the previously issued command copy src myfile if _lastrc EQ 0 delete src myfile end udm user 3207 Confidential amp Proprietary 188 UDM Variables UDM Scripting Language _lines The _lines built in variable specifies whether or not the line number of a command relative to the script in whic
214. it code set udm user 3207 Confidential amp Proprietary 302 UDM Manager for OS 400 Examples Examples HFS file system O AN DMN AUNA set _echo yes set _halton warn open unix sol9 user top098 pwd p100m filesys local hfs cd unix opt app data mode type text attrib local createop replace copy unix datal0 txt local opt appdata quit This HFS file system example is basically the same as the LIB file system example with these changes Addition of line 4 which changes the local file system from the default of LIB to HFS The file system type dictates the syntax and semantics of file specifications such as in the copy command Addition of line 7 which sets the local attribute createop The createop attribute controls how a file is created By default its value is new which indicates that only new files are created and existing files are not written over replaced In this case its value is being set to replace specifying that if the file exists it should be replaced otherwise it is created udm user 3207 Confidential amp Proprietary 303 UDM Manager for OS 400 Examples Examples A 4 2 Copy an OS 400 Data Physical File to a File This example copies in text mode a Data Physical File on OS 400 to a remote UNIX system Note A text transfer by default does not trim spaces from the end of a record If the data set being copied is a fixed record format each record is padded with sp
215. ities e X 509 Certificates udm user 3207 Confidential amp Proprietary 38 Configuration Features 2 2 Configuration Product configuration consists of specifying options that control product behavior and resource allocation An example of configurable product behavior is whether or not data transferred over the network is compressed An example of configurable resource allocation is the directory location in which the product creates its log files Each option is comprised of a pre defined parameter which identifies the option and one or more values The format of the parameter depends on the method being used to specify the option Although there are many configurable product options Universal Products in general are designed to require minimal configuration and administration The default options will work very well in most environments When local requirements do require a change in product configuration there are multiple methods available to configure the products in order to meet your needs 2 2 1 Configuration Methods All Stonebranch Inc Universal Products provide a consistent and flexible method of configuration An operating system s native configuration methods such as configuration files are utilized in order to integrate with existing system management policies and procedures for the platform Depending on specific Universal Products and the operating system on which it is being run product confi
216. itten to a console file or system log that 1 Document the actions taken by a program 2 Inform users of error conditions encountered by a program This section describes the message and audit facilities that are common to all Universal Products See the individual Universal Product documentation for additional details 2 9 1 Message Types There are six types or severity levels of Universal Products messages The severity level is based on the type of information provided by those messages 1 Audit messages document the configuration options used by the program s execution and resource allocation details They provide complete description of the program execution for auditing and problem resolution 2 Informational messages document the actions being taken by a program They help determine the current stage of processing for a program Informational messages also document statistics about data processed 3 Warning messages document unexpected behavior that may cause or indicate a problem 4 Error messages document program errors They provide diagnostic data to help identify the cause of the problem 5 Diagnostic messages document diagnostic information for problem resolution 6 Alert messages document a notification that a communications issue which does not disrupt the program or require action has occurred The MESSAGE_LEVEL configuration option in each Universal Product component lets you specify which messages are
217. ity enabled you transfer files using a specific user s security context 10 4 4 Universal Access Control List UDM Server uses the Universal Access Control List UACL file as an extra layer of security The UACL file contains UDM Server entries that contain Access Control List ACL rules that permit or deny access to the UDM Server See Section 2 8 Universal Access Control List for details on the Universal Access Control List feature UACL Entries The syntax of a UACL entry file is the same as the UDM configuration file See Section 2 2 6 Configuration File Syntax for detailed syntax information Table 10 3 identifies all UDM Server for OS 400 UACL entries Each UACL Entry Name is a link to detailed information about that UACL entry in the Universal Data Mover 3 2 0 Reference Guide UDM_ACCESS Allows or denies access to Universal Data Mover Server services UDM_MGR_ACCESS Allows or denies access based on the host name and or user of the Manager trying to initiate a UDM session Table 10 3 UDMr Server for OS 400 UACL Entries udm user 3207 Confidential amp Proprietary 160 Security Universal Data Mover Server for OS 400 UACL Examples The following set of rules permit services for the subnet 10 20 30 and denies all other connections udm_access 10 20 30 allow auth udm_access ALL deny auth The following set of rules effectively permit connections from any host but has limited
218. ke to re establish a transfer session when a network fault occurs RECONNECT_RETRY_INTERVAL Number of seconds that UDM will wait between each successive attempt to re establish a transfer session when a network fault occurs RECV_BUFFER_SIZE Size of the TCP receive buffer for UDM SEND_BUFFER_SIZE Size of the TCP send buffer for UDM TCP_NO_DELAY Specification for whether or not to use TCP packet coalescing TMP_DIRECTORY Directory that UDM Server uses for temporary files TRACE_DIRECTORY Directory that UDM Server uses for its Trace files TRACE_FILE_LINES Maximum number of lines to write to the trace file TRACE_TABLE Size of a wrap around trace table maintained in memory UMASK File mode creation mask USER_SECURITY User security option Table 9 2 UDM Server for UNIX Configuration Options Confidential amp Proprietary 151 Security Universal Data Mover Server for UNIX 9 4 Security Universal Data Mover Server is designed to be a secure system As the level of security rises so does the administrative complexity of the system Universal Data Mover Server has balanced the two to avoid the administrative complexity with a minimum sacrifice to security Universal Data Mover security concerns are Access to Universal Data Mover files and directories Access to Universal Data Mover configuration files Universal Data Mover user account
219. l or external table for code page to CCSID mapping DATA_COMPRESSION Specification for whether or not data is compressed on all standard I O files DATA_SSL_CIPHER_LIST SSL cipher suites to use for data session between UDM primary and secondary servers EVENT_GENERATION Events to be generated as persistent events FRAME_INTERVAL Number of UDM transfer blocks transferred before a frame sync message is sent with network fault tolerance turned on MESSAGE_LEVEL Level of messages that UDM will write to the Universal message Catalog UMC file NETWORK_DELAY Expected network latency in seconds OUTBOUND_IP Host or IP address that UDM binds to when initiating outgoing connections to another UDM server RECONNECT_RETRY_COUNT Number of attempts that the UDM Manager will make to re establish a transfer session when a network fault occurs RECONNECT_RETRY_INTERVAL Number of seconds that UDM will wait between each successive attempt to re establish a transfer session when a network fault occurs RECV_BUFFER_SIZE Size of the TCP receive buffer for UDM SEND_BUFFER_SIZE Size of the TCP send buffer for UDM SIZE_ATTRIB Default size for file creation of physical files for both data and source file types TMP_DIRECTORY Directory that UDM Server uses for temporary files TRACE_FILE_LINES Maximum number of lines to write to the trace file TRACE_TABLE Size of a wrap around trace table maintained in memory UMASK
220. ld have write permission to the following Universal Products libraries and all objects within these libraries e Installation library UNVPRD320 by default Product temporary library UNVTMP320 Universal spool library UNVSPL320 For maximum security only trusted accounts administrators and the UNVUBR320 profile should have management existence alter add update and delete authority to these objects Note System value QCRTAUT controls public access authority to created objects unless overridden by specific commands udm user 3207 Confidential amp Proprietary 131 Chapter 7 Universal Data Mover Server for z OS 7 1 Overview This chapter provides the following information on the Universal Data Mover UDM Server specific to the z OS operating system e Component Definition e Configuration e Security udm user 3207 Confidential amp Proprietary 132 Component Definition Universal Data Mover Server for z OS 7 2 Component Definition All Universal Products 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 3 2 0 User Guide The syntax of a component definition file is the same as a configuration file See Section 2 2 6 Configuration File Syntax for detailed syntax information T
221. lectronic object that identifies an entity It is analogous to a passport in that it must be issued by a party that is trusted by all who accept the certificate Certificates are issued by trusted parties called Certificate Authorities CA s For example VeriSign Inc is a CA that most parties trust We all have faith that a trusted CA takes the necessary steps to confirm the identity of a user before issuing the user a certificate Certificate technology is based on public private key technology There are a few different types of public private keys RSA DH and DSS As their name denotes the private key must be kept private like a password The public key can be given to anyone or even published in a newspaper A property of public private keys is that data encrypted with one can be decrypted only with the other Therefore if someone wants to send you a secret message they encrypt the data with your public key which everyone has However since you are the only one with your private key you are the only one who can decrypt it If you want to send someone message such as a request for 100 000 purchase you can sign it with your private key Note Signing does not encrypt the data Once a person receives your request that person can verify it is from you by verifying your electronic signature with your public key A certificate ties a statement of identity to a public key Without the public key the certificate is meaningless Posse
222. lest method of specifying configuration values that will not change with each command invocation The UDM Server configuration file name is specified in the UDM Server component definition The default name is UDSCFG00 The name refers to a member in the PDS allocated to the Universal Broker ddname UNVCOMF udm user 3207 Confidential amp Proprietary 134 Configuration Universal Data Mover Server for z OS 7 3 2 Configuration Options Figure 7 2 below identifies all UDM Server for z OS command options Each Option Name is a link to detailed information about that command option in the Universal Data Mover 3 2 0 Reference Guide ACTIVITY_MONITORING Specification for whether or not product activity monitoring events are generated ALLOC_ABNORMAL_DISP Abnormal disposition of a data set being allocated ALLOC_BLKSIZE Block size used for newly allocated data sets ALLOC_DATACLAS SMS data class used for newly allocated data sets ALLOC_DIR_BLOCKS Number of directory blocks for newly allocated partitioned data sets ALLOC_DSORG Data set organization used for newly allocated data sets ALLOC_INPUT_STATUS Status of data sets being allocated for input ALLOC_LRECL Logical record length used for newly allocated data sets ALLOC_MGMTCLAS SMS management class used for newly allocated data sets ALLOC_NORMAL_DISP Normal disposition of a data set being allocated ALLO
223. lls the user corruption is likely This is because text translation on the field level is governed by the DDS UDM does not support independent field level text translation Caution about Text Mode Transfer of Files with DDS In general files with DDS should be transferred using binary mode only There are instances when a user may want to use text mode However without an advanced user s thorough understanding of CCSID and code page unexpected results will occur As of Universal Products for OS 400 release 3 2 0 when the correct conditions are met UDM maps the code page attribute associated with the data stream to a CCSID This occurs only when data is transferred to a data physical file in text mode with an associated DDS file This mapping is used on the LIB file open to obtain translation between the data stream and data in fields with CCSIDs other than 65535 The translation is done by OS 400 UDM is in no way involved with this translation process udm user 3207 Confidential amp Proprietary 255 0S 400 I O Transfer Operations OS 400 Specific 14 2 5 Source Physical Files Support Source physical files have a common known DDS This DDS specifies the following record format e First six bytes contain a sequence number e Next six bytes contain a line modification date e Remaining number of bytes are text data This length can be between 1 and 32754 bytes for single byte character systems A single attribute
224. lows or denies access to Universal Data Mover Server services UDM_MGR_ACCESS Allows or denies access based on the host name and or user of the Manager trying to initiate a UDM session Table 9 3 UDM Server for UNIX UACL Entries udm user 3207 Confidential amp Proprietary 153 Security Universal Data Mover Server for UNIX UACL Examples The following set of rules permit services for the subnet 10 20 30 and denies all other connections udm_access 10 20 30 allow auth udm_access ALL deny auth The following set of rules effectively permit connections from any host but has limited access from host 10 20 30 40 to user TS1004 on that host No host can execute commands as local user root User TS1004 on host 10 20 30 40 can execute commands as local user tsup1004 without providing the password Users TS1004 from host 10 20 30 40 can execute commands as any local user by providing the local user password udm_access 10 20 30 40 TS1004 tsup1004 allow noauth udm_access 10 20 30 40 1TS1004 allow auth udm_access 10 20 30 40 deny auth udm_access ALL root deny auth udm user 3207 Confidential amp Proprietary 154 Chapter 10 Universal Data Mover Server for OS 400 10 1 Overview This chapter provides the following information on the Universal Data Mover UDM Server specific to the OS 400 operating system Component Definition e Configuration e Security u
225. lt yes EQ yes gt Conversely the following expression results in an error because the strings being compared are not quoted lt yes EQ yes gt For these next two examples assume that a variable called myvar has been defined with a value of yes This expression results in an error because when myvar is referenced its value yes is not quoted lt myvar EQ yes gt Instead the correct expression should be lt myvar EQ yes gt Index Position and Sequence When working with strings the following policy regarding the inclusion exclusion of positional length index and sequences should be followed e Positional Index or Length Include the value at that position in the operations e Sequences Exclude the value in operations See deletestring insertstring and substring in the Universal Data Mover 3 2 0 Reference Guide udm user 3207 Confidential amp Proprietary 170 UDM Command Format UDM Scripting Language 11 3 5 Examples of Expressions gt gt gt X N VV VV aVV V set x lt 2 4 gt set y lt x 10 gt echo x y lt x y gt y 360 set x 4 set y 2 set z lt x y 10 gt echo z z 60 set x 10 z 20 set q lt x LT z gt echo q q 1 udm user 3207 Confidential amp Proprietary 171 Script Files UDM Scripting Language 11 4 Script Files You can execute UDM commands interactively or in ba
226. lt was used specify that key with the key parameter These parameters and the format of the file containing these parameters work exactly like the corresponding option in the open command The option parameter is used to pass options to the UCMD Server see the SCRIPT_OPTIONS option for UCMD Manager in the Universal Command 3 2 0 Reference Guide for more details Two streams of data come back from the remote command By default output from standard out and standard error of the remote command are written to standard out and standard error by the UDM Manager SYSPRINT and SYSOUT respectively under z OS The mergelog option can be set to yes if you want both output streams written to the UDM transaction log standard out under UNIX Windows and OS 400 SYSPRINT under z OS By default if the UDM Manager is invoked with tracing turned on tracing will be turned on in the UCMD Manager when UDM invokes it via the exec command Likewise if trace is turned off in the UDM Manager the UCMD Manager is invoked with tracing turned off You can override this behavior for the UCMD Manager invocation by setting the trace option in the call to the exec command There are some commands that require input from standard input To provide this input you must create a data element with the data command containing the input Specifying the name of the data element with the input parameter will cause the information in the data element to be sent over as
227. lue is less than the right hand value The less than comparator performs a numeric comparison The following are examples of the less than comparator if 0 LT 8 print msg 0 is less than 8 end if _rc LT 8 print msg No errors have occurred end if filename length LT 8 print msg The length of the filename is less than 8 end GT Greater Than The greater than comparator GT evaluates to true if the left hand value is greater than the right hand value As with the less than comparator the comparison is between to numeric values as in this example if 8 GT 0 print msg 8 is greater than 0 end LE Less Than or Equal The less than or equal comparator LE is similar to the less than comparator except that it evaluates to true if the left hand value is less than or equal to the right hand value as in these examples if 8 LE 8 print msg 8 is less than or equal to 8 end if filename length LE 8 print msg The length of the filename is less than or equal to 8 end udm user 3207 Confidential amp Proprietary 194 if Statement UDM Scripting Language GE Greater Than or Equal The greater than or equal comparator GE is similar to the greater than comparator except that it evaluates to true if the left hand value is greater than or equal to the right hand value as in this example if filename length GE 9 print msg The filename is longer than 8 characters end udm user 3207 Confid
228. m user 3207 Confidential amp Proprietary 288 UDM Manager for z OS Examples Examples A 2 UDM Manager for z OS Examples This section describes how to use UDM in the z OS environment It provides specific examples for the following topics which explain how to use UDM ina two party mode between z OS and UNIX Copy a File to an Existing z OS Sequential Data Set Copy az OS Sequential Data Set to a File e Copy a Set of Files to an Existing z OS Partitioned Data Set Copy a File to a New z OS Sequential Data Set Copy a Set of Files to a New z OS Partitioned Data Set For each topic there is an example as appropriate for both the DSN and DD file systems Note These z OS examples apply equally as well to the Windows operating systems with appropriate changes for the file system syntactical differences udm user 3207 Confidential amp Proprietary 289 UDM Manager for z OS Examples Examples A 2 1 Copy a File to an Existing z OS Sequential Data Set These examples copy in text mode one sequential file to another This is the simplest form of data transfer DD file system S1 EXEC UDMPRC APOUT DD DSN APP DATA DAILY DISP SHR UNVSCR DD 1 set _echo yes set _halton warn open unix sol9 user top098 pwd p100m filesys local dd cd unix opt app data mode type text copy unix datal0 txt local APOUT quit Nn ON DM BW YN For this first z OS example the following is a line by line explanat
229. ment variables are specified in the JCL EXEC statement PARM keyword Environment variables are part of the IBM Language Environment LE and as such are specified as LE runtime options The PARM value is divided into LE options and application options by a slash character Options to the left of the slash are LE options and options to the right are application options Example of setting an environment variable Set option UDMLEVEL to a value of INFO PARM ENVAR UDMLEVEL INFO UNIX Environment variables in UNIX are defined as part of the shell environment As such shell commands are used to set environment variables The environment variable must be exported to be used be a called program Example of setting an environment variable Set option UDMLEVEL to a value of INFO in a bourne bash or korn shell UDMLEVEL INFO export UDMLEVEL udm user 3207 Confidential amp Proprietary 43 Configuration Features Environment variables in Windows are defined as part of the Windows console command environment As such console commands are used to set environment variables Example of setting an environment variable Set option UDMLEVEL to a value of INFO SET UDMLEVEL INFO OS 400 Environment variables in OS 400 are defined with Command Language CL commands for the current job environment Example of setting an environment variable Set option UDMLEVEL to a value of INFO
230. meric representation of data under OS 400 The default code page for UDM is IBM037 This is the internal code page as well as the default external code page used for the control session and data session unless overridden by the configuration file or the CODEPAGE parameter on the open command data session only udm user 3207 Confidential amp Proprietary 260 Codepage CCSID Mappings Transfer Operations OS 400 Specific 14 3 1 CCSID Mapping In order to get data to and from a file with a given CCSID a corresponding CCSID matching the data session code page must be used in order to map the data correctly The data stream CCSID is mapped from the code page via the code page to CCSID mapping table By default internal tables provide this mapping however see the UDM Manager CODEPAGE_TO_CCSID_MAP configuration option or the UDM Server CODEPAGE_TO_CCSID_MAP configuration option in the UDM Reference Guide regarding setting up an external file If a mapping cannot be made the following occurs 1 Warning is issued to the user 2 Copy operation fails ASCII code pages can map to CCSIDs that are available in the HFS file system but not the LIB file system If one of these code pages is used a different warning should be issued that lets the user know that the mapping will work for HFS but the behavior in the LIB file system is indeterminate Table 14 1 below contains those mappings Note If a code page contains a das
231. mines the type of eo1 ASCII vs EBCDIC The default ASCII eo1 is n and the default EBCDIC eol is r 1 It is important to note the difference between eo1 definitions as just described and eo1 characters when transferred as data Due to code page translations and Unicode mappings that take place during data transfer translated values may be surprising Please refer to appropriate translation tables or Unicode mapping tables to understand the values used when eo1 and other control characters are transferred as data UDM provides default definitions and allows user defined eo1 attribute overrides in order to avoid translation surprises and associated difficulties The following example sets an end of line sequence of an exclamation point for a transfer server attrib mylogicalname eol udm user 3207 Confidential amp Proprietary 224 Transfer Modes and Attributes UDM Transfer Operations 12 7 4 Line Length and Line Operations Note The attributes discussed in this subsection apply solely to the destination side of the transfer Other attributes can be used to manipulate transferred data as well The 1inelen attribute is used to specify the length in characters of a line of data that has been transferred This value is independent of the end of line sequence and for record oriented file systems the transfer type If 1inelen is set to a value other than zero its default value UDM will manipulate the data according to
232. n process the Broker returns the components configuration data When the Universal Broker is operating in managed mode the configuration information for the various Universal Products is locked down and can be modified or viewed only via the Universal Management Console see Section 2 3 2 Managed Mode Configuration files are members of a PDSE The data set record format is fixed or fixed block with a record length of 80 No line numbers can exist in columns 72 80 All 80 columns are processed as data All configuration files are installed in the UNVCONF library See Section 2 2 6 Configuration File Syntax for the configuration file syntax udm user 3207 Confidential amp Proprietary 45 Configuration Features UNIX Configuration files are regular text files on UNIX Universal Broker searches for the configuration files in a fixed list of directories The Broker will use the first configuration file that it finds in its search The directories are listed below in the order they are searched etc opt universal etc universal Installation default etc stonebranch Obsolete as of version 2 2 0 etc usr etc universal usr etc stonebranch Obsolete as of version 2 2 0 usr etc Table 2 1 UNIX Configuration File Directory Search See 2 2 6 Configuration File Syntax for the configuration file syntax Although configuration files can be edited with any text editor for example Notepad
233. nager s internal variables that can be set by the user Stoneman s Tip The set command also can be used to set other UDM Manager variables See Section 6 45 set in the Universal Data Mover 3 2 0 Reference Guide for detailed information on using the set command Note You cannot use the set command to set the _lastrc variable Issuing the set Command 1 If the set command is issued without any parameters variables all of the global variables and their current values are displayed 2 If the set command is issued with variable names but no following equal signs the values to which the variables resolve are displayed 3 Ifthe set command is issued with variable names followed by an equal signs but no values the values are set to an empty string 16 3 2 Return Codes in return Return Command You also can use the return command to set the return code value integer only in the _rc variable See Section 6 42 return in the Universal Data Mover 3 2 0 Reference Guide for detailed information on using this command udm user 3207 Confidential amp Proprietary 287 Appendix A Examples A 1 Overview This chapter provides operating specific examples that demonstarte the use of Universal Data Mover UDM Manager for z OS Examples e UDM Manager for UNIX and Windows Examples UDM Manager for OS 400 Examples The first example in each section provides a line by line explanation of that example ud
234. names Changes for UDM Release 1 1 0 February 17 2004 Release Added control and data session cipher list configuration to UNIX UDM Server configuration section Added information about the NULL NULL cipher to the documentation for the OPEN command Added information about the NULL NULL cipher for the data session in the UDM Server configuration sections Updated UDM Manager configuration sections with information about setting the default transfer mode type Updated information about default port in the UDM Manager configuration sections Added information about a message timestamp to the MESSAGE_LEVEL configuration option for UNIX and z OS versions of UDM Added documentation on the resetattrib command udm user 3207 Confidential amp Proprietary 12 Contents Summary of CHANGES so wien eden ee Sie wee a we nrnna anann 5 Contents sepo isc coerce ale owt Geld Bbw a o a A Sree le soe dy Ade prada Ea E WYeiie a wth ROR cae ae 13 List OF FiQUICS ion tebe ethene tae ew eared ies ban eae eed DERE nae wares 25 Listof Tables M ies iaa iaa a Mala Ad 27 A Re Er E re 30 Document Structure o 30 Format cee hoses A O a selene guna eater 30 Conventions 31 Vendor References cc cece teeta 32 Document Organization ci csece Signe rd a a 33 Chapter 1 OVervieW 0000 cia a aaa 34 1 1 Introduction to Universal Data Mover 0000 34 1 2 Transfer Components o 35 1 2 1 Managen misesa aaae a o i vaa
235. nent Definition 0 002 000 eee 133 Tea COMMGUIAMON sepas pl ed ews See a Oh Eesha ed eee Loe ewe 134 7 3 1 Configuration File 2cii 20k crea ern eeeeRaaxciked aCe AR 134 7 3 2 Configuration Options 450 26 cee nbs e ove eer eee h ieee Dawe 135 TA OO seriei d riren ees snc e ahh eteade ens acon aanhe Sa eee eee 137 7 4 1 File Permissions 0 0 00 ccc ee eee eens 137 7 4 2 Configuration Files tnccd decree cotarro a e 137 7 4 3 Universal Data Mover Server UserID 20 2000000 0 137 7 4 4 User Authentication 2 0 0 0 0 eee eee 137 7 4 5 Universal Access Control List 000 0c cece eee 138 UACL ENIES uri dew sew eA Kaa ee Eas we ate eG et dhe bows 138 WVACLIEXAMpIES i i 284 5844 00245 aed head doe w ERA Re 139 Chapter 8 Universal Data Mover Server for Windows 000 cece eee eeee 140 81 OVEIVIGW 422 24 0045 284k eee he ee a hae Pe eRe ees 140 8 2 Component Definition 0 0000 ee 141 8 3 Configuration ot serra ss sew B a we whew aed 143 8 3 1 Configuration File osuna an eee ee OR ew ae REDS Meee Raw 143 8 3 2 Configuration Options ocio ds e ee ease 144 84 OO anete e 3p bees adh Oma ay eens Ree eee saa Sale a 145 8 4 1 File Permissions o oo o oooooooooo eee eee eee 145 8 4 2 Configuration Files os ccesnee ses tteu cerros seaweed edsaeeane ane 145 8 4 3 Universal Data Mover Server UserID 20000000 145 8 4 4 User Authentication 2 0 0 onnaa
236. nent Definition e Configuration e Security udm user 3207 Confidential amp Proprietary 140 Component Definition Universal Data Mover Server for Windows 8 2 Component Definition PJ Universal Configuration Manager NX Installed Components Component Definitions A a 4 All Universal Products 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 3 2 0 User Guide The syntax of a component definition file is the same as a configuration file See Section 2 2 6 Configuration File Syntax for detailed syntax information Although component definition files can be edited with any text editor for example Notepad the Universal Configuration Manager application is the recommended way to edit component definitions for Windows see Section 2 4 Universal Configuration Manager Note The component definitions for all Universal Products are identified in the Component Definitions property page of the Universal Broker see Figure 8 1 below Universal Application Container a Universal Broker Message Options Network Options Runtime Options H SSL Protocol Options Event Subsystem Options Access Control Lists Component Definitions Ac
237. network session is terminated immediately Certificate Verification The Universal Product must be configured with a list of trusted CA certificates When a peer certificate is received the trusted CA certificates are used to verify that the peer certificate is issued by one of the trusted CA s The trusted CA certificate list must be properly secured so that only authorized accounts have update access to the list Should the trusted CA list become compromised there is a possibility that an untrusted CA certificate was added to the list The CA certificate list configuration option is CA_CERTIFICATES It specifies a PEM formatted file that contains one or more CA certificates used for verification Should a peer certificate not be signed by a trusted CA the session is immediately terminated Certificate Revocation After a certificate is verified to have come from a trusted CA the next step is to check if the CA has revoked the certificate Since a certificate is held by the entity for which it identifies a CA cannot take a certificate back after it is issued So when a CA needs to revoke a certificate for some reason it issues a list of revoked certificates referred to as the Certificate Revocation List CRL A program that validates certificates needs to have access to the latest CRL issued by the CA The CERTIFICATE_REVOCATION LIST configuration option specifies the PEM formatted file that contains the CRL This option is available
238. nfiguration option dsntype Type of SMS data set to allocate e Equivalent to the JCL DSNTYPE parameter DSNTYPE type No default or UDM configuration option dsorg Data set organization with which the data set is allocated Equivalent to the JCL DSORG parameter DSORG org Default is PS it can be set with the UDM configuration option ALLOC_DSORG expat e Expiration date of the data set Equivalent to the JCL EXPDT parameter EXPDT date No default or UDM configuration option label Data set label type used for mostly tape data sets Equivalent to the label sub parameter of the JCL LABEL parameter LABEL label e No default or configuration option like SMS data set name from which to model data set attributes Equivalent to the JCL LIKE parameter LIKE dsname No default or UDM configuration option Irecl e Logical record length with which the data set is allocated Equivalent to the JCL LRECL parameter LRECL len Default is 1024 it can be set with the UDM configuration option ALLOC_LRECL mgmtclas SMS management class name Equivalent to the JCL MGMTCLAS parameter MGMTCLAS name No default it can be set with the UDM configuration option ALLOC_MGMTCLAS normaldisp e Disposition of a data set after the job ends e Equivalent to the JCL DISP parameter DISP status normaldisp abnormaldisp Default is CATLG it can be set with the UDM configuration option
239. nininininnno 169 Table 11 3 Built In Variables ooccccccccncnnnnnnncnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnninininnnn 184 Table 11 4 _file Built in Variable Special Attributes oooccccccccccncccniccncccnnnnnnnns 186 Chapter 12 UDM Transfer Operations 2 0c eee 209 Table 12 1 CFS Terminology for Hierarchical File Systems cccceceesceeteeeeeeees 216 Table 12 2 CFS Terminology Associated with z OS Data Sets ooooccciccciccncccncccnnnn 218 Table 12 3 CFS Terminology Associated with z OS ddnames ceceeeeeees 218 Table 12 4 CFS Terminology Associated with LIB File Types ooocccicccicnncicncccnnnn 220 Chapter 13 Transfer Operations z OS Specific 220 222 e eee eee eee 235 Table 13 1 attrib Command Dynamic Allocation Attributes oocccicccininnicnnccninn 243 Table 13 2 cd Command in DSN File System cccceeeeeeseeeeeneneeeeseeteeeeneeeeeees 244 Table 13 3 copy Command File Specifications for Sequential Data Sets 246 Table 13 4 copy Command Destination File Specifications for Partitioned Data DOS sta a a 247 Table 13 5 copy Command Source File Specifications for Partitioned Data Sets 247 Table 13 6 copy Command Destination File Specifications for Sequential AANAMES sisas 248 Table 13 7 copy Command Source File Specification for Sequential ddnames 248 Table 13 8 copy Command Destination File Spe
240. nly trusted user accounts should have write permission to the Universal Data Mover Server configuration files 7 4 3 Universal Data Mover Server User ID Universal Data Mover Server requires read access to its installation data sets and its HFS working directory defined in the component definition 7 4 4 User Authentication User authentication is the process of verifying that a user is known and valid to the system The process used by UDM Server requires the user to provide a user name ID and a password The UDM Server passes the name ID and password to the operating system for verification this is referred to as logging on the user udm user 3207 Confidential amp Proprietary 137 Security Universal Data Mover Server for z OS 7 4 5 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 See Section 2 8 Universal Access Control List for details on the Universal Access Control List feature UACL Entries The syntax of a UACL entry file is the same as the UDM configuration file See Section 2 2 6 Configuration File Syntax for detailed syntax information Table 7 3 identifies all UDM Server for z OS UACL entries Each UACL Entry Name is a link to detailed information about that UACL entry in the Universal D
241. nsferred automatically in binary to the destination machine udm user 3207 Confidential amp Proprietary 258 0S 400 I O Transfer Operations OS 400 Specific 14 2 8 File Specifications File specifications in the LIB file system consist of up to three components library file and member that take the following form LIBRARY FILE MEMBER Note Data physical files and source physical files have members Save files do not 14 2 9 Wild Cards In source file specifications in the LIB file system for the delete command and for the copy command and file specifications for the forfiles statement wildcards can appear in the library file and or member portions An asterisk represents a match of zero or more characters A question mark represents a match of exactly one character Wildcards only apply to the library file or member portion of the fully qualified file name in which they appear For example in the statement COPY SRC ABC DEF the wildcard only applies to the file portion of the name and an error will result because the user did not provide a member name To copy all of the files that begin with DEF along with all of their members from library ABC use the format COPY SRC ABC DEF Likewise to copy all of the files and their members in libraries that begin with ABC use the format COPY SRC ABC In destination file specifications wild cards are not allowed Examples COPY SRC ABC DEF Co
242. nt 196 Alternate Path without else Statement o o oooococococooco o 196 Alternate Path with else Statement 2 0000 cece 197 11 7 3 Nested Conditionals 0 0 ee 198 11 7 4 Returning Early Using the return Command 0 05 199 11 8 while Statement 0 0 0 0 0 0000 cc teens 200 11 9 fordata Statement 0 00 00 tees 201 A eck hers toc aE bab hisGi sacha PhboG ae was ease 201 11 10 forfiles Statement 20 0000 0 ccc tee 202 11 10 1 forfiles Built In Variables 0 0 0 0 ccc ee 203 _file Variable Attributes 2 0 0 0 00 cee 204 11 10 2 forfiles File Specification 0 0 0 cc ee 205 11 10 3 Breaking Out Using the break Command 00000 206 11 11 Creating In Stream Data with the data Command 207 11 11 1 Creating an In Stream Data Element 000 0000 ee 207 EXample searre a ee daa a des 208 11 11 2 Printing Data Element Information ooooccccoooooo 208 Chapter 12 UDM Transfer Operations oooooocccccccooo o 209 12 1 Overview o oooococo tte tet eeteeeeeee 209 12 2 Transfer Sessions 00 ccc teenies 210 12 2 1 Opening a Transfer Session 00 cee eee eee 210 Opening a Two Party Transfer Session 2 000000 cee eee 210 Opening a Three Party Transfer Session o o ooooooooooooooo 211 12 2 2 Session Options 2
243. nt to the JCL BLKSZLIM parameter BLKSZLIM size No default or UDM configuration option dataclas SMS data class name Equivalent to the JCL DATACLAS parameter DATACLAS name No default it can be set with the UDM configuration option ALLOC_DATACLAS udm user 3207 Confidential amp Proprietary 240 UDM Commands under z OS Transfer Operations z OS Specific datasetseq Data set sequence number that specifies the relative position of a tape data set on the volume Equivalent to the data set sequence sub parameter of the JCL LABEL parameter LABEL datasetseq No default or UDM configuration option ddndcbref DCB reference to a ddname Equivalent to the ddname sub parameter of the JCL DCB parameter DCB ddname No default or UDM configuration option den e Tape density to use Equivalent to the DEN sub parameter of the JCL DCB parameter DCB DEN density No default or UDM configuration option dirblocks Number of directory blocks to allocate for a partitioned data set Equivalent to the third positional parameter of the second positional parameter of the JCL SPACE parameter SPACE dirblocks e Default is 20 it can be set with the UDM configuration option ALLOC_DIR_BLOCKS dsndcbref DCB reference to a cataloged data set name Equivalent to the data set name sub parameter of the JCL DCB parameter DCB dsn No default or UDM co
244. ntax Operating System Specific Text Most of this document describes the product in the context of all supported operating systems At times it is necessary to refer to operating system specific information This information is introduced with a special header which is followed by the operating system specific text in a different font size from the normal text This text pertains specifically to the z OS line of operating systems This text resumes the information pertaining to all operating systems udm user 3207 Confidential amp Proprietary 31 Preface Tips from the Stoneman Look to the Stoneman for suggestions or for any other information that requires special attention Stoneman s Tip Vendor References References are made throughout this document to a variety of vendor operating systems We attempt to use the most current product names when referencing vendor software The following names are used within this document z OS is synonymous with IBM z OS and IBM OS 390 line of operating systems Windows is synonymous with Microsoft s Windows 2000 2003 2008 Windows XP Windows Vista and Windows 7 lines of operating systems Any differences between the different systems will be noted UNIX is synonymous with operating systems based on AT amp T and BSD origins and the Linux operating system OS 400 is synonymous with IBM OS 400 IBM i 5 and IBM i operating systems AS 400 is synonymous for IBM A
245. number of connections needed for three party transfers see Section 1 3 3 Three Party Transfer Sessions 1 2 3 Secondary Server The secondary server acts as the second endpoint in a transfer operation Data is transferred between primary and secondary servers with either endpoint able to act as the source in a transfer operation udm user 3207 Confidential amp Proprietary 35 Transfer Sessions Overview 1 3 Transfer Sessions As discussed in Section 1 2 Transfer Components transfer operations take place within the context of a transfer session A transfer operation is initiated once the UDM Manager has established a transfer session with the primary and secondary transfer servers All subsequent transfer operations take place between the primary and secondary transfer servers UDM transfer sessions can be either two party or three party 1 3 1 Logical Names When a transfer session is established the user gives each server a unique logical name Commands addressed to a particular server reference this logical name 1 3 2 Two Party Transfer Sessions For a two party transfer session the UDM Manager also acts as the primary transfer server running in the directory and under the user ID under which the UDM Manager was launched This means that the machine on which UDM Manager resides is the first endpoint of the transfer With a two party transfer session the secondary server is invoked by the manager primary se
246. ny determine whether the session can be established between the manager and primary server using this certificate A similar thing happens when setting up the remainder of the three party transfer session between the primary and secondary There are some differences though A UDM server cannot have a certificate of its own so the primary server in a three party transfer session obtains its certificate from the broker in effect it uses the Broker s certificate running on that machine to try to establish a connection with the secondary If certificate access rules in the UACL configuration file on the secondary are used to allow or deny this connection with the secondary they must refer to the Broker s certificate on the primary See Section 1 3 Transfer Sessions for further information on two party and three party transfer sessions In order to help minimize the amount of certificate management and set up that needs to be done with a large number of systems UDM provides alternative way of using certificates in a three party transfer session proxy certificates A proxy certificate is a certificate generated on the fly that is signed by an original certificate holder and allows the holder of the proxy certificate to act on behalf of as the proxy of the original certificate holder In a three party UDM session this removes the need to use the Broker s certificate on the primary when establishing a connection from the primary to the
247. o re establish a transfer session when a network fault occurs udm user 3207 Confidential amp Proprietary 135 Configuration Universal Data Mover Server for z OS RECONNECT_RETRY_INTERVAL Number of seconds that UDM will wait between each successive attempt to re establish a transfer session when a network fault occurs RECV_BUFFER_SIZE Size of the TCP receive buffer for UDM SEND_BUFFER_SIZE Size of the TCP send buffer for UDM TCP_NO_DELAY Specification for whether or not to use TCP packet coalescing TMP_DIRECTORY Directory that UDM Server uses for temporary files TRACE_FILE_LINES Maximum number of lines to write to the trace file TRACE_TABLE Size of a wrap around trace table maintained in memory UMASK File mode creation mask USER_SECURITY User security option Table 7 2 UDM Server for z OS Configuration Options udm user 3207 Confidential amp Proprietary 136 Security Universal Data Mover Server for z OS 7 4 Security Universal Data Mover Server security concerns are Access to product data sets Access to Universal Product configuration files Universal Broker user account Privacy and integrity of transmitted network data User authentication Oe ONS 7 4 1 File Permissions Only trusted user accounts should have write permission to the Universal Data Mover Server installation data sets No general user access is required 7 4 2 Configuration Files O
248. ocation of the configuration spool file from which the Broker retrieves configuration information for all Universal Products Universal Broker updates its memory from the configuration spool file and automatically after changes are made via UMC If more configuration information than needed is included in the Universal Broker configuration file at Universal Broker start up Universal Broker will update its running configuration with the information that it retrieved from the spool file The configuration file that was used at start up is made obsolete udm user 3207 Confidential amp Proprietary 51 Universal Configuration Manager Features 2 4 Universal Configuration Manager The Universal Configuration Manager is a Universal Products graphical user interface application that enables you to configure all of the Universal Products that have been installed on a Windows operating system It is the recommended method of specifying configuration data that will not change with each command invocation Universal Configuration Manager helps protect the integrity of the configuration file by validating all changes to configuration option values The configuration data for a Universal Products for Windows system is stored in the configuration file 2 4 1 Availability Universal Configuration Manager is installed automatically on the Windows operating system as part of every Universal Products for Windows installation It is available
249. oking Stoneman s Tip UDM script files with s and o command line options SCRFILE and OPTIONS command parameters under OS 400 udm user 3207 Confidential amp Proprietary 173 Script Files UDM Scripting Language 11 4 3 Invoking Scripts from within Scripts As mentioned in the previous section scripts can use the ca11 command to invoke other scripts Scripts can be nested up to ten levels deep As each script finishes processing control is returned to the script that invoked it immediately following the point of invocation When nesting scripts parameters from higher level invocations are available to scripts invoked at a lower level If the same parameter name is used in more than one invocation of a series of nested scripts the value for the instance of the parameter at the lowest level is used 11 4 4 Parameter Processing A parameter is referenced inside of a UDM script using the following format parameter_name When a parameter reference is encountered it is replaced with the value of parameter matching the enclosed name Continuing with copyfiles udm script example used previously in this section 11 4 Script Files a reference to source would be replaced with c source An example of how the copyfiles udm script might look is as follows cd src source cd dst dest copy src file In this example 1 Transfer server with the logical name src would change its directory to c source 2
250. only the destination is operating in the LIB file system produce slightly different results The following rules apply for e Copies from non OS 400 machines to an OS 400 machine operating in the LIB file system e Copies from OS 400 machines working in the HFS file system to an OS 400 machine operating in the LIB file system These operations do not make use of source attributes describing all the library and file portions of the source file specification in the following example the source file being copied is MYFILE and the current library on the destination side is MYDSTLIB 1 If the destination file specification contains an empty path no library file or member portions the source file name is used for the file and member names on the destination side If the destination file is to be a save file the absolute path in this case would be DSTLIB MYFILE If the destination file is to be a physical file the absolute path would be DSTLIB MYFILE MYFILE Example COPY SRC MYFILE DSTLIB MYFILE MYFILE will be used as the destination name if the destination file type is a physical file and DSTLIB MYFILE will be used if the destination file type is a save file 2 If the destination file specification contains only a file portion the current library is pre pended to the absolute path and the source file name is used for the member if it applies In this case if the destination file is to be a save file the absolute path woul
251. only when a new file is being created If UDM is replacing or appending to an existing source physical file the values of SEQSTART and SEQINCR of the existing destination file are used udm user 3207 Confidential amp Proprietary 256 OS 400 I O Transfer Operations OS 400 Specific 14 2 6 Copying Source Physical Files Source physical files can be copied in both text and binary mode There are three possible copy operations involving source physical files 1 Like Copies of Source Physical File Data 2 Non Source Physical to Source Physical Copies 3 Source Physical to Non Source Physical Copies Like Copies of Source Physical File Data OS 400 to OS 400 copy both the source and destination are source physical files In this case if the sequence and date fields are not stripped from the source this data is written as is to the destination If the fields are stripped the SEQSTART and SEQINCR attributes define how the sequence data is generated described later in this section and the current date is placed in the date field Non Source Physical to Source Physical Copies Non source physical file is the source and a source physical file is the destination In this case the SECSTART and SEQINCR attributes are used to create the sequence number and the date field is seeding with the current date Source Physical to Non Source Physical Copies Source records are read and formatted as described above and the destination sy
252. ons on variable names except e They cannot contain double quote marks or spaces UDM reserves variable names beginning with an underscore _ for its own internal built in variables see 11 6 8 Built in Variables You cannot create a script variable or user defined global variable that begins with an underscore _ 11 6 2 Variable Reference To obtain the value of a variable you must create a reference for that variable The reference can appear anywhere in a script line It is replaced with the value of the referenced variable Referencing the value of a global variable in a script is done exactly the same way as for a script variable variable_name For example set srcfile myfile txt set dstfile yourfile txt copy src srcfile dst dstfile udm user 3207 Confidential amp Proprietary 178 UDM Variables UDM Scripting Language 11 6 3 Script Variables Script variables are user defined variables visible only to a called script and any of its children for which they have been defined When the called script has ended the script variables definitions are removed from the scripting engine environment You must use the ca11 command to define script variables The variables are specified as parameters in a call command after the script name that loads and executes a script They are created during execution of the script The value of a script variable cannot be changed once it has been created
253. or exec in _lastrc and _rc tells you whether exec was successful in executing the command that it was supposed to execute while _execrc is the return code of that executed command The value of _execrc can be set using the set command udm user 3207 Confidential amp Proprietary 185 UDM Variables UDM Scripting Language _file The _ file built in variable contains the name of the file for the current iteration in a forfiles loop _file also has special attributes as shown in Table 11 4 below For information on using _file and its special attributes see _file Variable Attributes in Section 11 10 1 forfiles Built In Variables accessdate Date on which the file was last accessed Format ISO 8601 is yyyy mm dd accesstime Time when the file was last accessed Format ISO 860 is hh mm ss accesstimestamp Combination of accessdate and accesstime yyyy mm dd hh mm ss If the file does not have an access time but does have a access date 00 00 00 is used for the time portion createdate Date on which the file was created Format ISO 8601 format of yyyy mm dd createtime Time when the file was created Format ISO 8601 is hh mm ss createtimestamp Combination of createdate and createtime yyyy mm dd hh mm ss If the file does not have a creation time but does have a creation date 00 00 00 is used for the time portion moddate Date on which the file was last modified referenced for z OS
254. ost all data set allocation attributes can be specified as UDM attributes giving you the ability to dynamically allocate any supported Data Physical File Care should be taken that conflicting allocation attributes are not specified The results of the allocation should be checked to verify they meet your intentions Although UDM checks attribute values some values are provided by the system from sources that UDM cannot verify and can result in invalid or unintentional attribute combinations udm user 3207 Confidential amp Proprietary 306 UDM Manager for OS 400 Examples Examples A 4 5 Copy a File to a New 0S 400 Source Physical File This example copies in text mode a file from a remote UNIX system to a Source Physical File on OS 400 The Source Physical File does not exist on OS 400 UDM is instructed to create it The Source Physical File is allocated based on the local UDM allocation attributes UDM provides default attributes that can be changed to meet local requirements The UDM defaults as delivered create a Data Physical File with a logical record length of 92 and maximum members of 1 This example changes the file type to src in order to demonstrate how to set allocation attributes LIB file system set _echo yes _halton warn open unix sol9 user top098 pwd p100m cd unix opt app data mode type text attrib local filetype src copy unix datal0 txt local MYLIB APPDATA DAILY quit NOM PWN pp Alm
255. ost all data set allocation attributes can be specified as UDM attributes giving you the ability to dynamically allocate any supported Data Physical File Care should be taken that conflicting allocation attributes are not specified The results of the allocation should be checked to verify they meet your intentions Although UDM checks attribute values some values are provided by the system from sources that UDM cannot verify and may result in invalid or unintentional attribute combinations udm user 3207 Confidential amp Proprietary 307 UDM Manager for OS 400 Examples Examples A 4 6 Copy a Set of Files to a New Data Physical File on OS 400 This example copies in text mode a set of files from a remote UNIX system to a data physical file on OS 400 The data file does not exist on OS 400 UDM is instructed to create it The data set is allocated based on the local UDM allocation attributes UDM provides default attributes that can be changed to meet local requirements The UDM defaults as delivered create a data physical file with a logical record length of 92 and maximum members of 1 This example changes the record length to 80 and the maximum members to unlimited nomax LIB file system set _echo yes _halton warn open unix sol9 user top098 pwd p100m cd unix opt app data mode type text attrib local maxmbrs nomax rcdlen 80 truncext yes copy unix txt local MYLIB APPDATA quit N DO Ww bh WN A u
256. ot and QOpenSys are certified Currently Stonebranch Inc Does not support other IFS file systems e Recommends that users do not use other IFS file systems e Provides no warranty for use of other IFS file systems e Certifies that users assume all risks in using other IFS file systems Risks involved in the use of non supported IFS files systems include but are not limited to Loss of data Corrupted data Non recoverable exceptions 12 6 1 HFS HFS follows the common file system CFS It supports stream files under the root and QOpenSys IFS file systems Users using UDM to access file systems under IFS other than root and QOpenSys do so at their own risk udm user 3207 Confidential amp Proprietary 219 OS 400 File Systems UDM Transfer Operations 12 6 2 LIB UDM for OS 400 supports the following file types of the LIB library file system e Physical files source and data e Save files Table 12 4 below associates CFS terminology with these LIB file types path An absolute or relative path Examples MYLIB DATA NAMES DATA NAMES An absolute or relative path Examples MYLIB BACKUP BACKUP absolute path A fully qualified name containing a library file and member Example MYLIB DATA NAMES A fully qualified name containing a library and file Example MYLIB BACKUP relative path A name without a library The name is relative to the current
257. ows Each Option Name is a link to detailed information about that configuration option in the Universal Data Mover 3 2 0 Reference Guide ACTIVITY_MONITORING Specification for whether or not product activity monitoring events are generated CA_CERTIFICATES File name ddname of the PEM formatted trusted CA X 509 certificates CERTIFICATE File name ddname of UDM Manager s PEM formatted X 509 certificate CERTIFICATE_REVOCATION_LIST File name ddname of the PEM formatted CRL CODE_PAGE Character code page used to translate text data received and transmitted over the network COMMENT User defined string CTL_SSL_CIPHER_LIST Acceptable and preferred SSL cipher suites to use for the control session between UDM components DATA_COMPRESSION Specification for whether or not data is compressed on all standard 1l O files DATA_SSL_CIPHER_LIST Acceptable and preferred SSL cipher suites to use for the data session on which file data is transferred between UDM primary and secondary servers EVENT_GENERATION Events to be generated as persistent events FRAME_INTERVAL Number of UDM transfer blocks transferred before a frame sync message is sent when UDM is operating with network fault tolerance turned on HELP Writes a description of the command options and their format IDLE_TIMEOUT Number of seconds of inactivity in an interactive UDM session after which the manager will close the session INSTAL
258. p Proprietary 235 z OS I O Transfer Operations z OS Specific 13 2 z OS I O This section provides an overview of the z OS file systems 13 2 1 Data Sets There are a variety of data sets on z OS The UDM supported data set organizations and data set attributes are listed below Data Set Names A z OS data set name is composed of one or more qualifiers separated by periods A data set has a maximum length of 44 characters A qualifier has an maximum length of eight characters The first character of a qualifier must start with A Z O or The remaining characters can be 0 9 A Z O or The first qualifier is commonly referred to as the high level qualifier HLQ An example data set name is SYS1 CEE CEEPRC where e SYS1 is the high level qualifier e CEE is the second qualifier e CEEPRC is the third and last qualifier In some applications contexts the HLQ can be left off TSO and ISPF are such applications UDM also behaves in this manner A distinction is the made between a data set that specifies the HLQ and one that does not specify the HLQ When the HLQ is specified it is referred to as a fully qualified data set name and is enclosed in apostrophes udm user 3207 Confidential amp Proprietary 236 z OS I O Transfer Operations z OS Specific Data Set Organization A data set s organization is obtained from the VTOC s format 1 DSCB If the data set is cataloged the DSCB is only
259. p Matching Criteria cccceceneeeeeseeeeeeeeeeeeeeeeeseneeeeeneees 79 Table 25 Certificate Identifier Field ooonnnncnnncnnnnnnncnnnnonicniccnncnnncrnncrnnrnnnrrnnrrns 79 Table 2 6 Client IP Address Matching Criteria ooonnonnccnnnnnnnnnnncccccnccnccnnnnnanarcccnnnn 80 Table 2 7 Certificate Fields ooooooncnncnnnnnnnnccnnccnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnns 91 Chapter 3 Universal Data Mover Manager for z OS oooooooconoomonmmmmmoo 94 Table 3 1 UDM Manager for z OS DD Statements in JOL oociiniicicicinicicccnocnonnnos 97 Table 3 2 UDM Manager for z OS Configuration Options coccciccncccnicnncccnncnicnn 102 Chapter 4 Universal Data Mover Manager for Windows 000 eee eee eee ees 107 Table 4 1 UDM Manager for Windows Configuration Options ceee 111 Chapter 5 Universal Data Mover Manager for UNIX 0 0 e ee eee eee eee eee 114 Table 5 1 UDM Manager for UNIX Configuration Options ccocccicccicnnnccincinnnn 118 Chapter 6 Universal Data Mover Manager for OS 400 1 0 cece eee 122 Table 6 1 UDM Manager for OS 400 Configuration Options cocooccccicnnncinnccinn 128 Chapter 7 Universal Data Mover Server for Z OS 1 0 0c ccc es 132 Table 7 1 UDM Server for z OS Component Definition Options o 133 Table 7 2 UDM Server for z OS Configuration Options ooomononncccnnnnnnncccocccccnnnnns
260. pies all files beginning with DEF from all libraries beginning with ABC COPY SRC ABC DEF Copies all the members in the physical file DEF in the library ABC DELETE SRC MYLIB MYFILE Deletes all files in the library MYLIB starting with MYFILE and containing one additional character FORFILES SRC Lists all members in all files in all libraries udm user 3207 Confidential amp Proprietary 259 Codepage CCSID Mappings Transfer Operations OS 400 Specific 14 3 Codepage CCSID Mappings Information that is stored moved and displayed on OS 400 has a CCSID Coded Character Set IDentifier number associated with it UDM uses these CCSID numbers where appropriate when creating data files transferring data and storing data Each language available on OS 400 has an associated CCSID The CCSID identifies the mapping of numeric representations associated with each letter or symbol represented by the computer It also identifies the glyphs required to represent those characters and symbols when displayed UDM is not concerned about the display aspect of a CCSID or the associated data only about the mapping between these numeric representations Code pages provide one mechanism of mapping translating between these numeric representations Another means of representing these mappings is to use two CCSIDs one for the data origin and another for the data destination For example when writing data to a file on OS 400
261. ples COPY SRC MYLIB MYFILE MYMBR DST YOURFILE The result is a destination name of DSTLIB YOURFILE MYMBR if the destination file type is a physical file COPY SRC MYLIB MYFILE DST YOURFILE The result is a destination name of DSTLIB YOURFILE if the destination file type is a save file 3 Ifthe destination file specification contains only a file portion with an empty member the result is exactly the same as when just a destination file name is given Example COPY SRC MYLIB MYFILE MYMBR DST YOURFILE The result is a destination name of DSTLIB YOURFILE MYMBR if the destination file type is a physical file udm user 3207 Confidential amp Proprietary 271 Command Reference Transfer Operations OS 400 Specific If the destination file specification contains only file and member portions the resulting absolute path is DSTLIB YOURFILE YOURMBR if a physical file is wanted Example COPY SRC MYLIB MYFILE MYMBR DST YOUFILE YOURMBR The result is a destination name of DSTLIB YOURFILE YOURMBR if the destination file type is a physical file If the destination file specification contains only a library portion that library is used instead of the current library In this case an absolute path of YOURLIB MYFILE is used if a save file is wanted If a physical file is wanted an absolute path of YOURLIB MYFILE MYMBR is used Examples COPY SRC MYLIB MYFILE MYMBR DST YOURLIB The result is a destination name of YO
262. ples The following example uses the exec command to execute a simple directory listing on a Windows machine that is part of a transfer session exec winmachine cmd dir c The following example uses the exec command to invoke a started task exec mvsmachine stc mytask parm TASK_PARM The following example calls the exec command that uses a data element for input to the remote command Define the data element data shellinput echo Comparing _file with _file old diff _file _file old exit end Rename all existing files on the destination forfiles dst rename dst _file _file old end Copy the new files over and compare them forfiles src copy src _file exec dst cmd sh input she11input end udm user 3207 Confidential amp Proprietary 282 execsap Command Remote Execution 15 3 execsap Command 15 3 1 Triggering SAP Events within UDM If you have a licensed version of the Universal Connector version 3 1 1 or later on the same system with the UDM Manager you can execute SAP events using the execsap command The execsap command has the following format execsap host host name destination type event generic eventid event 7d parm event parm client c 7ent user userid pwd password codepage codepage file F7 ename xfile f7 7ename key key mergelog yes no trace yes no Note UDM does not support the execsap command for OS 400 and Windows The first
263. pports two types of file systems 1 LIB Library file system 2 HFS IFS root and QOpenSys The default file system for UDM on the OS 400 is LIB 14 2 2 HFS for 0S 400 File System HFS follows the CFS rules in Section 12 4 UDM Common File System It supports stream files under the root and QOpenSys IFS file systems Users using UDM to access file systems under IFS other than root and QOpenSys do so at their own risk HFS also provides enhanced eo1 handling and eo attribute values for the mixed ASCII and EBCIDIC environment See Section 12 7 3 End of Line Sequence for details 14 2 3 LIB File System LIB follows the extensions to CFS outlined in Section 8 5 2 LIB File Types UDM for OS 400 supports three file types of the LIB file system 1 Data Physical Files 2 Source Physical Files 3 Save Files The type of file created in a copy command on the destination side is governed by the OS 400 specific FILETYPE attribute see Table 14 2 OS 400 Specific LIB File Attributes for Creating New Files The default file type created in a copy command is a data physical file udm user 3207 Confidential amp Proprietary 254 0S 400 I O Transfer Operations OS 400 Specific 14 2 4 Data Physical Files Support UDM for OS 400 supports data physical files with a CCSID and with no DDS default CCSID of 65535 If a DDS is attached to a data physical file on the source side that same DDS is used when doing an OS 400
264. prietary 216 z OS File System UDM Transfer Operations 12 5 z OS File System The z OS data set file system is a flat file system There are no concepts of directories The files are more commonly referred to as data sets z OS data sets supported by UDM fall into two major categories Sequential Sequential data set has a data set organization of Physically Sequential PS e Partitioned Partitioned Data Set PDS has a data organization of Partitioned Organization PO which also includes system managed Partitioned Data Set Extended PDSE organization A PDS is treated as a directory in CFS A PDS contains a set of individual files called members which is analogous to a directory containing a set of files A PDS member has a maximum length of 8 characters Table 12 2 below associates CFS terminology with z OS partitioned and sequential data sets Fully qualified data set names are enclosed in apostrophes path Data set name A path includes fully qualified names and relative names Examples PHONE DATA MYUID PHONE DATA PDS name and member name in parenthesis or just a member name A path includes fully qualified names and relative names Examples JCL CNTL JOBAB MYUID JCL CNTL JOBAB JOBAB absolute path Fully qualified data set name Example MYUID PHONE DATA Fully qualified PDS name and member name in parenthesis Example MYUID JCL CNTL JOB
265. property pages The text describes the selected component Universal Data Mover Manager Universal Configuration Manager E Universal Application Container S E Universal Broker H Universal Command Manager El Universal Command Server E Universal Control Manager E Universal Control Server sal Data Mover Manager i Message Options Network Options Data Transfer Fault Tolerance i Runtime Options E SSL Protocol Options Certificate Options Event Subsystem Options License Information niversal Data Mover Serve ni i t gitin ise Figure 2 5 Universal Configuration Manager UDM Manager udm user 3207 Confidential amp Proprietary 58 Universal Configuration Manager Features Universal Data Mover Server Figure 2 6 illustrates the Universal Configuration Manager screen for the Universal Data Mover Server The Installed Components list identifies all of the UDM Server property pages The text describes the selected component Universal Data Mover Server 3 Universal Configuration Manager Universal Application Container 4 Universal Broker t Universal Command Manager H Universal Command Server Universal Control Manager Universal Control Server H Universal Data Mover Manager S Universal Data Mov i Message Options i Server Options E Network Options Fault Tolerance i SSL Protocol Options Event Subsystem Options Access Control Lists Access ACL i Ac
266. r Windows and UNIX e Section 6 2 Invoking UDM Manager Under z OS e Section 6 3 Invoking UDM Manager Under OS 400 Added the OPEN_RETRY UDM Manager configuration option in the following sections e Section 3 1 Configuring UDM Manager of Section 3 Configuring UDM under UNIX e Section 4 1 Configuring UDM Manager of Section 4 Configuring UDM under z OS e Section 6 1 Invoking the UDM Manager under Windows and UNIX e Section 6 2 Invoking the UDM Manager Under z OS Changes for Universal Data Mover 3 1 1 User Guide udm user 31110 December 15 2006 Added List of Figures and List of Tables Added Customer Support Universal Data Mover 3 1 1 6 Added Section 1 4 Configuration File or System Registry udm user 3207 Confidential amp Proprietary 10 Summary of Changes Added Section 5 Configuring UDM under OS 400 e Added Section 6 3 Invoking the UDM Manager Under OS 400 e Added Section 8 5 OS 400 File Systems e Added Section 10 OS 400 Specific Transfer Operations Changed name of Configuration File Keyword from receive_buffer_size to recv_buffer_size throughout document e Added default values for options in Section 2 Configuring UDM under Windows e Added Section 2 3 1 Component Definitions to Section 2 3 Configuring Universal Data Mover Server Added the MERGE_LOG option to the following sections e 3 1 Configuring the UDM Manager of Section 3 Configuring UDM under UNIX e 4 1 Configuring the UDM Manager of Se
267. r message catalog and code page tables are located OUTBOUND_IP Host or IP address that UDM binds to when initiating outgoing connections to another UDM server RECONNECT_RETRY_COUNT Number of attempts that the UDM Manager will make to re establish a transfer session when a network fault occurs RECONNECT_RETRY_INTERVAL Number of seconds that UDM will wait between each successive attempt to re establish a transfer session when a network fault occurs RECV_BUFFER_SIZE Size of the TCP receive buffer for UDM SEND_BUFFER_SIZE Size of the TCP send buffer for UDM TCP_NO_DELAY Specification for whether or not to use TCP packet coalescing TMP_DIRECTORY Directory that UDM Server uses for temporary files TRACE_DIRECTORY Directory name that UDM Server uses for its Trace files TRACE_FILE_LINES Maximum number of lines to write to the trace file TRACE_TABLE Size of a wrap around trace table maintained in memory USER_SECURITY User security option Table 8 2 UDM Server for Windows Configuration Options Confidential amp Proprietary 144 Security Universal Data Mover Server for Windows 8 4 Security UDM Server is designed to be a secure system As the level of security rises so does the administrative complexity of the system UDM Server has balanced the two to avoid the administrative complexity with a minimum sacrifice to security UDM sec
268. ration and configuration options and command line syntax of UDM Manager for Windows Section 4 3 Examples of UDM Manager for Windows provides examples demonstrating the flexibility of Universal Data Mover 4 2 1 Modes of Operation Under Windows UDM can be run either in e Interactive mode e Batch mode Running UDM in Interactive Mode To invoke UDM in interactive mode enter the following at the command prompt udm This will start the UDM Manager You will be greeted with a startup message and the UDM prompt similar to this UNV2800I Universal Data Mover 3 2 0 Level 0 started udm gt At the udm gt prompt you can enter any UDM command To exit UDM enter the following command at the udm gt prompt quit Running UDM in Batch Mode When running in batch mode UDM processes a script file When the script file has finished executing UDM will exit automatically udm s script_filename udm user 3207 Confidential amp Proprietary 108 Usage Universal Data Mover Manager for Windows 4 2 2 Configuration Configuration consists of e Setting default options and preferences for all executions of UDM Manager e 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
269. rations z OS Specific DD ddname File System The DD ddname file system like the DSN file system has no directories DD is the simplest form of file system in UDM A ddname is defined with a JCL DD statement All the allocation attributes are specified with on the JCL DD statement UDM initializes the current directory to blanks in the DD file system A cd value specifies an allocated ddname to use as the current directory udm user 3207 Confidential amp Proprietary 245 UDM Commands under z OS Transfer Operations z OS Specific 13 3 3 copy Copy Command The copy command copies files between two systems The source and destination files are specified with a file specification The file specification syntax depends on the file system being referenced This section describes the syntax and semantics of the copy command s file specification The copy command also can be used to copy load modules see Section 13 4 Copying Load Modules DSN File System The semantics of a file specification is determined primarily by whether a sequential or a partitioned file is being referenced A sequential file is treated as a single entity in regards to reading and writing A partitioned file is treated as a composite of multiple sequential files each operated on individually Sequential Data Sets A file is considered sequential if it has a data set organization of Physical Sequential PS A file is referenced directly
270. rce side indicates that it is packaging the load modules into a temporary data set MYHLQ UDMTMP STC07047 R2EED53 NO000000 This is the temporary data set that is transferred using a data set name of YOURHLQ UDMTMP JOB07063 RD36420 N0000000 on the destination side It is from YOURHLQ UDMTMP JOB07063 RD36420 N0000000 that the load modules are unpacked into the temporary staging data set before being moved into the final destination PDS E YOURHLQ TEST LOAD which was specified in the copy command As you can see some of the output from a copy operation involving load modules may vary from the output when copying other types of data sets However the nomenclature of the copy command has not changed Likewise attributes such as CREATEOP DIRBLOCKS and others work the same way with load modules as they do with other types of data sets This includes the caveat that the attribute settings must be compatible with the type of data set s involved in the transfer 13 4 2 Error Reporting It is possible for the IEBCOPY portions of a load module transfer to fail If this occurs UDM prints the output from IEBCOPY in the transaction log 13 4 3 Special Attributes UDM uses heuristics in determining the space attributes for allocating the temporary data sets The volume that these data sets reside is chosen by the system The TMPVOLSER attribute lets you set the volume on which the temporary files will be allocated e Setting this at
271. re that the party you are communicating with your peer is who you believe A common form of network attack is a malicious user representing themselves as another user or host Peer authentication insures that the peer is truly who they identify themselves as Peer authentication applies to users computer programs and hardware systems SSL uses X 509 certificates and public and private keys to identify an entity An entity may be a person a program or a system A complete description of X 509 certificates is beyond the scope of this documentation Section 2 10 X 509 Certificates provides an overview to help get the reader oriented to the concepts terminology and benefits For additional details the following web site is recommended http www faqs org rfcs rtc3280 html udm user 3207 Confidential amp Proprietary 62 Network Data Transmission Features 2 5 2 Universal Products Protocol The Universal Products protocol UNVv2 is a proprietary protocol that securely and efficiently transports data across data networks UNVv2 is used in Universal Products prior to version 3 and will be available in future versions UNVv2 addresses data privacy and integrity It does not address peer authentication Data Privacy and Integrity Data privacy is insured with data encryption algorithms UNVv2 utilizes 128 bit RC4 encryption for all data encryption Data integrity is insured with message digest algorithms UNVv2 utilizes 128 bi
272. record for record based file systems such as dd and dsn in z OS udm user 3207 Confidential amp Proprietary 221 Transfer Modes and Attributes UDM Transfer Operations 12 7 2 Transfer Attributes While the mode command is used to control the settings for transfer operations as a whole the attrib command can be used to set up the handling of transfer operations for each side of the transfer session The attrib command can set transfer attributes that apply to either the primary or secondary server It takes the following form attrib Iname dd dsn hfs attribute 1 value1 attribute n valuen Where 1name is the logical name of the server the attributes are to be applied By default any attributes listed in the attrib command are applied to the currently selected files system unless a specific file system is assigned to the logical name In that case the attributes are applied to the specified file system The remainder of the attrib command contains a series of attributes and their values some of which will be discussed in further detail in the remainder of this section If the attrib command is issued with just a logical name UDM will list the currently set attributes for the corresponding server When you change file systems for a server using the filesys command the currently set attributes are those that were applied to that file system type In other words attributes are not carried over from one file syst
273. roker to be configured either e Locally by editing configuration files e Remotely via UMC The system administrator for the machine on which a Universal Agent resides can use any text editor to modify the configuration files of the various local Universal Products Via UMC selected users can modify all configurations of any Universal Agent including the local Universal Agent UMC sends the modified data to the Universal Broker of that agent which Universal Broker then uses to update the appropriate configuration files If UMC sends modifications for a Universal Broker configuration Universal Broker validates the modified data before it accepts it If the data fails validation Universal Broker does not update its configuration file If UMC sends modification to the configuration of any other Universal Products component the Universal Broker updates the appropriate configuration file The component will use this new configuration at its next invocation Note If errors or invalid configuration values are updated via UMC for a component other than Universal Broker the component may not run successfully until the configuration has be corrected udm user 3207 Confidential amp Proprietary 48 Remote Configuration Features 2 3 2 Managed Mode When a Universal Broker is operating in managed mode the configuration information for all Universal Products components managed by that Universal Broker is locked down Univers
274. rol panel using recommended settings This instructs the PCA to shim Microsoft term the Configuration Manager establishing it as an application that requires elevated privileges Windows Vista User Account Control UAC then displays a prompt seeking permission to elevate the logged in account s access token Select Continue to give the account full administrative privileges Subsequent attempts to open Universal Configuration Manager should result only in the UAC prompt udm user 3207 Confidential amp Proprietary 53 Universal Configuration Manager Features 2 4 2 Accessing the Universal Configuration Manager To access the Universal Configuration Manager 1 Click the Start icon at the lower left corner of your Windows operating system screen to display the Start menu Click Settings Control Panel on the Start menu to display the Control Panel screen Select the Universal Configuration Manager icon to display the Universal Configuration Manager screen see Figure 2 4 Windows XP Windows Vista Windows Server 2008 Newer versions of Windows support a Control Panel view that places applet icons within categories This category view may affect the location of the Universal Configuration Manager icon w N For example the Windows XP Category View places the Universal Configuration Manager icon under the Other Control Panel Options link Windows Vista and Windows Server 2008 place the icon within the Additional Opt
275. rsal Products utilize the Universal Access Control List UACL feature as an extra layer of security to the services they offer The UACL determines if a request is denied or allowed to continue and can assign security attributes to the request This section describes the UACL capabilities in general non component specific terms See the appropriate component security sections for complete details on how a component utilizes the UACL feature The following Universal Product components use the UACL feature Universal Broker uses UACLs to permit or deny TCP IP connections based on the remote host IP address See the Universal Broker User Guide for complete details Universal Command Server uses UACLs to permit or deny Manager access based on the Managers IP address and user ID and to control whether or not the Manager request requires user authentication See the Universal Command 3 2 0 User Guide for complete details Universal Control Server uses UACLs to permit or deny Manager access based on the Managers IP address and user ID and to control whether or not the Manager request requires user authentication See the Universal Control chapter of the Universal Products Utilities 3 2 0 User Guide for complete details Universal Data Mover Server uses UACLs to permit or deny Manager access based on the Managers IP address and user ID See the UACL section for each operating system in this user guide for complete details udm user 320
276. rt of the destination path name may be derived using a name or names in the case of OS 400 to OS 400 LIB file system copies coming from the source side of a transfer operation Source and Destination in LIB File System The following rules apply for OS 400 to OS 400 transfers where both the source and destination are operating in the LIB file system In these example the current destination library is DSTLIB and the absolute path of the source file being copied is MYLIB MYFILE MYMBR 1 If the destination file specification contains an empty path no library file or member portions the file and member portions are derived from the source path If the destination file is to be a save file the absolute path in this case would be DSTLIB MYFILE If the destination file is to be a physical file the absolute path would be DSTLIB MYFILE MYMBR Examples COPY SRC MYLIB MYFILE MYMBR The result is a destination name of DSTLIB MYFILE MYMBR if the destination file type is a physical file COPY SRC MYLIB MYFILE The result is a destination name of DSTLIB MYFILE if the destination file type is a save file 2 If the destination file specification contains only a file portion the current library is pre pended to the absolute path In this case if the destination file is to be a save file the absolute path would be DSTLIB YOURFILE If the destination file is to be a physical file the absolute path would be DSTLIB YOURFILE MYMBR Exam
277. rver via the Universal Broker The second endpoint of the transfer session will be on the machine in which the secondary server was spawned Transfer operations occur between the manager primary server and the secondary server See Figure 1 1 UDM Transfer Sessions 1 3 3 Three Party Transfer Sessions For a three party transfer session the UDM Manager acts solely as a control point for transfer operations sending commands to the primary and secondary servers to be executed Both the primary and secondary servers are spawned via the Universal Broker and transfer operations take place between the two machines under which these servers are running See Figure 1 1 UDM Transfer Sessions udm user 3207 Confidential amp Proprietary 36 Transfer Sessions Overview Two Party Transfer Files Transferred UDM Manager UDM Server Primary Secondary Three Party Transfer Files Commands Transferred UDM Server UDM Server UDM Manager Primary Secondary Figure 1 1 UDM Transfer Sessions udm user 3207 Confidential amp Proprietary 37 Chapter 2 Features 2 1 Overview This chapter provides information on Universal Data Mover UDM features that apply to all operating systems e Configuration e Universal Configuration Manager e Remote Configuration Network Data Transmission e Fault Tolerance z OS CANCEL Command Support e Universal Access Control List Message and Audit Facil
278. ryption a0 94 ca f4 d5 4f 2d da a8 6d e3 41 6e 51 83 57 b3 b5 31 95 32 b6 ca 7e d1 4f fb 01 82 db 23 a0 39 d8 69 71 31 9c 0a 3b ce f6 c6 e2 5c af 23 f0 d7 ee 87 3e 8a 7b 40 03 39 64 a1 8c 29 7d 5b 99 93 fa 23 19 e1l e4 ac 4d 13 0f de ad 51 27 e3 4e 4b 9f 40 4c 05 fd f2 82 09 3e 46 05 f0 ad cc f7 78 25 3e 11 f8 ca b6 df f7 37 57 9b 63 00 d0 b5 b5 18 ec 38 73 d2 85 a3 Cc7 24 21 47 ee f2 8c 0d Figure 2 8 X 509 Version 3 Certificate sample udm user 3207 Confidential amp Proprietary 90 X 509 Certificates Features Note The contents of a certificate file does not look like the information in Figure 2 8 which is produced by a certificate utility using the certificate file as input Certificates can be saved in multiple file formats so their file contents will look very different Certificate Fields A certificate is composed of many fields Table 2 7 below describes the main fields Version X 509 certificates come in two versions 1 and 3 Serial Number CA is required to provide each certificate it issues a unique serial number The serial number is not unique for all certificates only for the certificates issued by each CA Issuer DN name of the CA that issued the certificate Validity Starting and ending date for which this certificate is valid Subject Identity of the certificate A certificate may identify a person or a computer In this case the certificate identifies Joe B
279. s NETWORK_DELAY Expected network latency udm user 3207 Confidential amp Proprietary 117 Usage Universal Data Mover Manager for UNIX NETWORK_FAULT_TOLERANT NLS_DIRECTORY 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 OPEN_RETRY Level of fault tolerance for the open command OPEN_RETRY_COUNT Maximum number of attempts that will be made to establish a session by the open command OPEN_RETRY_INTERVAL Number of seconds that UDM will wait between each open retry attempt OUTBOUND_ IP Host or IP address that UDM binds to when initiating outgoing connections to another UDM server PLF_DIRECTORY Program Lock File directory that specifies the location of the UDM Manager program lock file PRIVATE_KEY ddname of Manager s PEM formatted RSA private key PRIVATE_KEY_PWD Password for the Manager s PRIVATE_KEY PROXY_CERTIFICATES Specification for whether or not UDM will use proxy certificates in three party transfer sessions if a certificate is supplied to the UDM Manager RECONNECT_RETRY_COUNT Number of attempts the manager will make to re establish a transfer session when a network fault occurs RECONNECT_RETRY_INTERVAL Number of seconds that UDM will wait between each successive attempt to re establish a
280. s modify enter data by clicking radio buttons selecting from drop down lists and or typing in data entry fields Some property pages provide panels that you must click in order to e Modify or adjust the displayed information e Display additional modifiable information Note You do not have to click the OK button after every modification or entry or on every property page on which you have modified and or entered data Clicking OK just once on any page will save the modifications and entries made on all pages and will exit Universal Configuration Manager see Section 2 4 5 Saving Data Rules for Modifying Entering Data The following rules apply for the modification and entry of data Quotation marks are not required for configuration values that contain spaces e Edit controls used to input free form text values handle conversion of any case sensitive configuration values Except where specifically noted values entered in all other edit controls are case insensitive udm user 3207 Confidential amp Proprietary 56 Universal Configuration Manager Features 2 4 5 Saving Data To save all of the modifications entries made on all of the property pages click the OK button at the bottom of any property page The information is saved in the configuration file and Universal Broker is automatically refreshed Clicking the OK button also exits the Universal Configuration Manager If you click OK after ever
281. s a save file YOURLIB YOURFILE is used If the destination file type is a physical file YOURLIB YOURFILE YOURMBR is used Examples COPY SRC MYLIB MYFILE MYMBR DST YOURLIB YOURFILE YOURMBR The result is a destination name of YOURLIB YOURFILE YOURMBR if the destination file type is a physical file COPY SRC MYLIB MYFILE DST YOURLIB YOURFILE The result is a destination name of YOURLIB YOURFILE if the destination file type is a save file 9 In cases where a member is specified explicitly in the destination file name and the destination file type is a save file an error is issued Note If the user issues a cd dst 1logical name command to blank out the current library on the destination side the library name in the absolute path of the source file is used in the destination absolute path in cases where no library is specified explicitly This works only for OS 400 to OS 400 copies where both operating systems are operating in the LIB file system Example CD DST COPY SRC MYLIB MYFILE MYMBR The result is a destination of MYLIB MYFILE MYMBR using the source s library file and member names because none are supplied explicitly in the copy command The current directory on the destination side is empty because the command cd DST was issued udm user 3207 Confidential amp Proprietary 273 Command Reference Transfer Operations OS 400 Specific Destination only in LIB File System Transfers where
282. second to highest in the precedence order after command line options see Section 2 2 1 Configuration Methods Individual command line options can be specified on one or multiple lines Blank lines are ignored Lines starting with the hash character are ignored and can be used for comments The command line file can be encrypted if it is necessary to secure the contents Note If the contents of the file contain sensitive material the operating system s native file and user security facilities should be used in addition to the file encryption provided by the Universal Products udm user 3207 Confidential amp Proprietary 42 Configuration Features 2 2 4 Environment Variables Environment variables like command line options allow options to be specified for one instance of a program execution Each time that you execute a program environment variables allow you to tailor the behavior of the program to meet the specific needs for that execution Environment variables are the third to highest in the precedence order after command line file options see Section 2 2 1 Configuration Methods Each operating system has its own unique method of setting environment variables All environment variables used by Universal Products are upper case and are prefixed with a product identifier consisting of three or four characters The product sections specify the value of the environment variables Values are case sensitive Environ
283. secondary Instead once the manager s certificate is validated on the primary just as happens when not using proxy certificates in a three party transfer session a proxy certificate is generated by the primary and signed by the manager The primary uses this proxy certificate to establish a connection between it and the secondary The subject name of the proxy certificate is the same as the original certificate supplied to the manager A certificate ACL rule for a certificate containing this subject can be used on both the primary and secondary Proxy certificates simplify things by allowing the same ACL rule to be used in both places instead having a rule for the manager s certificate on the primary and a rule for the primary s actually the broker on the primary system certificate on the secondary Proxy certificates can only be used under the following conditions 1 Manager primary and secondary must all be version 3 2 or later 2 Manager primary and secondary must all use OpenSSL as their SSL type If any of these are running on the mainframe they cannot use system SSL and proxy certificates at the same time 3 PROXY_CERTIFICATES configuration option must be set to yes for the manager udm user 3207 Confidential amp Proprietary 83 Message and Audit Facilities Features 2 9 Message and Audit Facilities All Universal Products have the same message facilities Messages in this context are text messages wr
284. ser me pwd mypwd if _lastrc EQ 0 print msg Connected to _remote host _remote port print msg as _remote user from _local end This example produces the following output Connected to mymachine 10000 as me from local udm user 3207 Confidential amp Proprietary 191 if Statement UDM Scripting Language 11 7 if Statement The if statement is used to add conditional branching of UDM commands An if statement consists of e Comparison operation e Series of UDM commands that are carried out if the comparison operation evaluates to true e end statement that indicates the end of the if statement For example if comparison UDM commands end If the comparison does not evaluate to true UDM will pick up execution from the line after the end statement Note The indentation of commands underneath the conditionals is not required in UDM This is done for the sake of readability you can indent lines in your own scripts if and as you see fit 11 7 1 Comparison Operations In an if statement a comparison consists of three parts 1 Left hand value 2 Comparator 3 Right hand value The left hand and right hand values can be either e Variable reference e Variable attribute Constant Comparators A comparator determines the type of comparison to be made between the left hand and right hand values There are six comparators EQ NE LT GT LE GE udm user 3207 Confident
285. server with the specified logical name is working filetype Set a series of masks and corresponding transfer mode types find Finds a specific occurrence of a substring in an existing string or list element format Creates a formatted string insertstring Inserts a substring into an existing string udm user 3207 Confidential amp Proprietary 163 UDM Commands UDM Scripting Language loaddata Loads the contents of a data element from a file instead of setting them in a script via the data command logdata Writes the content of a data element to the open log file lower Forces all alpha characters in a given variable or list element to lower case mode Sets the current transfer mode move Initiates a move operation open Opens a UDM session openlog Opens a log file on disk for writing custom log information pad Takes a string in an existing variable or list element and pads it to make it the given length parse Parses a string placing the components of the string into variables print Prints a message in the UDM manager s transaction output query Prints out the UDM Manager version quit Exits the UDM Manager same as the exit command rename Renames a file replace Replaces one or more instances of a sequence with another sequence report Sets UDM s reporting options resetattribs Resets the attributes for all UDM file systems on the
286. spective owners 2003 2010 by Stonebranch Inc All rights reserved udm user 3207 Confidential amp Proprietary 4 Summary of Changes Changes for Universal Data Mover 3 2 0 User Guide udm user 3207 February 19 2010 e Added _execrc built in variable in Section11 6 8 Built in Variables Changes for Universal Data Mover 3 2 0 User Guide udm user 3206 September 8 2009 Moved Universal Data Mover Manager examples for all operating systems to Appendix A Examples Universal Data Mover 3 2 0 6 Added LOGON_METHOD configuration option in Chapter 8 Universal Data Mover Server for Windows Changes for Universal Data Mover 3 2 0 User Guide udm user 3205 July 29 2009 Universal Data Mover 3 2 0 1 for OS 400 e Modified document for upgrade from Universal Data Mover 3 1 1 for OS 400 to Universal Data Mover 3 2 0 for OS 400 including e Changed the following OS 400 names throughout the document Universal Broker subsystem name from UBROKER to UNVUBR320 Universal Broker user profile name from UBROKER to UNVUBR320 e Universal Products installation library name from UNIVERSAL to UNVPRD320 udm user 3207 Confidential amp Proprietary 5 Summary of Changes e Universal Products spool library name from UNVSPOOL to UNVSPL320 e Universal Products temporary directory from UNVTMP to UNVTMP320 Added Section 6 2 1 Universal Products for OS 400 Commands Added the following configuration options in
287. ssion of a certificate alone does not prove your identity You must have the corresponding private key The two together prove your identity to any third party that trusts the CA that issued your certificate This is a key point if you do not trust the CA that signed a certificate you cannot trust the certificate Since certificates originally were designed to be used for internet authentication global directory technologies were developed to make them available via the internet This directory technology is known as X 500 Directory Access Protocol Later LDAP was introduced by Netscape to make it Lightweight Directory Access Protocol X 500 divides the world into a hierarchical directory A person s identity is located by traversing down the hierarchy until it reaches the last node Each node in the hierarchy consists of a type of object such as a country state company department or name udm user 3207 Confidential amp Proprietary 88 X 509 Certificates Features 2 10 1 Sample Certificate Directory Figure 2 7 below provides a sample diagram of a small X 500 directory ST Georgia ST Florida l l O 5tonebranch O Acme Inc OU Sales OU Sales CN Joe Buck CN Joe Black CN Joe Simpson Figure 2 7 X 500 Directory sample The keywords listed on each node are referred to as a Relative Distinguished Name RDN A person is identified by a Distinguished Name DN The DN value for Joe Black is C US ST Georgi
288. standard input to the remote command The svropt parameter can be used to override UCMD Server options Note UDM does not require a space before the server options as does Universal Command The stdout and stderr parameters specify data elements to contain standard out and standard error respectively from the remote commana If the data elements do not exist they are created If the data elements do exist they are overwritten with the output from the remote command If the value portion refers to an existing non data element variable or the name of a built in variable that is any variable beginning with an underscore an error is issued The exec command output will still be written to UDM stdout the transaction log and UDM stderr where appropriate even with the presence of the stdout and or stderr udm user 3207 Confidential amp Proprietary 281 exec Command Remote Execution 15 2 2 Return Values When the exec command is invoked the return value from the exec command indicates whether or not UDM was able to invoke the remote command The return value from the exec command will be 0 none if the remote command was invoked Upon successful invocation of the remote command it might be useful to have the return value of the remote command itself in addition to whether or not the remote command could be executed The remote command s return value is stored in the built in variable _execrc 15 2 3 exec Command Exam
289. stem writes them out as dictated by its attributes udm user 3207 Confidential amp Proprietary 257 0S 400 I O Transfer Operations OS 400 Specific 14 2 7 Save Files Support Save SAVF files are essentially binary archives of data They may contain one or more objects inside These objects can be extracted individually or in their entirety UDM for OS 400 supports NEW and REPLACE operations for CREATEOP when a Save file is the destination file type It does not support append operations on Save files SAVF to SAVF Transfers Copying a Save file to a Save file always should be performed via a binary transfer regardless of the mode type setting All of the source data is read in binary and written in binary This type of transfer succeeds only if the CREATEOP is set to NEW or REPLACE If the destination Save file already exists and the CREATEOP is set to APPEND UDM issues an error and aborts the transfer Non SAVF to SAVF Transfers As with all cases when a Save file is involved a binary transfer should be forced The source data is written to the destination in the form it is read Only the values of NEW and REPLACE are supported for CREATEOP on the destination side when the destination file type is a Save file Note The non Save file must be a file that originally was created as a Save file on an OS 400 system and then stored as a binary file on a non OS 400 system SAVF to Non SAVF Transfers Data is read and tra
290. structured Most importantly links to detailed information in a companion document the Universal Data Mover Reference Guide have been created in the user guide In order for the links between these documents to work correctly e Place the documents in the same folder In Adobe Reader Adobe Acrobat de select Open cross document link in same window in the General category of your Preferences dialog selected from the Edit menu udm user 3207 Confidential amp Proprietary 30 Preface Conventions Specific text formatting conventions are used within this document to represent different information The following conventions are used Typeface and Fonts This Font identifies specific names of different types of information such as file names or directories for example abc 123 help txt Command Line Syntax Diagrams Command line syntax diagrams use the following conventions bold monospace font Specifies values to be typed verbatim such as file data set names 7talic monospace font Specifies values to be supplied by the user Encloses configuration options or values that are optional Encloses configuration options or values of which one must be chosen Separates a list of possible choices Specifies that the previous item may be repeated one or more times BOLD UPPER CASE Specifies a group of options or values that are defined elsewhere Table P 1 Command Line Sy
291. t MD5 MAC s for data integrity UNVv2 referred to data integrity as data authentication Encryption and integrity may be enabled and disabled on an individual bases Encryption keys are generated using a proprietary key agreement algorithm A new key is created for each and every network session udm user 3207 Confidential amp Proprietary 63 Network Data Transmission Features 2 5 3 Universal Products Application Protocol Universal Product components use an application layer protocol to exchange data messages The protocol has the following characteristics Low Overhead e Secure e Extensible e Configurable Attributes The following sections refer to two categories of data transmitted by Universal Products e Control data or messages consists of messages generated by Universal Products components in order to communicate with each other The user of the product has no access to the control data itself e Application data or messages consists of data that is transmitted as part of the requested work being executed For example standard input and output data of jobs Universal Command executes The data is created by the job and read or written by Universal Command on behalf of the job Low Overhead The protocol is lightweight in order to minimize its use of network bandwidth The product provides application data compression options which reduces the amount of network data even further There are two possible
292. t can be specified Client Identification Rule matching is based on the client identity and the client request There are two client identification methods 1 X 509 certificate authentication 2 Client IP address and reported user account udm user 3207 Confidential amp Proprietary 77 Universal Access Control List Features X 509 Certificate Authentication X 509 certificates identify an entity An entity can be a program person or host computer When an X 509 certificate is authenticated it authenticates that the entity is who it claims to be X 509 certificates are utilized in UACL entries by first mapping a client certificate to a UACL certificate identifier The certificate identifier then is used in the UACL entries A certificate identifier provides for 1 Concise representation of certificates in UACL entries There are a large number of certificate fields that may be used and many of the fields have lengthy tedious naming formats A certificate map only needs to be defined once and then the concise certificate identifier can be used in the UACL entries 2 Mapping of one or more certificates to a single certificate identity A group of entities that share a common security access level may be represented by one certificate identity reducing the number of UACL entries to maintain UACL certificate map entries are searched sequentially that is top to bottom matching the client certificate to each entry until
293. t is no There is no UDM configuration option Setting the attribute value to yes turns on the attribute secspace Secondary amount of space to allocate for the data set Equivalent to the second positional parameter of the second positional parameter of the JCL SPACE parameter SPACE secspace Default is 15 it can be set with the UDM configuration option ALLOC_SEC_SPACE spaceunit Allocation unit used to specify the space to allocate for the data set e Equivalent to the first positional parameter of the JCL SPACE parameter SPACE unit Default is TRK it can be set with the UDM configuration option ALLOC_SPACE_UNIT status e Status of the data set to be allocated e Equivalent to the first positional parameter of the JCL DISP parameter DISP status normaldisp abnormaldisp Default is OLD for input and output data sets that exist NEW for output data sets that don t exist e Default input status can be set with UDM configuration option ALLOC_INPUT_STATUS Default output status can be set with UDM configuration option ALLOC_OUTPUT_STATUS storclas SMS storage class name Equivalent to the JCL STORCLAS parameter STORCLAS name No default default value can be set with UDM configuration option ALLOC_STORCLAS udm user 3207 Confidential amp Proprietary 242 UDM Commands under z OS Transfer Operations z OS Specific unit e Unit on which
294. t month e dd resolves to a two digit day of the month e ddd resolves to the Julian day mm resolves to the two digit month of the year e yy prints the two digit year e wwresolves to the two digit current week of the year yyyy resolves to the four digit year Note The value of ww is zero based not one based That is the first week of the year is 0 the second week is 1 the third week is 2 and so on The _date variable can be referenced only in your scripts and cannot be set You can use the _date variable in combination with the print command to display custom date information in UDM s transaction log print msg Today is _date day _date month _date dd Produces the following output Today is Wednesday January 19 Stoneman s Tip _echo The _echo built in variable specifies whether or not a command is echoed prior to processing It can have a value of either yes or no If the value is yes each UDM command is echoed prior to processing e If the value is no the command is not echoed The value of _echo can be set using the set command as in the following example set _echo yes _execrc The _execrc built in variable holds the value of the process executed by the last exec command issued The return code of the exec command itself is stored in _lastrc and _rc if the return code is greater than the current value of _rc The difference between the two values is that the return code f
295. ta Mover Server is in regarding its network connection with a manager and the completion of the user process and its associated spooled data The communication state values are described in Table 2 3 Component Communication States below The Reconnect column indicates whether or not a network reconnect request is valid The Restart column indicates whether or not a restart request is valid COMPLETED NO NO The server and manager have completed All standard output and standard error files have been sent to the manager and the user process s exit status DISCONNECTED YES YES The server is not connected to the manager This occurs when a network error has occurred the manager halted or the manager host halted The server is executing with either the network fault tolerant protocol is restartable or both Note The server cannot tell if the manager is still executing or not since it cannot communicate with it ESTABLISHED NO NO The server and manager are connected and processing normally This state is the most common state when all is well RECONNECTING NO NO The server has received a reconnect request from the manager to recover a lost network connection This state should not remain long only for the time it takes to re establish the network connections STARTED NO NO The server has started If the server is restartable it is receiving the standard input file from the manager and spooling it T
296. tch depending on the operating system On all platforms other than OS 400 the batch method reads the UDM commands from a script file specified by the SCRIPT_FILE option SCRIPT_FILE is not specified the commands are read from the file allocated to the UNVSCR DD statement in the execution JCL OS 400 The script file and member can be specified by position as the first two command parameters or by using the SRCFILE and SRCMBR command parameters The UDM interactive method also can read UDM commands from a script file Syntactically there is no differences in the command structure between the two methods with the exception that commands in the batch method script files can contain parameters 11 4 1 Invoking UDM in Batch Mode with Commands from a Script File To launch UDM in batch from the Windows or UNIX command line use the SCRIPT_FILE option to specify the filename of the script For example udm s script_filename Scripts also can have parameters which are specified in the same name value format of command parameters To specify options parameters for a script file on the command line use the SCRIPT_OPTIONS option For example udm s copyfiles udm o file source c source dest c destination In this example UDM is invoked with a script file name copyfiles udm It has three parameters that are passed to the script file 1 file with a value of 2 source with a value of c source 3 dest with a value of c
297. th UDM UDM Transfer Operations 12 8 3 Copying Multiple Files Using Wildcards In addition to copying single files the copy command can be used to copy multiple files by using wildcards in the source file specification When wildcards are used any file matching the source file specification will be copied There are two types of wildcards 1 Asterisk wildcard matches zero or more characters 2 Question mark wildcard matches a single character Here are some examples of wildcard matching given the following filenames in the source directory e test txt e test1 txt e test2 txt e test3 txt e test bin e test1 bin e test2 bin e test3 bin A source file specification of will copy all of the files in the directory as will test and tes A source file specification of txt will copy the first three files A source file specification of bin will copy the last three files A source file specification of test txt will copy the files test1 txt test2 txt and test3 txt Wildcards can be used only in the source file specification not the destination file specification Under some operating systems it is possible for and to be valid characters in a filename When they appear in the destination portion of a UDM copy operation they are treated as file characters and not as wild cards Also keep in mind that while UDM can copy all of the files at a single directory level in a hierarchical
298. the Windows and UNIX environments It provides specific examples for the following topics which explain how to use UDM ina two party mode e Simple File Copy to the Manager Simple File Copy to the Server Copy a Set of Files Each example illustrates a procedure that occurs under the platform s default file system See Section A 2 UDM Manager for z OS Examples for z OS examples that apply equally as well to the Windows operating systems udm user 3207 Confidential amp Proprietary 297 UDM Manager for UNIX and Windows Examples Examples A 3 1 Simple File Copy to the Manager This example copies in text mode one file to another This is the simplest form of data transfer 1 set _echo yes 2 set _halton warn 3 open unix sol9 user top098 pwd p100m 4 cd unix opt app data 5 mode type text 6 copy unix datal0 txt 7 quit For this UNIX and Windows example the following is a line by line explanation 1 Line 1 turns on command echo which results in each command being printed out prior to processing 2 Line 2 sets error condition value on which script process halts Any error equal to or greater than 4 halts script processing A value of 4 effectively means halt on any error or warning 3 Line 3 opens a session between the local UDM Manager and a remote UDM Server running on host so19 The host so19 is given the a logical name of unix The open command also provides user credentials for the UDM Server
299. the method specified with the 1ineop attribute The lineop attribute specifies what happens to each line or record from z OS s dd and dsn file systems of data coming from the source transfer If the value for 1ineop is none the line record is written as is however if its length from the source is greater than the value of 1inelen UDM issues an error If the value of 1ineop is stream the data from the source side of the transfer is treated as a single record and is subdivided when it is written as a series of lines or records depending on the file system each 1inelen characters in length If the value of 1ineop is trunc each record or line from the source is truncated so that it is at most 1inelen characters in length Finally if the value of 1ineop is wrap each line or record from the source side of the transfer that is longer than 1inelen characters is wrapped into multiple lines records so that the maximum length of each line on the destination side is at most 1inelen characters long Binary data that is transferred from a Windows or UNIX platform including HFS under USS is looked at by UDM as one large line or record of source data The same can be said when transferring text data from these platforms if the end of line sequence is zero length for the source server or the end of line sequence does not exist in the source data Stoneman s Tip Under z OS except for the HFS file system UDM will set the 1inelen attribut
300. the word end It must appear separately on its own line However it is possible that end is valid instream data and you can change the end sequence with the end parameter of the data command udm user 3207 Confidential amp Proprietary 207 Creating In Stream Data with the data Command UDM Scripting Language Example The following example shows how to use the data command in conjunction with the exec command to look through a series of copied files and display lines with the occurrence of some string under UNIX open remote yourmachine user someguy pwd somepwd data mydata resolve a11 grep this is my sequence _file exit end copy local txt forfiles remote txt exec remote cmd ksh input mydata end close 11 11 2 Printing Data Element Information Issuing the data command by itself prints a list of the names of all the data elements that have been defined Note Data elements persist beyond individual UDM transfer sessions Issuing the data command with the print parameter and the name of a data element will print the data in that element Continuing with the previous example issuing data print mydata Will produce the following output gt Begin mydata lt grep this is my sequence _file exit gt End mydata lt udm user 3207 Confidential amp Proprietary 208 Chapter 12 UDM Transfer Operations 12 1 Overview This chapter provides information on Universal Data Mov
301. there ACL entries can be added changed deleted or sorted rules are applied in the order in which they are listed Figure 8 2 below illustrates an example The set of ACL entries only allows connections from host 10 20 30 40 if the user on that host is TS1004 All other remote users will be blocked TS1004 may run processes on the local system using any user account provided the correct password is supplied No processes may be run with Universal Data Mover using the Administrator account on the local system regardless of where the request originated FJ Universal Configuration Manager 21x Installed Components Access ACL Universal Application Container a Universal Broker Universal Command Manager Universal Command Server Universal Control Manager Universal Control Server Universal Data Mover Manager Universal Data Mover Server Message Options Server Options H Network Options SSL Protocol Options Event Subsystem Options Access Control Lists Listed below are the entries in the Universal Data Mover Server s access control list These entries are rules that specify which machines and user accounts are allowed to establish a connection with the Server FF 2 4 E Remote Host Manager User Account Local User Account Access 10 20 30 40 TS1004 x allow 10 20 30 40 s deny ALL j Administrator deny o AC 4 gt Manager Access ACL Cert
302. these references udm user 3207 Confidential amp Proprietary 123 Usage Universal Data Mover Manager for OS 400 6 2 2 Modes of Operation Under OS 400 UDM can be run either e In interactive mode From a script file Asa batch application Additionally under OS 400 UDM can use either the LIB or HFS file system Running UDM Interactively To invoke UDM as an interactive application 1 Enter the following on the command line STRUDM 2 Press lt Enter gt This will start the UDM Manager You will be greeted with a startup message and the udm gt prompt similar to this UNV2800I Universal Data Mover 3 2 0 Level 0 started udm gt At the udm gt prompt you can enter any UDM command To exit UDM enter the following command at the udm gt prompt quit Running UDM from a Script To invoke a UDM script 1 Enter the following on the command line STRUDM SCRFILE library file SCRMBR member 2 Press lt Enter gt This will start the UDM Manager using the script located by library file and member When the script file has finished executing UDM will exit automatically UDM requires the member name there is no default Requiring the member name makes script specification under OS 400 behave as it does on other platforms On other systems there is no default search order as exists under OS 400 However users may explicitly provide FILE as a member name to use the OS 400 default file search order
303. ting environment Script variables supersede global variables in precedence That is if a script variable has the same name as an existing global variable any references to that variable name will result in the script variable value not the global variable value If more than one script variable exists with the same name the script variable defined in the last ca11 command has precedence For example if UDM encounters the variable_name sequence it first checks to see if a variable with a matching name was passed into the script it currently is executing If so UDM uses this variable s value If not UDM goes up the chain of calling scripts and uses the value of the first instance of a variable that it finds that matches the name in the sequence If no variable with a matching name was passed into any script along the chain UDM looks to see if a global variable exists with the name If one is found its value is used If no instances are found anywhere an error is issued udm user 3207 Confidential amp Proprietary 180 UDM Variables UDM Scripting Language Variable Scope Scripts The following three scripts demonstrate variable scope script1 udm set varl a global variable set var2 a global variable set var3 a global variable print msg The value of varl is varl print msg The value of var2 is var2 print msg The value of var3 is var3 call script2 udm varl passed into script2 var2 passe
304. ting system Universal Data Mover Server for OS 400 Chapter 10 Description of Universal Data Mover Server specific to the OS 400 operating system UDM Scripting Language Chapter 11 Description of the Universal Data Mover scripting language UDM Transfer Operations Chapter 12 General description of the Universal Data Mover transfer operations Transfer Operations z OS Specific Chapter 13 Description of the Universal Data Mover transfer operations specific to the z OS operating system Transfer Operations OS 400 Specific Chapter 14 General description of the Universal Data Mover transfer operations specific to the OS 400 operating system Remote Execution Chapter 15 Description of remote execution procedures for Universal Data Mover Return Code Processing Chapter 16 Description of Universal Data Mover return code processing Examples Appendix A Examples of Universal Data Mover Manager for specific operating systems Customer Support Appendix B Customer support contact information for users of Universal Data Mover udm user 3207 Confidential amp Proprietary 33 Chapter 1 Overview 1 1 Introduction to Universal Data Mover This chapter provides general information on Universal Data Mover UDM UDM is a secure and reliable data transfer solution developed specifically for corporate IT infrastructures and automated data center environments UDM is a cost effective alternative to the traditional comple
305. tive Components Information Universal Command Manager Universal Command Server Universal Control Manager Universal Control Server Universal Data Mover Manager Universal Data Mover Server v Universal Enterprise Con o El Edit Universal component definitions are listed below To edit a component definition choose the item from the list and select the Edit button Component Name Component Type Start Command Configurati C Program Files C Docum C Program Files C Docurn C Program Files C Docurn C Program Files C Docurn C Program Files C Docurn C Program Files C Docum Figure 8 1 Universal Configuration Manager Component Definitions udm user 3207 Confidential amp Proprietary 141 Component Definition Universal Data Mover Server for Windows The UDM Server component definition is located in the component definition directory of the Universal Broker Table 8 1 below identifies all of the options that comprise the UDM for Windows component definition Each Option Name is a link to detailed information about that component definition option in the Universal Data Mover 3 2 0 Reference Guide AUTOMATICALLY_START Specification for whether or not UDM Server starts automatically when Universal Broker is started COMPONENT_NAME Name by which the clients know the UDM Server CONFIGURATION_FILE Full path name of the UDM Server configuration file RU
306. to all user accounts in the Windows Administrator group Windows Vista When opening the Universal Configuration Manager for the first time on Windows Vista two new operating system features the Program Compatibility Assistant PCA and User Account Control UAC may affect its behavior With these two features enabled the expected Universal Configuration Manager behavior is as follows 1 Universal Configuration Manager may issue the following error 2 Universal Configuration Manager Error x You must have administrator privileges to use Universal Configuration Manager Figure 2 2 Universal Configuration Manager Error dialog Windows Vista 2 Click OK to dismiss the error message The Windows Vista Program Compatibility Assistant PCA displays the following dialog udm user 3207 Confidential amp Proprietary 52 Universal Configuration Manager Features gt Program Compatibility Assistant EX Did this control panel work correctly If it didn t try using settings that are compatible with this version of Windows Control Panel Universal Configuration Manager o amp Publisher Stonebranch Inc Location C Program Files x86 Universal UCfgMogr ucfgmgr cpl Open the control panel using recommended settings This control panel works correctly Cancel What settings are applied Figure 2 3 Windows Vista Program Compatibility Assistant To continue select Open the cont
307. transfer session when a network fault occurs RECV_BUFFER_SIZE Size of the TCP receive buffer for UDM REMOTE_PORT TCP port number on the remote computer used for invoking UDM Server instances SCRIPT_FILE Script file containing UDM commands to execute SCRIPT_OPTIONS Parameters to pass to the script file SEND_BUFFER_SIZE Size in bytes of the TCP send buffer for UDM TCP_NO_DELAY Specification for whether or not to use TCP packet coalescing TRACE_FILE_LINES Maximum number of lines to write to the trace file TRACE_TABLE Size of a wrap around trace table maintained in memory UCMD_PATH Sets the complete path to UCMD for calls by the exec command UMASK File mode creation mask USAP_PATH Sets the complete path to USAP for calls by the execsap command VERSION Writes the program version information and copyright Table 5 1 UDM Manager for UNIX Configuration Options udm user 3207 Confidential amp Proprietary 118 Usage Universal Data Mover Manager for UNIX 5 2 4 Command Line Syntax Figure 5 1 below illustrates the command line syntax of UDM Manager for UNIX udm bif_directory directory plf_directory directory ca_certs f7 e cert file private_key file private_key_pwd password proxy_certificates yes no crl f77e script f7 ename options options codepage codepage ctl_ssl_cipher_list 7
308. tribute on the source side specifies the location of the temporary sequential data set that will be transferred e Setting this attribute on the destination side specifies the volume for the temporary transfer file as well as the volume used by the temporary staging PDS E The TMPPRIMSPACE TMPSECSPACE and TMPSPACEUNIT attributes specify the amount of primary space and secondary space used when allocating the temporary files as well as the space unit used When set on the source side these attributes affect the temporary sequential data set that will be transferred When set on the destination side these attributes are used in allocating the temporary transfer file and the temporary staging PDS E The TMPDIRBLOCKS attribute is used only on the destination side It specifies the number of directory blocks used by the staging PDS E Note Although you can override these attributes it is not recommended udm user 3207 Confidential amp Proprietary 252 Chapter 14 Transfer Operations OS 400 Specific 14 1 Overview This section describes information that is specific to OS 400 file transfer operations e OS 400 I O Codepage CCSID mappings UDM commands under OS 400 udm user 3207 Confidential amp Proprietary 253 OS 400 I O Transfer Operations OS 400 Specific 14 2 0S 400 1 0 This section describes the file systems and file types available in UDM for OS 400 14 2 1 File Systems UDM for OS 400 su
309. trimmed Variable record formats do not normally have trailing spaces so trimming normally is not required DD file system S1 EXEC UDMPRC APOUT DD DSN APP DATA DAILY DISP SHR UNVSCR DD NY ON DU bh uu NN pp set _echo yes set _halton warn open unix sol9 user top098 pwd p100m filesys local dd cd unix opt app data mode type text trim yes copy local apout unix datal0 txt quit DSN file system S1 EXEC UDMPRC UNVSCR DD NN OW PWN pp set _echo yes set _halton warn open unix sol9 user top098 pwd p100m cd unix opt app data mode type text trim yes copy local app data daily unix datal0 txt quit udm user 3207 Confidential amp Proprietary 292 UDM Manager for z OS Examples Examples A 2 3 Copy a Set of Files to an Existing z OS Partitioned Data Set These examples copy in text mode multiple files with one copy command to an already allocated partitioned data set PDS on a z OS system The file names used to create the member names in the destination PDS are the source file names However note that file names on UNIX and Windows file systems often have a file extension as part of their name A file extension is a suffix separated from the file s base name with a period for example BASE TXT The period in the file extension is not a valid character in PDS member names so UDM must be instructed to remove the file extensions before copying them into the PDS
310. uck in the Sales organization of the Acme company in the state of Florida in the United States Public Key Public key associated with the certificate identity X509v3 Extensions X 509 version 3 introduced this section so that additional certificate fields may be added In this case the identity s email address is included as a Subject Alternative Name field This section is not available in X 509 version 1 Signature CA s digital signature of the certificate Table 2 7 Certificate Fields udm user 3207 Confidential amp Proprietary 91 X 509 Certificates Features 2 10 3 SSL Peer Authentication The SSL protocol utilizes X 509 certificates to perform peer authentication For example a Universal Command Manager may want to authenticate that it is connected to the correct Broker Peer authentication is performed by either one or both of the programs involved in the network session If a Manager wishes to authenticate the Broker to which it connects the Broker will send its certificate to the Manager for the Manager to authenticate Should the Broker wish to authenticate the Manager the Manager sends its certificate to the Broker Certificate authentication is performed in the following steps 1 Check that the peer certificate is issued by a trusted CA 2 Check that the certificate has not been revoked by the CA 3 Check that the certificate identifies the intended peer If a step fails the
311. urity concerns are Access to Universal Data Mover files and directories Access to Universal Data Mover configuration files Universal Data Mover user account Privacy and integrity of transmitted network data User authentication ON PONS 8 4 1 File Permissions Only trusted user accounts should have write permission to the UDM Server installation directory and subdirectories and all of the files within them 8 4 2 Configuration Files Only trusted user accounts should have write permission to the UDM Server configuration files and add and delete access to the directories in which they reside 8 4 3 Universal Data Mover Server User ID UDM Server requires read access to its installation directory and its working directory defined in the component definition udm user 3207 Confidential amp Proprietary 145 Security Universal Data Mover Server for Windows 8 4 4 User Authentication User authentication is the process of verifying that a user is known and valid to the system The process used by UDM Server requires the user to provide a user name ID and a password The UDM Server passes the name ID and password to the operating system for verification this is referred to as logging on the user For Windows user authentication is optional However if security is enabled a user name ID and password are required in order to verify the user s credentials With security enabled you transfer files using a specific
312. versal Data Mover 3 2 0 User Guide udm user 3201 September 5 2008 Added toll free telephone number for North America in Appendix B Customer Support Changes for Universal Data Mover 3 2 0 User Guide udm user 320 May 16 2008 Universal Data Mover 3 2 0 0 Added support for the following features e Script Language UDM has made vast improvements in the power of its scripting language with the addition of new control structures and built in functions e X 509 Certificates UDM provides full support for X 509 certificates e UNIX Permissions When transferring UNIX files between two UNIX systems the file permission modes of the destination files may now be based upon the source file modes e z OS Load Module Copies UDM on z OS now supports the transfer of load modules and program objects between z OS systems e z OS Relative GDG Delete Support for deleting z OS generation data sets based upon a relative number using the UDM DELETE command e z OS GDG Resolution Method The method used for resolving for generation data set relative numbers with a UDM script can be selected between the original job method and the new reference method e Manager Identification in Three Party Transfers The UDM manager identity either user identifier and IP address or X 509 certificate information is propagated to the primary and secondary UDM servers and available for UACL processing e Deleted the following values in Table 2 3 Component Communi
313. vocation of an inline script CALLME using the STRUDM command from a database job e Invocation of an inline script CALL1 using the CALL command from a database job BCHJOB JOB testcal1 ENDSEV 10 OUTQ mytest UDMOUTQ LOGCLPGM YES LOG 2 20 SECLVL MSGQ USRPRF DATA FILE CALL1 ENDCHAR ENDDATAFILE print msg I made it to cal11 an inline file ENDDATAF ILE DATA FILE CALLME ENDCHAR ENDDATAFILE OPEN S AS400V5 USER qatest PWD PORT 4311 CALL CALL1 FIRST CLOSE ENDDATAFILE STRUDM SCRFILE CALLME ENDBCHJOB udm user 3207 Confidential amp Proprietary 267 Command Reference Transfer Operations OS 400 Specific 14 4 3 cd Change Directory Command When you authenticate with a UDM Server running under OS 400 the current library is set to the default library for that user In file operations where the library is not identified explicitly as a part of the file specification the current library is used instead Example COPY SRC C MYFILE DST MYFILE MYMEMB With a current library set to MYUSER this command will result in a destination file specification name of MYUSER MYFILE MYMEMB You can change the current library by issuing the cd Change Directory command with the new library name as in this example CD DST YOURUSER There is a special case when using UDM from one OS 400 machine to another where the source library name can be used instead see Section 14 Samples for more deta
314. when a network fault occurs RECV_BUFFER_SIZE Size of the TCP receive buffer for UDM REMOTE_PORT TCP port number on the remote computer used for invoking UDM Server instances SAF_KEY_RING SAF certificate key ring name SAF_KEY_RING_LABEL SAF key ring certificate label SCRIPT ddname from which to read a UDM script command file Confidential amp Proprietary 101 Usage Universal Data Mover Manager for z OS SCRIPT_OPTIONS Options to pass to the script command file SEND_BUFFER_SIZE Size of the TCP send buffer for UDM SERVER_STOP_CONDITIONS Exit codes that cause Universal Broker to cancel the corresponding UDM Server of the exited UDM Manager SSL_IMPLEMENTATION SSL implementation SYSTEM_ID Local Universal Broker with which the UDM Manager must register TCP_NO_DELAY Specification for whether or not to use TCP packet coalescing TRACE_FILE_LINES Maximum number of lines to write to the trace file TRACE_TABLE Size of a wrap around trace table maintained in memory UMASK File mode creation mask VERSION Writes the program version information and copyright Table 3 2 UDM Manager for z OS Configuration Options udm user 3207 Confidential amp Proprietary 102 Usage Universal Data Mover Manager for z OS 3 2 6 Command Line Syntax Figure 3 3 and Figure 3 4 below illustrate the command line syntax of UDM Manager for z OS udm
315. when the command to copy load module s is issued On the source side of the transfer UDM uses IEBCOPY to unload the load modules matching the source file mask from the PDS E in which they reside into a temporary data set It is this temporary data set that is transferred to the destination system As a result when UDM displays the status messages indicating that it is copying a file it is the name of the temporary file that is displayed since that is what is actually being transferred A temporary file name is also used on the destination side of the transfer After the temporary file has been transferred the load modules are unpacked using IEBCOPY into a staging PDS E also using a temporary data set name This PDS E is created using the same attributes as the source PDS E From there IEBCOPY is called a final time to move the load modules from the staging PDS E to the final destination PDS E At this point all of the temporary files are cleaned up The two step process on the destination side of the transfer is used in case the blocking of the final destination data set does not match that of the source PDS E udm user 3207 Confidential amp Proprietary 250 Copying Load Modules Transfer Operations z OS Specific 13 4 1 Example Figure 13 1 below illustrates an example script of a load module transfer open src dst dst zos attrib dst createop new copy src MYHLQ UDM TESTLM dst YOURHLQ TEST LOA
316. x and hard to implement offerings that makes transferring data between various enterprise and desktop platforms reliable and easy udm user 3207 Confidential amp Proprietary 34 Transfer Components Overview 1 2 Transfer Components There are three components to any UDM transfer operation 1 Manager 2 Primary server 3 Secondary server The manager may act as the primary server depending on the type of transfer session two party or three party see Section 1 3 Transfer Sessions The secondary server is always a separate and distinct component invoked via the Universal Broker 1 2 1 Manager The UDM Manager processes commands using UDM s scripting language The UDM Manager receives commands from the user through an interactive session an external script file or some combination of the two Before the UDM Manager can initiate any transfer operations it must first establish a transfer session where it invokes the primary and secondary servers which actually conduct the transfer operations 1 2 2 Primary Server When a transfer session is being established the UDM Manager invokes the primary server which acts as the first endpoint in a transfer operation In turn the primary server invokes the secondary server providing a single path of communication The primary server also acts a relay for the UDM Manager forwarding on any messages for the secondary server from the UDM Manager This single message pipeline reduces the
317. xdaaltiad Satdeds seed dees 157 10 3 2 Configuration Options Vers corte AE oe be eu eee 158 104 NOUNS sexe ct ese A 159 10 4 1 Object Permissions 2ix2tdet4 arado as 159 10 4 2 Universal Data Mover Server User Profile 159 10 4 3 User Authentication 2 0 0 ee 160 10 4 4 Universal Access Control List 0 000000 cece eee 160 UACL Entries theca a e a a tee tenes 160 UACL Examples 0 0 00 en a a a A KARAER ERE 161 Chapter 11 UDM Scripting Language 0c cece eee eee 162 11 1 OVOIVISW osuna eho ae Raye AR a aes a ee alae de a 162 11 2 UDM Commands siai a n a a a a a eens 163 11 3 UDM Command Format anaana ce eee 165 11 3 1 Basic Rules 2 0 0 0 02 eee 165 Parameters ui ida deh deed th besarte dad deo aah aed 165 SPACES bad cdot nee AA aos adi ak voted Meas 165 Escape Sequences 00 0 cece eens 165 Line Continuation 000 cee 166 Comments 00 0c eee eee 166 11 3 2 Sample UDM Script nananana aaan 166 11 33 EXPreSSIONS nigh ceed ee ede SELB ER ORAL E EE A ed eed ded 167 Appearance cc 167 Integer ONIY asi e Eu ei ae a hob e dea a dea s 167 Delimit rs coi a a K E ee aa eae E ede 167 Operand Operator Delimiters 0 0 ccc nes 167 Operator Precedence o 168 PUN A O AE E a ack hie atest 168 Operations oo 169 11 3 4 Strings in Expressions gt visa vee ovenkek aa Chae He 170 Index Position and Sequence
318. xpression must be separated by a space For example the following is not legal lt 2 4 gt There must be a space before and after the operator lt gt lt 2 4 gt udm user 3207 Confidential amp Proprietary 167 UDM Command Format UDM Scripting Language Operator Precedence The operator order of precedence and reading left to right is 1 NOT 2 and 3 and 4 EQ NE LT GT LE and GE 5 AND OR and XOR To manually indicate that an operation is of higher precedence enclose it in parentheses and An expression is evaluated going from the inner most set of parentheses out Sets on the same level are evaluated left to right The following examples illustrates how parentheses can affect results In the following expression where lt gt takes precedence over lt gt lt 5 4 2 gt The expression yields the following value 13 However when the expression includes the following parentheses lt 5 4 2 gt The expression yields the following value 18 Nesting Expressions can be nested in order to indicate desired change precedence Nested expressions are bound by parentheses and When nested expressions are a part of an expression the deepest nested portions are evaluated first Also spaces are not required between the and when they are used for nesting as they are between operators and operands For example gt echo lt 5 5 2 gt 15 gt
319. y for the corresponding transfer server udm user 3207 Confidential amp Proprietary 232 Auditing Transfer Operations UDM Transfer Operations 12 9 Auditing Transfer Operations 12 9 1 Logging File Transfer Operations When the message level in the UDM server s configuration is set to audit the server writes audit messages to the broker log for each file transferred The following is an example of the audit messages produced NV3950A 1110470739 Transferring from host Enderlyn local 10 0 0 101 user root file Volumes Archive VPC Images DS_Store UNV3951A 1110470739 Transferring to host Aluminum local 10 0 0 100 user kevin file Users kevin Desktop tmp DS_Store UNV3952A 1110470739 Successfully transferred Volumes Archive VPC Images DS_Store on Enderlyn local to Users kevin Desktop tmp DS_Store on Aluminum local The first message is written when the transfer server receives a request to initiate a file transfer and contains the host name of the source machine the IP address of the source machine the user authenticated with UDM at the source of the transfer and the name of the source file to be transferred The second message is written when the destination transfer server acknowledges the file transfer requested and contains the host name of the destination machine the IP address of the destination machine the user authenticated with UDM at the destination of the transfer
320. y modification you will have to re access Universal Configuration Manager To exit Universal Configuration Manager without saving any of the modifications entries made on all property pages click the Cancel button 2 4 6 Accessing Help Information Universal Configuration Manager provides context sensitive help information for the fields and panels on every Universal Products component options screen To access Help 1 Click the question mark icon at the top right of the screen 2 Move the cursor now accompanied by the to the field or panel for which you want help 3 Click the field or panel to display Help text 4 To remove the displayed Help text click anywhere on the screen Windows Vista Windows Server 2008 The Universal Configuration Manager s context sensitive help is a WinHelp file which Windows Vista and Windows Server 2008 does not support Microsoft offers the 32 bit WinHelp engine as a separate download from its website If you require access to the Universal Configuration Manager s context sensitive help simply download and install the WinHelp engine udm user 3207 Confidential amp Proprietary 57 Universal Configuration Manager Features 2 4 7 Universal Data Mover Installed Components Universal Data Mover Manager Figure 2 5 illustrates the Universal Configuration Manager screen for the Universal Data Mover Manager The Installed Components list identifies all of the UDM Manager
321. y text editor udm user 3207 Confidential amp Proprietary 150 Universal Data Mover Server for UNIX 9 3 2 Configuration Options Table 9 2 identifies all UDM Server for UNIX configuration options Each Option Name is a link to detailed information about that configuration option in the Universal Data Mover 3 2 0 Reference Guide ACTIVITY_MONITORING Specification for whether or not product activity monitoring events are generated CODE_PAGE DATA_COMPRESSION Character code page used to translate text data Specification for whether or not data is compressed on all standard I O files DATA_SSL_CIPHER_LIST EVENT_GENERATION SSL cipher suites to use for data session between UDM primary and secondary servers Events to be generated as persistent events FRAME_INTERVAL Number of UDM transfer blocks transferred before a frame sync message is sent with network fault tolerance turned on INSTALLATION_DIRECTORY Directory on which UDM is installed MESSAGE_LEVEL Level of messages that UDM will write to the Universal message Catalog UMC file NETWORK_DELAY Expected network latency in seconds NLS_DIRECTORY Directory where the UDM Manager message catalog and code page tables are located OUTBOUND_IP RECONNECT_RETRY_COUNT Host or IP address that UDM binds to when initiating outgoing connections to another UDM server Number of attempts that the UDM Manager will ma

Universal Data Mover 3.2.0 User Guide

Contents

Download Pdf Manuals

Related Search

Related Contents