EMS FastStart Manual Abstract This manual provides information about the EMS FastStart program including installation, event message design, instructions for running the program, and customizing EMS FastStart to fit the specific needs of your application. In addition, this manual covers event message design to help you make the best use of the EMS FastStart program. The code examples in this manual are written in COBOL85.
Document History Part Number Product Version Published 031022 Guardian 90 C20 March 1990 058659 Guardian 90 C20 February 1991 133701 Guardian 90 C20 August 1997 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .99 site update tape (SUT).
New and Changed Information This is the third edition of the EMS FastStart Manual. This is only a revision of the format. No content has been changed. The following is the New and Changed Information from the second edition, the last edition with changes in content: New Features EMS FastStart has the following new features: • • • • • • The token ZEMS-TKN-SUPPRESS-DISPLAY is now supported. Viewpoint and the EMS distributors use this token to select whether a specific event is displayed.
Changed Information New and Changed Information definitions, which will then be used later by the EMS Template Services for generating your application template file. Changed Information EMS FastStart has the following changed information: • • The file names of the ATM example have changed. See Section 3, Installing and Configuring EMS FastStart.
Contents New and Changed Information iii About This Manual xi Notation Conventions xiii 1. Introduction EMS FastStart Features 1-1 How EMS FastStart Works 1-3 EGEN 1-3 Test Program and Filter 1-3 DDL Source Files for C, COBOL85, and TAL 1-4 Choosing Between EMS and EMS FastStart 1-4 System and Program Requirements 1-5 Using Template Services with EMS FastStart 1-5 2.
4. Preparing the Application Configuration File Contents Security Considerations 3-6 Compiler Access 3-6 READ Access to Files 3-6 4. Preparing the Application Configuration File Application Configuration File 4-1 Default Application Configuration File 4-2 Modifying the ACF 4-3 Field Definitions 4-7 Adding Data Types with EXTRADDL 4-7 EGEN Default Values 4-9 Example 4-9 5.
. Testing Program and Filter Contents EGEN Operating Modes (continued) Open^egen^collector 6-3 EGEN 6-4 Complete^egen^operation 6-6 Close^egen^collector 6-7 EGEN Parameters 6-7 Egen-record Fields Definition 6-8 An Example Using Mode 2 6-9 EGEN Default Values 6-11 Example 6-11 Application Modifications 6-13 Global Program Modifications 6-14 Event-Specific Modifications 6-15 Specify Event Types 6-15 Specify Event Subject 6-17 Move Values to the Event Record 6-18 Pass the Record Structure to EGEN 6-19 Error
Contents D. DDL, Copy Libraries and Templates Example D. DDL, Copy Libraries and Templates Example ATM Example, EVENT DEFINITION SOURCE FILE: SATMDDL D-1 ATM Example, COBOL85 COPYLIB: ATM1COB D-3 ATM Example, DSM Templates Services Source File: SATMTMPL D-10 E. Filter Index Examples Example 3-1. Example 4-1. Example 4-2. Example 4-3. Example 6-1. Example 6-2. Example 6-3. Example 6-4. Example 6-5. Example 6-6. Example 6-7. Example 6-8. Example 6-9. Example 6-10. Example 6-11. Example 6-12. Example 6-13.
Tables Contents Figure 6-1. Application Modification Phases 6-13 Tables Table 2-1. Table 4-1. Table 4-2. Table 6-1. Table 6-2. Table 6-3. Table 6-4. Table 6-5.
Contents EMS FastStart Manual– 133701 x
About This Manual This manual provides information about the EMS FastStart program including installation, event message design, instructions for running the program and customizing EMS FastStart to fit the specific needs of your application. In addition, this manual covers event message design to help you make the best use of the EMS FastStart program. The code examples in this manual are written in COBOL85.
Related Documents About This Manual • • Section 7, Testing Program and Filter, contains information on the EMS FastStart test program and the use of the filter program with a printing distributor. Appendixes A through E contain the EMSFS and EGEN error, warning, and advisory messages, a COBOL85 program example, copy libraries, a sample template source file, and the filter program.
Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name [ ] Brackets.
Notation for Messages Notation Conventions An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.
Notation for Management Programming Interfaces Notation Conventions [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
Change Bar Notation Notation Conventions Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
1 Introduction EMS FastStart enhances development of applications under Distributed Systems Management (DSM). EMS FastStart provides a simple, cost-effective way for programmers to develop and test EMS event messages. Event Management Service (EMS) is a component of DSM that is used for collecting and distributing events. EMS FastStart generates and compiles a number of source files which are used to simplify event generation and testing.
EMS FastStart Features Introduction Figure 1-1 shows the EMS FastStart process and the resulting components. Figure 1-1. The EMS FastStart Process ACF User Subvol App Prefix App SSID owner App SSID # App SSID version FIELD 1 TYPE FIELD 1 NAME FIELD x TYPE FIELD x NAME EMS Faststart The ACF (Application Configuration File) is an edit file you use to setup your event parameters.
How EMS FastStart Works Introduction How EMS FastStart Works EMS FastStart is a TACL-based code generator which generates and compiles a number of source files which are used to simplify event generation and testing. EMS FastStart creates these routines, programs, and copy libraries: • • • EGEN Test Program and Filter DDL Source Files for C, COBOL85, and TAL EGEN EGEN is a TAL routine that provides a high-level interface between your application and the Event Management Service (EMS).
Introduction DDL Source Files for C, COBOL85, and TAL validation. Also, you can isolate testing data from production data by writing events to a location other than the event log. When used with EGEN, the testing program and filter create an interactive testing facility which allows immediate testing of newly defined events through an easy-to-use conversational interface.
System and Program Requirements Introduction • • • • The application has events that include error lists or foreign tokens (tokens owned by a different subsystem than the subsystem generating the event). The user of the application needs to check that the correct set of tokens is included in an event at the time the event is generated. EMS FastStart cannot perform explicit checking of the event-generating subprogram.
Introduction Using Template Services with EMS FastStart EMS FastStart Manual– 133701 1 -6
2 Brief Review of Event Design This section provides guidelines and standards for programmers to follow when designing events. EMS FastStart is designed to simplify the process of generating EMS event messages. It is necessary to design event standards for programmers to follow, whether EMS is used by itself or with EMS FastStart. These standards can increase the overall efficiency of development efforts as well as enable more efficient operation and management of the subsystem.
How to Design Events Brief Review of Event Design 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.
Step 3: Identify Data in the Messages Brief Review of Event Design Example: 1. ATM SFMAIN01 is up at 245 A St. San Francisco. 2. ATM SFMAIN02 is up at 245 A St. San Francisco. 3. Insufficient funds in account 34503933. Access denied on ATM OAKWEST1 at 245 Oak St. Oakland. 4. Insufficient funds in account 23409344. Access denied on ATM SACTO99 at 341 Main St. Sacramento. 5. ATM SFMAIN02 at 245 A St. San Francisco is low on funds. 6. ATM SFMAIN01 at 245 A St. San Francisco is low on funds. 7.
Step 4: Identify Groups of Variables Brief Review of Event Design 6. ATM SFMAIN01 at 245 A St. San Francisco is low on funds. 7. ATM LACENT99 is down at 320 Main St. Los Angeles. 8. ATM LACENT91 is down at 320 Main St. Los Angeles. 9. Security breach on account 23457320. Number of accesses attempted 3; ATM SACTO02 is down at 230 State St. Sacramento. 10. Security breach on account 34094443. Number of access attempted 2; ATM SACTO01 is down at 230 State St. Sacramento. 11.
Step 4: Identify Groups of Variables Brief Review of Event Design 245 A St. San Francisco 245 Oak St. Oakland 341 Main St. Sacramento 320 Main St. Los Angeles 230 State St. Sacramento 125 8th Ave. Los Angeles 3. Account Number 23409344 23457320 34094443 4. Hardware Component cash dispenser 5. Hardware Subcomponent 321561ac 6. Serial Number 231234093 343223480 7. Sense Status 0101110101 1010111011 8.
Step 5: Assign Field Name, Type, and Number to Variables Brief Review of Event Design Step 5: Assign Field Name, Type, and Number to Variables This step is the beginning of defining the variable data fields for your application. Each variable data field has three components: • • • FIELD-x-NAME FIELD-x-TYPE FIELD-x-NUMBER Note that the number between the hyphens (for example, x in the example above) is the group field number.
Step 5: Assign Field Name, Type, and Number to Variables Brief Review of Event Design FastStart uses the data types (see the DSM Programming Manual for more information) listed in Table 2-1 below. Table 2-1.
Step 5: Assign Field Name, Type, and Number to Variables Brief Review of Event Design Examples of Field Names, Types, and Numbers Assigned to Variables Here are examples of field names, types, and numbers assigned to variables: Field name: ATM-NAME Field type (DDL): ZSPI-DDL-CHAR8 Field number: 100 Variables: SFMAIN01 SFMAIN02 OAKWEST1 SACTO01 SACTO02 SACTO99 LACENT98 LACENT99 Field name: ATM-LOCATION Field type (DDL): ZSPI-DDL-CHAR24 Field number: 200 Variables: 245 A St.
Step 6: Assign Event Numbers Brief Review of Event Design Variables: 3 2 Field name: ATM-HW-COMPONENT Field type (DDL): ZSPI-DDL-CHAR24 Field number: 500 Variables: cash dispenser Field name: ATM-HW-SUBCOMPONENT Field type (DDL): ZSPI-DDL-CHAR24 Field number: 600 Variables: 321561AC Field name: ATM-SERIAL-NUMBER Field type (DDL): ZSPI-DDL-INT2 Field number: 700 Variables: 231234093 343223480 Field name: ATM-SENSE-STATUS Field type (DDL): ZSPI-DDL-INT2 Field number: 800 Vari
Step 6: Assign Event Numbers Brief Review of Event Design An event message template is the design of the fixed text and variable data for one event. All of the event messages produced by the numbered event type will differ only in the contents of the variable data fields. There are several reasons to assign unique event numbers: • • • An event can have a probable cause and a recommended action database within Viewpoint. This database is keyed into by a subsystem ID and an event number.
Step 7: Determine Event Subject Brief Review of Event Design Security breach on account 34094443. Number of accesses attempted 3; ATM SACTO01 is down at 230 State St. Sacramento. EVENT 202 ATM-EVT-HW-FAILURE Hardware failure on ATM LACENT99 at 125 8th Ave. Los Angeles. Component failed is cash dispenser; subcomponent 321561ac; serial number 231234093; sense status 0101110101. Hardware failure on ATM LACENT98 at 125 8th Ave. Los Angeles.
Step 9: Build Template File Brief Review of Event Design can be used without the other. An event is classified informative by default unless otherwise specified. Section 6, Building Your Application for Event Generation, has more information on event types and lists sample code for each. Each programmer decides which type is appropriate for each message needed for an application.
Step 10: Assign a Group Field Number to Each Field Brief Review of Event Design For more information on how to build this file, see the DSM Template Services Manual. In order to create and then compile your application template source file, you need to know the name of the corresponding token that matches each of the application fields you define in the ACF. These tokens are created by EMS FastStart during the generation process and are defined in a DDL source file (for example, ATM1DDLS).
Step 10: Assign a Group Field Number to Each Field Brief Review of Event Design not work. (The group field number is an internal value used by the program to keep track of the number of fields.) Note that the group field number is distinct from the field number (for example, 1 in FIELD-1-NUMBER) and the event number. When you follow these steps in designing your event messages, you create the subsystem portion of the ACF.
Brief Review of Event Design Step 10: Assign a Group Field Number to Each Field EMS FastStart Manual– 133701 2- 15
3 Installing and Configuring EMS FastStart This section has three parts. The first part describes the EMS FastStart Installation procedure, including Installing EMS FastStart on the Installation Subvolume and Installing EMS FastStart on a Working Subvolume, and a list of Post-installation Files that should be on your system after successful installation of EMS FastStart.
Installing and Configuring EMS FastStart Post-installation Files Post-installation Files After the installation is complete, the following files will be in the EMS FastStart installation subvolume (ISV) and in your working subvolume: CCF Compiler Configuration File, used to modify the run time environment of EMS FastStart. CEGNDECS C Library Header for EGEN Procedure (Needed by C programs). EGENDECS EGEN TAL Procedures Declaration File. EMSFS TACL macro file used to attach the segment file.
The Default Compiler Configuration File (CCF) Installing and Configuring EMS FastStart The Default Compiler Configuration File (CCF) The Compiler Configuration File (CCF) is used to modify the EMS FastStart generation compiler attributes to reflect a specific installation. The CCF contains key words which have parameters you can modify for each installation. Example 3-1 shows the contents of the default CCF for EMS FastStart. Example 3-1.
Modifying the CCF Installing and Configuring EMS FastStart Modifying the CCF The CCF contains key words which are reserved by EMS FastStart and cannot be modified. However, each key word has a parameter which you can modify to customize the CCF for a specific installation. The list below and on the following page shows the EMS FastStart CCF key words and their parameters.
Installing and Configuring EMS FastStart Key Word Parameter DDL-PRIORITY ddl-priority Modifying the CCF The parameter specifies the priority at which the DDL compiler will execute (for example, 100). Valid values for this parameter are 1 through 199. DDL-WORK-VOLUME ddl-work-volume The parameter specifies the volume which will be used by the DDL compiler to create its temporary files during the compilation process (for example, $SWAP).
Installing and Configuring EMS FastStart Security Considerations After the CCF is modified to reflect your specific environment, the system manager can run EMS FastStart with the default ACF (ATMACF) supplied to test the installation and configuration (also see Section 5, Running EMS FastStart, and Section 7, Testing Program and Filter, for more information). Security Considerations There are two security considerations: compiler access and READ access to files.
4 Preparing the Application Configuration File Before you use EMS FastStart, you must modify the Application Configuration File (ACF) parameters to generate the customized EGEN procedure for your application. This section outlines the procedure for Modifying the ACF. In Application Configuration File the features and restrictions of the ACF are described. Next, a listing of the Default Application Configuration File is shown followed by the key words and parameters used to modify the ACF.
Preparing the Application Configuration File • Default Application Configuration File The FIELD-X-TYPE parameter must be a Subsystem Programmatic Interface (SPI) definition supported by EMS FastStart (for example, ZSPI-DDL-CHAR8). If you are creating an application, you can design your application’s events to take advantage of EMS FastStart’s features. If you are converting an existing application, you can search your application’s code for event messages and organize them for EMS FastStart.
Preparing the Application Configuration File Modifying the ACF Example 4-1.
Preparing the Application Configuration File Key Word Parameter USER-SUBVOL user-subvol Modifying the ACF The parameter specifies the location where EMS FastStart will create all the source and object files. EMS FastStart creates files on behalf of the user. Therefore, the user must have CREATE access on the designated USER-SUBVOL.
Preparing the Application Configuration File Key Word Parameter APPLICATION-SSIDOWNER application-ssid-owner Modifying the ACF The parameter defines the owner of the event buffer and must be an eight-character string or less to identify your company or organization. The owner name must start with an alpha character and contain only alphanumeric characters and hyphens. Blanks are allowed only at the end for padding.
Preparing the Application Configuration File Key Word Parameter FIELD-X-TYPE field-x-type Modifying the ACF The parameter specifies which variable data types are supported by EGEN.
Preparing the Application Configuration File Field Definitions Field Definitions For each field defined in the ACF, you need to specify three things: the field name, the field type, and the field number. Each must share the same value for X, the group field number. For example: FIELD-x-NAME field-x-name FIELD-x-TYPE field-x-type FIELD-x-NUMBER field-x-number The field name, type, and number are always defined as a group. The “x” represents the group field number.
Preparing the Application Configuration File Adding Data Types with EXTRADDL Example 4-2. Adding a New Data Type to the EXTRADDL File *--------------------------------------------------------------------* * EMS Fast Start - T9263020 - (17MAR91) * * File Type: DDL Source Schema * * Source File Name: Extraddl * * Generation Time: July 7, 1988 * * Language Compiler Required: Data Definition Language (DDL) * * Compiler Version Required: C20 * * Source Library File Produced: None, see below.
EGEN Default Values Preparing the Application Configuration File EGEN Default Values EGEN default values are used by the EGEN procedure to determine if information should be added to the event buffer. EGEN compares the value of each field defined in your ACF against a set of default values. Each field type supported by EGEN has a specific default value.
Example Preparing the Application Configuration File Table 4-1. Field Content After Call to Initialize^egen^record Procedure (page 2 of 2) FIELD-NAME FIELD-TYPE FIELD-VALUE ATM-HW-SUBCOMPONENT ZSPI-DDL-CHAR24 24 spaces ATM-SERIAL-NUMBER ZSPI-DDL-INT2 2147483647 ATM-SENSE-STATUS ZSPI-DDL-INT2 2147483647 Note. For character fields such as ZSPI-DDL-CHAR8 and ZSPI-DDL-CHAR24, the default value is 8 and 24 spaces respectively.
Preparing the Application Configuration File Example TAL module with your application. Remember, it is important to choose default values which are unlikely to occur in your application. Do not use a common or likely value as a default. In the example above, a “real-life” ATM-RETRY-LIMIT value is unlikely to match the default value of 32767; however, it is likely that a value of 4 might be passed to the field-value. Therefore, 4 would not be a wise choice as a default value for that field type.
Preparing the Application Configuration File EMS FastStart Manual– 133701 4- 12 Example
5 Running EMS FastStart This section describes how to run EMS FastStart. It outlines the procedure for first Setting Up the EMS FastStart Environment and then Running EMSFS with the GENERATE command. The message you receive after a successful completion of the setup as well as two possible error messages if the setup cannot be completed are shown and explained. Then, Stopping EMSFS and Detaching the Segment File after the run is completed is described.
Running EMS FastStart Setting Up the EMS FastStart Environment Setting Up the EMS FastStart Environment Before using EMS FastStart, you must attach the EMSFSC20 segment file to your TACL. A TACL macro is provided to simplify this operation. Enter the following commands exactly as specified to be sure that your working environment is properly initialized.
Running EMSFS Running EMS FastStart Error Message 2 EMS FastStart - T9263C20 - (17MAR91) Copyright Tandem Computers Incorporated 1989,1990,1991 ** Error 2 ** Unable to locate the EMSFSC20 segment files. Probable Cause: Your current default subvolume () does not contain EMSFSC20 segment files. Recommended Action: Please change your default subvolume to the location of the EMS FastStart subvolume and reissue the RUN command by entering the following commands: VOLUME $.
Running EMS FastStart–ATM Example Running EMS FastStart Running EMS FastStart–ATM Example This section shows you how to generate a sample run of EMS FastStart using the default ACF called SATMACF. Following the command entries, a listing of what you will see on your screen is shown.
Parameter Validation (Steps 1-2) Running EMS FastStart --- Source File Name: SATMACF --- Description: This ACF implements the ATM example. --- Modifications Summary: Date of Modification --- This is the first release of this file 16 September, 1989 --- Modified for the T9263C20 release 21 November, 1990 --- 1- Added the following key words: SAVE-DDL-DICTIONARY -USER-DDL-FILE --- 2- Changed the version from A00 to B00.
Cleaning the Subvolume (Step 3) Running EMS FastStart STEP #2: Reading and validating the CCF: $DATA.ZEMSFS.CCF.
Automatic Compilation (Steps 9 - 13) Running EMS FastStart October 15, 1989 22:25:08 STEP #6: Creating the FILTER source file: $DATA.ATM.ATM1EMFS. October 15, 1989 22:25:10 STEP #7: Creating the COBOL85 test program source file: $DATA.ATM.ATM1PROS. October 15, 1989 22:25:17 STEP #8: Creating the TAL EGEN module source file: $DATA.ATM.ATM1EGES. October 15, 1989 22:25:38 Automatic Compilation (Steps 9 - 13) Next, EMS FastStart automatically compiles the various files just created.
File Creation: ATM1TEST and ATM1INDX (Steps 14 - 16) Running EMS FastStart Object file: $DATA.ATM.ATM1EGEN. Listing file: $S.#EMSFS.ATM1EGEN. October 15, 1989 22:33:49 STEP #12: Starting the compilation of the COBOL85 test program. COBOL85 COBOL85 COBOL85 COBOL85 compiler compiler compiler compiler location: execution cpu: execution priority: work volume: $SYSTEM.SYSTEM.COBOL85. 0. 100. $SYSTEM. Source file: $DATA.ATM.ATM1PROS. Object file: $DATA.ATM.ATM1PROG. Listing file: $S.#EMSFS.ATM1PROG.
EMSFS Messages Running EMS FastStart The EMS FastStart generation process is now complete. Use the EMSFS:STOP command to free memory segment space within your TACL by detaching the EMSFSC10 or EMSFSC20 segment file. At the TACL prompt enter the STOP command: TACL> EMSFS:STOP This message will be displayed: EMS FastStart - T9263C20 - (17MAR91) Copyright Tandem Computers Incorporated 1989,1990,1991 ** Comment 2 ** Environment stopped.
EMSFS Components Running EMS FastStart ATM1TAL TAL definitions used by EGEN. ATM1TEST TACL macro file to set up the defines for EGEN and start the ATM1PROG. ATM1UCOB User-defined event numbers in a COBOL85 copylib format. ATM1UDDL User-defined event numbers in a DDL schema source file. EMSFS Components The EMS FastStart generation and compilation process produces a TAL routine called EGEN, a test program, a filter, copy libraries, and DDL source files.
DDL Running EMS FastStart DDL After the generation process, the user subvolume contains DDL source code that produces the copy libraries for COBOL85 and TAL, the two programming languages supported by EMS FastStart. Files: ATM1DDLS Copy Libraries Copy libraries for your application are produced by the compilation of the DDL source file.
Filter Running EMS FastStart Filter A filter is created and compiled by EMS FastStart which can be run with a printing distributor or Viewpoint to test your application events. The interactive testing facility allows immediate testing of newly-defined events and filters through an easy-to-use conversational interface.
6 Building Your Application for Event Generation To use EMSFS, you must modify your application to use the EGEN module generated by EMS FastStart. These modifications will enable you to generate the event messages needed for your application. This section includes information on defining, modifying, and compiling an application (EGEN Operating Modes). It details the specific steps a programmer must take to use EGEN with a specific application and shows how to use EGEN with a COBOL85 program (Mode 1).
Mode 2 Building Your Application for Event Generation Mode 2 Mode 2 can be used by applications which generate many events. Mode 2 is like mode 1 but opens the defined collector only once, which reduces the use of system resources to generate events. The only disadvantage of this mode is that EGEN completes the write operation before returning to the calling program. In some cases, this may cause unacceptable delays for the application.
Building Your Application for Event Generation Open^egen^collector Example 6-1. Syntax for the Initialize^egen^record Procedure { status := } INITIALIZE^EGEN^RECORD ( egen^record ) ! i/o { CALL } status returned value INT on return, is one of the following numbers: <> 0 No Error 0 An error occurred when initializing the egen^record. Please refer to Appendix B for the list of warnings or errors that can be returned by this procedure. egen^record INT input, output .
Building Your Application for Event Generation EGEN Example 6-2. Syntax of the Open^egen^collector Procedure { status := } Open^egen^collector ( collector^file^number, ! o { CALL } [sync^depth], ! i error^detail ) ! o status returned value INT on return, is one of the following numbers: <> 0 No Error 0 An error occurred when opening the collector. Please refer to Appendix B for the list of warnings or errors that can be returned by this procedure.
EGEN Building Your Application for Event Generation Example 6-3. Syntax for the EGEN Procedure { status := } EGEN ( egen^record, { CALL } [collector^file^number], [event^buffer^ptr], [tag], [event^buffer^used] ) status ! ! ! ! ! i i i i o returned value INT on return, is one of the following numbers: <> 0 No Error 0 An error occurred within Egen. Please refer to Appendix B for the list of warnings or errors that can be returned by this procedure. egen^record INT input .
Building Your Application for Event Generation Complete^egen^operation Complete^egen^operation This procedure is used to complete the WRITEX or WRITE-READX nowaited I/O on the collector file on behalf of the user application. Example 6-4 shows the syntax for this procedure. Example 6-4.
Close^egen^collector Building Your Application for Event Generation Close^egen^collector The Close^egen^collector procedure is used to close the current collector file on behalf of the user application. Example 6-5 shows the syntax for this procedure. Example 6-5.
Building Your Application for Event Generation Egen-record Fields Definition Egen-record Fields Definition The Egen-record structure is the principal interface between an application and EGEN. Based on the values of these fields, EGEN will generate an event. Table 6-3 shows each of the fields and their descriptions. Note that all the user defined fields in the ACF will also be added to the egen-record. These fields are not described here because they are specific to each application. Table 6-3.
Building Your Application for Event Generation An Example Using Mode 2 Table 6-3. Egen-record Fields and Descriptions (page 2 of 2) Field Name Field Data Type and Description suppress-display ZSPI-DDL-BOOLEAN If TRUE, tells the Viewpoint application not to display the event message; Viewpoint will display it if the token is either FALSE or missing. By default, the value is FALSE, which mean that the event will be displayed on Viewpoint.
An Example Using Mode 2 Building Your Application for Event Generation Example 6-6 opens the collector at the beginning of the program and stores the filenumber in a variable (section 205-open-collector in the example). In Example 6-6 the variable is called file-number.
EGEN Default Values Building Your Application for Event Generation EGEN Default Values EGEN default values are used by the EGEN procedure to determine if information should be added to the event buffer. EGEN compares the value of each field defined in your ACF against a set of default values. Each field type supported by EGEN has a specific default value.
Example Building Your Application for Event Generation Table 6-4. Field Content After Call to Initialize^egen^record Procedure (page 2 of 2) FIELD-NAME FIELD-TYPE FIELD-VALUE ATM-HW-SUBCOMPONENT ZSPI-DDL-CHAR24 24 spaces ATM-SERIAL-NUMBER ZSPI-DDL-INT2 2147483647 ATM-SENSE-STATUS ZSPI-DDL-INT2 2147483647 Note. For character fields such as ZSPI-DDL-CHAR8 and ZSPI-DDL-CHAR24, the default value is 8 and 24 blanks respectively.
Application Modifications Building Your Application for Event Generation however, it is likely that a value of 4 might be passed to the field-value. Therefore, 4 would not be a wise choice as a default value for that field type. Example 6-7.
Global Program Modifications Building Your Application for Event Generation Global Program Modifications Add the SEARCH Directive Add the ?SEARCH directive to the user application, specifying the location of EGEN. The compiler must know where EGEN resides in order to bind it with your application. Example: ?SEARCH $data.atm.atm1egen Add New Variables Add variables for the specific values needed by EGEN.
Event-Specific Modifications Building Your Application for Event Generation Example 6-8. Copy Statement Example from the COBOL85 ATM Sample Program COPY egen-record COPY atm-ssid COPY egen-interface-definitions OF "$data.atm.atm1cob". OF "$data.atm.atm1cob". OF "$data.atm.atm1cob". COPY user-event-numbers COPY user-action-id OF "$data.atm.atm1cob". OF "$data.atm.atm1cob".
Specify Event Types Building Your Application for Event Generation Example 6-10. Sample Code for Generating Action-Attention Events GENERATE-ACTION-ATTENTION. PERFORM 300-initialize-egen-record. MOVE MOVE MOVE MOVE MOVE MOVE ACTION-ATTENTION-EVENT USER-ACTION-ID-1 ATM-EVT-LOW-ON-CASH "SFMAIN02" "atm-name" "245 A St., San Francisco" TO TO TO TO TO TO event-type OF egen-record. action-id OF egen-record. event-number OF egen-record. atm-name OF egen-record. subject-field-name OF egen-record.
Specify Event Subject Building Your Application for Event Generation Example 6-12. Sample Code for Generating Action Completion Events with Suppress Display GENERATE-ACTION-COMPLETION. PERFORM 300-initialize-egen-record. MOVE MOVE MOVE MOVE MOVE MOVE MOVE ACTION-COMPLETION-EVENT COBOL-VAL-TRUE ATM-ACTION-ID-1 ATM-EVT-BACK-ONLINE "SFMAIN02" "atm-name" "245 A St., San Francisco" TO TO TO TO TO TO TO event-type OF egen-record. SUPPRESS-DISPLAY OF egen-record. action-id OF egen-record.
Building Your Application for Event Generation Move Values to the Event Record The application needs to tell EGEN which field in the event buffer is the subject of the event. This is accomplished in the user's application by moving the name of the selected field to another field called subject-field-name. At this point, you can move the specific values into the field that will become the subject. The following example illustrates the point.
Pass the Record Structure to EGEN Building Your Application for Event Generation Example 6-15. ATM COBOL85 Example ?HEADING "240-ATM-DOWN SECTION" / 240-atm-down. *----------------------------------------------------------------------* EVENT # 200: ATM IS DOWN: * * the fields within the EGEN record which are used for event # 200: * * event-type PIC S9(4). * event-number NATIVE-2. * atm-name PIC X(8). * atm-location PIC X(24). * event-text PIC X(254).
Building Your Application for Event Generation Compile Application The following is a list of procedures for which errors, warnings, and advisory return codes are returned to the calling application. (The return codes for each procedure are listed and described in Appendix B, EGEN Messages.
Building Your Application for Event Generation Define Run-time Parameters Using TACL to Set up and Change DEFINEs To add the DEFINEs to your application, use the following TACL macro. Example 6-16 shows how to add DEFINE values for =_EMS_COLLECTOR and =_EGEN_ADD_EVENT_TEXT. Example 6-16. TACL Macro File == == ?TACL MACRO == #OUTPUT Adding the =_EMS_COLLECTOR define. == == == The define =_EMS_COLLECTOR is used to specify the location of the == collector to EGEN. (The default collector is $0).
Building Your Application for Event Generation EMS FastStart Manual– 133701 6- 22 Define Run-time Parameters
7 Testing Program and Filter EMS FastStart generates a Testing Program, xxxxPROG (where xxxx is the name of your USER-SUBVOL-FILE-PREFIX), and an EMF filter (Using the Filter Program with a Printing Distributor), xxxxEMFO, to help you test your customized EGEN module before you bind EGEN with your application. You can use the testing program and the filter to generate event messages similar to those you want your application to generate.
Testing Program Sample Session Testing Program and Filter • • • Text of the event Value for each field defined in the ACF Field which will be the subject of this event. Testing Program Sample Session A TACL macro file is created for you on the subvolume which contains the EMSFS testing program. This macro file adds the =_EMS_COLLECTOR and the =_EGEN_ADD_EVENT_TEXT DEFINES and then initializes them with default values ($NO is the =_EGEN_ADD_EVENT_TEXT default value).
Testing Program Sample Session Testing Program and Filter Example 7-1.
Using the Filter Program with a Printing Distributor Testing Program and Filter Using the Filter Program with a Printing Distributor This section shows how to display the event messages generated by the EMS FastStart testing program. Please refer to the Event Management Service Manual for a detailed explanation of how to start and configure an EMS distributor (EMSDIST).
Filtering on Specific Tokens Testing Program and Filter The following examples show the token name created by the ATM example used throughout this manual. Please note that the token field name syntax is shown as TACL compatible since this syntax will be used by the filter compiler. In this example, the USER-VARIABLES-PREFIX is ATM.
Filtering on Specific Tokens Testing Program and Filter EMS FastStart Manual– 133701 7 -6
A EMS FastStart Messages These code samples show the run-time errors, warnings, and advisory messages you may receive when you run EMS FastStart.
EMS FastStart Messages The following errors and warnings and their probable causes and recommended actions may appear on your terminal during an EMS FastStart run. ** Error 4 ** Unable to purge a file in the subvolume. Probable cause: Purge error: on file . Recommended action: EMS FastStart cannot continue because of this error and is terminating. Please check the file security on your user subvolume. ** Warning 50 ** The ACF does not exist.
EMS FastStart Messages ** Error 53 ** Missing Parameter or Invalid key word. Probable cause: EMS FastStart detected that no parameters were supplied for this keyword or the key word expected was: . Recommended action: Please correct the ACF by specifying a valid key word or a valid parameter. ** Error 54 ** Invalid ACF file or missing key word. Probable cause: EMS FastStart was expecting the .
EMS FastStart Messages ** Error 59 ** The ZSPIDEF-SUBVOL parameter is invalid. Probable cause: One of the following files: ZEMSTACL, ZEMSTAL, ZEMSDDL, ZSPIDDL, ZSPITACL, or ZSPITAL was not validated by EMS FastStart because of the following reason: The file does not exist. Recommended action: Please correct the ZSPIDEF-SUBVOL parameter to point to the right location. ** Error 60 ** The USER-SUBVOL parameter is invalid.
EMS FastStart Messages ** Error 64 ** The APPLICATION-SSID-NUMBER parameter is invalid. Probable cause: It must be between 0 and 32767. Recommended action: Please correct the APPLICATION-SSID-NUMBER parameter in the ACF. ** Error 65 ** The APPLICATION-SSID-VERSION parameter is invalid. Probable cause: It must be exactly 3 characters long ( 1 alphabetic character + 2 numeric characters (e.g. A00, C10). Recommended action: Please correct the APPLICATION-SSID-VERSION parameter in the ACF.
EMS FastStart Messages ** Warning 70 ** The FIELD--TYPE parameter was not validated. Probable cause: EMS FastStart was not able to validate this field data type since it is not one of the default data type supported. The supported data type are described in the EMS FastStart manual. Recommended action: If this data type was added in the EXTRADDL file, then you can ignore this warning.
EMS FastStart Messages ** Error 74 ** Invalid field type. Probable cause: The FIELD--TYPE keyword parameter does not start with a ZSPI- DDL-CHAR form. Recommended action: Please specify a valid FIELD--TYPE. ** Error 75 ** The SAVE-DDL-DICTIONARY parameter is invalid. Probable cause: The following values are valid: YES (to save the dictionary) and NO (to purge the dictionary after the compilation). Recommended action: Please correct the SAVE-DDL-DICTIONARY parameter in the ACF.
EMS FastStart Messages ** Error 102 ** Missing Parameter or Invalid key word. Probable cause: EMS FastStart detected that no parameters were supplied for this keyword or the key word expected was . Recommended action: Please correct the CCF by specifying a valid key word or a valid parameter. ** Error 103 ** Invalid CCF or missing key word. Probable cause: EMS FastStart was expecting the . Recommended action: Please correct the key word in the CCF file.
EMS FastStart Messages ** Error 107 ** Invalid parameter. Probable cause: The parameter should be between 0 and 15 or the CPU is not currently available. Recommended action: Please correct the parameter in the CCF file. ** Error 108 ** Invalid parameter. Probable cause: The parameter should be between 1 and 199.
EMS FastStart Messages ** Error 151 ** Compiler abended. Probable cause: The compilation was not successful and terminated abnormally. Recommended action: EMS FastStart cannot continue operation because of this error, please verify the listing file for detailed information. ** Error 152 ** Compiler failed because of CPU failure. Probable cause: The compilation was not successful and terminated abnormally.
B EGEN Messages Each time you call one of the procedures implemented in the EGEN module you should verify the value of the return code to determine whether or not an error occurred during event generation. This appendix describes the return codes defined between EGEN and a user application (implemented by EGEN as a set of TAL procedures). A return code for each procedure implemented in the EGEN module informs the calling application of the status of the operation requested.
Close^egen^collector Return Codes EGEN Messages 10: Egen-open-missing-param Returned if this procedure is called without the collector^file^number and the error^detail parameters. The value of egen-error has no meaning for this message. 11: Egen-open-invalid-sync-depth Returned if this procedure is called with an invalid sync^depth parameter. The value of egen-error has no meaning for this message. The value must be 0 through 15.
Get^egen^event^text^define Return Codes EGEN Messages Get^egen^event^text^define Return Codes 0: Egen-get-text-define-ok Returned when the procedure processes the =_EGEN_ADD_EVENT_TEXT Define properly. The value of egen-error has no meaning for this message. 40: Egen-get-text-definemode-error Returned when the procedure detects an error with the DEFINEMODE procedure. The value of egen-error will contain the define error returned by DEFINEMODE.
Write^event^buffer Return Codes EGEN Messages Returned when the event-type is an action-attention-event or an action-completion-event and the action ADD ID is not initialized properly. The value of egen-error has no meaning for this message. 56: Egen-initialize-action-error Returned when the EMSADDTOKENS procedure detects an error when trying to add action variable data fields (tokens) ZEMS^TKN^ACTION^NEEDED, ZEMS^TKN^ACTION^ID to the event-buffer.
EGEN Return Codes EGEN Messages 70: Egen-missing-parameter-error Returned if this procedure is called without a valid combination of parameters. The value of egen-error has no meaning for this message. 71: Egen-record-not-initialized Returned if this procedure is called but the egen-record is not initialized properly. This can happen if you call EGEN without first calling the Initialize^egen^record procedure. The value of egen-error has no meaning for this message.
EGEN Return Codes EGEN Messages EMS FastStart Manual– 133701 B- 6
C COBOL85 Program Example This appendix contains the COBOL85 source code file SATMCOB that is located on the EMS FastStart subvolume after installation: ?HEADING "SATMCOB : COBOL PROGRAM EXAMPLE USING EGEN FOR AN ATM APPLICATION" ?SYMBOLS, INSPECT, SAVEABEND, NOMAP, NOICODE, ERRORS 0 *--------------------------------------------------------------------* * File Type: COBOL85 Source File for the ATM example * Source File Name: SATMCOB * Program File Produced: OATMCOB * Generation Time: October 31, 1989 09:4
COBOL85 Program Example * egen-record & atm-ssid: * COPY libraries specific to each ACF. * * egen-interface-definitions: * COPY library that is used to interface between user * application and Egen. * * atm-event-numbers, atm-action-id & atm-constant-values: * COPY libraries that are defined by the application * programmer and sourced by the compilation of the * main DDL.
COBOL85 Program Example MOVE MOVE MOVE MOVE MOVE INFORMATIVE-EVENT ATM-EVT-UP "SFMAIN01" "atm-name" "245 A St., San Francisco" TO TO TO TO TO event-type OF egen-record. event-number OF egen-record. atm-name OF egen-record. subject-field-name OF egen-record. atm-location OF egen-record. ENTER TAL "Egen" USING egen-record, file-number GIVING return-code. IF return-code NOT = ZERO PERFORM 400-validate-return-code. ?HEADING "215-ATM-BACK-ONLINE SECTION" / 215-atm-back-online.
COBOL85 Program Example ENTER TAL "Egen" USING egen-record, file-number GIVING return-code. IF return-code NOT = ZERO PERFORM 400-validate-return-code. ?HEADING "230-ATM-LOW-ON-CASH SECTION" / 230-atm-low-on-cash. *-------------------------------------------------------------------------* EVENT # 100: ATM IS LOW ON CASH. * * The fields within the egen-record which are used for event # 100: * * event-type PIC S9(4). * event-number NATIVE-2. * atm-name PIC X(8). * atm-location PIC X(24).
COBOL85 Program Example * EVENT # 201 ATM SECURITY BREACH. * * The fields within the egen-record which are used for event # 201: * * event-type PIC S9(4). * event-number NATIVE-2. * atm-name PIC X(8). * atm-location PIC X(24). * atm-account-num NATIVE-4. * atm-retry-limit NATIVE-2. *-------------------------------------------------------------------------PERFORM 300-initialize-egen-record. MOVE MOVE MOVE MOVE MOVE MOVE MOVE CRITICAL-EVENT ATM-EVT-SECURITY-BREACH "SACTO02" "atm-name" "230 State St.
COBOL85 Program Example ?HEADING "300-INITIALIZE-EGEN-RECORD SECTION" / 300-initialize-egen-record. *---------------------------------------------------------------------* This section will initialize the egen-record by calling the * Initialize^egen^record procedure. This procedure is included in the * Egen object file and sourced with the ?SEARCH compiler directive. * * Initialize^egen^record will move spaces to character fields and * high values to all fields in egen-record.
COBOL85 Program Example DISPLAY "Error Detail: " WITH NO ADVANCING DISPLAY egen-error OF egen-record ELSE IF return-code = EGEN-OPEN-COLLECTOR-ERROR DISPLAY "Egen Error: ** Egen-open-collector-error, error #12 **" DISPLAY "Error Detail: " WITH NO ADVANCING DISPLAY egen-error OF egen-record ELSE IF return-code = EGEN-OPEN-COLLECTOR-WARNING DISPLAY "Egen Error: ** Egen-open-collector-warning, error #13 **" DISPLAY "Error Detail: " WITH NO ADVANCING DISPLAY egen-error OF egen-record ELSE IF return-code = EGEN
COBOL85 Program Example DISPLAY egen-error OF egen-record ELSE IF return-code = EGEN-INITIALIZE-ACTION-ID DISPLAY "Egen Error: ** Egen-initialize-action-id, error #55 **" DISPLAY "Error Detail: " WITH NO ADVANCING DISPLAY egen-error OF egen-record ELSE IF return-code = EGEN-INITIALIZE-ACTION-ERROR DISPLAY "Egen Error: ** Egen-initialize-action-error, error #56 **" DISPLAY "Error Detail: " WITH NO ADVANCING DISPLAY egen-error OF egen-record ELSE IF return-code = EGEN-INITIALIZE-TEXT-ERROR DISPLAY "Egen Erro
D DDL, Copy Libraries and Templates Example This appendix contains the ATM DDL source file (ATM Example, EVENT DEFINITION SOURCE FILE: SATMDDL), the ATM COBOL85 copylib (ATM Example, COBOL85 COPYLIB: ATM1COB), and the ATM Template Source file (ATM Example, DSM Templates Services Source File: SATMTMPL). The first source file for ATM DDL event is SATMDDL and is provided on the distribution subvolume. You can modify the ATM DDL event source as necessary to meet the needs of your application.
DDL, Copy Libraries and Templates Example ATM Example, EVENT DEFINITION SOURCE FILE: SATMDDL * File Description: This DDL source schema file is an example of DDL * definitions which are used by the ATM example provided with EMS * FastStart. These definitions will ease the documentation and the * maintenance of an EGEN based application.
DDL, Copy Libraries and Templates Example ATM Example, COBOL85 COPYLIB: ATM1COB CONSTANT Atm-evt-security-breach VALUE IS 201. CONSTANT Atm-evt-hw-failure VALUE IS 202. ?SETSECTION Atm-action-id *---------------------------------------------------------------------* * ACTION EVENT IDENTIFIER DESCRIPTION: * * There is an action identifier associated with each action event * message.
DDL, Copy Libraries and Templates Example ATM Example, COBOL85 COPYLIB: ATM1COB * File Description: This DDL source schema file is an example of DDL * definitions which may me added to the base ZSPIDDL definitions * provided by Tandem. These definitions can then be used by * EMS FastStart and EGEN to create tokens of specific types. * * Modifications Summary: Date of Modification * * 1- Added the Zspi-ddl-char254 token.
DDL, Copy Libraries and Templates Example 02 SSID-OWNER. 03 Z-C 03 Z-S REDEFINES Z-C. 04 Z-I 03 Z-B REDEFINES Z-C 02 02 02 02 02 02 02 02 SSID-SUBSYSTEM-NUMBER SSID-VERSION EGEN-ERROR EVENT-TYPE EVENT-NUMBER ACTION-ID SUPPRESS-DISPLAY SUBSYSTEM-MANAGER. 03 Z-SYSNAME. 04 Z-C 04 Z-S REDEFINES Z-C. 05 Z-I 04 Z-B REDEFINES Z-C 03 Z-LOCALNAME. 04 Z-DISC. 05 Z-VOLUME. 06 Z-C 06 Z-S REDEFINES Z-C. 07 Z-I 06 Z-B REDEFINES Z-C 05 Z-SUBVOLUME. 06 Z-C 06 Z-S REDEFINES Z-C. 07 Z-I 06 Z-B REDEFINES Z-C 05 Z-FILENAME.
DDL, Copy Libraries and Templates Example ATM Example, COBOL85 COPYLIB: ATM1COB OCCURS 8 TIMES. 05 Z-QUAL2. 06 Z-C 06 Z-S REDEFINES Z-C. 07 Z-I 06 Z-B REDEFINES Z-C PIC X(8). NATIVE-2 OCCURS 4 TIMES. PIC X OCCURS 8 TIMES. 04 Z-DEVICE REDEFINES Z-DISC. 05 Z-DEVNAME. 06 Z-C PIC X(8). 06 Z-S REDEFINES Z-C. 07 Z-I NATIVE-2 OCCURS 4 TIMES. 06 Z-B REDEFINES Z-C PIC X OCCURS 8 TIMES. 05 Z-SUBDEVNAME. 06 Z-C PIC X(8). 06 Z-S REDEFINES Z-C. 07 Z-I NATIVE-2 OCCURS 4 TIMES.
DDL, Copy Libraries and Templates Example ATM Example, COBOL85 COPYLIB: ATM1COB 03 Z-B REDEFINES Z-C PIC X OCCURS 24 TIMES. 02 ATM-SERIAL-NUMBER NATIVE-4. 02 ATM-SENSE-STATUS NATIVE-4. ?Section EGEN-INTERFACE-DEFINITIONS,Tandem *--------------------------------------------------------------------* EGEN module interface variables definitions. *--------------------------------------------------------------------* * Used to define the EVENT-TYPE field of EGEN-RECORD.
DDL, Copy Libraries and Templates Example ATM Example, COBOL85 COPYLIB: ATM1COB * * Constants and returns code used by the Initialize^egen^record procedure * 01 EGEN-INITIALIZE-RECORD-OK NATIVE-2 VALUE IS 0. 01 EGEN-INITIALIZE-MISSING-PARAM NATIVE-2 VALUE IS 1. * * Constants and returns code used by the Open^egen^collector procedure * 01 EGEN-OPEN-COLLECTOR-OK NATIVE-2 VALUE IS 0. 01 EGEN-OPEN-MISSING-PARAM NATIVE-2 VALUE IS 10. 01 EGEN-OPEN-INVALID-SYNC-DEPTH NATIVE-2 VALUE IS 11.
DDL, Copy Libraries and Templates Example ATM Example, COBOL85 COPYLIB: ATM1COB * * File Type: DDL Source Schema * * Source File Name: SATMDDL * * Source Library File Produced: Sourced during the compilation of * the main DDL.
DDL, Copy Libraries and Templates Example ATM Example, DSM Templates Services Source File: SATMTMPL * These event message numbers describe the current set of CRITICAL * EVENTS supported by this application. For each event generated by a * Atm application, the programmer should select one of the following * event message numbers and move it into the EVENT-NUMBER field of * EGEN-RECORD. * *---------------------------------------------------------------------01 ATM-EVT-DOWN NATIVE-2 VALUE IS 200.
DDL, Copy Libraries and Templates Example == == == ATM Example, DSM Templates Services Source File: SATMTMPL GENERAL FORMATTING TEMPLATES MSG: ZEMS-TKN-EVENTNUMBER, ATM-EVT-UP "ATM <1> is up at <2>." 1: ATM-TKN-ATM-NAME 2: ATM-TKN-ATM-LOCATION MSG: ZEMS-TKN-EVENTNUMBER, ATM-EVT-ACCT-INSUF-FUNDS "Insufficient funds in account <1>." " Access denied on ATM <2>, at <3>.
DDL, Copy Libraries and Templates Example ATM Example, DSM Templates Services Source File: SATMTMPL EMS FastStart Manual– 133701 D -12
E Filter This is the program code for the EMS FastStart default filter program ATM1EMFS. ----------------------------------------------------------------------- EMS Fast Start - T9263C20 - (17MAR91) --- File Type: EMF Source file --- Source File Name: $DATA.ATM.ATM1EMFS --- Object File Produced: $DATA.ATM.
Filter --2. Subsystem ID: ............... Pass -Subsystem ID = ATM^VAL^SSID --3. Event Number: ............... Pass -Event Number = * --4. Token Present: .............. Pass -Token Name = * --5. Specific Token Value: ....... Pass -Token Value = * -6. Text: ....................... Pass -Text = * -7. Other ....................... Pass -Other = * ----------------------------------------------------------------------[#SET ZEMS^VAL^SSID [ZSPI^VAL^TANDEM].[ZSPI^SSN^ZEMS].0] [#SET ATM^VAL^SSID [ATM^VAL^OWNER].
Index A B ACF defined 4-1 field definitions 4-7 validating parameters 5-4 Action-attention events 2-11 Action-completion events 2-11 Application Configuration File (ACF) 4-1 Application modifications 6-13 Application, compiling 6-20 Assigning event numbers 2-9 Assigning group field numbers 2-13 ATM COBOL85 copy library D-3 DDL source file D-1 template source file D-10 ATM COBOL85 example 4-10 ATM example, running 5-4 ATM1ACF 5-10 ATM1C 5-10 ATM1COB 5-10, D-3 ATM1DDLS 5-10 ATM1EGEN 5-10 ATM1EGES 5-10 ATM1E
E Index Determining event subject 2-11 Documents, related xii DSM Template services 1-5 DSM Template source file D-10 E EGEN default values 4-9, 6-11 defined 1-3 detailed description 6-1 files 5-11 interface 1-3 messages B-1 modes and procedures 6-2 operating modes 6-1 parameters 6-7 procedure 6-4 EGENDECS 3-2 EMS FastStart choosing between it and EMS 1-4 components 5-10 configuring 3-2 features 1-1 filter program E-1 installation 3-1 messages A-1 process 1-2 requirements 1-5 running 5-1 setting up envir
G Index Filtering on tokens 7-4 GENERATE command 5-1 Global program modifications 6-14 Group field numbers 2-13 Open^egen^collector 6-3 return codes B-1 Procedures for EGEN mode 6-2 Procedure, Initialize^egen^record 4-9 Program modifications 6-14 Program requirements 1-5 I R Identifying data in messages 2-3 Identifying groups of variables 2-4 Index file 5-12 Informative events 2-11 Initialize^egen^record 4-9, 6-2 Installing EMS FastStart 3-1 Related documents xii Requirements 1-5 Return codes B-1 Ru
U Index Template source file D-10 Test program 1-3, 5-11 Testing program 7-1 Token 1-4 Tokens, filtering 7-4 U User subvolume files 5-9 V Variable data fields 2-6 Variables 2-4 W Warnings EGEN B-1 EMS FastStart A-1 EMS FastStart Manual–133701 Index- 4
