|
We have an application that sits on our mail server. I am able to use runrmtcmd to connect to this server and kick off the executable for it. All seems fine, until we just had a new version of this created. It resides in a different folder and a different .exe name so that we can have them both run at the same time while bugs are worked out. I can sign on to the mail server and start the job no problem. However if I run a cl program to start the job it hangs up. It is sitting there on TIMW on the connection string. The big difference between the verson 1 and version 2 is that version 2 was made generic and used the registry keys to point to where the data, log and help files of the app are located, where version 1 they were located in a direct path name. Would this be something that would confuse the runrmtcmd from being able to run? Can anyone think of any other things I can check to determine why I cannot run this command remotely? As I said I can sign on directly to the machine so I do not believe it is a security issue. Version 1: CHGVAR VAR(&CMD) VALUE('"\\ServerName\ZANY + ZOFTWARE\NUCOR CONNECT\NUCORCONN.EXE" + /JC:NUTRUCK-R') RUNRMTCMD CMD(&CMD) RMTLOCNAME('xxx.xxx.x.xxx' *IP) + RMTUSER(USER) RMTPWD('PASSWORD') Version 2: CHGVAR VAR(&CMD) VALUE('"\\ServerName\ZANY + ZOFTWARE\NUCOR CONNECT2\NC2.EXE" + /JC:NUTRUCK-R') RUNRMTCMD CMD(&CMD) RMTLOCNAME('xxx.xxx.x.xxx' *IP) + RMTUSER(USER) RMTPWD('PASSWORD') When I say the second version uses the registry keys to find the data I mean all data is actually stored in an access database on the second server. So within that app when NC2.exe gets started the registry keys tells it to look in d:\program files\zz\nucorconnect2\nc2.mdb for information. I am only trying to kick off this job. I am passing in the job code /jc:scrap-po to tell the application which part of the app to process on the other server. The path name on the iseries is hard coded, I am only calling the app on the server, all processing takes place there. It does actually open the job because it is open on the server (the .ldb is running) and the as/400 is locked. But it never finishes. That is why I think it has something to do with the registry possibly? Angela Wawrzaszek Programmer/Analyst awawrzaszek@xxxxxxxxxxxxxxx (315) 258-4205
As an Amazon Associate we earn from qualifying purchases.
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.