Event Types
Overview
Each Universal Agent event is categorized by event type. Each event type uniquely identifies a specific class of events.
Each event type has a unique three-digit number. This number is identified in the eventType field of an Event Header.
Each Universal Agent component is assigned a range of numbers for its event types:
Universal Agent Component | Event Type Range |
|---|---|
Universal Agent (all) | 100-199 |
200-299 | |
300-399 | |
400-499 | |
700-799 | |
800-899 |
For detailed information on a specific event type, as identified in one of the following tables, click its Event Type Name.
Universal Agent
Universal Agent event types represent events that apply generically to all Universal Agent components. The header source fields identify the component that generated the event.
Universal Agent event types are in the range of 100-199.
Event Type Name | Number | Category | Description |
100 | Security | Authentication of a user identifier failed. | |
101 | Security | A client request was denied access to a Universal Access Control List protected resource. | |
102 | Security | Authorization was denied to a general resource. The resource is a non-UACL protected resource. |
Universal Command
Universal Command (UCMD) event types represent events that are generated by Universal Command Managers and Servers.
Universal Command event types are in the range of 200-299.
Event Type Name | Number | Category | Description |
200 | Start | A UCMD Server starts a job process at the request of a UCMD Manager. | |
201 | Stop | A UCMD Server detects the job process stopped. | |
204 | Status | UCMD Manager logs the work it has performed. | |
205 | Status | UCMD Server logs the work it has performed. |
Universal Broker
Universal Broker event types represent events that are generated by Universal Brokers.
Universal Broker event types are in the range of 300-399.
Event Type Name | Number | Category | Description |
300 | Start | Universal Broker has started and completed its stage 1 initialization steps. Stage 1 initialization steps include all steps required to initialize the event subsystem. | |
301 | Stop | Universal Broker has stopped. | |
302 | Start | Universal Broker started a Server component at the request of a client. | |
303 | Stop | Server component that the Universal Broker started has stopped. | |
304 | Status | Component's communication state changed. | |
305 | Start | Universal Broker detected the start of a Manager component. | |
306 | Stop | Universal Broker detected the stop of a Manager component. | |
307 | Log | Universal Broker receives and processes a request to stop a component. | |
308 | Start | Universal Broker has been notified by a Universal Command Manager that it has successfully restarted with a Universal Command Server. |
Universal Data Mover
Universal Data Mover (UDM) event types represent events that are generated by Universal Data Mover Managers and Servers.
Universal Data Mover event types are in the range of 400-499.
Event Type Name | Number | Category | Description |
Command-Related Events | |||
400 | Start | UDM opens a session. | |
401 | Start | UDM starts a copy operation. | |
402 | Start | UDM starts a directory copy operation. | |
403 | Start | UDM starts a delete operation. | |
404 | Start | UDM starts a rename operation. | |
405 | Stop | UDM session has stopped. | |
406 | Stop | UDM copy operation has stopped. | |
407 | Stop | UDM directory copy operation has stopped. | |
408 | Stop | UDM delete operation has stopped. | |
409 | Stop | UDM rename operation has stopped. | |
410 | Start | UDM mkdir operation has started. | |
411 | Stop | UDM mkdir operation has stopped. | |
412 | Start | UDM rmdir operation has started. | |
413 | Stop | UDM rmdir operation has stopped. | |
File-Related Events | |||
450 | Status | UDM file or directory is deleted. | |
451 | Status | UDM file is renamed. | |
452 | Start | UDM starts a transfer operation for an individual file or directory. | |
453 | Stop | UDM transfer operation for an individual file or directory has stopped. | |
454 | Status | UDM directory is created. | |
Execution Events | |||
470 | Start | UDM starts an EXEC operation. | |
471 | Stop | UDM EXEC operation ends. | |
472 | Start | UDM starts an EXECSAP operation. | |
473 | Stop | UDM EXECSAP operation ends. | |
UDM Sessions
In most operations, UDM is session oriented. A UDM session is a connection between a UDM Manager and one or more UDM servers through which commands are executed. There is no limit to the number of commands that can be executed (sequentially) in a given session. Sessions are identified by a session UUID that is created when an open command is issued in UDM.
It is also important to keep in mind that a single UDM Manager instance may establish and close (sequentially) more than one session during its lifetime.
Events are not issued for every UDM command, but some commands (file operation and the open command) will have events that are issued by the UDM manager. The body of command events will have a session UUID (if applicable) and a transaction ID. The transaction ID is an identifier used by UDM that uniquely identifies a given command within the context the UDM Manager instance. This identifier cannot be assumed to be unique outside of the manager instance in which it was generated.
Universal Enterprise Controller
Universal Enterprise Controller (UEC) event types represent events that are generated by Universal Enterprise Controller.
Universal Enterprise Controller event types are in the range of 700-799.
Event Type Name | Number | Category | Description |
700 | Status | This is a consolidated event generated by UEC. The contents of the event are consolidated from multiple related events received by UEC. | |
701 | Status | This is a consolidated event generated by UEC. The contents of the event are consolidated from multiple related events received by UEC. | |
702 | Status | This is a consolidated event generated by UEC. The contents of the event are consolidated from multiple related events received by UEC. |
Universal Control
Universal Control event types represent events that are generated by Universal Control Managers and Servers.
Universal Control event types are in the range of 800-899.
Event Type Name | Number | Category | Description |
800 | Start | Universal Control Server initiates a request for a control command to be executed by the local Universal Broker on behalf of a Universal Control Manager client. | |
801 | Stop | A control command initiated by a Universal Control Server has stopped. | |
802 | Log | Universal Control Manager requests the execution of a control command by a Universal Control Server. |