I am having problems running a com file from a remote host. The target host, computer2, has a com file which does some simple system checks. The com file then sets host, using decnet, to another computer, computer3 which performs similar system checks with its own com file. Control is then returned to computer2. The comfile from computer2 will run quite happliy with '@comfile'. I am wanting to run the comfile on computer 2 from another computer, computer1, which performs system checks around my works site. I can' telnet username/password' to computer2 and run the com file, or I can' rlogin username/password' to computer2 and run the com file. However, if I create a com file on computer1 to do this, it connects but then sits at the username prompt. I have also tried' rsh /user_name /password computer2 @comfile' but this will run the checks on comuter2 but not computer3. I should further explain that computer1 is on a seperate subnet to computer2 and 3, so I cannot connect to computer3 direct from computer1 as decnet is not routed on my site, only IP. Computer1 has openvms7.1 with UCX and decnet, computer2 has vms6.1 with ucx decnet, and computer3 has vms7.1 with decnet only. I would welcome any suggestions to anyone who is still with me and reading !!

Let me see if I understand correctly what you're after. You want a command procedure on "computer2" (c2) to be able to kick off a similar, if not identical, command procedure on "computer1" (c1) and "computer3" (c3) You can get from c2 to c1 and c3, but c1 cannot get directly to c3. The command procedure starts this all off on c2. Correct? Assuming it is, the problem is in depending on a "set host" from within a command procedure. I've seen this work with squirrely results at best, and total failure (such as waiting at the "Username:" prompt) at worst. I have 2 possible suggestions: 1. Use SUBMIT/REMOTE on c2 to kick off the command procedures on the other 2 nodes. The command procedures themselves must be on the target nodes; if necessary, you can copy them from c2. This assumes you have batch queues enabled on c1 and c3. 2. Use some form of "TELL" command file to invoke the command procedures remotely. I've seen a variety of variations on this, but basically the sending end sends a DCL command, and the receiving end executes it using simple DCL symbol substitution. You can add logic to display remote results, if desired, but that gets significantly trickier. If you need to have c1 tell c3 to do something, you can use what I call "manual routing." To get a directory on c3 from c1, you'd type something like this: $ dir c2::c3::some_disk:[some_dir] Notice you specify two nodes; what DECnet does is go to c2, giving it the remainder of the filespec, c3::some_disk:[some_dir]. As far as I've seen, you can do this anywhere a DECnet node is required (but I haven't tried it everywhere, such as in a SUBMIT/REMOTE).