× 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.


  • Subject: Re: RAWT processing
  • From: Blair Wyman <wyman@xxxxxxxxxxxx>
  • Date: Fri, 9 Jun 2000 15:45:31 -0500 (CDT)

Excerpts from java400-l: 9-Jun'00 RAWT processing Rob
Persing@courts.state (3749*) 

> 1.  When I call my "TestFrame" class from a CL program it enters QSHELL
> to process.  I understand it has to do this to run the application, but
> is there anyway to do this without it displaying the QSHELL command
> line?  This probably would confuse users if I were to use this in an
> application. 

Actually, you should not need to use the QShell at all (I presume you're
using QSH CMD('java ...') eh?) 

You should be able to invoke the JAVA command with all the right
parameters...  If you post your QShell command line, I can help you
transliterate.  (The only trick, really, is the specification of the
properties, and that's not all that bad.  The QShell: 
        java -Dsome.option=a.value -Dos400.class.path.rawt=1
-DRmtAwtServer=megabox myClass  
would become 
        JAVA PROP(('some.option' 'a.value') ('os400.class.path.rawt' '1')
('RmtAwtServer' 'megaBox')) CLASS('myClass') 
) 

> 2.  When I exit my "TestFrame", a RAWT window pops stating "Application 
> program has ended" with a button to exit.  This means the user has to exit 
> the GUI twice, once for the "TestFrame" and once for the RAWT GUI.  Is there 
> anyway to skip the RAWT GUI that states the "Application has ended". 

Well, I was all set to point you to the '-DendBox=no' property for
1.1.x, which is supposed to prevent the end box from showing up, but it
does not currently work there.  While it might be fixable, the 1.1.x
RAWT is very difficult to maintain.  I'll see what I can do. 

If you can run your code under the 1.2 (aka 1.2.2) JVM (you just specify
-Djava.version=1.2 on the AS/400 side, in addition to the
-DRmtAwtServer=whatever and -Dos400.class.path.rawt=1 properties) then
you can specify '-DendBox=no' on the GUI side when you start up the
daemon with the 'java -jar <path>\RAWTGui.jar' command.  That will
prevent the end box from showing up, as you wish.  (You can also specify
-DendBox=fail to only have it show up if the RAWT fails somehow.) 

> 3.  When I press the button to exit the "Application has ended" GUI, it 
> returns control back to the QSHELL command line and not back to my CL 
> program.  Once again, the user would have to first know how to exit QSHELL 
> and then press a function key to exit QSHELL.  Is there a way to return 
> control directly back to the CL program?    

I think that if you run from the JAVA command, as per point 1 above,
this question becomes moot. 

HTH!  Again, I've just taken over responsibility for the RAWT very
recently, so it's all kind of new and exciting.  (Can you spot the
euphemisms? ;-) 

-blair 

  ___   _           Blair Wyman                  IBM Rochester 
 ( /_)  /  _  ' _   (507)253-2891            blairw@us.ibm.com 
__/__)_/_<_/_/_/_'  Opinions expressed may not be those of IBM 

+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---

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.