...
Due to this difference, in this example
stdout.txt is created in the current directory as set by the shell script and in the Windows example it is created in the UCMD server working directory.
| Panel |
|---|
set open exec quit1. set echo=yes
2. open r=houston user=joe pwd=abcdefg port=7887
3. exec r cmd="sh /home/joe/wrk/xmp/ls/ls.sh" user=joe pwd=abcdefg port=7887
4. quit |
UDM Script Explanation
...
The stdout stream is returned by the UDM Server to the UDM Manager and is output to the transaction log.
| Panel |
|---|
cd /home/joe/wrk/xmp/ls
ls > stdout.txt
cat stdout.txt |
Output sent to
stdout.txt.
Output sent to the UDM transaction log via stdout from the UDM Manager.
| Panel |
|---|
open exec quit2011.07.28 10.13.06.845 UNV2800I Universal Data Mover 6.3.0 Level 0 Release Build 104 started.
2011.07.28 10.13.06.845 Processing script: ls.udm
2011.07.28 10.13.06.847 open r=houston user=joe pwd=* port=7887
2011.07.28 10.13.07.114 Data session established using cipher: NULL-MD5
2011.07.28 10.13.07.159 Two party session established with r (component 1278600806)
2011.07.28 10.13.07.161 Transfer mode settings:
2011.07.28 10.13.07.198 type=binary
2011.07.28 10.13.07.198 trim=no
2011.07.28 10.13.07.198 Session options:
2011.07.28 10.13.07.198 Keep Alive Interval: 120
2011.07.28 10.13.07.198 Network Fault Tolerant: yes
2011.07.28 10.13.07.198 exec r cmd="sh /home/joe/wrk/xmp/ls/ls.sh" user=joe pwd=* port=7887
ls.sh
stdout.txt
2011.07.28 10.13.08.072 quit
2011.07.28 10.13.08.074 Session closed
2011.07.28 10.13.08.074 Finished processing script: ls.udm
2011.07.28 10.13.10.074 UNV2801I Universal Data Mover 6.3.0 Level 0 Release Build 104 ended successfully. |
UDM exec Command Parameters
...
