INFO-VAX Sat, 22 Mar 2008 Volume 2008 : Issue 164 Contents: How to stop DNS$ADVER running on EWB interface Re: How to stop DNS$ADVER running on EWB interface Re: How to stop DNS$ADVER running on EWB interface Patching: some questions from a relative newbie Re: Patching: some questions from a relative newbie Re: Patching: some questions from a relative newbie Re: Patching: some questions from a relative newbie Re: Too many files in one directory (again) Re: Tripwire on OpenVMS Best Practices? Re: VMS Mail translates incoming tilde character into a dollar sign. MICROSOFT C ---------------------------------------------------------------------- Date: Sat, 22 Mar 2008 13:58:59 +0100 From: Wilm Boerhout Subject: How to stop DNS$ADVER running on EWB interface Message-ID: <47e50298$0$25473$ba620dc5@text.nova.planet.nl> I have a two-node NI Cluster with nodes that have two network interfaces each. I want to dedicate each node's EWA interface to TCPIP and other networking stuff, while EWB handles SCS traffic. By not configuring DECnet and TCPIP on EWB I make sure that it does not run there. BY stopping SCS on EWA (using SYS$EXAMPLES:LAVC$STOP_BUS) I make sure that EWA carries no SCS. The only thing that remains is, DNS$ADVER claims a few EWBn: instances that I'd like to remove. What is the magic NCL-incantation that causes the DNS$ADVER process not to start on EWB? This is Alpha, VMS 6.2-1H3, DECnet-Plus T5.0.3 Thanks, Wilm -- Wilm Boerhout Zwolle, NL remove OLD PAINT from return address to reply ------------------------------ Date: Sat, 22 Mar 2008 06:41:07 -0700 (PDT) From: Volker Halle Subject: Re: How to stop DNS$ADVER running on EWB interface Message-ID: <2293b56b-1bc7-4f41-b9fb-79c7a5fa2373@p73g2000hsd.googlegroups.com> Wilm, the only supported method to do this is the DNS$ETHERNET_DEVICE logical, but it's only available in DECnet-OSI V7.3-2 ECO 1 or higher. I've recently answered this over in ITRC: http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1211669 That question mentioned a crude workaround as "def/sys/exec ewb0 nul" - maybe you can try, if that helps for your old version of DECnet- Plus. Volker. ------------------------------ Date: Sat, 22 Mar 2008 16:57:40 +0100 From: Wilm Boerhout Subject: Re: How to stop DNS$ADVER running on EWB interface Message-ID: <47e52c7b$0$10791$ba620dc5@text.nova.planet.nl> on 22-3-2008 14:41 Volker Halle wrote... > Wilm, > > the only supported method to do this is the DNS$ETHERNET_DEVICE > logical, but it's only available in DECnet-OSI V7.3-2 ECO 1 or higher. > I've recently answered this over in ITRC: > > http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1211669 > > That question mentioned a crude workaround as "def/sys/exec ewb0 nul" > - maybe you can try, if that helps for your old version of DECnet- > Plus. Thanks Volker, I'll give it a try. Funny to see in hindsight what my search terms should have been :-) -- Wilm Boerhout Zwolle, NL remove OLD PAINT from return address to reply ------------------------------ Date: Sat, 22 Mar 2008 01:45:45 -0700 (PDT) From: Zack Kline Subject: Patching: some questions from a relative newbie Message-ID: Hi, I go through phases with OpenVMS it seems. Not having any real hardware to worry about means that I can switch on the emulated system whenever I care to, and leave it off for six months or a year. Theoretically it'll just be fine when I get back. Anyhow, I'm in one of those phases now, with some questions about patches and versions of OpenVMS. I have Personal Alpha, and what seems to be VMS 8.2. I say seems to be because because of a strange result I got when patching today. I tried to install PCI-v0200, which I understand is a recommendation for everybody. It didn't install, claiming that the dependent product, DEC AXP OpenVMS V8.2, wasn't installed. The system I have says 'Welcome to OpenVMS Alpha Operating System, Version E8.2' when I log in. What is this E business? It seems to conflict with installations. Another patch-related question for you guys. I saw the 1100 Update patch for v8.2. I couldn't install it, naturally, because of the failed PCSI one. What I was wondering is what about patches I don't really need? Patches for an ADA runtime library which doesn't exist on my system, for instance. I'm just a little confused about that, but the thought of manually picking and choosing patches I do need scares me to death in more ways than one. I'll die of boredom and/or strained fingers from typing the same commands over and over. Any help or information about these questions would be appreciated. I'm slowly trying to learn the ropes, but it's slow going. So it goes. Thanks, Zack. ------------------------------ Date: Sat, 22 Mar 2008 03:08:19 -0700 (PDT) From: Bob Gezelter Subject: Re: Patching: some questions from a relative newbie Message-ID: On Mar 22, 4:45 am, Zack Kline wrote: > Hi, > I go through phases with OpenVMS it seems. Not having any real > hardware to worry about means that I can switch on the emulated system > whenever I care to, and leave it off for six months or a year. > Theoretically it'll just be fine when I get back. Anyhow, I'm in one > of those phases now, with some questions about patches and versions of > OpenVMS. > I have Personal Alpha, and what seems to be VMS 8.2. I say seems to > be because because of a strange result I got when patching today. I > tried to install PCI-v0200, which I understand is a recommendation for > everybody. It didn't install, claiming that the dependent product, > DEC AXP OpenVMS V8.2, wasn't installed. > The system I have says 'Welcome to OpenVMS Alpha Operating System, > Version E8.2' when I log in. What is this E business? It seems to > conflict with installations. > Another patch-related question for you guys. I saw the 1100 Update > patch for v8.2. I couldn't install it, naturally, because of the > failed PCSI one. What I was wondering is what about patches I don't > really need? Patches for an ADA runtime library which doesn't exist > on my system, for instance. I'm just a little confused about that, > but the thought of manually picking and choosing patches I do need > scares me to death in more ways than one. I'll die of boredom and/or > strained fingers from typing the same commands over and over. > Any help or information about these questions would be appreciated. > I'm slowly trying to learn the ropes, but it's slow going. So it > goes. > Thanks, > Zack. Zack, Welcome to Comp.os.vms. You are not the first to ask such a question, and I am sure that others merely sit in silence. From my memory, without checking my files, it sounds like you are running the pre-release kit ("Early adoptors kit"). The patches are against the actual release. The first step is to update your version of OpenVMS to either 8.2 or 8.3 (I presume that you are running for private educational purposes under the Hobbyist program). Once you have updated the system to the actual release, you will be able to apply all of the patches as issues. As to the missing ADA library, I would suspect that ADA was released AFTER the early adopters kit was issued. Switching to the real release will resolve that problem as well. - Bob Gezelter, http://www.rlgsc.com ------------------------------ Date: Sat, 22 Mar 2008 03:38:15 -0700 (PDT) From: Zack Kline Subject: Re: Patching: some questions from a relative newbie Message-ID: <4eb2d144-7760-478c-a01f-83dba2e6d0cf@i29g2000prf.googlegroups.com> Bob Gezelter wrote: > > Zack, > > Welcome to Comp.os.vms. You are not the first to ask such a question, > and I am sure that others merely sit in silence. > > From my memory, without checking my files, it sounds like you are > running the pre-release kit ("Early adoptors kit"). The patches are > against the actual release. The first step is to update your version > of OpenVMS to either 8.2 or 8.3 (I presume that you are running for > private educational purposes under the Hobbyist program). > > Once you have updated the system to the actual release, you will be > able to apply all of the patches as issues. > > As to the missing ADA library, I would suspect that ADA was released > AFTER the early adopters kit was issued. Switching to the real release > will resolve that problem as well. Hi Bob, Thank you very much for the quick response. I got this kit, which I am indeed using on a hobbyist license, from someone a couple years ago. I haven't really used it seriously until now, and so it makes sense that the pre-release might've been what I got. I've just ordered a new hobbyist kit from Montagar. With any luck it'll arrive here at my house before I need to leave for university. In the meantime I'll just enjoy what I have here and learn. V8.2 can't be too different from v8.3. I'll worry about patching when I get the new kit. For what it's worth, I really am liking VMS so far. It's a great system, and very different from much I'm used to. I'm glad the community's as nice as it is round here. Signing off for now. Thanks again. All the best, Zack. ------------------------------ Date: Sat, 22 Mar 2008 03:56:05 -0700 (PDT) From: Volker Halle Subject: Re: Patching: some questions from a relative newbie Message-ID: <6e8d67af-4fca-420b-894a-ea043c062dec@c65g2000hsa.googlegroups.com> Zack, OpenVMS E8.2 is the FIeldtest version of OpenVMS Alpha V8.2. As Bob already said, you need the OpenVMS Alpha V8.2 Operating System CD to install the 'real' version, before you can install any patches. Volker. ------------------------------ Date: Sat, 22 Mar 2008 08:56:04 -0500 (CDT) From: sms@antinode.org (Steven M. Schweda) Subject: Re: Too many files in one directory (again) Message-ID: <08032208560429_2020CE0A@antinode.org> From: Hein RMS van den Heuvel > > =A0 =A0So, it couldn't be improved to handle this case better? > > Yes. Maybe, Just maybe, Andy will get to release a b-tree based > implementation. I'm ready. > > =A0 =A0I didn't. =A0I didn't realize how doomed I was until I stepped well= > into this tar-pit. > > Oh yeah. Classic. Can't kill it now.. it must almost be done. :-) > Just wait till you get to delete them! I started out running it on my main XP1000 system. When that got into trouble, I fired up the zx2000, which soon got ahead of the Alpha, so I killed the job there. Only about 50k files at that time. DFU DELETE got rid of them pretty quickly. (I hadn't installed DFU on the zx2000 yet, but it's there now.) > > > > [...] =A0Even growing the allocation by, say, 25% > > > > instead of one block might pay off without a big penalty > > Mark Hopkins whisperred to me > "1) A directory extends by the maximum of 100 blocks or 1/2 the > current > file size (I just looked in the code). I'm pretty sure that this is > rounded up to the next cluster factor. None of the default extends > are honored here. That sounds good, but as I showed before, I wasn't seeing anything bigger than that 26384 - 26272 = 112, which is the smallest N* C_F >= 100. No sigh of any "1/2 the current file size" here. > Steven>> it should also (now) be using 127 > for the multi-block count ("fil_rab.rab$b_mbc"), and using two > buffers > ("fil_rab.rab$b_mbf"), and setting write-behind ("fil_rab.rab$l_rop | > =3D > RAB$M_WBH;") on > > Some argue to make it a multiple of 4 (124) to make live easier on > certain storage types (EVA Raid-5). > [...] The RMS parameter code here (which I use everywhere) will use any non-default SET RMS parameters set by the user instead of its own internal defaults. (And it's all open-source.) For the record: IT $ pipe t ; vmstar xf zip.tar ; t 20-MAR-2008 13:43:57 IT::_RTA3: 21:27:39 VMSTAR CPU=01:54:16.82 PF=1182 IO=44381972 MEM=357 IT::_RTA3: 23:33:39 VMSTAR CPU=02:36:08.14 PF=1182 IO=57161427 MEM=357 IT::_RTA3: 09:19:04 VMSTAR CPU=05:55:49.96 PF=1182 IO=120353399 MEM=357 IT::_RTA3: 15:33:39 VMSTAR CPU=08:08:25.16 PF=1182 IO=163580113 MEM=357 IT::_RTA3: 21:10:42 VMSTAR CPU=10:07:42.02 PF=1182 IO=202912695 MEM=357 IT::_RTA3: 23:47:42 VMSTAR CPU=11:02:55.68 PF=1182 IO=221024209 MEM=357 22-MAR-2008 00:35:48 IT $ IT::_RTA3: 08:25:11 (DCL) CPU=11:18:33.07 PF=1344 IO=225889468 MEM=247 So, it took only about 35 hours on a (newer, faster) VMS system to do what took about 35 minutes on the HP-UX system. Grand total of 1 directory, 189833 files, 1076441 blocks. This test case is easy to get, if anyone wants to share the fun. ------------------------------------------------------------------------ Steven M. Schweda sms@antinode-org 382 South Warwick Street (+1) 651-699-9818 Saint Paul MN 55105-2547 ------------------------------ Date: Sat, 22 Mar 2008 11:50:58 -0500 From: David J Dachtera Subject: Re: Tripwire on OpenVMS Best Practices? Message-ID: <47E538F2.BF960403@spam.comcast.net> rfc2307@gmail.com wrote: > > Good Morning, I'm looking for any information on best practices on > what to monitor, that is Operating System specific on the OpenVMS > platform. Any information or lessons learned would be appreciated. > Please reply to rfc2307@gmail.com > > Thanx in advance for all your assistance "Best practice" is a current industry buzz-phrase, highly-prized among the ITIL crowd (some say "idle" when they mean "eye-til"). Other than that, it is basically meaningless. "Best Practice" tends to be site-specific, and industry-wide generalizations have very little value in that context. That said, the on-line documentation site: http://www.hp.com/go/openvms/doc ...has some valuable documentation available, especially the System Management manuals. Again, these are not specific to any site or industry. Dunno if this helps. David J Dachtera (formerly dba) DJE Systems ------------------------------ Date: Sat, 22 Mar 2008 09:11:15 -0700 (PDT) From: Hein RMS van den Heuvel Subject: Re: VMS Mail translates incoming tilde character into a dollar sign. MICROSOFT C Message-ID: On Mar 21, 7:51=A0pm, kuhrt.nospa...@encompasserve.org (Marty Kuhrt) wrote: > In article <64hl7oF2c3h0...@mid.individual.net>, billg...@cs.uofs.edu (Bil= l Gunshannon) writes: > > In article <47e32132$1$23906$c3e8...@news.astraweb.com>, > > =A0 =A0JF Mezei writes: > >> Phillip Helbig---remove CLOTHES to reply wrote: > > >>> This really shows how quality control has gone down the drain. > > >> The only thing of value VMS still has is the clustering software. The > >> rest is all "legacy". When HP retires VMS, if the clustering is still > >> state of the art, they may get a few pennies giving it to Microsoft (ag= ain). > > >> The rest doesn't need to have much quality control or development. > > > Considering the internal differences between VMS and everything > > else, not even the clustering code would be worth anything to anybody > > else. > > M$lop had the clustering code and couldn't make it work. fwiw, a recent blog entry in that space I stumbled into.. http://pluralsight.com/blogs/jimjohn/archive/2008/03/16/50489.aspx Yes, that OpenVMS / RMS / ... Jim Johnson Cheers, Hein. ------------------------------ End of INFO-VAX 2008.164 ************************