Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

Notes, warnings or errors are not being issued when attempting to insert
data into a Sybase table with triggers using RAISERROR with PROC APPEND.
The automatic macro variables, SQLXRC, SQLXMSG, SYSDBMSG and SYSDBRC do
not return antything either.

However,  when attempting to see if this problem occurs outside of SAS
using ISQL and bogus data, an ERROR message is issued.  See example
below:

 1> use mercury
 2> go
 1> insert into mercury.dbo.merc_inv
  (investment_num,deal_num,property_use_cde,invest_status_cde,
  invest_type_cde,deal_type_cde,inv_grp_deal_num,currency_cde_re) values
  ('888315','888315','16','02','26','02','888315','yyy')
 2> go
 Msg 30002, Level 16, State 1:
 Server 'SDS_SY26', Procedure 'ti_merc_inv', Line 762:
 Foreign key in "merc_inv" cannot be inserted.  Row in "currency_val"
 does not
 exist.
 (1 row affected)


A Technical Support hot fix for Release 8.2 (TS2M0) for this
issue is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#012997

Once the HOTFIX is applied, you must also need to set an Operating
System environment variable, SY_SAS_MSG_CHECK, for the engine to check
for user / non- fatal messages.  The default behavior, without this
environment variable set, will be to NOT check for user/non-fatal
messages, because checking does impact performace.  The reason it
impacts performance, is because of the way MVA calls are structured,
error/message checking must be done in-line (explicitly) as opposed to
implicitly, using a call-back routine, because of the single thread
nature of MVA processing.

 To set the environment variable:

 PC:
  set SY_SAS_MSG_CHECK=1

 UNIX:
  export SY_SAS_MSG_CHECK=1

 OpenVMS
   assign 1 SY_SAS_MSG_CHECK

FOR THIS SAME PROBLEM IN SAS 9, PLEASE SEE SAS NOTE 017889

Operating System and Release Information

A fix for Release 8.2 (TS2M0) for this issue is available at: