Advanced Settings

The Advanced Settings dialog allows you to set the following optional connection and bind properties.

The default values supplied are suitable in most environments. If you need to change a property value, click in the Value field next to the property and type the new value. To remove a property, select the property name and click the Delete button. You can add a property by clicking the Add button, entering the name of the property, and entering a value. Note that the Advanced property values are not saved when you quit the StarAdmin application.

Important Note There is no confirmation for deleting a property from the Advanced Settings dialog. Be sure that any selected property is the one you want to delete before you click the Delete button.

The Advanced property values must be set before you bind packages, except for the AutoTypDefOvr and UseEncryption values which must be set before you connect to the database. Refer to the discussion of the AutoTypDefOvr and UseEncryption properties to determine if you need to modify either value prior to connecting to the database.

 

AutoTypDefOvr

The AutoTypDefOvr setting stores the Coded Character Set Identifiers (CCSIDs) that the DB2 host supplies upon connection. After the connection with the host is established, StarAdmin uses the CCSID values specified for AutoTypDefOvr to send SQL statement and parameter data to the host.

The AutoTypDefOvr keyword value consists of three comma-separated CCSIDs in the following format.

<single-byte CCSID>,<double-byte CCSID>,<mixed-byte CCSID>

For the complete list of supported CCSIDs, refer to the "StarSQL Character Conversion and National Language Support" document in the StarSQL technical documents of the StarQuest Web site.

It may be necessary to set or modify this value if a failure occurs when attempting to connect to a DB2 host using a double-byte character set (DBCS). This value should only be modified under the guidance of StarQuest Customer Support.

BindRules

The BindRules setting applies only to applications that run dynamic SQL on DB2 for z/OS and OS/390 v5.1 or later. The permissions required to run applications that use dynamic SQL depend on the value of the BindRules option.

Set this option to RUN or BIND as desired.

If this option is set to RUN, the Database Administrator needs to grant the StarSQL user explicit permissions to read and write the columns and tables accessed by the application.

If the BindRules option is set to BIND, the StarSQL user executes the dynamic SQL in the ODBC application with the permissions of the package owner instead of their own user permissions. However, when this option is set, users cannot execute the following SQL statements, regardless of the permissions set for the package owner:

The StarSQL DSN BindRules setting should match the BindRules property that was in effect when packages were bound with StarAdmin.

CustomizePrdid

DB2 for z/OS does not support the ESCAPE clause in SQL syntax when the LIKE argument uses a mixed-byte character set. The CustomizePrdid parameter customizes the behavior in StarSQL when connecting to a DB2 for z/OS and OS/390 host that is using a double-byte character set (DBCS).

The CustomizePrdid parameter value can be either No (default) or Mixed.

When the CustomizePrdid parameter is set to Mixed in the DSN, StarSQL will strip the backslash escape character (\) from the dynamic catalog SQL calls. If you need to set the CustomizePrdid parameter to Mixed in the StarSQL DSN, you must set the CustomizePrdid parameter to Mixed in the StarAdmin Advanced Settings dialog prior to binding packages.

Important Note The escape character precedes a special character, such as the underscore (_) character, to treat the character as a literal. To work with tables that include an underscore in the name, such as MY_TABLE, create an ALIAS, SYNONYM, or VIEW for the table with a name that includes no special characters instead of working directly with the table.

If you set CustomizePrdid to Mixed, the driver binds sections that access SYSDUMMYA and SYSDUMMYE tables when retrieving CLOB/DBCLOB data. The SYSDUMMYA, SYSDUMMYE, and SYSDUMMYU tables are created by applying PTFs that IBM made available in APAR PQ85495. You can verify whether these tables exist on the host by entering the following statement:

SELECT * FROM SYSIBM.SYSTABLES WHERE NAME LIKE ‘SYSDUMMY%’

If these tables do not exist, you can either:

Netlib

Set this property to SQSSL.DLL to instruct StarAdmin to connect to the host system using SSL (Secure Socket Layer). In addition, you must also set the SSL property to an appropriate value (e.g. TLS) and set the port on the Connect dialog to the host's listening port (e.g. 448).

PkgOwnId

The SQL Package Owner ID (maximum 8 characters) specifies the owner ID to associate with the StarSQL driver packages that reside on the host. The target DBMS host uses the PkgOwnID value to validate whether the user has authority to perform the functions represented by the SQL statements in the bound package. This option can be useful in situations where an administrator needs to bind the driver packages but does not want to be the owner of the packages.

SSL

Set this property to an appropriate value when connecting to the host with SSL. Valid values are: SSL, SSLv3, TLS (recommended), and TLSv1. You must also set Netlib to SQSSL.DLL and specify the host's listening port (e.g. 448) on the Connect dialog.

UseEncryption

The UseEncryption setting determines whether the login user ID and/or password is sent to the host encrypted or in clear text. StarAdmin automatically detects the host capabilities and populates the UseEncryption setting with a value that should be appropriate for connecting to the host to bind packages.

As described in the following table the default value for UseEncryption is Any, which should work in most environments. If the database rejects the connection because it either requires or does not support encryption, set this value to Yes or No, as appropriate.

UseEncryption Setting

Description
No StarSQL always sends the user ID and password to the host in clear text.
Yes StarSQL always sends the user ID and password to the host encrypted. If the host does not support encryption, StarSQL returns an error.
Any StarSQL sends the user ID in clear text and the password encrypted. If the log fails, StarSQL then sends both the user ID and password in clear text.

UseJumboPackages

The UseJumboPackages variable affects:

If you configure the StarSQL DSN to use jumbo packages (UseJumboPackages=Yes), StarSQL sets the maximum active statement handle limit to 1,314. Each handle can each be used by one ODBC statement at a time. If you set UseJumboPackages to No, StarSQL sets the active statement handle limit to 64.

To take full advantage of this option you must enable the UseJumboPackages Advanced Setting in StarAdmin before you bind packages, and it must be enabled in the StarSQL DSN that is used to connect to the database. The default StarAdmin value is No.

If a dynamic package that is bound with 64 sections (UseJumboPackages=No) receives 65 or more active statements because the StarSQL DSN is configured to use jumbo packages, DB2 may report an error that the sections cannot be found. If packages are bound with the jumbo option enabled (UseJumboPackages=Yes), users can connect to DB2 using a StarSQL DSN that is configured to use either the typical (64 statement handles) or jumbo-sized (1,314 statement handles) packages.

Add a property (e.g. drdaTrace)

You can use the Add button to add a new property; the name of the property should be one of the properties available when configuring the StarSQL for Java JDBC driver.

For instance, to enable DRDA tracing for the JDBC connection, click the Add button, enter drdaTrace, and set its value to True. To use DRDA tracing, you must have write permission to the StarAdmin program directory, which is typically protected. On Windows, you can either install StarAdmin to a location outside of Program Files or run StarAdmin elevated by right-clicking on the StarAdmin icon and select Run as Administrator. On Linux, either install or copy StarAdmin to a location other than /opt, or run the application as root.

Note that setting drdaTrace enables only the initial (StarSQL for Java JDBC) connection to the host; the actual bind operation is performed using StarSQL (ODBC); use trcstart to start a trace this operation. trcstart allows you to specify the location of the trace file.

 

©Copyright 2018, StarQuest Ventures, Inc. All rights reserved.
February 22 2018 edition