IBM DB2 Manual page 419

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
information can have the biggest impact on storage usage for character INOUT
parameters, LOB OUT parameters, and decimal OUT parameters.
When -zosDescProcParms is specified, the DB2 database server uses the
specified or default value of -zosProcedurePath to resolve unqualified names of
stored procedures for which DESCRIBE information is requested.
-zosProcedurePath procedure-path
Specifies a list of schema names that DB2 for z/OS uses to resolve unqualified
stored procedure names during online checking of an SQLJ program.
-zosProcedurePath applies to programs that are to be run on DB2 for z/OS
database servers only.
The list is a String value that is a comma-separated list of schema names that
is enclosed in double quotation marks. The DB2 database server inserts that list
into the SQL path for resolution of unqualified stored procedure names. The
SQL path is:
SYSIBM, SYSFUN, SYSPROC, procedure-path, qualifier-name, user-ID
qualifier-name is the value of the -qualifier parameter, and user-ID is the value
of the -user parameter.
The DB2 database server tries the schema names in the SQL path from left to
right until it finds a match with the name of a stored procedure that exists on
that database server. If the DB2 database server finds a match, it obtains the
information about the parameters for that stored procedure from the DB2
catalog. If the DB2 database server does not find a match, SQLJ sets the
parameter data without any DB2 catalog information.
If -zosProcedurePath is not specified, the DB2 database server uses this SQL
path:
SYSIBM, SYSFUN, SYSPROC, qualifier-name, user-ID
If the -qualifier parameter is not specified, the SQL path does not include
qualifier-name.
-genDBRM
Specifies that db2sqljcustomize generates database request modules (DBRMs).
Those DBRMs can be used to create DB2 for z/OS plans and packages.
-genDBRM applies to programs that are to be run on DB2 for z/OS database
servers only.
If -genDBRM and -automaticbind NO are specified, db2sqljcustomize creates
the DBRMs but does not bind them into DB2 packages. If -genDBRM and
-automaticbind YES are specified, db2sqljcustomize creates the DBRMs and
binds them into DB2 packages.
One DBRM is created for each DB2 isolation level. The naming convention for
the generated DBRM files is the same as the naming convention for packages.
For example, if -rootpkgname SQLJSA0 is specified, and -genDBRM is also
specified, the names of the four DBRM files are:
v SQLJSA01
v SQLJSA02
v SQLJSA03
v SQLJSA04
Chapter 7. JDBC and SQLJ reference information
403