SEO

Hi,
How can we specify the package names for sql stored procedures instead
of system generated names ?
(Db2 V8.2 on Windows.)

thanks.....

Do you mean the specificname of the sql sp? If so, just use the
"SPECIFIC <specific-name>" option on the create procedure statement.

From the SQL ref:
"SPECIFIC specific-name
Provides a unique name for the instance of the procedure that is
being defined. This specific name can be used when dropping the
procedure or commenting on the procedure. It can never be used to invoke
the procedure. The unqualified form of specific-name is an SQL
identifier (with a maximum length of 18). The qualified form is a
schema-name followed by a period and an SQL identifier. The name,
including the implicit or explicit qualifier, must not identify another
routine instance that exists at the application server; otherwise an
error (SQLSTATE 42710) is raised.

The specific-name may be the same as an existing procedure-name.

If no qualifier is specified, the qualifier that was used for
procedure-name is used. If a qualifier is specified, it must be the same
as the explicit or implicit qualifier of procedure-name or an error
(SQLSTATE 42882) is raised.

If specific-name is not specified, a unique name is generated by
the database manager. The unique name is SQL followed by a character
timestamp, SQLyymmddhhmmsshhn."

Hype wrote:
> Hi,
> How can we specify the package names for sql stored procedures instead
> of system generated names ?
> (Db2 V8.2 on Windows.)
>
> thanks.....
>

I am guessing, Hype is asking if it's possible to specify SQL package's
name like an option PACKAGE USING <package_name> to the PRECOMPILE
command.
AFAIK, it's not supported at least in V8.1.x LUW.

Regadrs,
-Eugene

efiryago@gmail.com wrote:

> I am guessing, Hype is asking if it's possible to specify SQL package's
> name like an option PACKAGE USING <package_name> to the PRECOMPILE
> command.

Have a look at the PACKAGE USING option that is available for the PRECOMPILE
command:
http://publib.boulder.ibm.com/infoce...e/r0001964.htm

--
Knut Stolze
Information Integration
IBM Germany / University of Jena

Hype wrote:
> Hi,
> How can we specify the package names for sql stored procedures instead
> of system generated names ?
> (Db2 V8.2 on Windows.)
>
> thanks.....
>

As far as I can tell - you cannot specify your own package name for SQL stored
procedures in V8.2.
You can specify <specific-name> which will be used instead of SQLnnnnnnnn
generated one.

Plan name associated with that procedure will have name Pmmmmm where mmmmm is
equal to LIB_ID of SYSCAT.ROUTINES view.

Do you have a specific need for user plan name instead of system generated one?


Jan M. Nelken

Jan M. Nelken wrote:
> Hype wrote:
> > Hi,
> > How can we specify the package names for sql stored procedures
instead
> > of system generated names ?
> > (Db2 V8.2 on Windows.)
> >
> > thanks.....
> >
>
> As far as I can tell - you cannot specify your own package name for
SQL stored
> procedures in V8.2.
> You can specify <specific-name> which will be used instead of
SQLnnnnnnnn
> generated one.
>
> Plan name associated with that procedure will have name Pmmmmm where
mmmmm is
> equal to LIB_ID of SYSCAT.ROUTINES view.
>
> Do you have a specific need for user plan name instead of system
generated one?
>
>
> Jan M. Nelken

Jan M. Nelken wrote:
> Hype wrote:
> > Hi,
> > How can we specify the package names for sql stored procedures
instead
> > of system generated names ?
> > (Db2 V8.2 on Windows.)
> >
> > thanks.....
> >
>
> As far as I can tell - you cannot specify your own package name for
SQL stored
> procedures in V8.2.
> You can specify <specific-name> which will be used instead of
SQLnnnnnnnn
> generated one.

Jan is correct. You cant.

(note - as of v82, SQL stored procedures no longer are compiled using
the system compiler, therefore there's no option to use the PACKAGE
USING clause during precompile)

jsoh