Use the IBM Database Tools page in the Options window
to customize the IBM® Database Add-Ins for Visual
Studio by setting various tool options.
To open the IBM Database Tools page in the Options
window:
From the Tools menu, select Options.
In the left box of the Options window, select the IBM Database
Tools node.
Database Access
Maximum Rows For Preview
The maximum number of rows to retrieve for
tables and views. Use 0 for unlimited.
The default value is 100.
Timeout
The amount of time, in seconds, until
a command execution times out. The default
value is 30.
Note: The default value of 30 is too
low for DB2® for z/OS®
and DB2 for i servers. To improve
your experience when you are connecting to a DB2 for z/OS
or a DB2 for i server, increase the timeout duration
to 300 seconds or more.
Prefetch Cache
Select True to reduce data access time by reading
data from the database ahead of its first use and
storing it in the cache for subsequent retrieval.
The default value is True.
Commit Transaction
Select True to automatically commit the transaction after running
a routine. The default value is False.
Table Type Filter
Click to open the Select
Table Type Filter window and select the default table
types to show under a data connection in the Server
Explorer for a specific data server.
Debugging Options
The SQL debugger daemon is used to store information for
debugging SQL procedures running on z/OS.
The daemon starts automatically when you begin to run an SQL
procedure in debug mode and stops after the specified period
of inactivity.
Debug Session Timeout
The maximum amount of time, in seconds, that a debugging
session can be inactive before it will be terminated.
The default value is 60.
Maximum Variable Display Length
The maximum length of a variable value that will be
displayed. The default value is 80.
Debug Daemon Host (DB2 for z/OS Version 8 only)
The host name or IP address where the debugger daemon is
running. This must be the host name or IP address of the
local machine. Use localhost unless your
machine has multiple IP addresses. If your machine has
multiple IP addresses, use an IP address that the
database server can connect to.
Debug Daemon Port (DB2 for z/OS Version 8 only)
The number of the TCP port on which the debugger
daemon listens for connections.
Diagnostic Trace Level
Indicates the type of diagnostic trace errors to log:
0 = no logging
1 = logging for serious problems only
2 = maximum logging
Session Manager Connection (DB2 Version 9 only)
The database connection on which to start the debugging session
manager. The session manager is similar to the debugger daemon
from Version 8, except that it is now required for all database
types. The session manager is explicitly started when needed,
and automatically stops after inactivity.
If you do not specify a value, the session manager is started
on the same connection as the procedure that is being debugged.
This option applies only to debugging on DB2®
Version 9 for Linux®, UNIX®,
and Windows®, DB2 for z/OS®
Version 9, and DB2 for i5/OS V5R4 servers.
Session Manager Port (DB2 Version 9 only)
The port on which the session manager listens for connections.
If you do not specify a value or specify 0,
the default port that is defined for the server is used.
This option applies only to debugging on DB2 Version 9 for
Linux, UNIX, and Windows, DB2 for z/OS Version 9, and DB2
for i5/OS V5R4 servers.
Editor Settings
Statement Separator
Type a character to use as the DB2 script file
statement delimiter. The default value is @.
IntelliSense Enabled
Select to enable IntelliSense in the editor.
The default value is True.
Environment
Font Name
The name of the font to use in IBM designers and windows.
Font Size
The size (in points) of the font to use in IBM designers and
windows.
Project
Show File Extensions
Select to show file name extensions in the
Solution Explorer. The default value is True.
Connect On New Project
Select to open the IBM Data Connection window when
a new project is created. The default value is True.
Update Service
Update Service Frequency
Select the frequency at which you want the update service
to check for updates to the IBM Database Add-Ins for Visual
Studio:
Never
Daily
Weekly
Monthly
Every X Days
Update Service Interval
If you select Every X Days for the
Update Service Frequency option,
enter the specific number of days that you want to
elapse between checks for updates.
z/OS Options
WLM Default
Type the name of the MVS workload manager
(WLM) environment in which to run the object.
The name can contain up to 18 alphanumeric
characters. When you do not specify a WLM
environment, the object runs in the DB2-established
object address space that was established
during installation. Using different WLM
environments lets you isolate one group of
programs from another. For example, you can
isolate programs based on security requirements.
Tip: Your system administrator can help you determine
whether to use this option.
Default Build Utility
Specify the name of the procedure build utility
to call when building an SQL procedure on
a z/OS server. The default build utility
name is SYSPROC.DSNTPSMP.
The database administrator can configure
copies of the build routine to use different
resources as necessary. The IBM Database Add-Ins for
Visual Studio query the current database to
retrieve valid build utility names. If valid names
are found, you can select them here. For
example, the DSNTPSMP build utility can be
entered in this field after the database
administrator configures it on the z/OS system.
Collection ID
Type the name of the collection ID. By specifying
a collection ID, you identify the package
collection that is used when the routine
is run. The name can contain up to 18 alphanumeric
characters. If you do not specify a name,
DB2 Universal Database uses the collection
name of the package that contains the CALL
statement. If the calling program does not
use a package, the package collection is
set to the special register value CURRENT
PACKAGESET.
External Security
Specify to run procedures and functions in
an external security environment. If the
procedure or function accesses resources
that an external security product protects,
the access is performed using the authorization
ID of the user who created the procedure
or function.
Stay Resident
Specify to keep the load module resident
in memory after the procedure or function
runs. If you select False, the load module
is deleted from memory after the procedure
or function runs. Keeping the routine in
memory can enhance performance by eliminating
the time that it takes to load the application;
however, using this feature increases the
amount of virtual storage that is required
by the address space of the procedure or
function.
Runtime Options
Type a string that specifies run-time test
options to use when debugging procedures.
The TEST runtime option generates debugging
information at runtime. If you type NOTEST,
no debugging information is generated.
Pre-Compile Options
Type the SQL precompile options for building
your procedures. You can enter PRECOMPILE
PROGRAM (PREP) and BIND options. The IBM
Database Add-Ins for Visual Studio do not recognize
SQL precompile options that name data sets.
Compile Options
Type a string that specifies compiler options
to use with your procedures. For example,
type NOTES(block, noline, nopath).
Pre-Link Options
Type a string that specifies prelink options
for the prelinker. The prelinker combines
the object modules that comprise an application
into a single object module.
Link Options
Type a string that specifies link options
for your linkage editor. The linkage editor
processes the object module created by the
prelinker and generates a load module that
can be retrieved for execution.
Bind Options
Type a string that specifies bind options
for SQL packages. For example, type
Package (PROCEDURE241), ACT(REP) ISO(CS).ACT(REP) specifies that the package
replaces an existing package with the same name.
ISO(CS) ensures that your application
does not read
a row that another process changes until
that process releases that row.
Build Owner
Type the DB2 Universal Database for z/OS
authorization ID that holds responsibility
for building, rebuilding, and dropping procedures
or functions. By specifying a secondary authorization
ID or group name as the build owner, more
than one user can share responsibility for
maintaining procedures and functions. If
you do not specify a build owner, the build
utility designates one of your process authorization
IDs, such as the CURRENT SQLID, as the build
owner. The maximum allowed length is 8 characters.