INFO-VAX Sun, 24 Feb 2008 Volume 2008 : Issue 110 Contents: Re: ANAL/DISK output, how to determine file Re: laboratory subroutines Question about DFU Re: Question about DFU Re: Question about DFU Re: Samba and text files Re: VMS 5.0 - VMS 5.5 RE: VMS 5.0 - VMS 5.5 RE: VMS 5.0 - VMS 5.5 Re: VMS 5.0 - VMS 5.5 ---------------------------------------------------------------------- Date: Sun, 24 Feb 2008 10:55:06 +0100 From: Jur van der Burg <"vdburg at hotmail dot com"> Subject: Re: ANAL/DISK output, how to determine file Message-ID: <47c13efb$0$14347$e4fe514c@news.xs4all.nl> Well, the original author was Ton Dorland, and since Ton does not do VMS anymore I'm in posession of the sources and doing the maintenance. http://www.digiater.nl/dfu Jur van der Burg. Richard B. Gilbert wrote: > VAXman- wrote: >> In article >> , >> IanMiller writes: >> >>> I usually use DFU >>> >>> DFU SEARCH/FID=(25695,87,0) devname >> >> >> $ DFU >> %DCL-W-IVVERB, unrecognized command verb - check validity and spelling >> \DFU\ >> > > DFU is a freeware utility. It does not, AFAIK, ship with VMS. ISTR the > author is Ton Dorfman. It can be very useful if you need what it does. > > It was a lifesaver once, years ago, when some moron managed to create > 7,000 files in a directory. Cleaning that one up was a chore that > occupied a couple of days and would have taken far longer without DFU to > do a directory compress. > ------------------------------ Date: Sun, 24 Feb 2008 06:40:52 -0800 (PST) From: RiverRoadRambler@gmail.com Subject: Re: laboratory subroutines Message-ID: On Feb 23, 12:18=A0pm, "John Wallace" wrote: > wrote in message > > news:143fc150-ef28-4663-aae8-468bcbbc02c8@p43g2000hsc.googlegroups.com... > > > I need some info on a subroutine from some VAX software > > =A0 =A0the different names were VAXLAB, LABSTAR, Dec laboratory > > subroutines DEC Real time integrator > > > =A0 =A0In some software I called a signal processing filter =A0 -- =A0LS= P > > $FILTER_NONREC > > > =A0 =A0 The documentation as to what the filter code was has disappeared= > > from our lab over the years. =A0Does anyone have the documentation > > DECrti was a fine product, but like many perfectly decent DEC products, it= > was almost invisible in the market. VAXlab predates it but had similar > challenges. > > Both come from an era where DEC documentation mostly came either on paper = or > CD. A set of consolidated documentation CDs from the relevant era may > contain the information you need, but there were exceptions which weren't = on > CD. Right now I can't remember the exact vintage we're looking for, perhap= s > someone else can. I can't even find the SPD online otherwise the relevant > era would be easily identifiable. It must be post 1988, based on where I w= as > working at the time; DECrti was probably early 1990s, but I can't currentl= y > be more specific than that. (A quick search of newsgroups confirms this bu= t > doesn't help be more specific). > > As per Hein's suggestion not long ago in this ng, you can use the online > docs athttp://www.sysworks.com.au/odl.html- for each issue of VAX docs > online there, look up the Online Documentation Library Contents and search= > it for your choice of VAXlab or DECrti (but I'm not 100% sure the > VAXlab/DECrti docs would be on those CDs). Sysworks collection in the > relevant era is far from complete, anyone interested in helping sysworks > fill their gaps ? > > I'm away from my realtime resources for a couple of days, and they don't > include full VAXlab/DECrti docs anyways, but hopefully something will turn= > up for you soon. > > Today's "equivalent" product would probably be NI's Labview, which is just= > as "proprietary"/closed as VAXlab/DECrti ever was, and for those doing rea= l > realtime, or for those who care about data integrity or security, has the > nontrivial snag of being Windows-based (or Linux if you prefer). But, like= > Windows, Labview has huge market visibility and support. > > Combine this with your need to reverse engineer some VAX assembly you post= ed > elsewhere, and it sounds like you have "interesting times ahead". > > Best of luck, > John I have two people who have offered to take a look at converting the vax macro code--so hopefully that part of my updating of an old system will proceed. In the mid 1980s I wrote some software to process signals coming from the digestive system using a PDP 11 23+ When the Microvax II came out with a VAXLAB version (software package to run Q-Bus instrumentation and lots of scientific routines), I moved the programs from pdp to VAX and extensively used the DECWINDOWS graphing routines, signal processing routines etc, but moved the data acquisition to pcs. Dec gave up on the VAXLAB stuff before Compaq bought it out. They also never ported the software to run on the Alpha (the "real time routines"). Anyway-- the analysis has been running on a VAXSTATION 90a since 1994 or so and finally the users decided to have it replaced with a pc version. I have been retired, and so am just coordinating some efforts to duplicate the old analysis. About the only parts that have to be exactly duplicated are the macro peak finding code and the filters. They were sort of blackbox routines I called. I have the source for the peaks, but no info for the filters--which I believe are pretty much off the shelf techniques. Sort of a stroll down memory lane, with a little pride that something I originally wrote in 1985 on a pdp is still useful 24 years later! Russ Hanson (I worked for a huge medical organization in Rochester MN for 25 years--and this is some research stuff we did). ------------------------------ Date: Sun, 24 Feb 2008 12:31:44 -0500 From: JF Mezei Subject: Question about DFU Message-ID: <47c1aa2d$0$1461$c3e8da3@news.astraweb.com> Is there a reason why DFU was never included with VMS ? Seems to me like a key utility that should have been an official part of VMS. I can understand its current status, along with the LDRIVER being maintained by volunteers as freeware. (and many thanks are owed to Jur for that). But before all the staff cuts and downsizing, was there some technical/political/whatever reason that prevented DFU from being included as part of VMS OS distribution ? ------------------------------ Date: Sun, 24 Feb 2008 12:41:10 -0500 From: "Richard B. Gilbert" Subject: Re: Question about DFU Message-ID: <47C1AC36.3030108@comcast.net> JF Mezei wrote: > Is there a reason why DFU was never included with VMS ? > > Seems to me like a key utility that should have been an official part of > VMS. > > I can understand its current status, along with the LDRIVER being > maintained by volunteers as freeware. (and many thanks are owed to Jur > for that). > > But before all the staff cuts and downsizing, was there some > technical/political/whatever reason that prevented DFU from being > included as part of VMS OS distribution ? How about the fact that it was third party software and DEC/Compaq/HP did not and do not own the rights to it? ------------------------------ Date: Sun, 24 Feb 2008 12:48:00 -0500 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= Subject: Re: Question about DFU Message-ID: <47c1adcd$0$90266$14726298@news.sunsite.dk> JF Mezei wrote: > Is there a reason why DFU was never included with VMS ? > > Seems to me like a key utility that should have been an official part of > VMS. > > I can understand its current status, along with the LDRIVER being > maintained by volunteers as freeware. (and many thanks are owed to Jur > for that). > > But before all the staff cuts and downsizing, was there some > technical/political/whatever reason that prevented DFU from being > included as part of VMS OS distribution ? It was never VMS policy to include tons of stuff with the base OS. And if it was included it would need to be supported. Some bean counter ask the questions: how much extra sale will we make ? what will it cost to support ? If the answers is 0 and >0, then it will not happen. Compare with a Linux distro where you will get thousands and thousands of packages. Either they do not have bean counters or they have bean counters that count differently. Arne ------------------------------ Date: Sun, 24 Feb 2008 06:47:29 -0500 From: "PEN" Subject: Re: Samba and text files Message-ID: Hi, "bradhamilton" wrote in message news:47C0E427.8020500@comcast.net... > Michael Moroney wrote: >> "Gorazd Kikelj" writes: >> >> >>> "Michael Moroney" wrote in message >>> news:fpn019$m28$1@pcls4.std.com... >> >>>>> vfs objects = varvfc >>>> Thanks, Paul, but quickly inserting that line in the [global] area of >>>> smb.conf and restarting samba had no effect. I'll study the >>>> documentation >>>> on that later. >> >>> It's per share parameter. Just put it into share definition. >> >> Still can't convince it to work, on two different systems. >> >> [global] >> server string = Samba %v running on %h (OpenVMS) >> netbios name = %h >> security = user >> passdb backend = tdbsam >> domain master = yes >> guest account = SAMBA$GUEST >> domain logons = Yes >> log file = /samba$root/var/log_%h.%m >> create mode = 0755 >> load printers = no >> printing = OpenVMS >> vfs objects = varvfc >> >> [homes] >> comment = Home Directories >> browseable = no >> read only = no >> create mode = 0750 >> vfs objects = varvfc >> >> [test1] >> comment = test folder >> path = /samba$root/tmp >> read only = No >> guest OK = Yes >> vfs objects = varvfc >> >> > > Googling for vfs object (notice the singular) claims that vfs object > should reside in the [public] area; however, I think that the singular for > is what's important. Plural or singular is allowed (see the smb.conf man page). Michael, please post the output from $ DIR/FULL for one of the affected files... Thanks, Paul ------------------------------ Date: Sat, 23 Feb 2008 23:33:06 -0800 (PST) From: Sue Subject: Re: VMS 5.0 - VMS 5.5 Message-ID: <6f4195de-fb98-4138-bffd-ec33f260e8d7@72g2000hsu.googlegroups.com> On Feb 23, 12:03=A0pm, "Richard B. Gilbert" wrote: > Arne Vajh=F8j wrote: > > Richard B. Gilbert wrote: > > >> Hein RMS van den Heuvel wrote: > > >>> Just google this newsgroup for 'orange wall' and you'll stumble in to > >>> a 1999 JF M topic "Colour of DEC documentation Options" as well as a > >>> recent offering by Tom Garcia "Free: VMS orange wall" > > >> Orange????? =A0 Officially it was "Chinese Red" > > > I have never heard about "chinese red wall". > > > Arne > > No, you wouldn't. =A0Nobody called it that outside of a few "suits" at > DEC. =A0To EVERYONE ELSE it was the "orange wall". As a DEC person it sure looked orange to me in spite of the official color, but then again I missed the dot changes for ages. Ivan, just so you are aware we do a youth scholarship for the Boot Camp in May and some of the Partners do a scholarship which in some cases cover transportation. If your interested, this location and www.openvms.org is a good place to keep informed. Warm Regards, Sue ------------------------------ Date: Sun, 24 Feb 2008 13:57:35 +0000 From: "Main, Kerry" Subject: RE: VMS 5.0 - VMS 5.5 Message-ID: > From: Sue [mailto:susan_skonetski@hotmail.com] > Sent: February 24, 2008 2:33 AM > To: Info-VAX@Mvb.Saic.Com > Subject: Re: VMS 5.0 - VMS 5.5 > > On Feb 23, 12:03 pm, "Richard B. Gilbert" > wrote: > > Arne Vajh=F8j wrote: > > > Richard B. Gilbert wrote: > > > > >> Hein RMS van den Heuvel wrote: > > > > >>> Just google this newsgroup for 'orange wall' and you'll stumble > in to > > >>> a 1999 JF M topic "Colour of DEC documentation Options" as well > as a > > >>> recent offering by Tom Garcia "Free: VMS orange wall" > > > > >> Orange????? Officially it was "Chinese Red" > > > > > I have never heard about "chinese red wall". > > > > > Arne > > > > No, you wouldn't. Nobody called it that outside of a few "suits" at > > DEC. To EVERYONE ELSE it was the "orange wall". > > As a DEC person it sure looked orange to me in spite of the official > color, but then again I missed the dot changes for ages. > > Ivan, just so you are aware we do a youth scholarship for the Boot > Camp in May and some of the Partners do a scholarship which in some > cases cover transportation. If your interested, this location and > www.openvms.org is a good place to keep informed. > > Warm Regards, > Sue For future reference - some additional OpenVMS links that may be of interest: http://h71000.www7.hp.com/openvms/os/openvms-release-history.html (OpenVMS release history) http://research.microsoft.com/users/gbell/Digital/timeline/1978.htm (click on timeline for different years) http://h71000.www7.hp.com/openvms/openvms_supportchart.html (Support version history) http://h71000.www7.hp.com/openvms/hw_supportchart.html (HW and min version support) http://h71000.www7.hp.com/doc/archived.html (Archived documentation. Btw, the Building Dependable Systems guide is just as prevalent today as it was back then.) 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: 24 Feb 2008 14:18:43 GMT From: VAXman- @SendSpamHere.ORG Subject: RE: VMS 5.0 - VMS 5.5 Message-ID: <47c17cc3$0$8077$607ed4bc@cv.net> In article , "Main, Kerry" writes: >{...snip...} >http://h71000.www7.hp.com/doc/archived.html >(Archived documentation. Btw, the Building Dependable Systems guide is >just as prevalent today as it was back then.) It seems to me that today many software producers, software products and OS manufacturers have archived the idea of 'Building Dependable Systems'. -- 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: Sun, 24 Feb 2008 08:59:22 -0800 (PST) From: Jerry Eckert Subject: Re: VMS 5.0 - VMS 5.5 Message-ID: On Feb 23, 4:29 am, Bob Gezelter wrote: > > My memory may be not completely accurate, but my offhand recollection > is that full, shared file clustering was available at 5.0 (4.7 if I > recall, allowed the use of shared HSC50s, but not writeable volume. > You're off by a version. Read-only sharing was available in V3.7; read/write sharing was available in V4.0. One of the major additions in V5.0 was SMP support; prior to that the multiprocessor support was asymmetric, with the primary CPU handling the I/O and interrupts. Jerry ------------------------------ End of INFO-VAX 2008.110 ************************