Migration toolkit question ....

[Raquel]

We ran Migration toolkit to look into the possibility of migrating
from SYBASE to UDB.

The following statement in SYBASE:
INSERT INTO GEST_TP (
GES_D,
PC_N,
IPD
)
VALUES (
@GES_D,
@PC_N,
@IPD
)

has been translated to the following on UDB:

INSERT INTO GEST_TP(GES_D, PC_N, IPD)
VALUES (v_GES_D, v_PC_N, SYB.rtrim_on_insert(v_IPD));

Does anyone know what "SYB.rtrim_on_insert" is supposed to do? Does
not look like a UDB function either.

Infact, there are several other "SYB." type functions that are
generated in the script (such as SYB.empty_to_null, SYB.substring
etc.). Any ideas what these are?

TIA
Raquel.

[Serge Rielau]

Raquel,

SYB fucntions are functions provided by MTK to match non-standard SQL
pehaiour from Sybase.
I imagine that Syabse removes trailing blancs when inserting a VARCHAR
column.
DB2 does not. Since MTK cannot know whether that matters for your
application it throws in the extra function.
empty_to_null() will replace an empty string '' with a NULL. Again a non
standard behaviour of Sybase that DB2 emulates.
Presumably there are alos soem differences with substr() (i don't know
what they are).
In general MTK tries its best to ensure emulation of the source system.
After MTK is done and you have verified corrected you should take a look
at the code and remove unnecessay functions using your knowledge of the app.
These functions are a major cause of performance degradation on migration.

Cheers
Serge

--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab

[Gert van der Kooij]

In article <cd*********@hanover.torolab.ibm.com>, Serge Rielau
(sr*****@ca.eye-be-em.com) says...

Raquel,

SYB fucntions are functions provided by MTK to match non-standard SQL
pehaiour from Sybase.
I imagine that Syabse removes trailing blancs when inserting a VARCHAR
column.
DB2 does not. Since MTK cannot know whether that matters for your
application it throws in the extra function.
empty_to_null() will replace an empty string '' with a NULL. Again a non
standard behaviour of Sybase that DB2 emulates.
Presumably there are alos soem differences with substr() (i don't know
what they are).
In general MTK tries its best to ensure emulation of the source system.
After MTK is done and you have verified corrected you should take a look
at the code and remove unnecessay functions using your knowledge of the app.
These functions are a major cause of performance degradation on migration.

Cheers
Serge

It looks like it's onion time again :)