Pretty sure it is. From the article:
" SQL Skin is a layer between the Sybase application and the DB2 engine, in which the Sybase syntax is transformed in DB2 syntax and where the representation of output data can be transformed on the way back to the application."
Further down:
"The estimates from the MEET DB2 tool were especially reliable for Oracle migrations. What I have witnessed myself is that using the SQL Skin layer can be successful in case you want to retire a Sybase application, but implementations in an agile environment are less successful due to the fact that there is not much harmony between developing in Sybase and seizing the benefits from the latest native DB2 features. It really becomes a nightmare if you want to mix procedures and triggers written in T-SQL with those natively written for DB2 in PL/SQL and have them interact. The SQL Skin layer is out of marketing and is deprecated in DataStudio 3.2."
Sounds like they kinda frown on it's usage in 3.2. Who knows how to interpret this? It's looking more and more like it just failed in the marketplace. IBM throws a lot of spaghetti against the wall. Some of it sticks, some doesn't. If it is indeed a failure our only possible hope lies with the ADS. And as everybody knows, that was Rik's baby.
News 
Market Data 
Discover 
