INFO-VAX Fri, 18 Jan 2008 Volume 2008 : Issue 35 Contents: old alphas available Re: print queues and IP Re: Send mail without a file Re: Send mail without a file Re: Send mail without a file Re: Send mail without a file Re: Send mail without a file Re: Send mail without a file Re: Send mail without a file Re: Why Writers Buy Asbestos Undies Re: Why Writers Buy Asbestos Undies ---------------------------------------------------------------------- Date: Thu, 17 Jan 2008 14:43:57 -0800 (PST) From: kczwei Subject: old alphas available Message-ID: <3dd1e0e2-acc6-4cd1-9df1-6e9b378bf4b6@v29g2000hsf.googlegroups.com> I have 2 old DecPc's/axp 150 I have at least 2 old personal workstations I have at least 3 alphastatioon 200/100 or 200/233's. They are available for free in western Colorado. I think the alphastations had their power supplies scavenged, but the others all worked when last un-plugged. kaycee-AT-kaycee-DOT-net 970.874.4795 going to dustbin shortly. ------------------------------ Date: Fri, 18 Jan 2008 02:28:51 +0200 From: =?ISO-8859-1?Q?Uusim=E4ki?= Subject: Re: print queues and IP Message-ID: <478feefe$0$21879$9b536df3@news.fv.fi> etmsreec@yahoo.co.uk wrote: > On 13 Jan, 12:01, Uusimäki > wrote: >> H Vlems wrote: >>> Yesterday I bought an Alpha Server 1200 5/400 (a blue one, not a white >>> box alpha). Since it is too heavy to put it in the same room as the >>> others as yet, it sits noisily in the living room. The only available >>> printer there is an old HP2100 with an IP printserver. >>> I want to create a printerqueue that allows me to print to that >>> HP2100, its IP address is 10.0.0.102. >>> IIRC the TCPIP$TELNETSYM processor is needed, but where do I put the >>> IP address? >>> Hans >> Why not use the DCPS? It is very easy to use and supports a wealth of >> different printers and almost any type of connection. >> It makes it possible to print PS etc. >> >> http://h71000.www7.hp.com/doc/82final/dcps/dcps025_release_notes.PDF >> >> And the Hobbyist license kit includes DCPS licenses. >> >> Kari > > Depends whether the HP 2100 has Postscript in it. Most of the HP > printers that I've seen in the last ten years have Postscript as an > added cost extra (often as a memory SIMM). The alternative way to > look at the situation is that the printer would be able to decode > whatever stream of data got fed to it if it was IP capable but > wouldn't be able to print output from a DCPS queue if it didn't have > Postscript in it. > You pays your money and take syour choice. > > Steve Sure, I know, but what I meant with PS was that if it was a required option, then DCPS could handle that out of the box also, not just ASCII. Kari ------------------------------ Date: Thu, 17 Jan 2008 13:30:49 -0800 (PST) From: FrankS Subject: Re: Send mail without a file Message-ID: <97312db7-5345-4fcc-821d-39981c7f4a73@x69g2000hsx.googlegroups.com> On Jan 17, 4:23=A0pm, vancouvercan...@yahoo.ca wrote: > Is it possible to send a VMS email without specifying a file to send? > Normal command is: > $ mail somefile.txt someuser /sub=3DTest > where somefile.txt is sent as the body. > > I want to send this > $ mail "Some text that I like!" someuser /sub=3DTest > > TIA > Van $ MAIL SYS$INPUT: someuser /subject=3D"Test" Some text that I like $ ------------------------------ Date: Thu, 17 Jan 2008 22:13:10 GMT From: =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= Subject: Re: Send mail without a file Message-ID: vancouvercancun@yahoo.ca wrote: > Is it possible to send a VMS email without specifying a file to send? > Normal command is: > $ mail somefile.txt someuser /sub=Test $ mail nl: someuser /sub=Test ------------------------------ Date: Thu, 17 Jan 2008 22:28:27 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: Send mail without a file Message-ID: In article , =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= writes: > > >vancouvercancun@yahoo.ca wrote: >> Is it possible to send a VMS email without specifying a file to send? >> Normal command is: >> $ mail somefile.txt someuser /sub=Test > >$ mail nl: someuser /sub=Test That will send a blank body message. Instead of NL:, use SYS$INPUT: Then follow up with the text. A previous post has already covered this. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Thu, 17 Jan 2008 17:32:32 -0500 From: "Ken Robinson" Subject: Re: Send mail without a file Message-ID: <7dd80f60801171432s1186c4cal85a92b937fca5192@mail.gmail.com> On Jan 17, 2008 4:30 PM, FrankS wrote: > On Jan 17, 4:23pm, vancouvercan...@yahoo.ca wrote: > > Is it possible to send a VMS email without specifying a file to send? > > Normal command is: > > $ mail somefile.txt someuser /sub=Test > > where somefile.txt is sent as the body. > > > > I want to send this > > $ mail "Some text that I like!" someuser /sub=Test > > > > TIA > > Van $ pipe write sys$output "Some text that I like" | mail/sub="This is a test of PIPE" sys$pipe "youremail@example.com" Ken ------------------------------ Date: Thu, 17 Jan 2008 14:43:05 -0800 From: glen herrmannsfeldt Subject: Re: Send mail without a file Message-ID: vancouvercancun@yahoo.ca wrote: > Is it possible to send a VMS email without specifying a file to send? Maybe, but it might create a file anyway. Many years ago on a VMS systems, my account was configured with the wrong name for my home directory. I wanted to send mail to the system administrator, but I couldn't, as it wanted to write the message into a file. (In my directory...) -- glen ------------------------------ Date: Thu, 17 Jan 2008 17:49:24 -0500 From: norm.raphael@metso.com Subject: Re: Send mail without a file Message-ID: This is a multipart message in MIME format. --=_alternative 007D5EEB852573D3_= Content-Type: text/plain; charset="US-ASCII" FrankS wrote on 01/17/2008 04:30:49 PM: > On Jan 17, 4:23 pm, vancouvercan...@yahoo.ca wrote: > > Is it possible to send a VMS email without specifying a file to send? > > Normal command is: > > $ mail somefile.txt someuser /sub=Test > > where somefile.txt is sent as the body. > > > > I want to send this > > $ mail "Some text that I like!" someuser /sub=Test > > > > TIA > > Van > > $ MAIL SYS$INPUT: someuser /subject="Test" > Some text that I like > $ More properly: $!.... $ MAIL SYS$INPUT: someuser /subject="Test" $ DECK Some text that I like Some more text etc. $EOD $!.... --=_alternative 007D5EEB852573D3_= Content-Type: text/html; charset="US-ASCII"



FrankS <sapienza@noesys.com> wrote on 01/17/2008 04:30:49 PM:

> On Jan 17, 4:23 pm, vancouvercan...@yahoo.ca wrote:
> > Is it possible to send a VMS email without specifying a file to send?
> > Normal command is:
> > $ mail somefile.txt someuser /sub=Test
> > where somefile.txt is sent as the body.
> >
> > I want to send this
> > $ mail "Some text that I like!" someuser /sub=Test
> >
> > TIA
> > Van
>
> $ MAIL SYS$INPUT: someuser /subject="Test"
> Some text that I like
> $


More properly:
$!....
$ MAIL SYS$INPUT: someuser /subject="Test"
$ DECK
Some text that I like
Some more text
etc.
$EOD
$!....


--=_alternative 007D5EEB852573D3_=-- ------------------------------ Date: Thu, 17 Jan 2008 23:01:55 GMT From: =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= Subject: Re: Send mail without a file Message-ID: VAXman- @SendSpamHere.ORG wrote: > In article , =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= writes: >> >> vancouvercancun@yahoo.ca wrote: >>> Is it possible to send a VMS email without specifying a file to send? >>> Normal command is: >>> $ mail somefile.txt someuser /sub=Test >> $ mail nl: someuser /sub=Test > > That will send a blank body message. I know. A body was not specified as an requirement... On the other hand, sys$input could also be seen as a "file"... :-) $ mail MAIL> send To: someuser Subj: Test Enter your message below. Press CTRL/Z when complete, or CTRL/C to quit: Some message... MAIL> $ 34 kaystrokes for the sys$input example. 26 keystrokes for my example. Not counting the "body" itself, as one keystroke and including all CR's. Jan-Erik. ------------------------------ Date: 17 Jan 2008 20:10:30 GMT From: billg999@cs.uofs.edu (Bill Gunshannon) Subject: Re: Why Writers Buy Asbestos Undies Message-ID: <5v9r1mF1lni5vU1@mid.individual.net> In article , yyyc186 writes: > Here is what the Kirkus reviewer had to say. I guess this explains > why there were no OpenVMS books in their review database. > > This hefty tome provides brief and > rambling introductions to programming on OpenVMS in a number of > languages. In overall structure, this guide to programming on an > OpenVMS platform is logically laid out. An introduction to OpenVMS is > followed by overviews of source control systems, programming to > interact with VMSMAIL, reporting services and finally, a number of > programming languages: DCL, BASIC, Fortran, COBOL, C and C++. The same > application--a simple lottery demonstration with input and out- put > datasets--is re-implemented in each of the languages. At its simplest, > this is a common and straight-forward layout for an introductory > programming manual. The individual chapters, however, are incoherent. > The introduction to VMS wanders from simple concepts such as logging > in and symbol assignment to a sweeping and unclear description of > system logicals to the complexity of ACLs. The chapter on Fortran > interrupts a discussion of Fortran fundamentals such as line numbers > and numeric operators with several paragraphs on the history of > Fortran batch processing. The COBOL chapter wonders why the owners of > the OpenVMS operating system haven't modified all programming > languages implemented on the operating system to match functionality > that text finds desirable in COBOL. The chapter on C and C++ treats C+ > + as a mere functional enhancement of C, and scoffs at the object- ^^^^^^^^^^^^^^^^^^^^^ > oriented functionality of C++. OpenVMS-specific variables, constants ^^^^^^^^^^^^^^^^^^^^^^^^ > and extensions are usefully listed, but the context does not allow for > clear explanation of their functionality. A clos- > ing chapter of "Ruminations and Observations" is an incoherent and > ranting distraction from what utility the technical chapters provide. > A nice idea but lacks clarity. Well, your mistake is obvious. See the pointers above. As soon as you questioned the world-saving notion of OO you were doomed. bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves bill@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: Thu, 17 Jan 2008 21:04:15 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: Why Writers Buy Asbestos Undies Message-ID: In article <5v9r1mF1lni5vU1@mid.individual.net>, billg999@cs.uofs.edu (Bill Gunshannon) writes: > > >In article , > yyyc186 writes: >> Here is what the Kirkus reviewer had to say. I guess this explains >> why there were no OpenVMS books in their review database. >> >> This hefty tome provides brief and >> rambling introductions to programming on OpenVMS in a number of >> languages. In overall structure, this guide to programming on an >> OpenVMS platform is logically laid out. An introduction to OpenVMS is >> followed by overviews of source control systems, programming to >> interact with VMSMAIL, reporting services and finally, a number of >> programming languages: DCL, BASIC, Fortran, COBOL, C and C++. The same >> application--a simple lottery demonstration with input and out- put >> datasets--is re-implemented in each of the languages. At its simplest, >> this is a common and straight-forward layout for an introductory >> programming manual. The individual chapters, however, are incoherent. >> The introduction to VMS wanders from simple concepts such as logging >> in and symbol assignment to a sweeping and unclear description of >> system logicals to the complexity of ACLs. The chapter on Fortran >> interrupts a discussion of Fortran fundamentals such as line numbers >> and numeric operators with several paragraphs on the history of >> Fortran batch processing. The COBOL chapter wonders why the owners of >> the OpenVMS operating system haven't modified all programming >> languages implemented on the operating system to match functionality >> that text finds desirable in COBOL. The chapter on C and C++ treats C+ >> + as a mere functional enhancement of C, and scoffs at the object- > ^^^^^^^^^^^^^^^^^^^^^ >> oriented functionality of C++. OpenVMS-specific variables, constants >^^^^^^^^^^^^^^^^^^^^^^^^ >> and extensions are usefully listed, but the context does not allow for >> clear explanation of their functionality. A clos- >> ing chapter of "Ruminations and Observations" is an incoherent and >> ranting distraction from what utility the technical chapters provide. >> A nice idea but lacks clarity. > >Well, your mistake is obvious. See the pointers above. As soon as you >questioned the world-saving notion of OO you were doomed. Oh Oh! -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ End of INFO-VAX 2008.035 ************************