When you access a Sybase Adaptive Server Enterprise database in PowerBuilder through Open Client, Sec_Data_Origin is one of several parameters that support per-packet security for network-based security services. (For other per-packet security parameters, see the See Also section.)
Sec_Data_Origin controls whether your connection's security mechanism performs data origin stamping. When Sec_Data_Origin is set to 1, the security mechanism attaches a digital signature to each packet that verifies the packet's origin and contents.
When Sec_Data_Origin is set to 0 (the default), no data origin stamping is performed.
You must specify a value for Sec_Data_Origin before connecting to the database in PowerBuilder.
Using third-party security mechanisms
For information about the third-party security
mechanisms and operating system platforms that Sybase has tested
with Open Client security services, see the Open Client documentation.
ASE, SYC Sybase Adaptive Server Enterprise
Sec_Data_Origin=value
Sec_Data_Origin=0
Not supported with CyberSafe Kerberos Sec_Data_Origin is not supported if your security mechanism is CyberSafe Kerberos.
Set Release parameter For this parameter to take effect, you must also set the Release parameter to 11or higher to specify that your application should use the appropriate version of Sybase Open Client Client-Library (CT-Lib) behavior. See the description of the Release parameter for more information.
Requirements for use To use Sec_Data_Origin or any other parameter supporting Open Client security services, you must meet certain requirements for using security services in your PowerBuilder application. For details, see “Requirements for using Open Client security services” in Connecting to Your Database.
Corresponding CT-Lib connection property Specifying a value for Sec_Data_Origin sets the corresponding Sybase CT-Lib connection property named CS_SEC_DATAORIGIN.
To specify that your connection's security mechanism performs data origin stamping:
Database profile Select the Verify Packet Origin check box on the Security page in the Database Profile Setup dialog box.
Application Type the following in code:
SQLCA.DBParm="Sec_Data_Origin=1;Release=15"
