RE: Remote Java calls to RPG AS400 programs ?

[Brad Sommerfeld <bsommerfeld@xxxxxxxxxxxxxxx>]

About users.  A job has a submit user (the one who started the job) and the user on whose behalf the job is running and getting permissions.

 

In most cases, these are the same.  The AS/400 however has some nice API's that allow a job to work on someone else's behalf through user handle switching.  This is how a server job (like the java API's you are using) perform work on the AS/400. 

 

RTVJOBA  USER - yields the submit user

RTVJOBA  CURUSER - yields user on whose behalf work is being performed.

 

Although you see QUSER as the user, go ahead and try some simple tests to access commands, functions, data that only the user you connected to the AS/400 with can access.  Also try some that you are restricted from.  Our experience is that it will behave as you expect.  If I remember any gotcha's I'll re-reply.

 

Brad Sommerfeld

Vertical Sky (formerly MKS, formerly part of Silvon Software)

 

 -----Original Message-----
From: Tim Truax [mailto:truax@telerama.com]
Sent: Saturday, January 06, 2001 10:11 AM
To: JAVA400-L list
Subject: Remote Java calls to RPG AS400 programs ?

• 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.
• 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?