jcc | Small C compiler for x86-64 Copyright 2012 Janne | Natural Language Processing library

Seems, that this very old Db2 jcc 2.3.63 version driver (from Db2 V8.2) doesn't have support for named parameters.
Contemporary Db2 jcc drivers do support such a functionality.
It's strongly advised to use Db2 jcc drivers corresponding to the Db2 Server version.

One option is to specify profile specific .yml files. These are then activated by activating the corresponding profile.

So you can create application-security.yml

And in your main yml file add:

As authentication (checking userid and password) happens inside the container (i.e not using the Win10 on the host), you must use a userid:password combibation that is already created inside the container, for example db2inst1 as per your env file.

You must also reference the database name that is created on the container (e.g. testdb as per your env file). You cannot use username db2admin until and unless you create that account inside the container.

Client info properties support by the IBM Data Server Driver for JDBC and SQLJ.

I get the same -440 symptom as your question, on Db2-LUW v11.5.6.0 from jdbc when I call sqlj.install_jar .

Possibly some regression or mistake by me.

It may also be worthwhile to compare the behaviour of method DB2Connection.installDB2JavaStoredProcedure (which supposedly runs sqlj.install_jar )

But the alternate method sqlj.DB2_INSTALL_JAR works ok from jdbc for me currently.

Sample below based on IBM's example code, and I run it locally on the Db2-LUW server so use passwordless style url.

Note that if you need to make it re-runnable, you have to extend it, to check sysibm.sysjarobjects for the jar_id , use sqlj.replace_jar and/or sqlj.remove_jar and sqlj.refresh_classes() as appropriate. For that reason I prefer to use shell-script instead of jdbc for orchestrating my build scripts, at the cost of having a properly configured Db2-client at the build hostname. The shell scripts are shorter and easier to manage than jdbc code in my case.

I think I have found what caused the problem, atleast I can now create the function without a problem. The root cause is that Flyway appears to:

A NOP is a separate instruction that had to decode and go through the pipeline separately. It's always better to pad instructions with prefixes to achieve desired alignment, not insert NOPs, as discussed in What methods can be used to efficiently extend instruction length on modern x86? (but only in ways that don't cause major stalls on some CPUs which can't handle large numbers of prefixes).

Perhaps Intel considered it worth the effort for toolchains to do it this way for this case since this would actually be inside inner loops, not just a NOP outside an inner loop. (And tacking on prefixes to one previous instruction is relatively simple.)

I now have some data point. The result of benchmarking for /QIntel-jcc-erratum on AMD FX 8300 is bad.

The slowdown is by a decimal order of magnitude for a specific benchmark, where the benefit on Intel Skylake for the same benchmark is about 20 percent. This aligns with Peter's comments:

I checked Agner Fog's microarch guide, and AMD Zen has no problem with any number of prefixes on a single instruction, like mainstream Intel since Core2. AMD Bulldozer-family has a "very large" penalty for decoding instructions with more than 3 prefixes, like 14-15 cycles for 4-7 prefixes

It's somewhat valid to consider Bulldozer-family obsolete enough to not care much about it, although there are still some APU desktops and laptops around for sure, but they'd certainly show large regressions in loops where the compiler put 4 or more prefixes on one instruction inside a hot inner loop (including existing prefixes like REX or 66h). Much worse than the 3% for MITE legacy decode on SKL.

Though indeed Bulldozer-family is obsolete-ish, I don't think I can afford this much of an impact. I'm also afraid of other CPUs that may choke with extra prefixes the same way. So the conclusion for me is not to use /QIntel-jcc-erratum for generally-targeted software. Unless it is enabled in specific translation units and dynamic dispatch to there is made, which is too much of the trouble most of the time.

One thing that probably safe to do on MSVC is to stop using /Os flag . It was discovered that /Os flag at least:

• Avoids jump tables in favor of conditional jumps
• Avoids loop start padding

Try the following example (https://godbolt.org/z/jvezPd9jM):

If freetext is a Clob column, try to annotate it properly with @Lob . Check this post Using EclipseLink JPA to bind Strings larger than 255 characters .

The error might be related to the JPA provider change between WAS7 and 9 (previously it was OpenJPA). If you dont care abouth JPA 2.1, you can switch back to 2.0 OpenJPA, for example like this using wsadmin:

In order to resolve the compilation failure issue you need to change this: