Use the sybevent.dll file and the regedt32 utility.
To create and define a Registry key:
Log in to Windows NT using an account with NT administrator privileges.
Copy the sybevent.dll file from an Adaptive Server machine if it does not exist on the local computer.
The sybevent.dll file is stored in the dll subdirectory of the Sybase installation directory (\sybase\dll, by default). The actual location of sybevent.dll on the logging computer is not important, however, you must record a fixed location for the file in the NT Registry.
You can use
the same sybevent.dll file on the event-logging computer,
as long as all Adaptive Servers are at the same Version level; for example,
11.5.1.
Start the NT regedt32 utility.
For instructions and screens on using this utility with Adaptive Server, see “Increasing Windows Sockets connections”.
Complete the steps in “To create a Registry key” to create a key for a single Adaptive Server.
Complete the steps in “To define a Registry key” to define the key that you just created.
Repeat steps 4 and 5 for each Adaptive Server that is to send messages to the logging site computer.
To create a Registry key
In the regedt32 utility, select the Registry window named HKEY_LOCAL_MACHINE.
Open the levels until you reach the Registry key named:
HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\EventLog\Application
From the Edit menu, choose Add Key to display the Add Key dialog box.
Complete the dialog box as follows:
Key Name – type the name of the Adaptive Server computer that is to store the messages at the central logging site.
Class – leave this box blank. You do not have to specify a class for the new key.
Verify that you have entered the new Registry key correctly.
Click OK.
Complete the steps in “To define a Registry key” to define the key that you just created.
To define a Registry key
In the regedt32 utility, open the Registry key that you just created.
From the Edit menu, choose Add Value.
Type an event-logging value name as shown in Table 7-2 for the new Registry key. Enter the value name exactly as it is shown in the table; value names are case sensitive.
Value name |
Datatype |
String |
Notes |
|---|---|---|---|
CategoryCount |
REG_DWORD |
0x6 |
Do not change the data value. Make sure the string value is hexadecimal (Hex). |
CategoryMessageFile |
REG_SZ |
D:\SYBASE\DLL\ SYBEVENT.DLL |
Replace d:\sybase\dll with the path to the sybevent.dll file. |
EventMessageFile |
REG_SZ |
D:\SYBASE\DLL\ SYBEVENT.DLL |
Replace d:\sybase\dll with the path to the sybevent.dll file. |
TypesSupported |
REG_DWORD |
0xff |
Do not change the data value. Make sure the string value is hexadecimal (Hex). |
Be sure to enter the correct path to the sybevent.dll file
for the CategoryMessageFile and EventMessageFile values.
Select the data type for the value as named in Table 7-2 from the drop-down list.
Verify that you have entered the new key value and datatype correctly, and click OK.
Type the data or string in the Editor box, and click OK.
Repeat steps 2–6 for the remaining three values in each Registry key.
The following screen shows a sample Registry Key with the four values for the server named PIANO.
To create another key begin again with“To create a Registry key”.
Once you have created a Registry key for each Adaptive Server, choose Exit from the Registry menu in the Registry Editor dialog box to quit regedt32.
