EMS FastStart Manual
Building Your Application for Event Generation
EMS FastStart Manual–133701
6-20
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.)
•
Initialize^egen^record 
•
Open^egen^collector 
•
Close^egen^collector 
•
Complete^egen^operation 
•
Get^egen^event^text^define 
•
Initialize^event^buffer 
•
Write^event^buffer 
•
EGEN 
Compile Application
After you have completed the global and the event specific modifications, compile the 
application program. If the application compiles successfully, you will receive no system 
error messages. If you receive a system error message, correct the problem and re-
compile the program. Consult your Tandem compiler manual for information about 
specific system errors. 
Define Run-time Parameters
EGEN supports two run time parameters which add flexibility to applications that use 
EMS FastStart. These parameters allow you to specify an alternate EMS collector (the 
default is $0.). These parameters are implemented with two DEFINEs which can be 
changed each time you run your application. (For more information about DEFINEs see 
the GUARDIAN 90 Operating System User’s Guide.)
The =_EMS_COLLECTOR DEFINE allows you to specify the location where you want 
EGEN to pass the buffer via a write-read command. The default location is the primary 
collector $0. You can also specify a disk file for testing purposes before you install your 
application in production. If you do not specify another collector in this DEFINE, 
EGEN will use $0 as the default collector. 
The second DEFINE, =_EGEN_ADD_EVENT_TEXT tells EGEN whether to add the 
token ZEMS^TKN^TEXT (plus its value, which in this case is the event text) to the 
event buffer. The valid values are $YES (add the event text) or $NO (do not add the 
event text). $NO is the default value.
Note. If you specify a disk file as a collector, it must have the same structure and attributes as 
the EMS event log file if you want to use a distributor to print the contents of this file.










