...
Using Handler Options when Storing Event Definitions
| Panel |
|---|
| Html bobswift |
|---|
<pre>
Example 1
UEMLoad utility:
uemload -add -event_id event001 -handler_opts ">netstat.txt"
-triggered_id handler001 -expired_id expiredhandler
-event_type file -filespec uemtest.dat
uemload -add -handler_id handler001 -cmd netstat
-encryptedfile userfile.enc
uemload -add -handler_id expiredhandler -cmd "echo Event expired"
-encryptedfile userfile.enc
UEM Manager command line:
uem -event_type file -filespec uemtest.dat
-host rmthost -user rmtuser -pwd password
-handler_opts ">dirout.txt" -triggered -cmd netstat
-expired -cmd "echo Event expired"
Example 2
UEMLoad utility:
uemload -add -event_id event002 -triggered_id handler002
-handler_opts "<appinput.dat >applog.txt 2>&1"
-event_type file -filespec uemtest.dat
uemload -add -handler_id handler002 -cmd someapp
-encryptedfile userfile.enc
UEM Manager command line:
uem -event_type file -filespec uemtest.dat
-host rmthost -user rmtuser -pwd password
-handler_opts "<appinput.dat >applog.txt 2>&1"
-triggered -cmd someapp
Example 3
UEMLoad utility:
uemload -add -event_id event003 -inact_date_time 2011.12.31,23:59
-handler_opts ">>backup.log 2>>backup_err.log"
-rejected_id handler003 -event_type file -filespec uemtest.dat
uemload -add -handler_id handler003 -cmd dailybkup
UEM Manager command line:
uem -event_type file -inact_date_time 2011.12.31,23:59 -filespec uemtest.dat
-host rmthost -user rmtuser -pwd password
-handler_opts ">>backup.log 2>>backup_err.log"
-rejected -cmd dailybkup
</pre>
|
|
For each of the event definitions shown above, the OS installed on the host
rmthost can be either Windows or UNIX. If the UEM Manager is executed from z/OS, the name of the executable (that is,
uem) would be omitted. However, the rest of the parameters would be entered as shown in the JCL's SYSIN DD statement.
...
