ACTION - UEMLoad configuration option
Description
The ACTION option specifies the requested database operation. It is a required option.
Only one database operation can be specified for each invocation of the UEMLoad utility. The database operations supported by the UEMLoad utility are listed in Values, below.
Usage
Specification Method | Parameter / Value | IBM i | HP NonStop | UNIX | Windows | z/OS |
Command Line, Short Form | n/a |
|
|
|
|
|
Command Line, Long Form | -action {add | update | delete | list | export} |
|
| | |
|
Definition File Keyword | n/a |
|
|
|
|
|
Values
There are no values for this option. Instead, the desired action is specified by the parameter:
add | Writes one or more new event definition and/or event handler records to the appropriate database. |
update | Changes one or more existing event definition and/or event handler records. |
delete | Removes the specified event definition and/or event handler records from the appropriate database. |
list | Displays the complete contents of the specified event definition and/or event handler records. |
export | Dumps the contents of the specified event definition and/or event handler records to a text file that can be used as input to a subsequent run of the UEMLoad utility. |
add
If add is specified, any optional event definition or event handler parameters not specified will be provided with default values as specified in the UEM Server configuration. If an attempt is made to add a record that already exists, the operation will fail.
update
If update is specified, only those parameters being changed are required. Values for other parameters are obtained from the existing event definition or event handler record. If an attempt is made to update a record that does not exist, the operation will fail.
list
If list is specified, the only other recognized configuration options are:
export
If export is specified, the only other recognized configuration options are:
A Stonebranch Tip
To list or export all event definition and event handler records, no configuration options are required; simply specify the list or export action, respectively.
To export all records to a text file, simply specify a definition load file using the DEFINITION_FILE option.
In both cases, if no event ID, assigned component name, or handler ID is specified, all records in the event definition and event handler databases will be retrieved.