50. Troubleshooting and Debugging WOW

Troubleshooting and Debugging WOW

My iSeries DB2 files are locked by WOW which is affecting my saves and other programs!

OS/400 may apply a READ lock on files that are accessed more than once from the same connection. This is a function of OS/400 and is done for performance and is not caused by WOW. If you need to use a file that OS/400 has locked use the following command:

ALCOBJ OBJ((QIWS/QCUSTCDT *FILE *SHRRD *FIRST)) CONFLICT(*RQSRLS)

NOTE: Adjust the library and file name as well as the locking level to suit your needs.

TODO: Add a section on looking at the Tomcat logs, Reference the WOW Toolbar and WOW Wizard which allow viewing of log information.

WOW is unable to connect to the IBM iSeries Metadata Server because of restricted ports

WOW can work with any metadata server. Every organization handles network controls and restrictions differently. If WOW is not able to connect to your server it may be caused by blocked ports. In the example of an iSeries machine there are numerous ports that need to be opened for full JDBC support that WOW uses, yet maybe your network administrator or firewall is blocking some of these ports.

At IBM’s website you can go to this link

http://www-1.ibm.com/servers/eserver/iseries/toolbox/faqports.htm

shown below and see what ports need to be opened for full JDBC and server controls. Do the same for your system and have your network administrator allow these ports so that WOW can connect. On the iSeries WOW requires the following ports to be open (other databases use different ports, check your database documentation):

• • 449

  • 8470

  • 8471

  • 8476

MCH3601 Issue After Upgrading the IBM i (AS/400) to V7R2 and V7R3:

IBM issued a PTF that should be applied: 5770SS1 SI67002 is the PTF that corrected the issue for V7R3M0.

There is also an associated PTF available for V7R2. Contact IBM support for details.