× 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: Remote Java calls to RPG AS400 programs ?
  • From: "Dave Wall" <dawall@xxxxxxxxxx>
  • Date: Sun, 7 Jan 2001 20:15:41 -0600
  • Importance: Normal




Hi All,

I am a very popular person where I work. Please let me explain. My large
company has merged with an even larger company, now this larger company has
via  a simplistic prototype program (RPG400) that I put together discovered
how easy  it is for them to write Java programs that call (remotely through
the IP  network) my tiny RPG400 AS400 programs that then interface with
massive legacy  programs that derive information from the workhorse AS400
systems and hand all  kinds of nifty information back to their Java program
callers. This larger  company is quite impressed with how this works, and
this type of processing is  going to take off where I work.

I hope I explained the scenario well, as I have a few issues:

   When the remote Java programs initiate a call to the AS400, the jobs
   enter  the AS400 as Prestart Jobs in the QUSRWRK subsystem named QRCSRVS
   under user  QUSER. Why is it under QUSER when the Java programmer
   actually uses a  different userid to gain access to the AS400 via their
   Java program? I  actually used the RTVJOBA from the program I wrote in
   hopes of identifying the  actual caller by their userid, but was
   perplexed as to only retireve the QUSER  userid.

   >> AS others have explained so well,  part of the Toolbox session start
   is
   >> to exchange userid and password with the server.  The server job
   >> switches to that profile before running the job or command so all
   >> the restrictions you place on those users still apply.

   If these Java call jobs enter the AS400 under QUSER and not the userid I
   assigned to the caller then I lose control of actually limiting a
   specific  users access, any suggestions?
   The Java programmer on the remote side uses a software called (Weblogic
   App Server) and this permits him/her to start one or several openings or
   portals to the AS400 system which appear as active prestart jobs on the
   AS400  system named as above, and then the Java program fires these
   calls to my  RPG400 interface programs through these openings or
   portals, so to speak. So  am I right in my description when I say the
   Weblogic software allows the Java  programmer the ability to create one
   or multiple openings/portals remotely to  the AS400, these
   openings/portals appear as active jobs and then repeatedly  call my
   program through these openings/portals.

What I want to find out from this distinguished group is this:

   Is my terminology in the third bullet point above correct, or does my
   description sound goofy?
   Does anyone have any words of caution or advice or things to be aware of
   when doing the process I describe above, as this is going to TAKE OFF
   big time  where I'm at and I am the alleged 'professional' that everyone
   wants to  talk to about this and I still feel like a relative novice?

Please give any advice, I will appreciate all responses.

Thanks so much!

Tim Truax and Caleb 7 yrs? but divorced now.



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


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.