[Francis Kalinoski]

hcixltconvert was run during the conversion from QDX-5.3.3 to CL-5.5.1 on the test system – as per instructions.

It appears that any xlt from QDX-5.3.3 on the upgraded test system is changed from version 5 to version 6 when it is edited in CL-5.5.1, and then it becomes backward incompatible.

[Francis Kalinoski]

Apparently whenever a xlt in test/5.5.1 is modified, the version number is changed from 5.0 (what it was in QDX-5.3.3) to 6.0.

Where do change the version?

[Francis Kalinoski]

This issue was submitted to QDX Support.  R&D responded that this is a known issue that will be corrected in version 5.4.  If a user-1 is in an Integrator IDE site NWMonitor and another user-2 enters the same Integrator IDE site NWMonitor and breaks the user-1 lock, the next user to enter this Integrator IDE site NWMonitor will get a Java NullPointer Exception – Error connecting to Monitor Daemon.  The IDE Monitor Daemon indicator is RED and all or the threads in the NWMonitor display as ‘dead’.  A check of the site’s monitor daemon will show the pid still active.  Apparently there is a lock file retained in the /integrator/qdx5.3/integrator/site/lock directory that causes the problem.  Deleting the lock file does not help.  Only cycling the Host Server seems to restore the offending NWMonitor to functionality.

[Francis Kalinoski]

We are curently running QDX5.1 on AIX v5.1, and planning an upgrade to QDX5.3 on a new AIX v5.2 box.

1) Can we apply QDX 5.3 Rev3 directly to our existing QDX 5.1 or do we have to up grade to 5.2 then 5.3 then 5.3 Rev3?

2) When we go live with QDX 5.3 Rev 3, do we notify Quovadx for support?

[Author]

Replies