RE: Client Access Incoming Remote Command

["Luke Dalton" <ldalton@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Hello Joe,

 
If you get too frustrated with RUNRMTCMD and Client Access and are looking
for a commercial solution, please check out the iSeries PC-Engine at
http://www.turbogorilla-software.com. You can download a full function trial
version and try it out to see if it'll do the trick for you.  It's a five
minute setup and then you never have to touch it again to configure (unless
you want to!). And we think it's quite a bit more flexible and forgiving
than RUNRMTCMD. For one thing, you don't have to worry about some additional
login between the PC and the iSeries because the PC-Engine uses the profile
of the user currently signed on to the iSeries. In addition, I don't know
what it is you are doing with your .BAT file, but if it's used to download
files or open PC files or start PC programs, then the PC-Engine can do all
that for you in a single step as well.

Hope this helps!
(And if it doesn't then feel free to ignore me!)

Luke Dalton
TurboGorilla Software






-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Giusto
Sent: Tuesday, November 22, 2005 6:46 PM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: Client Access Incoming Remote Command 

I have a CLP that does a RUNRMTCMD to a PC (W2K) to start a .BAT file that
does a few things and make a call to another .BAT file on a drive mapped to
a folder on the IFS.  Everything was working fine until the PC crashed and
we had to rebuild it.  I remember having trouble getting all the settings
lined up the last time to get it to work (much trial and error).  What seems
to be happening is that the mapped drive gets disconnected when we issue a
call to the .BAT file or try to copy something to the mapped drive thru the
original .BAT file started by the incoming remote command.  I know the ID
signed on to the PC has permissions to the shared folder because I can run
the .BAT file directly, but the IRC seems to be running under a different
profile which disables the mapped drive. Does anyone know the correct
settings in client access properties or in the W2K services options to keep
the command running under the profile of the PC user (which in our case is a
valid AS400 user profile with access to the shared folder)?

TIA