Running a SQL Statement with Period in the name of a Database Table
WOW 6.0 does not support a period in any of the names of a table that are being modified by a SQL statement.
For example:
SELECT * FROM PJDATA.EMPL.NM
where all the rows of EMPL.NM are being selected will not work. We suggest that you create a logical over “EMPL.NM” and give it a normal name such as “EMPLNM”.
When Running WOW off of a Linux or Unix machine and with MySQL, some operations don’t work
When running operations in on any UNIX machine and using MySQL as Metadata Server some of the operations
are throwing errors or not working. This may be because MySQL running on a Unix System requires all library
(schema names) and table name to be in UPPER CASE. Check to make sure all your files being accessed are in
UPPER CASE and restart the MySQL Server.
When creating a row, the Current Date -CURRENT returns the wrong date
When inserting a new row, a default timestamp can be obtained by putting *CURRENT in the FD of a Date Field.
Unfortunately, the time might be off by either a time zone or just by hours, minutes or seconds. This is normally
a configuration issue from your OS/400 or JDK.
Instructions on how to correctly setup the time zone offsets are in IBM Redbooks.
Changing Database Tables and Views
The JDBC driver provider may cache information about tables and views for performance reasons.
If you change the definition of a table or view, you may need to restart the associated WOW
connection for the database change to be enforced.