There are some differences in system tables if you are using a Cluster Edition of SAP
ASE.
timestamp Columns
In the SAP ASE server, if a table includes a timestamp column, its value is updated when a row is changed. Client applications can use this functionality to detect changes to rows using an access method called “optimistic locking.”
Changed Identity Values
Identity columns in the Cluster Edition behave differently from those in non-clustered editions of SAP ASE. Although the Cluster Edition guarantees that identity values are unique, for performance reasons the values may not monotonically increase.
Controlling Fake-Table Materialization
Certain stored procedures, such as sp_who and sp_lock, read from fake tables such as sysprocesses and syslocks. Because their rows are not stored on disk, fake tables present an exception to the shared-data nature of a shared-disk cluster, and special features apply.