EMS FastStart Manual

Brief Review of Event Design

EMS FastStart Manual–133701

2-2

How to Design Events

To help give an overview of event design, the process has been divided into ten steps.

Each step uses the same set of 12 sample event messages as an example. These are the

same 12 event messages used in the COBOL85 program in Appendix C, COBOL85

Program Example

Step 1: Identify Event Owner (SSID)

Step 2: List Messages

Step 3: Identify Data in the Messages

Step 4: Identify Groups of Variables

Step 5: Assign Field Name, Type, and Number to Variables

Step 6: Assign Event Numbers

Step 7: Determine Event Subject

Step 8: Define Event Type – Informative, Action-Attention, Action-Completion, or

Critical

Step 9: Build Template File

Step 10: Assign a Group Field Number to Each Field

Step 1: Identify Event Owner (SSID)

Before defining events, you must identify the owner of the events. The DSM architecture

and the Event Management Services requires that each event generated by an application

be identified by a specific subsystem ID (SSID). The SSID is made up of three parts: a

subsystem owner, a subsystem number and a version field. In the COBOL85 ATM

example, the SSID is CUSTOMER.1.J00 where CUSTOMER is the subsystem owner, 1

is the subsystem number, and the version is J00.

The SSID identifies the owner of each event in the EMS log files. It can be used to build

a filter which selects events generated by a specific subsystem, for example, print only

the messages generated by the ATM application. Each application or subsystem should

have a different SSID; this will make event filtering and selection much easier.

For your application, you must assign an SSID using the standards defined by EMS.

Please refer to the EMS Manual for a detailed description of the valid SSID values.

Step 2: List Messages

Make a list of all event messages necessary for your application. For existing

applications, list all of the current messages (for example, do a code search). For new

applications, create a list of the messages you will need to generate. The example below

shows a typical list of event messages for a banking application.

Note. Steps 1 through 9 apply to both EMS and EMS FastStart. Step 10 applies to EMS

FastStart only.