|
Shucks. Somebody finally asks a question that I can answer, because I've actually written this code, and I blow it! Thanks for picking up after me, Dave! For what it's worth, I do prefer the QSYSObjectPathName technique in cases where library name and object name are passed as variables. It just seems simpler to me than appending to a StringBuffer or something similar. Kendall -----Original Message----- From: Dave Wall [mailto:dawall@us.ibm.com] Sent: Thursday, May 09, 2002 11:22 AM To: java400-l@midrange.com Subject: RE: How to access dtaara using toolbox? Sorry, that won't work either. The correct invocation should be QSYSObjectPathName path = new QSYSObjectPathName("BRUCELIB", "TESTARA", "DTAARA"); When using this c'tor, the QSYSObjectPathName object knows it is building the IFS form of the name so it automatically adds the "QSYS". You need to give it the library name, object name, and type of object. path.getPath() will return a properly formatted IFS name. In this case /QSYS.LIB/BRUCELIB.LIB/TESTARA.DTAARA". Note the object and library name do not include the type extension. QSYSObjectPathName automatically adds them. In the original case QSYSObjectPathName would try to create an object called BRUCELIB.LIB.LIB. There is no magic to this object. In fact, once you get used to the qsys-ifs format you may choose to skip the QSYSObjectPathName altogether and simply make your own string. David Wall Toolbox for Java iSeries ODBC Driver for Linux "Kendall Coolidge" To: <java400-l@midrange.com> <Kendall.Coolidge cc: @ccbai.com> Subject: RE: How to access dtaara using toolbox? Sent by: java400-l-admin@m idrange.com 05/09/2002 10:08 AM Please respond to java400-l Bruce, Try this: QSYSObjectPathName path = new QSYSObjectPathName("QSYS", "BRUCELIB", "DTAARA"); -----Original Message----- From: Bruce Jin [mailto:JIN007M@hotmail.com] Sent: Thursday, May 09, 2002 1:03 PM To: java400-j Subject: How to access dtaara using toolbox? This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] Here is my code: AS400 system = new AS400("MRCBOX"); QSYSObjectPathName path = new QSYSObjectPathName("QSYS.LIB", "BRUCELIB.LIB", "TESTARA.DTAARA"); CharacterDataArea dataArea = new CharacterDataArea(system, path.getPath()); It produces this error: com.ibm.as400.access.ExtendedIllegalArgumentException: object(BRUCELIB.LIB): Length is not valid. at com.ibm.as400.access.QSYSObjectPathName.construct(QSYSObjectPathName.java:422) at com.ibm.as400.access.QSYSObjectPathName.<init>(QSYSObjectPathName.java:263) Thanks. Bruce _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.