Is the remote command (REXEC) server running on the target system? A number of companies do not start REXEC for security reasons.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Rogerson
Sent: Wednesday, September 25, 2013 1:30 PM
To: Midrange Systems Technical Discussion
Subject: Help setting up RUNRMTCMD...

Hi all, I have searched the web and these archives but I am still unable
to get RUNRMTCMD to work.

On the IBM i (7.1) i create user adminhc.
On the Windows 2003 (VM) server I created user adminhc with the same
password.
I changed the Client access properties:
Security Options
Command mode: New Console
Cache security: unchecked
Allow generic security: unchecked
Generic Security runs command as logged on user: unchecked
Command context options
Run as system: checked
Load user profile when command run in user context: unchecked

CWBRXD service Log on Tab
Local system account (selected)
Allow service to interact with desktop: checked

The service starts without error on the Windows service.

On the IBM i I try
RUNRMTCMD CMD('dir') RMTLOCNAME('10.10.10.130' *IP) RMTUSER('adminhc')
RMTPWD() WAITTIME(15)

The session locks up (for more than 15 seconds) and then issues 'Command
did not complete successfully'.

When I press F1 and check the joblog all I see is...

A remote host did not respond within the timeout period.
Command did not complete successfully.

I check for spoolfiles and there are none. I'm a little stumped and don't
know where else to look.

Has anyone have RUNRMTCMD working and could give me some help/advise?

Thanks,

Rob

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.