INFO-VAX Tue, 15 Apr 2008 Volume 2008 : Issue 211 Contents: Re: analyze/audit options to display password Re: analyze/audit options to display password Re: change password on node 1 from node 2 Re: F$PARSE SYNTAX_ONLY validating illegal version numbers Re: F$PARSE SYNTAX_ONLY validating illegal version numbers Re: Longtime VMS system manager/programmer available Re: Longtime VMS system manager/programmer available RE: Longtime VMS system manager/programmer available Re: set audit/listener Special EVA Fiberchannel Drive Pricing - VERY LOW Re: The Minimum You Need to Know About Service Oriented Architecture Re: VMS advertising ! Re: VMS advertising ! Re: VMS advertising ! Re: VMS advertising ! Re: VMS advertising ! Re: VMS advertising ! Re: VMS advertising ! [ANN] Data Plotting Library DISLIN 9.3 ---------------------------------------------------------------------- Date: Tue, 15 Apr 2008 00:32:09 -0700 (PDT) From: Cluster-Karl Subject: Re: analyze/audit options to display password Message-ID: <24e51412-19b7-44da-8b42-aae6a6254955@e39g2000hsf.googlegroups.com> To be precise, the qualifier is named /STATISTICS. /STATUS only worked because if the 4-letter check DCL is performing (/ STATSHIT will also work...) But I would suggest to use the correct qualifier in procedures. regards Kalle ------------------------------ Date: Tue, 15 Apr 2008 12:28:17 -0400 From: "Richard B. Gilbert" Subject: Re: analyze/audit options to display password Message-ID: Cluster-Karl wrote: > To be precise, the qualifier is named /STATISTICS. > /STATUS only worked because if the 4-letter check DCL is performing (/ > STATSHIT will also work...) > But I would suggest to use the correct qualifier in procedures. > > regards Kalle Indeed! I recall having to fix a DCL procedure that broke because it used "SE" for "SET". Easy enough to fix! Right? I figure that the lazy S.O.B. that wrote it cost the company about $30 by saving that single keystroke. ------------------------------ Date: Tue, 15 Apr 2008 09:22:28 +0100 From: Anton Shterenlikht Subject: Re: change password on node 1 from node 2 Message-ID: <20080415082228.GA13366@mech-aslap33.men.bris.ac.uk> On Mon, Apr 14, 2008 at 01:08:41PM -0500, Bob Koehler wrote: > In article <20080414110806.GA23337@mech-aslap33.men.bris.ac.uk>, Anton Shterenlikht writes: > > > > Are you saying a cluster with "multiple UAFs to enable node-specific quotas" > > (section 5.1 Shareable Resources from OpenVMS Cluster Systems, June 2002) > > is unsupported? > > Can't find that document on the HP VMS web site, nor via Google > search. http://h71000.www7.hp.com/doc/731FINAL/4477/4477pro_006.html#startup_ch see the table in section 5.1. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ------------------------------ Date: 15 Apr 2008 09:13:29 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: F$PARSE SYNTAX_ONLY validating illegal version numbers Message-ID: In article <6ce3c1fe-d986-4d78-b4ff-6828fc123080@d45g2000hsc.googlegroups.com>, Rich Jordan writes: > > It turns out I can enter any version number between -99999 (5 digits) > and 999999 (6 digits on the positive side) on a VAX/VMS V7.3 system, > -99999 through 99999 (5 digits on the positive side) on a Alpha VMS > V7.3-2 system and Alpha V8.3 system and F$PARSE will "validate" it. > On a VAX under 6.2 I can go from -99999 to 99999. I wonder why the change without the correct limits. ------------------------------ Date: Tue, 15 Apr 2008 08:12:47 -0700 (PDT) From: AEF Subject: Re: F$PARSE SYNTAX_ONLY validating illegal version numbers Message-ID: On Apr 15, 10:13 am, koeh...@eisner.nospam.encompasserve.org (Bob Koehler) wrote: > In article <6ce3c1fe-d986-4d78-b4ff-6828fc123...@d45g2000hsc.googlegroups.com>, Rich Jordan writes: > > > > > It turns out I can enter any version number between -99999 (5 digits) > > and 999999 (6 digits on the positive side) on a VAX/VMS V7.3 system, > > -99999 through 99999 (5 digits on the positive side) on a Alpha VMS > > V7.3-2 system and Alpha V8.3 system and F$PARSE will "validate" it. > > On a VAX under 6.2 I can go from -99999 to 99999. I wonder why the > change without the correct limits. There's something wrong with your VAX: $ SH SYS/NOPROC OpenVMS V6.2 on node IDS03 15-APR-2008 15:11:40.23 Uptime 441 15:50:33 $ EV F$PARSE(";123456") DISK$DATA1:[FELDMAN.VAX-SESSIONS].;123456 $ EV F$PARSE(";1234567") $ EV F$PARSE(";999999") DISK$DATA1:[FELDMAN.VAX-SESSIONS].;999999 $ EV F$PARSE(";1000000") $ EV F$GETSYI("HW_NAME") VAX 4000-100A $ $ SH SYM EV EV*ALUATE == "WRITE SYS$OUTPUT" $ AEF ------------------------------ Date: Tue, 15 Apr 2008 08:36:50 +0200 From: Michael Kraemer Subject: Re: Longtime VMS system manager/programmer available Message-ID: JF Mezei schrieb: > Today, C programmers are the ones who are old enough to know to make > efficient programs without bloated structures and giganourmous memory > and CPU requirements. It the younger generation who grew up on C++, > perl, php, all the visual microsoft crap who now are so far detached > from the machines that they write bloated inefficient code and they have > no experience in needing to write efficient code since they just buy > more memory and faster CPU when their app needs it. The regular Gnu/Linux crowd isn't much better. ------------------------------ Date: Tue, 15 Apr 2008 08:29:03 -0700 (PDT) From: AEF Subject: Re: Longtime VMS system manager/programmer available Message-ID: <29ec18b7-5277-4330-a8b6-56dbdda85765@s50g2000hsb.googlegroups.com> On Apr 14, 11:14 pm, JF Mezei wrote: > Arne Vajh=F8j wrote: > > And I would say that C is a language where the difference between > > good and bad programmers really show ! > > At the time C was relatively new outside of unix, it was said that > assembler programmers were old enough to remember the absolute need to > write efficient code in a very small memory footprint. > > Today, C programmers are the ones who are old enough to know to make > efficient programs without bloated structures and giganourmous memory > and CPU requirements. It the younger generation who grew up on C++, > perl, php, all the visual microsoft crap who now are so far detached > from the machines that they write bloated inefficient code and they have > no experience in needing to write efficient code since they just buy > more memory and faster CPU when their app needs it. Say what? Since when has this made things run acceptably fast? AEF ------------------------------ Date: Tue, 15 Apr 2008 15:41:15 +0000 From: "Main, Kerry" Subject: RE: Longtime VMS system manager/programmer available Message-ID: > -----Original Message----- > From: AEF [mailto:spamsink2001@yahoo.com] > Sent: April 15, 2008 11:29 AM > To: Info-VAX@Mvb.Saic.Com > Subject: Re: Longtime VMS system manager/programmer available > > On Apr 14, 11:14 pm, JF Mezei wrote: > > Arne Vajh=F8j wrote: > > > And I would say that C is a language where the difference between > > > good and bad programmers really show ! > > > > At the time C was relatively new outside of unix, it was said that > > assembler programmers were old enough to remember the absolute need > to > > write efficient code in a very small memory footprint. > > > > Today, C programmers are the ones who are old enough to know to make > > efficient programs without bloated structures and giganourmous > memory > > and CPU requirements. It the younger generation who grew up on C++, > > perl, php, all the visual microsoft crap who now are so far detached > > from the machines that they write bloated inefficient code and they > have > > no experience in needing to write efficient code since they just buy > > more memory and faster CPU when their app needs it. > > Say what? Since when has this made things run acceptably fast? > > AEF This is especially true these days with the advancement of multi-core cpu's. Applications not written with the concept of threads, SMP, job scheduling etc will have problems with performance no matter how many additional CPU's you throw at the solution. Regards Kerry Main Senior Consultant HP Services Canada Voice: 613-254-8911 Fax: 613-591-4477 kerryDOTmainAThpDOTcom (remove the DOT's and AT) OpenVMS - the secure, multi-site OS that just works. ------------------------------ Date: Tue, 15 Apr 2008 11:21:40 +0200 From: "P. Sture" Subject: Re: set audit/listener Message-ID: In article <47ff4ef0$0$25047$607ed4bc@cv.net>, VAXman- @SendSpamHere.ORG wrote: > In article , "P. Sture" > writes: > >In article > >, > > Pierre wrote: > > > >> I think DCL will be to slow in case of huge flow of audit. I will > >> have to write a program ;) > >> for the language, C examples are fine, but I prefer to write Pascal > > > >Please note that if your program which reads the audit mailbox fails, > >the audit server will carry on writing to the mailbox. > > > >When the audit mailbox becomes full, the audit server will suspend any > >process which creates an audit event. The end result is that the system > >effectively hangs, and you won't be able log in to sort the problem out. > > Yup. I've always considered this to be a rather clumsy interface into > the VMS security audit server. > Agreed, and I have witnessed how it can go wrong. > > >Therefore you need to take special care developing your listener program > >to make sure that is it robust and if it does fail, it restarts or does > >a > > > > $ set audit /nolistener > > > >_before_ the mailbox has chance to fill up. > > There should be a program interface into the VMS security audit server > that would allow a listener to inform that server that it is no longer > interested in what it has to say. Something that could be invoked in > the listener's rundown handling would provide a good way to circumvent > problems which arise when the listener mailbox fills. > The last time I looked into this I poked into some sources which listened to the audit server, hoping for some insight. All I found were a couple of $CREPRC calls which spawned the DCL commands. No good if the audit server mailbox is already full :-( > > >Since you might run into this problem during development, > > > > $ copy audit_mbx NL > > > >can be used to clear out unread audit messages, although of course you > >then need to go to the audit log for the messages you have "thrown away". > > $ COPY MBAnnn: NL: > > can be useful in other cases too. A good little Q&D trick to know. Yes indeed. It can be useful when testing or debugging any application handling mailboxes. -- Paul Sture Sue's OpenVMS bookmarks: http://eisner.encompasserve.org/~sture/ovms-bookmarks.html ------------------------------ Date: Tue, 15 Apr 2008 11:26:56 -0400 From: "David Turner, Island Computers" Subject: Special EVA Fiberchannel Drive Pricing - VERY LOW Message-ID: In stock in large quantity 238921-B21 72GB FC 1" 10K HDD ALL $160 293568-B21 72GB FC 15K 1" HDD ALL $189 293556-B21 146GB FC 10K 1" HDD ALL $219 These are current products We have special pricing on these and do have a large quantity ! Call or email if interested -- David B Turner ============================================= Island Computers US Corp PO Box 86 Tybee GA 31328 Toll Free: 1-877 636 4332 x201, Mobile x251 Email: dturner@islandco.com International: 001 706 993 1787 Fax: 912 786 8505 Web: www.islandco.com ============================================= ------------------------------ Date: Tue, 15 Apr 2008 04:25:45 -0700 (PDT) From: yyyc186 Subject: Re: The Minimum You Need to Know About Service Oriented Architecture Message-ID: <17996f18-0463-425c-bfc5-475d498e5636@m36g2000hse.googlegroups.com> On Apr 14, 1:21 pm, s...@obanion.us wrote: > Might this by available at the upcoming Bootcamp? > The short answer would be no. ------------------------------ Date: Tue, 15 Apr 2008 08:13:57 +0200 From: Michael Kraemer Subject: Re: VMS advertising ! Message-ID: Bill Gunshannon schrieb: > It had no meaning in regards VMS even then. It was a marketing gag. > What about VMS has ever been > "open"? It is built with proprietary code and uses proprietary api's. > The very antithesis of the term "open". You should know better that "open" back then meant "open standards" and not "open source code", the former being much more important than the latter anyway. In the case of VMS that meant adoption of POSIX, AFAIK. However, this didn't mean much except maybe for programmers. In daily operations a decent, well-integrated TCP/IP stack and a revamped filesystem (with less restrictions), allowing seamless cross-mounts to Unix systems for example, would have been much more important. ------------------------------ Date: Tue, 15 Apr 2008 08:32:00 +0200 From: Michael Kraemer Subject: Re: VMS advertising ! Message-ID: Bill Gunshannon schrieb: > Maybe not, but they don't seem to have a problem still using OS/400 or > CICS. Don't see any rebranding there. You're not quite up-to-date here. OS/400 has been renamed more than once, since a couple of days it's simply "i" (before it was called i5/OS for a couple if years). ------------------------------ Date: 15 Apr 2008 08:59:03 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: VMS advertising ! Message-ID: In article <66i6cfF2kj7atU2@mid.individual.net>, billg999@cs.uofs.edu (Bill Gunshannon) writes: > > It had no meaning in regards VMS even then. What about VMS has ever been > "open"? It is built with proprietary code and uses proprietary api's. > The very antithesis of the term "open". VMS has always met the real definition of open: you could see inside. At first ship the source listing fiche shipped with the binaries. Later the source listing fiche were available at low cost. Now they're on CD. For most of those times UNIX source was too expensive for any program I was on, and MicroSoft never shipped source to anyone. But when POSIX compliance was the standard being pushed for the buzzword "open", VMS was POSIX compliant. Nowdays LOinux and Solaris sources are freely accessable and the customer wants "open" platforms running MicroSoft's proprietary code, while MicroSoft struggles to make sure that nobody else's stuff can talk to thiers. ------------------------------ Date: 15 Apr 2008 09:05:47 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: VMS advertising ! Message-ID: In article <66ibd7F2kj7atU7@mid.individual.net>, billg999@cs.uofs.edu (Bill Gunshannon) writes: > > Why? What was wrong with a name like VMS with all the recognition it > had in the IT world? It didn't. VAX was the name with all the recognition. You and I know that VAX is a 32 bit CISC architecture that ran VMS, the real BSD, Ultrix, VAXeln, and now various free UNIX, but management thought VAX was the company that built those computers than ran "VAX". When we got DECsystem 5400 running ULTRIX-MIPS the manager called it "VAX UNIX". When DEC was describing its upcoming Alpha processor writers called them the "new VAXes". And when we installed Alphas running VMS people discussed doing things on "the VAX". ------------------------------ Date: Tue, 15 Apr 2008 08:18:57 -0700 (PDT) From: AEF Subject: Re: VMS advertising ! Message-ID: <3bbc708b-1495-4732-9abf-a17ddb9b6940@59g2000hsb.googlegroups.com> On Apr 15, 10:05 am, koeh...@eisner.nospam.encompasserve.org (Bob Koehler) wrote: > In article <66ibd7F2kj7a...@mid.individual.net>, billg...@cs.uofs.edu (Bill Gunshannon) writes: > > > Why? What was wrong with a name like VMS with all the recognition it > > had in the IT world? > > It didn't. VAX was the name with all the recognition. You and I > know that VAX is a 32 bit CISC architecture that ran VMS, the real > BSD, Ultrix, VAXeln, and now various free UNIX, but management > thought VAX was the company that built those computers than ran "VAX". > > When we got DECsystem 5400 running ULTRIX-MIPS the manager called it > "VAX UNIX". When DEC was describing its upcoming Alpha processor > writers called them the "new VAXes". And when we installed Alphas > running VMS people discussed doing things on "the VAX". Yet more support for how cool VAX is as a name. VAX. And VAX/VMS. How can you beat that for a name? VAX ... VAX/VMS ... AEF ------------------------------ Date: Tue, 15 Apr 2008 08:24:31 -0700 (PDT) From: AEF Subject: Re: VMS advertising ! Message-ID: <70555e0d-bb59-40fb-b679-dd2f42c57e9e@m3g2000hsc.googlegroups.com> On Apr 14, 5:15 pm, hel...@astro.multiCLOTHESvax.de (Phillip Helbig--- remove CLOTHES to reply) wrote: > In article , Bob Willard > > writes: > > > While it may or may no matter for VMS, at least one company protects > > > its old names: Exxon Mobil. Before the merger I distinctly remember > > > seeing tiny Esso labels on their gas pumps. (And post-merger we still > > > see separate Exxon and Mobil gas stations.) But I admit this may be > > > because it's still sold as Esso outside the U.S. But I'd think they'd > > Yes, it's still Esso in Germany. I don't know why. The oil companies > were among the first multinational corporations, and their names had > little "local colour" or any other reason to have different ones in > different countries. There was no reason to change it in Europe as it was Esso throughout all of Europe. For reasons unknown to me, Esso had to sell as Humble in some parts of the U.S., and Enco in others. Esso could only be used in the remaining parts of the U.S. So they wanted one single name to advertise nationally under. And I think ENCO meant something bad in Japanese, and I don't know what was wrong with Humble). So after a great computer-aided search to be sure the new name offended no one and met certain characteristics given by management (things like starting with an E, and perhaps having two syllables, and what not), Exxon somehow emerged. It was primarily for the U.S. I guess they're happy with it being Esso almost everywhere else. Besides, you'd have to spend money to change all the signs and labels! Anyway, there's obviously more to the story. Maybe wikipedia has something about it, or even Exxon's Web site. But this should help answer your question. AEF [...] ------------------------------ Date: 15 Apr 08 13:40:19 EDT From: cook@wvnvms.wvnet.edu (George Cook) Subject: Re: VMS advertising ! Message-ID: In article <70555e0d-bb59-40fb-b679-dd2f42c57e9e@m3g2000hsc.googlegroups.com>, AEF writes: > On Apr 14, 5:15 pm, hel...@astro.multiCLOTHESvax.de (Phillip Helbig--- > remove CLOTHES to reply) wrote: >> In article , Bob Willard >> >> writes: >> > > While it may or may no matter for VMS, at least one company protects >> > > its old names: Exxon Mobil. Before the merger I distinctly remember >> > > seeing tiny Esso labels on their gas pumps. (And post-merger we still >> > > see separate Exxon and Mobil gas stations.) But I admit this may be >> > > because it's still sold as Esso outside the U.S. But I'd think they'd >> >> Yes, it's still Esso in Germany. I don't know why. The oil companies >> were among the first multinational corporations, and their names had >> little "local colour" or any other reason to have different ones in >> different countries. > > There was no reason to change it in Europe as it was Esso throughout > all of Europe. For reasons unknown to me, Esso had to sell as Humble > in some parts of the U.S., and Enco in others. Esso could only be used > in the remaining parts of the U.S. So they wanted one single name to > advertise nationally under. And I think ENCO meant something bad in > Japanese, and I don't know what was wrong with Humble). So after a > great computer-aided search to be sure the new name offended no one > and met certain characteristics given by management (things like > starting with an E, and perhaps having two syllables, and what not), > Exxon somehow emerged. It was primarily for the U.S. I guess they're > happy with it being Esso almost everywhere else. Besides, you'd have > to spend money to change all the signs and labels! Anyway, there's > obviously more to the story. Maybe wikipedia has something about it, > or even Exxon's Web site. But this should help answer your question. See http://en.wikipedia.org/wiki/Standard_oil#Successor_companies and http://en.wikipedia.org/wiki/Esso Esso = Eastern States Standard Oil (aka Standard Oil of New Jersey) Standard Oil of New Jersey (aka Exxon) could not use Esso in states where other Standard Oil companies held the trademark rights to 'Standard'. Chevron (aka Standard Oil of California), Amoco (Standard Oil of Indiana), Sohio (Standard Oil of Ohio), Mobil (Standard Oil of New York), Conoco, Pennzoil and Marathon were all once part of Standard Oil. George Cook WVNET ------------------------------ Date: Tue, 15 Apr 2008 10:23:57 +0200 From: Helmut Michels Subject: [ANN] Data Plotting Library DISLIN 9.3 Message-ID: Dear VMS users, I am pleased to announce version 9.3 of the data plotting software DISLIN. DISLIN is a high-level and easy to use plotting library for displaying data as curves, bar graphs, pie charts, 3D-colour plots, surfaces, contours and maps. Several output formats are supported such as X11, VGA, PostScript, PDF, CGM, WMF, HPGL, TIFF, GIF, PNG, BMP and SVG. The software is available for the most C, Fortran 77 and Fortran 90/95 compilers. Plotting extensions for the interpreting languages Perl, Python and Java are also supported. DISLIN distributions and manuals in PDF, PostScript and HTML format are available from the DISLIN home page http://www.dislin.de and via FTP from the server ftp://ftp.gwdg.de/pub/grafik/dislin All DISLIN distributions are free for non-commercial use. Licenses for commercial use are available from the site http://www.dislin.de. ------------------- Helmut Michels Max Planck Institute for Solar System Research Phone: +49 5556 979-334 Max-Planck-Str. 2 Fax : +49 5556 979-240 D-37191 Katlenburg-Lindau Mail : michels@mps.mpg.de ------------------------------ End of INFO-VAX 2008.211 ************************