Skip Navigational Links
LISTSERV email list manager
LISTSERV - LISTSERV.MIAMIOH.EDU
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - MU-VMS Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

MU-VMS Archives

November 1996

MU-VMS@LISTSERV.MIAMIOH.EDU

Menu
LISTSERV Archives LISTSERV Archives
MU-VMS Home MU-VMS Home
MU-VMS November 1996

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: OpenVMS, Perl, and Process IDs
From:
Kent Covert <[log in to unmask]>
Reply To:
Miami University OpenVMS <[log in to unmask]>
Date:
Tue, 5 Nov 1996 08:15:54 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
In article <[log in to unmask]>,
 [log in to unmask] (Micah James Cooper) writes:
> Chris Carman ([log in to unmask]) wrote:
>> This just results in a filename like 4-NOV-199615-04-56.41, which is as close
>> to unique as I can get.  Anyway, it didn't work out; I'm having prolems
>> getting a script to send a mail message right now.
>
> Say, is there a command equiv to
> mail << "text"?
 
Not exactly.  At the $ prompt, you could do something like the following,
though:
 
    $ PIPE TYPE filename.ext | MAIL SYS$INPUT "[log in to unmask]"
 
Or, a more efficient approach would be:
 
    $ MAIL filename.ext "[log in to unmask]"
 
--
                                     Kent Covert, Software Coordinator
                                     Miami Computing and Information Services
                                     Miami University, Oxford, OH
                                     [log in to unmask]

ATOM RSS1 RSS2

LISTSERV.MIAMIOH.EDU CataList Email List Search Powered by LISTSERV