RE: QSYSObjectPathName -- Length is not valid???

Thor raised a good point. Do you have the old jt400 on the production machine and the new one on the test machine?

One trick I learned from Tim Rowe: IBM puts all the latest code into jtopen.jar on sourceforge. So if you want the latest fixes, download the jar from there. The PTF's to fix the current official release of jt400.jar can lag weeks or months behind.

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Thorbjoern Ravn Andersen
Sent: Thursday, December 03, 2009 12:35 AM
To: Java Programming on and around the iSeries / AS400
Subject: Re: QSYSObjectPathName -- Length is not valid???

Clapham, Paul skrev:

QSYSObjectPathName fileName = new QSYSObjectPathName("%LIBL%",
"BLPEDI94", "MAVERIK", "MBR");

and when I run it in my complex environment it throws this exception:

com.ibm.as400.access.ExtendedIllegalArgumentException: objectName
(/QSYS.LIB/%LIBL%.LIB/BLPEDI94.FILE/MAVERIK.MBR): Length is not valid.

If I copy and paste the line of code into a simple program which just
does that and then prints the result, I get the result printed. But in
my multi-threaded message-processing system, I get the exception. Not
only that, the line of code is working correctly in the production
environment and it's just failing in the test environment.

In all cases it's the QSYSObjectPathName class which is being loaded
from here:

/QIBM/ProdData/OS400/jt400/lib/jt400Native.jar

I would transfer that jt400Native.jar to my personal computer, and use a decompiler for analyzing the stack trace with the ExtendedIllegalArgumentException (my guess is that %LIBL%.LIB should be just %LIBL%).

I have good experiences with the Jadclipse plugin to Eclipse for this (for which you need the jad binary) when you remember to set up Jadclipse to generate source corresponding to the original line numbers in the Preferences.

We are currently shipping jt400.jar with a Java program being deployed on V6R1 as the native library had some issue with AS400 connections not remembering CHGLIBL commands which had been issued earlier. We worked around it by including the jt400 5.0 jar instead.


--
Thorbjørn Ravn Andersen "...plus... Tubular Bells!"

--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l.