INFO-VAX Tue, 26 Feb 2008 Volume 2008 : Issue 113 Contents: Re: ANAL/DISK output, how to determine file Re: anal/disk/shadow weirdnes Re: anal/disk/shadow weirdnes Re: anal/disk/shadow weirdnes Re: anal/disk/shadow weirdnes Re: anal/disk/shadow weirdnes Re: Documentation Colors (was: Re: VMS 5.0 - VMS 5.5) Re: Errors during shadow set merge how to use ^UP^/ from DCL ? Re: how to use ^UP^/ from DCL ? Re: how to use ^UP^/ from DCL ? RE: how to use ^UP^/ from DCL ? Re: Question about DFU Re: Wollogong TCP/IP stack Re: Wollogong TCP/IP stack Re: Wollogong TCP/IP stack Re: Wollogong TCP/IP stack Re: Wollogong TCP/IP stack ---------------------------------------------------------------------- Date: 25 Feb 2008 23:12:24 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: ANAL/DISK output, how to determine file Message-ID: <47c34b58$0$8063$607ed4bc@cv.net> In article , tadamsmar writes: >On Feb 22, 4:58=A0pm, "Richard B. Gilbert" >wrote: >> VAXman- wrote: >> > In article s.com>, IanMiller writes: >> >> >>I usually use DFU >> >> >>DFU SEARCH/FID=3D(25695,87,0) devname >> >> > $ DFU >> > %DCL-W-IVVERB, unrecognized command verb - check validity and spelling >> > =A0\DFU\ >> >> DFU is a freeware utility. =A0It does not, AFAIK, ship with VMS. > >It came on pair of freeware CD's with 7.3.2 I know full well about DFU. My point was that it is not a standard part of VMS distribution. The OP was told to enter the command $DFU SEARCH/FID=3D(25695,87,0) devname without pointing out first that DFU needed to be installed. -- 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: Mon, 25 Feb 2008 11:15:18 -0800 (PST) From: Volker Halle Subject: Re: anal/disk/shadow weirdnes Message-ID: <87e22c1f-ca1a-4fb3-95be-1395b828a415@e23g2000prf.googlegroups.com> ANAL/DISK/SHADOW Examines the entire contents of a shadow set or a specified range of blocks in a shadow set for discrepancies. ANAL/DISK/READ only reads blocks allocated to files. So the bad blocks are NOT in a file. Volker. ------------------------------ Date: Mon, 25 Feb 2008 19:25:07 GMT From: John Santos Subject: Re: anal/disk/shadow weirdnes Message-ID: In article <87e22c1f-ca1a-4fb3-95be-1395b828a415 @e23g2000prf.googlegroups.com>, volker_halle@hotmail.com says... > ANAL/DISK/SHADOW > > Examines the entire contents of a shadow set or a specified range > of blocks in a shadow set for discrepancies. > > ANAL/DISK/READ only reads blocks allocated to files. > > So the bad blocks are NOT in a file. > > Volker. > $ anal/disk/shad/blocks=file_system apparently does what the OP claims ana/disk/shadow is supposed to do. (I've never had occasion to use this.) -- John ------------------------------ Date: Mon, 25 Feb 2008 13:29:01 -0800 (PST) From: tadamsmar Subject: Re: anal/disk/shadow weirdnes Message-ID: On Feb 25, 2:15=A0pm, Volker Halle wrote: > ANAL/DISK/SHADOW > > Examines the entire contents of a shadow set or a specified range > =A0 =A0 =A0 =A0 =A0of blocks in a shadow set for discrepancies. > > ANAL/DISK/READ only reads blocks allocated to files. > > So the bad blocks are NOT in a file. > > Volker. But HELP says /BLOCKS=3DFILE_SYSTEM is the default. Check HELP. I am running 7.3.2 ------------------------------ Date: Mon, 25 Feb 2008 13:30:21 -0800 (PST) From: tadamsmar Subject: Re: anal/disk/shadow weirdnes Message-ID: <2bf2c280-5ed6-47e4-8855-ed0065a6bbd0@q78g2000hsh.googlegroups.com> On Feb 25, 2:25=A0pm, John Santos wrote: > In article <87e22c1f-ca1a-4fb3-95be-1395b828a415 > @e23g2000prf.googlegroups.com>, volker_ha...@hotmail.com says... > > > ANAL/DISK/SHADOW > > > Examines the entire contents of a shadow set or a specified range > > =A0 =A0 =A0 =A0 =A0of blocks in a shadow set for discrepancies. > > > ANAL/DISK/READ only reads blocks allocated to files. > > > So the bad blocks are NOT in a file. > > > Volker. > > $ anal/disk/shad/blocks=3Dfile_system > > apparently does what the OP claims ana/disk/shadow is supposed > to do. > > (I've never had occasion to use this.) > > -- > John What do you mean by OP. Blocks=3Dfile is the default, according to help. But I will try it. ------------------------------ Date: Mon, 25 Feb 2008 22:29:09 GMT From: John Santos Subject: Re: anal/disk/shadow weirdnes Message-ID: In article <2bf2c280-5ed6-47e4-8855-ed0065a6bbd0 @q78g2000hsh.googlegroups.com>, tadamsmar@yahoo.com says... > On Feb 25, 2:25 pm, John Santos wrote: > > In article <87e22c1f-ca1a-4fb3-95be-1395b828a415 > > @e23g2000prf.googlegroups.com>, volker_ha...@hotmail.com says... > > > > > ANAL/DISK/SHADOW > > > > > Examines the entire contents of a shadow set or a specified range > > >          of blocks in a shadow set for discrepancies. > > > > > ANAL/DISK/READ only reads blocks allocated to files. > > > > > So the bad blocks are NOT in a file. > > > > > Volker. > > > > $ anal/disk/shad/blocks=file_system > > > > apparently does what the OP claims ana/disk/shadow is supposed > > to do. > > > > (I've never had occasion to use this.) > > > > -- > > John > > What do you mean by OP. > OP == Original Poster, I.e. You! > Blocks=file is the default, according to help. > I don't see anywhere where it says it's the default on either Alpha V7.3-2 or on Alpha V8.3. Maybe it used to say that, and was wrong, and an ECO fixed the help text? ... Oh, wait, under FILE_SYSTEM under /BLOCKS, it does say: This is the default. But I think that only applies if you say anal/disk/shadow/blocks without specifying either =all or =file_system... But /BLOCKS *is not* the default for anal/disk/shadow, so it doesn't matter what the default style of /blocks is if you don't specify it at all. In my experience, it (without the /blocks) has always compared everything. > But I will try it. > -- John ------------------------------ Date: Mon, 25 Feb 2008 16:37:56 -0800 From: Malcolm Dunnett Subject: Re: Documentation Colors (was: Re: VMS 5.0 - VMS 5.5) Message-ID: <47c35f65$1@flight> Bill Gunshannon wrote: >> The RSTS documentation I remember came with the books stapled >> together, with a "sunset" coloured cover that had a hole in it that you >> could read the title through. > > Yup. I have Version 7 in Blue and Version 9 in Orange. Ah, We only got as far as RSTS 6B before we got rid of the PDP-11. Does anyone still run RSTS? ------------------------------ Date: Mon, 25 Feb 2008 15:32:47 -0500 From: Pete Subject: Re: Errors during shadow set merge Message-ID: You haven't offered much in the way of configuration around SCSI devices. I guess I would start by verifing a valid config. IE: all internal SCSI devices external or a mix. Where does termination happen on the system and is it right are the devices models supported on the same bus... It really sounds like a configuration/termination issue may have led to some potential file system issues. Pete ------------------------------ Date: Mon, 25 Feb 2008 13:37:04 -0800 (PST) From: Pierre Subject: how to use ^UP^/ from DCL ? Message-ID: <7bff3774-3109-441f-91fa-3b12229e6689@o77g2000hsf.googlegroups.com> hi, I can not mak ^UP^/ syntax work :( I haveOpenVMS 8.3 and GNV 2.1 $ sh dev DISK$OVMSX4 Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt TLSAX4$DKC0: Mounted 0 OVMSX4 912690 424 1 $ dir TLSAX4$DKC0:[system.test]foobar.txt Directory TLSAX4$DKC0:[SYSTEM.TEST] foobar.txt;1 Total of 1 file. $ mnt DISK$OVMSX4:[SYSTEM]TEST.DIR;1 on /mnt/TEST $ bash -c "cat /mnt/TEST/foobar.txt" foobar! $ type TLSAX4$DKC0:[system.test]foobar.txt foobar! $ type "^UP^/mnt/TEST/foobar.txt" %TYPE-W-SEARCHFAIL, error searching for "^UP^/mnt/TEST/foobar.txt" -RMS-E-FNF, file not found $ dir "^UP^/mnt/TEST/foobar.txt" %DIRECT-W-NOFILES, no files found where am I wrong with the ^UP^/ syntax ?... TIA, Pierre. ------------------------------ Date: Mon, 25 Feb 2008 14:00:19 -0800 (PST) From: Bob Gezelter Subject: Re: how to use ^UP^/ from DCL ? Message-ID: <1fab7d6e-73dc-4551-ad12-87ccea25d9fb@n58g2000hsf.googlegroups.com> On Feb 25, 4:37 pm, Pierre wrote: > hi, > > I can not mak ^UP^/ syntax work :( > I haveOpenVMS 8.3 and GNV 2.1 > > $ sh dev DISK$OVMSX4 > > Device Device Error Volume Free > Trans Mnt > Name Status Count Label Blocks > Count Cnt > TLSAX4$DKC0: Mounted 0 OVMSX4 > 912690 424 1 > > $ dir TLSAX4$DKC0:[system.test]foobar.txt > > Directory TLSAX4$DKC0:[SYSTEM.TEST] > > foobar.txt;1 > > Total of 1 file. > > $ mnt > DISK$OVMSX4:[SYSTEM]TEST.DIR;1 on /mnt/TEST > > $ bash -c "cat /mnt/TEST/foobar.txt" > foobar! > > $ type TLSAX4$DKC0:[system.test]foobar.txt > foobar! > > $ type "^UP^/mnt/TEST/foobar.txt" > %TYPE-W-SEARCHFAIL, error searching for "^UP^/mnt/TEST/foobar.txt" > -RMS-E-FNF, file not found > > $ dir "^UP^/mnt/TEST/foobar.txt" > %DIRECT-W-NOFILES, no files found > > where am I wrong with the ^UP^/ syntax ?... > > TIA, > Pierre. Pierre, Perhaps because the presence of GNV does not add *IX style filenames to regular DCL (although apparently bash, probably meaning the C run time) accepts either syntax. The syntax in conventional OpenVMS file naming, to a parent directory would be [-], two levels up, [-.-], up one and down one [-.xxx]. - Bob Gezelter, http://www.rlgsc.com ------------------------------ Date: Mon, 25 Feb 2008 14:27:03 -0800 (PST) From: Pierre Subject: Re: how to use ^UP^/ from DCL ? Message-ID: <2abd8fc3-8d3a-43a8-987a-ddd8cb203b4a@z17g2000hsg.googlegroups.com> On Feb 25, 11:00 pm, Bob Gezelter wrote: > On Feb 25, 4:37 pm, Pierre wrote: > > > > > hi, > > > I can not mak ^UP^/ syntax work :( > > I haveOpenVMS 8.3 and GNV 2.1 > > > $ sh dev DISK$OVMSX4 > > > Device Device Error Volume Free > > Trans Mnt > > Name Status Count Label Blocks > > Count Cnt > > TLSAX4$DKC0: Mounted 0 OVMSX4 > > 912690 424 1 > > > $ dir TLSAX4$DKC0:[system.test]foobar.txt > > > Directory TLSAX4$DKC0:[SYSTEM.TEST] > > > foobar.txt;1 > > > Total of 1 file. > > > $ mnt > > DISK$OVMSX4:[SYSTEM]TEST.DIR;1 on /mnt/TEST > > > $ bash -c "cat /mnt/TEST/foobar.txt" > > foobar! > > > $ type TLSAX4$DKC0:[system.test]foobar.txt > > foobar! > > > $ type "^UP^/mnt/TEST/foobar.txt" > > %TYPE-W-SEARCHFAIL, error searching for "^UP^/mnt/TEST/foobar.txt" > > -RMS-E-FNF, file not found > > > $ dir "^UP^/mnt/TEST/foobar.txt" > > %DIRECT-W-NOFILES, no files found > > > where am I wrong with the ^UP^/ syntax ?... > > > TIA, > > Pierre. > > Pierre, > > Perhaps because the presence of GNV does not add *IX style filenames > to regular DCL (although apparently bash, probably meaning the C run > time) accepts either syntax. > > The syntax in conventional OpenVMS file naming, to a parent directory > would be [-], two levels up, [-.-], up one and down one [-.xxx]. Bob, according to chapter 12 (Symbolic Links and POSIX Pathname Support) of HP C v7.3 Run-Time Library Reference Manual for OpenVMS Systems, especially 12.4 RMS Interface (http://h71000.www7.hp.com/doc/83final/ 5763/5763pro_022.html#rms_interface), ^UP^ is the supported DCL syntax for the pseudo file system root used by GNV. at least, as far as I understant the doc. I tried with all the documented value for DECC $POSIX_COMPLIANT_PATHNAMES (http://h71000.www7.hp.com/doc/83final/ 5763/5763pro_022.html) with no change in the result :( > - Bob Gezelter,http://www.rlgsc.com Pierre ------------------------------ Date: Mon, 25 Feb 2008 21:31:29 -0500 From: "Peter Weaver" Subject: RE: how to use ^UP^/ from DCL ? Message-ID: <032f01c8781f$b18ebc60$2802a8c0@CHARONLAP> >... > $ mnt > DISK$OVMSX4:[SYSTEM]TEST.DIR;1 on /mnt/TEST > > $ bash -c "cat /mnt/TEST/foobar.txt" > foobar! > > $ type TLSAX4$DKC0:[system.test]foobar.txt > foobar! > > $ type "^UP^/mnt/TEST/foobar.txt" > %TYPE-W-SEARCHFAIL, error searching for "^UP^/mnt/TEST/foobar.txt" > -RMS-E-FNF, file not found > > $ dir "^UP^/mnt/TEST/foobar.txt" > %DIRECT-W-NOFILES, no files found > > where am I wrong with the ^UP^/ syntax ?... If the command SHOW ROOT gives you the [MNT] directory then I think you need $ type "^UP^/TEST/foobar.txt" In my case SHOW ROOT points to [0000000] on my SYS$SYSDEVICE so "^UP^/vms$common/sysmgr/login.com" is the same as SYS$SYSDEVICE:[VMS$COMMON.SYSMGR]LOGIN.COM. One thing that can help you track down where ^UP^ is pointing to is to try $ DIR /FULL "^UP^/*" That will give you the first file in the directory ^UP^ points to, you can use the FID to figure out where the file you found is. Peter Weaver www.weaverconsulting.ca CHARON-VAX CHARON-AXP DataStream Reflection PreciseMail HP Commercial Hardware ------------------------------ Date: Mon, 25 Feb 2008 12:53:56 -0800 From: Fred Bach Subject: Re: Question about DFU Message-ID: Does this mean that DFU for OpenVMS is available from you? Are you currently supporting it? What would be your costs? Thanks.... . fred bach music at triumf dot c a Jur van der Burg wrote: > I was a member of VMS engineering when there was talk about including DFU > in VMS. I had setup everything ready to go to have it included in the VMS > build procedures, but management higher up the chain did not give the final > word to do so, so we never included it. There was never a technical reason, > it was purely political. Since I left HP I'm treating it as a private > project. > > Jur. > > > 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 ? ------------------------------ Date: Mon, 25 Feb 2008 19:50:11 GMT From: John Santos Subject: Re: Wollogong TCP/IP stack Message-ID: In article <47C2C324.7124.6DF980@infovax.stanq.com>, infovax@stanq.com says... > I have a client running the very-ancient Wollogong IP stack. While it works just fine, > they'd like to add DCPS for printing, but DCPS doesn't support that stack. > > I vaguely remember that Wollogong became TCPware. Is that correct? No. When the owners of Wollongong got out of the business, they made a deal with Process Software that you could get a license for either TCPware or Multinet (your choice) by buying one year of support for the chosen software, I.e. a free license transfer. But the stack was completely different from either Process product. > > Adding to the "fun" is that they may have written some programs to that stack, so those > need to be migrated... > I don't remember if Wollongong ever supported UCX emulation (UCX compatible BG: device driver.) I think at one time NETLIB supported it, so you could write stack-independent code that way. You might need a very old version of NETLIB, though. > --Stan Quayle > Quayle Consulting Inc. -- John ------------------------------ Date: Mon, 25 Feb 2008 22:20:25 +0100 From: "Martin Vorlaender" Subject: Re: Wollogong TCP/IP stack Message-ID: Stanley F. Quayle wrote: > I have a client running the very-ancient Wollogong IP stack. While it works just fine, > they'd like to add DCPS for printing, but DCPS doesn't support that stack. > > I vaguely remember that Wollogong became TCPware. Is that correct? Nope. It went to Attachmate, and it was dopped there, AFAIK. > Adding to the "fun" is that they may have written some programs to that stack, so those > need to be migrated... cu, Martin -- One OS to rule them all | Martin Vorlaender | OpenVMS rules! One OS to find them | work: mv@pdv-systeme.de One OS to bring them all | http://vms.pdv-systeme.de/users/martinv/ And in the Darkness bind them.| home: martin.vorlaender@t-online.de ------------------------------ Date: 25 Feb 08 16:44:42 EST From: cook@wvnvms.wvnet.edu (George Cook) Subject: Re: Wollogong TCP/IP stack Message-ID: In article , John Santos writes: > In article <47C2C324.7124.6DF980@infovax.stanq.com>, infovax@stanq.com > says... >> I have a client running the very-ancient Wollogong IP stack. While it works just fine, >> they'd like to add DCPS for printing, but DCPS doesn't support that stack. >> >> I vaguely remember that Wollogong became TCPware. Is that correct? > > No. When the owners of Wollongong got out of the business, they made a > deal with Process Software that you could get a license for either > TCPware or Multinet (your choice) by buying one year of support for > the chosen software, I.e. a free license transfer. But the stack was > completely different from either Process product. > >> >> Adding to the "fun" is that they may have written some programs to that stack, so those >> need to be migrated... >> > > I don't remember if Wollongong ever supported UCX emulation (UCX > compatible BG: device driver.) I think at one time NETLIB supported > it, so you could write stack-independent code that way. You might > need a very old version of NETLIB, though. I never used Wollongong Pathway, but I believe it did support UCX emulation (the Mosaic build procedure supports building against its UCX emulation library). If the release they have supports it, the emulation object library is TWG$ETC:[000000]UW$IPC.OLB. George Cook WVNET ------------------------------ Date: 25 Feb 2008 23:20:36 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: Wollogong TCP/IP stack Message-ID: <47c34d44$0$8063$607ed4bc@cv.net> In article <47C2C324.7124.6DF980@infovax.stanq.com>, "Stanley F. Quayle" writes: >I have a client running the very-ancient Wollogong IP stack. While it works just fine, >they'd like to add DCPS for printing, but DCPS doesn't support that stack. > >I vaguely remember that Wollogong became TCPware. Is that correct? I would opin that that is INCORRECT. BTW, it's Wollongong. Wollongong, IIRC, became Attachmate. When I worked for the DREN ET&D Labs, we had Wollongong for TCP/IP. We called it AllIsWrong, and for good reason. Machines would crash within components of Wollongong with great frequency. One day I happened upon an ad for a product called TGV MultiNet. I think, IIRC, that they of- fered an enticement offer of free license and a year and half of support for the price of a year's support if you had an existing TCP/IP product installed. I obtained a copy and installed it on one of the machines. Configured it and we beat on it and beat on it hard. No crashes. The labs purchased a number of copies of MultiNet and Wollongong was Wollongone. -- 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: Mon, 25 Feb 2008 19:04:12 -0600 From: "Bob Blum" Subject: Re: Wollogong TCP/IP stack Message-ID: What version of Wollongong are they running? I seem to recall using version 3.x and upgrading to 5.0 around the late 1980s. I don't recall when they transitioned to Attachmate, but I have a copy of the Attachmate PathWay 3.1 documentation and CD. It supports UCX emulation, and still appears to use the TWG$* logicals and directories. I'd be afraid to run a newer version of DCPS on an old version UCX emulation IP stack, but then again, I've done stranger things! What version of VMS are they running? Bob wrote in message news:47c34d44$0$8063$607ed4bc@cv.net... > In article <47C2C324.7124.6DF980@infovax.stanq.com>, "Stanley F. Quayle" > writes: >>I have a client running the very-ancient Wollogong IP stack. While it >>works just fine, >>they'd like to add DCPS for printing, but DCPS doesn't support that stack. >> >>I vaguely remember that Wollogong became TCPware. Is that correct? > > I would opin that that is INCORRECT. BTW, it's Wollongong. Wollongong, > IIRC, became Attachmate. > > > > When I worked for the DREN ET&D Labs, we had Wollongong for TCP/IP. We > called it AllIsWrong, and for good reason. Machines would crash within > components of Wollongong with great frequency. One day I happened upon > an ad for a product called TGV MultiNet. I think, IIRC, that they of- > fered an enticement offer of free license and a year and half of support > for the price of a year's support if you had an existing TCP/IP product > installed. > > I obtained a copy and installed it on one of the machines. Configured it > and we beat on it and beat on it hard. No crashes. The labs purchased a > number of copies of MultiNet and Wollongong was Wollongone. > > -- > 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.113 ************************