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

As in previous versions of SAS, a DB2 SQLCODE 535 may occur when
updating a DB2 table via a SAS/ACCESS view descriptor or the LIBNAME
engine if any columns are part of the primary key.  This occurs if you
are running Version 4 or later of DB2.  Because this is considered a
warning, depending on the release of SAS that is being used the UPDATE
may or may not occur.

In Version 6 of SAS, the DB2PKCHK option can be set prior the access
descriptor creation to circumvent this problem.  When set to Y, SAS
queries DB2 to determine if a primary key exists on the table and any
columns that make up the primary key are excluded from the update
statement.  This is needed in Version 6 of SAS since, prior to Version
4, DB2 considered the updating of the primary key an error, not a
warning.  Since the supported version of DB2 considers the condition a
warning, the importance of the option is not as critical.  Starting in
Version 7 of SAS, the system option is no longer supported and is
ignored if specified.

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#002892

Starting in SAS 9.1.3(9.1 TS1M3) the +535 has resurfaced.  However, the
warning causes a rollback to be issued if there is more than one record
in the SAS data set.  If there is only 1 record the warning is outputted
to the log but the update occurs.

Operating System and Release Information

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