× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



It should be there in JTOpen 4.0.  It is the last writeMessage method listed
on the javadoc.

Gary

> -----Original Message-----
> From: java400-l-bounces@xxxxxxxxxxxx 
> [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Knotts, Bill
> Sent: Thursday, July 03, 2003 12:39 PM
> To: 'Java Programming on and around the iSeries / AS400'
> Subject: RE: Joblog and QZRCSRVS
> 
> 
> Gary,
> 
> I haven't tried Trace yet, but will shortly.
> 
> Regarding your other questions:
> 1. jt400native.jar is the only Toolbox jar in the classpath
> 
> 2. The manifest from jt400native.jar lists the following for 
> the access package - 
> 
>  Name: com/ibm/as400/access/                      
>  Specification-Title: IBM Toolbox for Java        
>  Specification-Version: 5.2.0.2                   
>  Specification-Vendor: IBM Corporation            
>  Implementation-Title: com.ibm.as400.access       
>  Implementation-Version: JTOpen 3.3               
>  Implementation-Vendor: IBM Corporation and others
> 
> 3. I don't see any doc's (neither JTOPEN 3.3 nor 4.0) that indicate a
> writeMessage() method signature that you described.  Am I 
> missing something?
> 
> 
> Thanks,
> WRK
>  
> -----Original Message-----
> From: Gary L Peskin 
> Sent: Thursday, July 03, 2003 12:41 PM
> To: 'Java Programming on and around the iSeries / AS400'
> Subject: RE: Joblog and QZRCSRVS
> 
> 
> Are you sure that jt400native.jar is the first thing in the CLASSPATH?
> 
> What version of the toolkit are you using?  I'm not sure but 
> a quick glance at the code indicates that the javadoc may not 
> be telling the truth for the latest release.
> 
> Can you call the writeMessage() method that explicitly 
> includes the onThread boolean as the last argument and set 
> that to true?
> 
> Also, I would call
> 
>   Trace.setTraceAllOn(true);
>   Trace.setTraceOn(true);
> 
> This should put out fairly good trace messages about where your
> writeMessage() is being run.
> 
> HTH,
> Gary
> 
>   
> 
> > -----Original Message-----
> > From: java400-l-bounces@xxxxxxxxxxxx
> > [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Knotts, Bill
> > Sent: Thursday, July 03, 2003 8:37 AM
> > To: 'java400-l@xxxxxxxxxxxx'
> > Subject: Joblog and QZRCSRVS
> > 
> > 
> > I am a bit perplexed by the following, hopefully someone on
> > the list can provide some insight:
> > 
> > For reasons best ignored for now, I need to write logging
> > entries from my code to the Joblog.
> > 
> > Consulting the javadocs for the AS400 object indicates that
> > the no-arg constructor  - 
> > "...has the same effect as using localhost for the system 
> > name, *CURRENT for the user ID, and *CURRENT for the password."
> > 
> > The docs for the static WriteMessage() methods indicates - "If the 
> > system specifies localhost, the message is written to the 
> job log of 
> > the process from which this method is called. Otherwise the 
> message is 
> > written to the QZRCSRVS job."
> > 
> > The code is executing within the OS/400 JVM on V5R1 using
> > jt400native.jar. The no-arg constructor is used to 
> > instantiate the AS400 object which in turn is passed to the 
> > appropriate WriteMessage() method.
> > 
> > I would expect the entries to be written to the Joblog of the
> > job that is running the JVM but they always appear only in 
> > the JobLog of a QZRCSRVS job. Nothing else in my code would 
> > necessitate the use of the QZRCSRVS job (removing my logging 
> > statements causes it not to appear).
> > 
> > Could it be that since I am using the native optimizations
> > provided by jt400native.jar?
> > 
> >  
> > Thanks,
> > WRK
> > _______________________________________________
> > 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.
> > 
> 
> 
> _______________________________________________
> 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.
> _______________________________________________
> 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.
> 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.