01-06-2011
It sounds like you logged into another system using expect features in a PERL program on the current system. If you want to run some PERL on the remote system, you have to call PERL there and provide it with scripting either from a file there or pushed down the pipe from the first system/script. That is two main PERL scripts running on two systems, with a login pipeline between them.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Problem: I have a shell script that will be called by a Perl module that will connect to a db and delete rows. The Perl module will be called by CRON. I am using a Perl module to call a shell script because I need to get the db connection from Perl.
Here is the Perl pseudocode:
... (4 Replies)
Discussion started by: mh53j_fe
4 Replies
2. Shell Programming and Scripting
I want to replace a Perl module name in all my Perl Scripts in the cgi-bin directory. How is it possible?
I have the following statement in my scripts
use myUtil;
I want to change it to
use myUtil777;
Regards,
Rahul (2 Replies)
Discussion started by: rahulrathod
2 Replies
3. Shell Programming and Scripting
I call a EXPECT script from my perl script with machine IP and a FIle. The script logins to the machine and exports the value. The values to be exported or stored in a file.
I have close to 10 machines and I have created 10 files and pass the corresponding files in command line, Now I could like... (4 Replies)
Discussion started by: ramkriz
4 Replies
4. Shell Programming and Scripting
Hi,
I can't get this script ot work and I wa wondering if anyone could help?
I need to open a file and use a subroutine to search each line for a regular expression. If it matches then I need to return a match from the subroutine and print the result?
Any help would be greatly... (11 Replies)
Discussion started by: jmd2004
11 Replies
5. Shell Programming and Scripting
Hi All,
I have a doubt whether expect module in perl will work in SQL prompt or its applicable only for shell prompt ?
Thanks,
Arun V (2 Replies)
Discussion started by: arun_maffy
2 Replies
6. Shell Programming and Scripting
The following subroutine prints 1 instead of the content of the Equipment variable. Can someone tell me why?
#!c:/perl/bin/perl.exe
#
use strict 'vars';
my $Equipments = "data/equips.txt";
unless (open(EQUIP_FH, "$Equipments")) {
print "errors: $Equipments\n"; # This line prints... (1 Reply)
Discussion started by: tqlam
1 Replies
7. Shell Programming and Scripting
Hi,
ive a perl script, where it has a subroutine clear() in it, and i've one shell script which runs in background, from that shell script i wanted to call subroutine which is in perl script, that's perl script is not module, just simple script.
Eg:
perl script <test>
#!... (4 Replies)
Discussion started by: asarunkumar
4 Replies
8. Programming
Hi everyone,
I have given up finally trying to find a way to do this.
I have a subroutine called LoginFirst where I am starting a new SSH session.
I have bunch of subroutines, each one of them uses a (or I have to create
a new SSH constructor everytime) ssh connection to get some value so ... (2 Replies)
Discussion started by: dummy_code
2 Replies
9. Shell Programming and Scripting
Hello All,
I am in the process of learning perl.I have a perl script and based on the arguments passed it would the appropriate subroutine that is defined in the script.
Now, I need to check a value that is defined in the Environment variables and should call the subroutine only if the... (1 Reply)
Discussion started by: filter
1 Replies
10. Shell Programming and Scripting
Hi,
I am an occasional PERL user. I am trying to call a sub routine (passing parameters) in perl module from a driver .pl file. I have been "tinkering" for a while now and have confused myself.
Could someone please look at the code below and spot where I am going wrong.
testPerl.pl
... (0 Replies)
Discussion started by: chris01010
0 Replies
LEARN ABOUT MOJAVE
perlvos5.18
PERLVOS(1) Perl Programmers Reference Guide PERLVOS(1)
NAME
perlvos - Perl for Stratus OpenVOS
SYNOPSIS
This file contains notes for building perl on the Stratus OpenVOS operating system. Perl is a scripting or macro language that is popular
on many systems. See perlbook for a number of good books on Perl.
These are instructions for building Perl from source. This version of Perl requires the dynamic linking support that is found in OpenVOS
Release 17.1 and thus is not supported on OpenVOS Release 17.0 or earlier releases.
If you are running VOS Release 14.4.1 or later, you can obtain a pre-compiled, supported copy of perl by purchasing the GNU Tools product
from Stratus Technologies.
BUILDING PERL FOR OPENVOS
To build perl from its source code on the Stratus V Series platform you must have OpenVOS Release 17.1.0 or later, GNU Tools Release 3.5 or
later, and the C/POSIX Runtime Libraries.
Follow the normal instructions for building perl; e.g, enter bash, run the Configure script, then use "gmake" to build perl.
INSTALLING PERL IN OPENVOS
1. After you have built perl using the Configure script, ensure that you have modify and default write permission to ">system>ported" and
all subdirectories. Then type
gmake install
2. While there are currently no architecture-specific extensions or modules distributed with perl, the following directories can be used
to hold such files (replace the string VERSION by the appropriate version number):
>system>ported>lib>perl5>VERSION>i786
3. Site-specific perl extensions and modules can be installed in one of two places. Put architecture-independent files into:
>system>ported>lib>perl5>site_perl>VERSION
Put site-specific architecture-dependent files into one of the following directories:
>system>ported>lib>perl5>site_perl>VERSION>i786
4. You can examine the @INC variable from within a perl program to see the order in which Perl searches these directories.
USING PERL IN OPENVOS
Restrictions of Perl on OpenVOS
This port of Perl version 5 prefers Unix-style, slash-separated pathnames over OpenVOS-style greater-than-separated pathnames. OpenVOS-
style pathnames should work in most contexts, but if you have trouble, replace all greater-than characters by slash characters. Because
the slash character is used as a pathname delimiter, Perl cannot process OpenVOS pathnames containing a slash character in a directory or
file name; these must be renamed.
This port of Perl also uses Unix-epoch date values internally. As long as you are dealing with ASCII character string representations of
dates, this should not be an issue. The supported epoch is January 1, 1980 to January 17, 2038.
See the file pod/perlport.pod for more information about the OpenVOS port of Perl.
TEST STATUS
A number of the perl self-tests fails for various reasons; generally these are minor and due to subtle differences between common POSIX-
based environments and the OpenVOS POSIX environment. Ensure that you conduct sufficient testing of your code to guarantee that it works
properly in the OpenVOS environment.
SUPPORT STATUS
I'm offering this port "as is". You can ask me questions, but I can't guarantee I'll be able to answer them. There are some excellent
books available on the Perl language; consult a book seller.
If you want a supported version of perl for OpenVOS, purchase the OpenVOS GNU Tools product from Stratus Technologies, along with a support
contract (or from anyone else who will sell you support).
AUTHOR
Paul Green (Paul.Green@stratus.com)
LAST UPDATE
February 28, 2013
perl v5.18.2 2013-11-04 PERLVOS(1)