Sponsored Content
Top Forums Shell Programming and Scripting RSH use for executing a script Post 41264 by RTM on Wednesday 1st of October 2003 01:27:16 PM
Old 10-01-2003
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.

Last edited by RTM; 10-01-2003 at 02:45 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

remote login through a script ( except rsh)

Hi Guys, I'm having a problem trying to change to a different user within a script . I want to change to a specific user and then run the subsequent commands using his previleges . I remember having used ' su ' some years back for this , can't figure it out now !! Help appreciated . (3 Replies)
Discussion started by: rahma
3 Replies

2. Shell Programming and Scripting

Multiple rsh in a script not working

Hi, From one of the unix servers i want execute an rsh command to 5 different servers. i want to go to these servers execute a command and come back. i have a main program which calls a function, where in i use the rsh command. The server name is passed as a parameter to teh function. it is... (3 Replies)
Discussion started by: praphul
3 Replies

3. Shell Programming and Scripting

Script using rsh(remote shell)

Hi, I am writing a script that will require me to perform tasks across servers. I tried to use rsh <host> "Commands..." > /dev/null 2>&1. However, I am required to execute a long series of commands after that and rsh does not seem to support this and its also insecure. I tried to use rsh to... (5 Replies)
Discussion started by: joseph_ng
5 Replies

4. Shell Programming and Scripting

unzip in script using rsh

Hi I have searched usr/bin and usr/sbin to try to find unzip but I cannot find it. My script is using the ksh #!/usr/bin/ksh but when I rsh to another box it cannot find unzip to unzip to a new archive, but I can unzip files when I am using a telnet session on the box. The error message... (4 Replies)
Discussion started by: speedieB
4 Replies

5. Shell Programming and Scripting

running multiple rsh command in a script

hi scripting experts, juz wondering if it's possible to have multiple rsh command in a single script? :confused: ie: rsh -l <username> "<command>" rsh -l <username> "<command>" thanks. regards, wee :) (0 Replies)
Discussion started by: lweegp
0 Replies

6. Shell Programming and Scripting

rsh script with inside a for loop

hi everyone, I have the following problem: the foreach loop inside rsh doesn'work. I have tried the for command but it's not recognized. with the foreach command I don't receive any error, but it doesn't really make the cycle, ignoring the foreach and executing 1 time the echo command. Anyone has... (5 Replies)
Discussion started by: trekianov
5 Replies

7. Shell Programming and Scripting

Permission denied while executing rsh

Hi All, I have two servers, say server1 and server2. I have put the entries of both servers in /.rhosts file of both servers. So, when I tried to run following from server1- rsh server2 "ls" Permission denied was printed on console. Can anyone help me out? Regards, akash mahakode (4 Replies)
Discussion started by: akash_mahakode
4 Replies

8. Linux

rsh to other machine using script

Hi, I want to rsh to other machine & run a script, but it is nt working eg: rsh host command but after this it doesn't login into that machine & run the command on y machine but if i write rsh host then after loggi i write commands it works. Is i am doing something wrong. I jus need... (2 Replies)
Discussion started by: sarbjit
2 Replies

9. Shell Programming and Scripting

help with RSH script

Hi All, I wrote a quick script but don't know how to execute the command and bring the info back to me. Please advise. #!/usr/bin/ksh for SYSTEM in xyz abc do echo $SYSTEM rsh $SYSTEM lscfg -v |grep hdisk ## Need to find out how many disk drives it has done (1 Reply)
Discussion started by: samnyc
1 Replies

10. Solaris

Problem on rsh to run script

Hi, i want to run a touch_file_script.sh on host2 by rsh -ing from host1 to host 2 <host1># rsh <host2> <path>/touch_file_script.sh No error was prompt. However it did not create the file as in the script. # rsh <host2> # sh -x <path>/touch_file_script.sh + touch <file> Run it... (1 Reply)
Discussion started by: beginningDBA
1 Replies
vmsish(3pm)						 Perl Programmers Reference Guide					       vmsish(3pm)

NAME
vmsish - Perl pragma to control VMS-specific language features SYNOPSIS
use vmsish; use vmsish 'status'; # or '$?' use vmsish 'exit'; use vmsish 'time'; use vmsish 'hushed'; no vmsish 'hushed'; vmsish::hushed($hush); use vmsish; no vmsish 'time'; DESCRIPTION
If no import list is supplied, all possible VMS-specific features are assumed. Currently, there are four VMS-specific features available: 'status' (a.k.a '$?'), 'exit', 'time' and 'hushed'. If you're not running VMS, this module does nothing. "vmsish status" This makes $? and "system" return the native VMS exit status instead of emulating the POSIX exit status. "vmsish exit" This makes "exit 1" produce a successful exit (with status SS$_NORMAL), instead of emulating UNIX exit(), which considers "exit 1" to indicate an error. As with the CRTL's exit() function, "exit 0" is also mapped to an exit status of SS$_NORMAL, and any other argument to exit() is used directly as Perl's exit status. "vmsish time" This makes all times relative to the local time zone, instead of the default of Universal Time (a.k.a Greenwich Mean Time, or GMT). "vmsish hushed" This suppresses printing of VMS status messages to SYS$OUTPUT and SYS$ERROR if Perl terminates with an error status, and allows programs that are expecting "unix-style" Perl to avoid having to parse VMS error messages. It does not suppress any messages from Perl itself, just the messages generated by DCL after Perl exits. The DCL symbol $STATUS will still have the termination status, but with a high-order bit set: EXAMPLE: $ perl -e"exit 44;" Non-hushed error exit %SYSTEM-F-ABORT, abort DCL message $ show sym $STATUS $STATUS == "%X0000002C" $ perl -e"use vmsish qw(hushed); exit 44;" Hushed error exit $ show sym $STATUS $STATUS == "%X1000002C" The 'hushed' flag has a global scope during compilation: the exit() or die() commands that are compiled after 'vmsish hushed' will be hushed when they are executed. Doing a "no vmsish 'hushed'" turns off the hushed flag. The status of the hushed flag also affects output of VMS error messages from compilation errors. Again, you still get the Perl error message (and the code in $STATUS) EXAMPLE: use vmsish 'hushed'; # turn on hushed flag use Carp; # Carp compiled hushed exit 44; # will be hushed croak('I die'); # will be hushed no vmsish 'hushed'; # turn off hushed flag exit 44; # will not be hushed croak('I die2'): # WILL be hushed, croak was compiled hushed You can also control the 'hushed' flag at run-time, using the built-in routine vmsish::hushed(). Without argument, it returns the hushed status. Since vmsish::hushed is built-in, you do not need to "use vmsish" to call it. EXAMPLE: if ($quiet_exit) { vmsish::hushed(1); } print "Sssshhhh...I'm hushed... " if vmsish::hushed(); exit 44; Note that an exit() or die() that is compiled 'hushed' because of "use vmsish" is not un-hushed by calling vmsish::hushed(0) at runtime. The messages from error exits from inside the Perl core are generally more serious, and are not suppressed. See "Perl Modules" in perlmod. perl v5.18.2 2014-01-06 vmsish(3pm)
All times are GMT -4. The time now is 02:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy