Iseries Connect Shared Drives with Windows 2003 Server

0 pts.
Tags:
Application development
AS/400
DataCenter
Interoperability
PC/Windows Connectivity
Software
I am currently setting up an iSeries 520 at v5r3 which has a number of shared drives, holding data in IFS. I am using RUNRMTCMD to call a batch program on Windows 2003 Server R2 machine. The job starts fine, but the Shares that have been set up then show as disconnected on the 2003 server, as a result the job fails. I can manually run the job on the 2003 Server, and yet when I try with RUNRMTCMD the disconnect occurs. (I am already doing this process on an XP Machine, but at a different location, still accessing the same iSeries. Any suggestions gratefully received.
ASKED: June 2, 2006  7:23 AM
UPDATED: December 8, 2009  6:58 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

I had some similar problems and you will need to get further information, but I can point you in the right direction. There are a number of options available to you on the PC iSeries Access for Windows Remote Command, and it is quite confusing. In summary, the issue relates to the fact that the remote command is running under a job which is a service. I suspect that there are some user ID issues. I eventually gave up with my situation and created a job on the PC (not running as a service) which communicated with the iSeries with a data queue. I look forward to the wisdom of others in this matter which could help me out as well.

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • DaddyCOZ
    I had some similar problems and you will need to get further information, but I can point you in the right direction. There are a number of options available to you on the PC iSeries Access for Windows Remote Command, and it is quite confusing. In summary, the issue relates to the fact that the remote command is running under a job which is a service. I suspect that there are some user ID issues. I eventually gave up with my situation and created a job on the PC (not running as a service) which communicated with the iSeries with a data queue. I look forward to the wisdom of others in this matter which could help me out as well.
    0 pointsBadges:
    report
  • TomLiotta
    The job starts fine, but the Shares that have been set up then show as disconnected on the 2003 server, as a result the job fails. What happens? The job fails how? What error or result is reported? RUNRMTCMD over IP will create a spooled file related to the execution of the remote command. What was spooled? When the mapped drive was assigned, what profile created it? Was it the same profile that the remote command runs under? Does the remote command run under a profile that has permissions (under the Windows environment) to access that mapped drive? To see the mapped drive? Is that profile a Windows network profile or a local system profile? Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following