Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Macro name changed from html to html-bobswift during server to cloud migration processing.

...

The following example shows the same options for a batch execution in z/OS:

Panel

Html bobswift

<pre>
//jobname JOB CLASS=A,MSGCLASS=X
//STEP1 EXEC UDMPRC*
//UNVSCR1 DD * 
udm commands?? 
*/ 
//SYSIN DD * 
-script UNVSCR1 -options "file=* source=c:\source dest=c:\destination"*
*/ 
</pre>


For IBM i examples, see Universal Data Mover Manager for IBM i.

...

The following example illustrates the call command executing the copyfiles.udm script (as identified in the previous example):

Panel

Html bobswift

<pre>
UDM
UDM>call copyfiles.udm file=* source=c:\source dest=c:\destination
UDM>
UDM>quit
</pre>


Unlike executing a script from the command line, UDM will not exit automatically when it finishes processing a script invoked using the call command.

...

An example of how the copyfiles.udm script might look is as follows:

Panel

Html bobswift

<pre>
cd src=$(source)
cd dst=$(dest)
copy src=$(file)
</pre>


In this example:

  • Transfer server with the logical name src would change its directory to c:\source.
  • Transfer server with the logical name dst would change its directory to c:\destination.
  • All files in the c:\source directory then would be copied from the first transfer server over to the second.