January 13, 1998

Urgent Customer Information
Adaptive Server Enterprise Version 11.5

Dear Customer,

You are receiving this notification because you are a designated
Sybase Technical Support Contact at a customer site that is using
Adaptive Server Enterprise 11.5. We are proactively notifying you
about a data modification problem that occurs when user-defined codes
are values greater than zero. This causes the change to rollback
without a corresponding message.

Attached is a TechNote, "Urgent from Sybase to Customers: Data
Modification Trigger Problem with User-defined Return Value Greater
than Zero" that describes the problem and provides details for a
workaround as well as EBF information.

We apologize for any inconvenience this problem may have caused you
and your company. Sybase is committed to you and your success. We have
communicated this problem to you as soon as possible to minimize or
eliminate any impact on your business. We would like to encourage each

of you to connect periodically to the technical support section of the

Sybase Web site (http://support.sybase.com) for continued updates.

For contact changes or inquiries please email Customer Service at:
custserv@sybase.com and use the following contact ID:

Sincerely,

Sybase Customer Service and Support

----------------------------------------------------------------------------

Urgent from Sybase to Customers:
Data Modification Trigger Problem with User-defined Return
Value Greater than Zero

----------------------------------------------------------------------------

Summary
-------

Data modification trigger fails silently if the trigger calls a stored
procedure that returns a greater than zero value.

Attributes
----------

OS: Not OS Specific Version: 11.5

Platform: Not Platform Specific Last Revision: Jan 12,1998

Product: Adaptive Server Enterprise ID: 20169


Problem
-------

System-generated failure messages, range -1 to -99, behave as expected
and display appropriate messages when trigger modification is rolled
back. A problem occurs when user-defined return codes are values
greater than zero. This causes the change to rollback without a
corresponding message.

For example, let's say you create the following table, stored
procedure, and trigger:

1> create table tb1 (field1 int)
2> go

1> create proc p_tb1 as print "insert" return1
2> go

1> create trigger t_tb1 on tb1 for insert as execute p_tb1
2>go

Then you use an insert command to add a row:

1> insert tb1 values(1)
2> go
insert
(1 row affected)

The trigger and insert fail, however, when it calls the stored
procedure because its return value is 1, not 0:

1> select * from tb1
2> go
field1
- - - - - - --

(0 rows affected)

Workaround
----------

As a temporary action, pending a fix from Sybase, ensure that either
the:

* User-defined stored procedure return value is zero, or

* Stored procedure does not return a value

Actions from Sybase
-------------------

This problem is logged as CR#140265. An upcoming EBF enables you to
define return values greater than zero for procedures called by
triggers. Sybase is releasing an EBF for each platform in January,
1998:

Platform EBF
-------- ---
Digital UNIX 7751

HP-UX 7753

IBM RS/6000 7754

Sun Solaris 2.x (SPARC)7750

Windows NT 7752