× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: How to pass parms to Perl
  • From: "Gary Kuznitz" <docfxit@xxxxxxxxxxx>
  • Date: Mon, 15 Nov 1999 08:03:06 -0800

For some reason I can't seem to figure out the correct syntax for calling 
a Perl script with parms.  The error  I am getting is:

Can't open perl script "/QOPENSYS/DYNDNSUPDATE.PL 
'209.162.41.222' 'POSTMASTER' 16660 'DOMAIN.COM'": No such path 
or directory.                          

I'm calling it With:
PGM                                                                   
             CALL       PGM(PERL5/PERL) +                             
                          PARM('/QOPENSYS/DYNDNSUPDATE.PL +           
           ''209.162.41.222'' ''POSTMASTER'' 16660 ''DOMAIN.COM''')  
ENDPGM 

The Perl script starts out with:                                           
#!/usr/bin/perl -W
use diagnostics;
use strict;

($ip, $user, $pass, $domain) = @ARGV;

I'd sure appreciate it if anyone could give me a clue how to pass parms to 
Perl.

TIA,

Gary Kuznitz
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.