The syntax "cmd :== $executable" defines what VMS calls a "foreign command".
These commands are set up individually for each process, so if you want the
perl command to be available for everyone on the system, you will need to
put the command into a system-wide login command file, such as SYLOGIN.C
VMSPerl,
I've come up with a solution to my TCPIP auxiliary service question. I'll
include the code if anyone is interested.
1) I create a server account in UAF with the desired priviledges
2) I create an auxilary service
TCPIP> set service x /protocol=tcp /port={wakeup port #} /proc={proce
VMSPerl,
I've writen numerous client/server routines using IO::Socket and
IO::Socket::INET to communicate between VMS and other platforms with great
success. Recently, I decided to look into creating a TCPIP Services
"Auxliary Service" using
TCPIP> SET SERVICE x /port=x /proc=xfer /prot=tcp /fil
"Martin Vorlaender" <[EMAIL PROTECTED]> wrote:
> You prefix the perl script with
> $ perl 'f$env("procedure")' "''p1'" "''p2'" "''p3'" "''p4'" "''p5'"
"''p6'"
> "''p7'" "''p8'"!
> $ exit++ + ++$status!=0 and $exit=$status=undef; while($#ARGV != -1 and
> $ARGV[$#ARGV] eq ''){pop @ARGV;}
> eva
> When I write my perl scripts on UNIX, the first line I would usually put:
> #!/usr/bin/perl
On Unix this type of line at the start of a script tells the system which shell
to use. Perl just uses the same mechanism on Unix to tell the system that this
is a perl script.
VMS doesn't have such a me
