Hi,

I am running a job on Windows
which executes a remote command on a
SCO UNIX machine.

This is done using RSH utility on Windows
as follows:

Set Command, "rsh unixhost -l root TestScript"
RunAndWait Command, "", 0, rcol

The command executes on the SCO host
but the command window on the Windows machine
remains open waiting for input. The command
I run on the SCO machine does not expect
any input.

If I manually press ENTER then the window
closes and the job continues.

I have tried the JAL command RunWithInput
but to no avail.

Does anyone know what the problem is?

Thanks
Sotiris

Try this

Command, "cmd /C rsh unixhost -l root TestScript"
RunAndWait Command, "", 0, rcol

You can also set the timeout value (third parameter in RunAndWait) to have 24x7 forcibly close this process after certain time.

: Hi,

: I am running a job on Windows
: which executes a remote command on a
: SCO UNIX machine.

: This is done using RSH utility on Windows
: as follows: Set Command, "rsh unixhost -l root TestScript"
: RunAndWait Command, "", 0, rcol

: The command executes on the SCO host
: but the command window on the Windows machine
: remains open waiting for input. The command
: I run on the SCO machine does not expect
: any input.

: If I manually press ENTER then the window
: closes and the job continues.

: I have tried the JAL command RunWithInput
: but to no avail.

: Does anyone know what the problem is?

: Thanks
: Sotiris

SysOp,

Thanks.

I solved this problem by doing:

rsh -n .....

However, if the remote command takes
a very long time to complete (ie more
than 5 minutes)rsh times out and the
Windows command prompt shuts down.

Is there a way to entend the timeout for
rsh?

Sotiris

: Try this

: Command, "cmd /C rsh unixhost -l root TestScript"
: RunAndWait Command, "", 0, rcol

: You can also set the timeout value (third parameter in RunAndWait) to have
: 24x7 forcibly close this process after certain time.

You will need to find an alternative utility supporting no timeouts or user-defined timeouts. I think there exist many shareware replacements for RSH. Try searching www.download.com.

Another solution is to run 24x7 RA Server on your Unix system. In your case you can use it as a replacement for RSH service. From 24x7 you will be able to execute any commands with any timeouts, capture remote output (both error and standard) as well as access remote files (both read and write) as if they were your local files.
For more info about 24x7 RA see your 24x7 Automation Suite documentation.

: SysOp,

: Thanks.

: I solved this problem by doing: rsh -n .....

: However, if the remote command takes
: a very long time to complete (ie more
: than 5 minutes)rsh times out and the
: Windows command prompt shuts down.

: Is there a way to entend the timeout for
: rsh?

: Sotiris

Thanks SysOp,

I looked at your UNIX agents and I did not
find one for SCO.

Is there one, or can I use an equivalent.

Sotiris

: You will need to find an alternative utility supporting no timeouts or
: user-defined timeouts. I think there exist many shareware replacements for
: RSH. Try searching www.download.com.

: Another solution is to run 24x7 RA Server on your Unix system. In your case
: you can use it as a replacement for RSH service. From 24x7 you will be
: able to execute any commands with any timeouts, capture remote output
: (both error and standard) as well as access remote files (both read and
: write) as if they were your local files.
: For more info about 24x7 RA see your 24x7 Automation Suite documentation.

You can use Universal Java version if you have JDK 1.4

: Thanks SysOp,

: I looked at your UNIX agents and I did not
: find one for SCO.

: Is there one, or can I use an equivalent.

: Sotiris