I have a script on one server.. which I am trying to run remotely from another server using rsh....

The command that i use from my second server is as follows

rsh /user_name="ops" /password="ops1" server1 "cd /users/ops ; ./script1"


When I run this I receive an error containing the below errors:
grc_error() says: GRC file /users/ops/.ops.rc open failed: No such file or directory (result 3)

I can run the script with no problems on server1 but when I try remotely from another server using rsh I receive the error above.. Any help would be appreciated - Anyone know what this file is or needs to contain??

The syntax on your rsh command is very odd. What versions of unix are running on these systems?

If server1 works like versions of unix that I know, I may have an idea. Sign on to it and type env to see your environment. Then run an rsh command with just "env". I'll bet that your script needs an environment variable set. I would figure out which one and set it in the script.

I am running the rsh command from an openvms system to a unix alpha system.

I hadnt checked the env variables yet but I will do so now...
Any idea what variable it could be?

No idea about which variable. Just clobber them one by one until it fails.

openvms supports rsh?! Now that is interesting....

Well, I posted that your DCL may in the wrong order, but then I jumped on a free VMS account and looked further - it should be fine.

Follow Perderabo's suggestion.

A lot of variables, so I am going through one by one.. I will let you know...



I am using openvms 7.3-1 and it supports rsh no problem... and I am pretty sure anything from at least 7.2 up does, not sure to prior to those versions.

Can the author of the script provide any guidance? There should be some documentation, even if it is only in comments inside the script.

This page seems to suggest that a perl module named named getrc might need RC_PATH. Could that be it?

And understand that once you get past this error, you could encounter another error generated by a missing environment variable. You can eventually find them all by trial and error. But someone who understands the tools being used by the script can probably find them all in a few seconds.