Description

The Sybase Systems 10 and 11 database interface and the SQL Server 4.x database interface in PowerBuilder and InfoMaker now differ in the way they treat PRINT statements in user-written stored procedures.

• Sybase Systems 10 and 11 interface

The Sybase Systems 10 and 11 interface on all platforms (SYC DBMS identifier) and the Sybase Systems 10 and 11 distributed application interface on UNIX (SYD DBMS identifier) no longer treat PRINT statements in stored procedures as fatal errors. For example, if you turn on the Database Trace tool when accessing the database through one of these interfaces, PRINT messages appear in the PBTRACE.LOG file but they no longer return errors or cancel the rest of the stored procedure.

• SQL Server 4.x interface

By contrast, the SQL Server 4.x interface (SYB or SYT DBMS identifier) still treats PRINT statements in stored procedures as fatal errors. This is the same behavior as earlier versions of the PBSYB0x0 and PBSYC0x0 interfaces.

Purpose

When you access a SQL Server database in PowerBuilder or InfoMaker with one of the Sybase Systems 10 and 11 interfaces, you can now use PRINT statements in your stored procedures for debugging purposes.