RE: runrmtcmd and the registry

Angela,

I could be wrong.  But I don't believe that the HKEY_Current_User should be
used by anything but an interactive application as it refers to the
Currently logged on user.  Which explains why the job runs fine if the user
is logged on.

I'd put the registry info in another subtree, HKEY_Local_Machine perhaps?


HTH,
Charles


> -----Original Message-----
> From: Angela Wawrzaszek [mailto:awawrzaszek@xxxxxxxxxxxxxxx]
> Sent: Friday, October 15, 2004 12:55 PM
> To: Midrange Systems Technical Discussion
> Subject: runrmtcmd and the registry
> 
> 
> I wrote earlier with a problem running rmtcmd from the as/400 to a
> windows 2003 server.   I have made some progress.   The 'old' 
> job on the
> server works fine.   I use a runrmtcmd from the as/400 to 
> execute a .exe
> file on a server on our network.     The application has been modified
> to now use the registry keys for information.   This seems to be the
> problem.   When this job runs from the as/400 it hangs up.   
> In a log we
> produces it is when reading the HKEY_Current_user.    There 
> are 3 fields
> in there that it is not able to read,  that the application 
> requires to
> run.  So the application is basically hung up waiting for user input.
> HOWEVER    I can log on to that machine as this rmtuser and then the
> AS400 job DOES run fine.   However we do not want the server to be
> logged into as this user.  The user does have administrative rights.
> So is there shome mystery with registry keys and the as400?  
> 
>  
> 
> Any help would be great
> 
>  
> 
> Angela Wawrzaszek
> 
> Programmer/Analyst
> 
> awawrzaszek@xxxxxxxxxxxxxxx
> 
> (315) 258-4205
> 
>  
> 
> --
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>