1 INFO-VAX	Thu, 15 Jun 2006	Volume 2006 : Issue 331       Contents:8 Re: Alphaserver 2100 needs a good home - South Cambs, UK' Ann Livermore mentions OpenVMS, blades! + Re: Ann Livermore mentions OpenVMS, blades!  Re: DS10 big memory ! How can I read a locked VMS file? % Re: How can I read a locked VMS file? % RE: How can I read a locked VMS file? % Re: How can I read a locked VMS file? % Re: How can I read a locked VMS file? , Just Ask The Vendor: Can OpenVMS Scale Down?0 Re: Just Ask The Vendor: Can OpenVMS Scale Down?0 Re: Just Ask The Vendor: Can OpenVMS Scale Down?0 Re: Just Ask The Vendor: Can OpenVMS Scale Down?0 Re: Just Ask The Vendor: Can OpenVMS Scale Down? Re: Multi-homed DHCP server  Re: Multi-homed DHCP server # Re: Open VMS OS recovery on Itanium # Re: Open VMS OS recovery on Itanium   Pathworks authentication problem> Re: Slowin' machine while zipping or deleting big binary files> Re: Slowin' machine while zipping or deleting big binary files> Re: Slowin' machine while zipping or deleting big binary files> Re: Slowin' machine while zipping or deleting big binary files> Re: Slowin' machine while zipping or deleting big binary files& Re: Sue Skonetski's Get Well Soon Gift want to get rid of an HSC70  Re: XPO error messages ? Re: XPO error messages ? Re: XPO error messages ?  F ----------------------------------------------------------------------  + Date: Thu, 15 Jun 2006 16:23:05 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)A Subject: Re: Alphaserver 2100 needs a good home - South Cambs, UK $ Message-ID: <e6s1h9$a76$1@online.de>  C In article <1150274152.888084.115040@y41g2000cwy.googlegroups.com>,  paco.linux@gmail.com writes:    # > Same question from Spain(Seville)   0 I won't be making it that far down south, sorry.   ------------------------------    Date: 15 Jun 2006 06:07:44 -0700 From: bob@instantwhip.com 0 Subject: Ann Livermore mentions OpenVMS, blades!B Message-ID: <1150376864.835576.13830@g10g2000cwb.googlegroups.com>  6 http://www.itjungle.com/breaking/bn061406-story01.html   ------------------------------    Date: 15 Jun 2006 06:26:38 -0700  From: "Ian Miller" <ijm@uk2.net>4 Subject: Re: Ann Livermore mentions OpenVMS, blades!C Message-ID: <1150377998.535561.110120@g10g2000cwb.googlegroups.com>   G According to the VMS Roadmap, VMS support for these blades is scheduled  for H2 2007    ------------------------------  % Date: Thu, 15 Jun 2006 10:14:54 -0400 C From: "David Turner, Island Computers US Corp" <dbturner@icusc.com>  Subject: Re: DS10 big memory: Message-ID: <6Ydkg.76761$QU3.73917@bignews8.bellsouth.net>   DS15 memory is 133Mhz memory The DS10 requires 100Mhz memory   E We have of course tried it - wouldn't suggest even thinking about it.   G The DS10 and Ds10L are identical boards - the limitation (which dataram J worked around for a while) is the riser card for the memory on the DS10L -D it requires covering two of the memory slots ergo only 1GB permittedJ Dataram made a low profile memory kit for a while which allowed removal of5 the riser cards and thus 2GB was able to be installed    DT   --     David B Turner Island Computers US Corp 2700 Gregory St, Suite 180 Savannah GA 31404  Tel: 912 447 6622 X201 Cell: 912 447 6622 X251  Fax: 912 201 0402  Email: dbturner@icusc.com  Web: http://www.islandco.com% ===================================== < All orders are subject to the following terms and conditions. of sale. These should be read before ordering.% http://www.islandco.com/warranty.html   , "Rod" <rregier@dymaxion.ca> wrote in message= news:1150320686.601917.324130@c74g2000cwc.googlegroups.com... 0 > The Quickspecs for the DS10 say 2G max memory. > I > Is that enforced by the hardware, or would it be possible to add 2 - 2G  > memory options?  > H > Looks to me like the 2G DS15 memory option would work if the CPU would > permit > that size. >  > Tks  >    ------------------------------    Date: 15 Jun 2006 08:43:14 -0700 From: StevensSpam@cfl.rr.com* Subject: How can I read a locked VMS file?C Message-ID: <1150386194.884818.146550@c74g2000cwc.googlegroups.com>   F I have a log file that is locked. The process that has the file lockedE is production critical; I cannot terminate it. However, I really need E to view the contents of this log file. Is there a way to override the 9 VMS file lock in order to view the contents of this file?    Thanks!    ------------------------------    Date: 15 Jun 2006 08:47:46 -0700 From: StevensSpam@cfl.rr.com. Subject: Re: How can I read a locked VMS file?C Message-ID: <1150386466.698070.285270@u72g2000cwu.googlegroups.com>   B Bah. Never mind. I am not getting a file protection violation. TheG problem is that there is no committed data in the file (I misunderstood D the initial problem). The file size is 0/432 blocks. Then I type theE file, it shows nothing. I guess there is a concept of uncomitted data / here. Any ideas on how I may look at this data?    Thanks!!   ------------------------------  % Date: Thu, 15 Jun 2006 12:26:59 -0400 ' From: "Main, Kerry" <Kerry.Main@hp.com> . Subject: RE: How can I read a locked VMS file?T Message-ID: <FA60F2C4B72A584DBFC6091F6A2B8684015B4287@tayexc19.americas.cpqcorp.net>   > -----Original Message-----A > From: StevensSpam@cfl.rr.com [mailto:StevensSpam@cfl.rr.com]=20  > Sent: June 15, 2006 11:43 AM > To: Info-VAX@Mvb.Saic.Com , > Subject: How can I read a locked VMS file? >=20H > I have a log file that is locked. The process that has the file lockedG > is production critical; I cannot terminate it. However, I really need G > to view the contents of this log file. Is there a way to override the ; > VMS file lock in order to view the contents of this file?  >=20	 > Thanks!  >=20 >=20   Steve,  H If the log file has no comitted data written to it, this might not work,	 but try -    $ Edit/TPU/read filename.log   Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  4 OpenVMS - the secure, multi-site OS that just works.   ------------------------------  # Date: Thu, 15 Jun 2006 16:28:13 GMT A From: "Colin Butcher" <colin_DOT.butcher_AT@xdelta_DOT.co_DOT.uk> . Subject: Re: How can I read a locked VMS file?= Message-ID: <xUfkg.86465$wl.81173@text.news.blueyonder.co.uk>   6 BACKUP <locked_file>/IGNORE=INTERLOCK <temporary_file>D Then look at the temporary file and with a bit of luck you might see something of use.   J If you really mean a LOG file (eg: batch output from SYS$OUTPUT:) then youJ might find making carefully considered changes to the output rate with SET OUTPUT <interval> useful.    --     Hope this helps, Colin. ) colin DOT butcher AT xdelta DOT co DOT uk E It's not mine, but I like this definition: Legacy = stuff that works.    ------------------------------  # Date: Thu, 15 Jun 2006 17:21:59 GMT  From: hoffman@hp.nospam (). Subject: Re: How can I read a locked VMS file?0 Message-ID: <XGgkg.1923$m_.188@news.cpqcorp.net>  b In article <1150386194.884818.146550@c74g2000cwc.googlegroups.com>, StevensSpam@cfl.rr.com writes:I |> I have a log file that is locked. The process that has the file locked H |> is production critical; I cannot terminate it. However, I really needH |> to view the contents of this log file. Is there a way to override the< |> VMS file lock in order to view the contents of this file?  F   In addition to BACKUP and such, another approach is the DCL command:  !   CONVERT/SHARE from-spec to-spec   C   Should you have access to the source code for the application (or D if you are willing to patch the image directly to resolve this), theA commands necessary to open the file for shared access are readily A available.  (The FAQ has a discussion of this issue specific to C @ programmers, but the solution and the flags can be generalized.)A Tweaking the file-sharing flags is trivial to code in most any of C the available languages, and equally easy within a direct RMS file   open.   B   If you're not sure how to do this, post the section of code that6 opens the log file here, and we can take a look at it.  G   Adjusting the file options is the best and most appropriate approach, D well, barring some comparatively draconian site-specific application (re)qualification requirements.    ------------------------------  # Date: Thu, 15 Jun 2006 13:33:18 GMT * From: Mandala support <support@mandala.ca>5 Subject: Just Ask The Vendor: Can OpenVMS Scale Down? 8 Message-ID: <46o292dgd08qtffi35j3irspvhepf6u7so@4ax.com>  , Just Ask The Vendor: Can OpenVMS Scale Down?  
 Mr Vendor,  H    While it is great to see that you have decided to create a SMB marketG for OpenVMS, your definition of SMB is different than mine. Starting at ? 64 users, your minimum configuration is larger than most of our 
 customers.   <from># http://www.brilliant.com/qsoft.html   G Quintara is very affordable. Pricing is based on concurrent user count. F Packages are available in concurrent user counts as small as 64 users,< perfect for small and growing businesses, schools, and other organizations. </from>   E Does this restriction have to do with the fact that you have no plans B to sell small box OpenVMS? I fear that without a small box OpenVMSH solution, the really small business (RSB) community will miss out on the computing wave of the future.   G While the RSB market may not buy a lot of user licenses, they could buy F lots of boxes. I see this as a win-win-win solution. OpenVMS gets soldH in quantities that matter, Mr ChipHead finally gets a market to sell itsG wares, and the world will get to benefit from a simple, stable, secure, 4 reliable and affordable solution to common problems.  E I can appreciate that until you get your product firmed up enough to  E successfully compete against the current crop of industry idiots that E you need to restrict the product to only serious SMB users. But don't  forget about us little guys.  1 Once again I ask in the only way that I know how.   D Please hP, can you scale OpenVMS down to the RSB market? I fear thatG without a product that I can sell to my tiny user base, I may be forced ) to miss out on the "New OpenVMS" revival.   F Maybe if I knew who came up with the "brilliant" idea, I could talk toF them directly about RSB OpenVMS. But I fear that I may be just talking
 to myself.  /    Still too small to make any real difference,        Duane Gillespie          Dartmouth            Nova Scotia   F We are currently proposing a non-OpenVMS Vendor email solution to some7 of our Alpha customers. Now how funny is that!!! (sob)     ------------------------------  # Date: Thu, 15 Jun 2006 16:50:44 GMT * From: Mandala support <support@mandala.ca>9 Subject: Re: Just Ask The Vendor: Can OpenVMS Scale Down? 8 Message-ID: <dt339292hsnp1dvvfhod68mkq9cfkt5jue@4ax.com>  , On Thu, 15 Jun 2006 14:24:59 GMT, you wrote:   >Mandala support wrote: / >> Just Ask The Vendor: Can OpenVMS Scale Down?  >  > I >   I might well reverse the question/request, and ask for what specific  G >feature(s) you need to sell products into your target market(s).  And  F >yes, you obviously need to make a profit selling the boxes into your G >customers (as does HP), and you need to have a value-add of some sort.    Thanks Hoff for reading.  C I have no influence in selling or choosing a directon for OpenVMS.    = Just a (misguided?) desire to identify some target market(s).   D And yes, I would love to pick up some new OpenVMS customers. But for3 some reason, OpenVMS is not an easy sell :-( (yet).   5    A few million dollars short of building an empire, 
         Duane    >to organize as D >an application service provider (ASP), to use a recent buzz-phrase.  C We do have experience in being an ASP (we used to sell time-sharing A services on our PDP and later our VAX), but all our customers now D have their own puter's. We still provide ASP like banking services.    ------------------------------    Date: 15 Jun 2006 10:09:09 -0700 From: bob@instantwhip.com 9 Subject: Re: Just Ask The Vendor: Can OpenVMS Scale Down? C Message-ID: <1150391349.559347.148640@h76g2000cwa.googlegroups.com>    Hoff Hoffman wrote:  > Mandala support wrote:0 > > Just Ask The Vendor: Can OpenVMS Scale Down? > H >    There are comparatively few folks running Apache, web spiders, SMTPI > mail servers, or multi-user time-share boxes for their small businesses I > -- and there are even fewer that want to.  (In this regard, us computer   > folks are, um, different.  :-)  B we are one of them, and I know of many others who where forced offG of OpenVMS because of lack of economic solutions for small business ...   @ One of DECs strengths used to be small and medium business ... I= started out on a PDP11/24 RSTS box ... these boxes along with > Microvax later and MCBA dibol and other apps thrived until DEC0 forgot about their small/medium cutomer base ...  @ small customers are willing to pay for rock solid solutions over> freeware, but OpenVMS owners have failed to give them that ...  > remember, small customers in volumes brings additional revenue% and keeps the entire base growing ...   B Quintara has the perfect product to go head to head with Micro$oft< and linux ... our VP was estatic that we could now eliminate outhouse express ...  @ They need to offer 1-X user licenses and HP needs to do the same! with apache small web servers ...   < a healthy customer base includes both small/medium and large9 customers ... one or the other alone is a weaker base ...    ------------------------------  # Date: Thu, 15 Jun 2006 17:27:48 GMT & From: hoffman@xdelta.zko.dec.nospam ()9 Subject: Re: Just Ask The Vendor: Can OpenVMS Scale Down? / Message-ID: <oMgkg.1924$m_.74@news.cpqcorp.net>   e In article <dt339292hsnp1dvvfhod68mkq9cfkt5jue@4ax.com>, Mandala support <support@mandala.ca> writes: / |> On Thu, 15 Jun 2006 14:24:59 GMT, you wrote:  |>   |> >Mandala support wrote:2 |> >> Just Ask The Vendor: Can OpenVMS Scale Down? |> > |> >L |> >   I might well reverse the question/request, and ask for what specific J |> >feature(s) you need to sell products into your target market(s).  And I |> >yes, you obviously need to make a profit selling the boxes into your  J |> >customers (as does HP), and you need to have a value-add of some sort. ...F |> I have no influence in selling or choosing a directon for OpenVMS.     F   Again, what specific OpenVMS features or changes do you need to sell your products and/or services?    H   I obviously can't guarantee we'll implement the changes, but -- if we F don't know about the features or changes that would help your case, we( can't even discuss implementing it/them.   ------------------------------  # Date: Thu, 15 Jun 2006 17:30:03 GMT  From: hoffman@hp.nospam ()9 Subject: Re: Just Ask The Vendor: Can OpenVMS Scale Down? 1 Message-ID: <vOgkg.1925$m_.1263@news.cpqcorp.net>   _ In article <1150391349.559347.148640@h76g2000cwa.googlegroups.com>, bob@instantwhip.com writes:   C |> They need to offer 1-X user licenses and HP needs to do the same $ |> with apache small web servers ...  D   OpenVMS I64 offers unlimited licenses, and Apache is licensed withC OpenVMS.  As for Brilliant's pricing for Quintara (and the apparent B beliefs of my omnipotence among a few folks here aside :-), that's not something that I can set.    ------------------------------  % Date: Thu, 15 Jun 2006 02:47:26 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> $ Subject: Re: Multi-homed DHCP server, Message-ID: <44910255.D73E4385@teksavvy.com>   "John E. Malmberg" wrote: F > That is because until a DHCP client is rebooted, it will continue toH > always go to the specific DHCP server that leased it it's I.P. address. > unless that DHCP server becomes unavailable.     I think I would reword this to:   D A DHCP client gets to choose between multiple DHCP Server Offers andI responds to the one it prefers.  A renewall is still done as a broadcast.     F The DHCP server on VMS seems to be quite basic. Consider a cable ISP'sH DHCP server.  The DHCP requests are augmented as they travel through theF bridges and routers between the customer and the DHCP server. The DHCPE server knows the coax address of the cable modem used by the customer D and uses that as a key to authorize the user against some subscriberG database which defines many attributs such as number of IPs that can be F handed out for a single cable modem. And for this to work, it also has> to know how many IPs have been given to that customer already.  E And more importantly, the DHCP server knows the identity of the first G router that handled the DHCP request, and will hand out an IP that that  particular router can handle.       F I remember reading one those moving-target roadmap documents that theyC planned VLAN support for VMS. If that is the case, then it might be G conceivable for a VMS hosted DHCP server to receive "augmented" packets F that would contain the VLAN identification of the DHCP client and thenH decide which IP range to allocate. (eg: people in "accounting" get theirF pool of IPs, people in "engineering" get a different pool of IPs etc).   ------------------------------  # Date: Thu, 15 Jun 2006 14:18:11 GMT 7 From: John Malmberg <malmberg@dskwld.zko.hp.compaq.dec> $ Subject: Re: Multi-homed DHCP server0 Message-ID: <D_dkg.1913$UT.233@news.cpqcorp.net>   JF Mezei wrote:  > "John E. Malmberg" wrote:  > F >>That is because until a DHCP client is rebooted, it will continue toH >>always go to the specific DHCP server that leased it it's I.P. address. >>unless that DHCP server becomes unavailable. > ! > I think I would reword this to:  > F > A DHCP client gets to choose between multiple DHCP Server Offers andK > responds to the one it prefers.  A renewall is still done as a broadcast.   H But that would not be correct.  A DHCP client remembers which server it E obtained a lease from and will attempt to renew that lease with that  2 specific DHCP server before the lease has expired.  F A DHCP client that already has a lease will only send out a broadcast C message if it is unable to renew that lease with the specific DCHP   server it got the lease from.   H On a reboot, there usually is no existing lease, so a broadcast is used.  B This cuts down on broadcast traffic, and makes renewals very fast.   The side effects are:   G 1. You have to pay attention to the maximum lease time before moving a  E DHCP zone from one server to another where they are not coordinating  F addresses.  You must deactivate the original DHCP server and wait for = all the leases to expire before starting the new DHCP server.   I 2. If someone sets up two uncoordinated DHCP servers by mistake to serve  G the same area, the problem will usually not get noticed until the DHCP  6 clients are rebooted and get incorrect I.P. addresses.   -John ! malmberg@dskwld.zko.hp.compaq.dec  Personal Opinion Only    ------------------------------    Date: 15 Jun 2006 07:26:43 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) , Subject: Re: Open VMS OS recovery on Itanium3 Message-ID: <ojEUY68l94qh@eisner.encompasserve.org>   d In article <IaGdnfbrubKg7g3ZnZ2dnUVZ_r6dnZ2d@comcast.com>, "Earl Lakia" <elakia@hotmail.com> writes:  < > * Acpi(HWP0002,700)/Pci(1|1)/Uart(9600 N81)/VenMsg(Vt100+)  1 > * Acpi(PNP0501,0)/Uart(9600 N81)/VenMsg(PcAnsi)   D    Gee, that looks painfull.  How well are these strings documented?%    (I don't have my first IA-64 yet.)    ------------------------------  # Date: Thu, 15 Jun 2006 13:24:54 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>, Subject: Re: Open VMS OS recovery on Itanium1 Message-ID: <Gcdkg.1910$rM.1834@news.cpqcorp.net>    Earl Lakia wrote: . > During one of the HP DSPP sponsored events I > received an RX2600 server.    C    The current round of servers from the Itanium porting event are   rx2620 series boxes, AFAIK.    > This system doesn't ) > have any real way of backing itself up.   H    As of V8.3, you can record to DVD as part of the release, though (if I this was an older system, as implied by the model and by the old OpenVMS  G I64 releases) then you may not have a DVD+R/RW drive integrated in the  H box.  And if this is an older system, do check the firmware loaded into A the system, as there are firmware upgrades for the rx2600 series.   ) > Anyway after an 8.1 Field Test to 8.2,    G    OpenVMS I64 V8.2 is a clean-install release.  There is no supported  F upgrade from earlier releases, and there is no supported upgrade from I even the earlier 8.2 pre-releases.  V8.2 is the first production release   for the platform, after all.   > I find that neither of0 > my disks will boot.  Additionally, I was never< > given any VMS distribution (there weren't enough copies at
 > the event).   B    That's a problem -- the lack of a formal distribution, that is.  * > I was able to get a VMS 8.2 distribution3 > from my customer hoping the DVD would allow me to # > restore to a virgin distribution.   "    As others have stated, it will.  1 > I tried to boot it with the EFI and it seems to : > hit the DVD for sometime, but then hangs.  Additionally,< > I am able to boot the Linux kit and the offline diagnostic3 > utilities CDs.  Looking at my documentation under 3 > "Restoring the OS", only HPUX, Windows, and Linux 4 > are mentioned.  What is the procedure for OpenVMS?  I    The procedures for an OpenVMS I64 installation are in the OpenVMS I64  D manuals -- "my documentation" doesn't indicate what manuals you are H looking at, but I'm guessing they're (older) platform-generic documents.  6 > Any help out there?  Should the VMS 8.2 distribution > DVD boot?   I    I'd be looking to V8.2-1 (current) or to the SDK for the 8.3 release;  F we're approaching release of V8.3.  Not unsurprisingly, we've learned = and upgraded and enhanced since V8.2 shipped, in other words.   + > I have seen the documentation on updating : > from a zip download file (this is what I did originally): > but not for an OpenVMS system recovery from a DVD or CD.  F    Subsequent messages have indicated the connection was with mis-set F serial ports.  The EFI console is a full run-time environment, with a > very large number of commands, a file system, and a number of E capabilities and configuration settings.  To make things rather more  D interesting, you can add on a management processor (MP), which adds E additional capabilities, commands, and local and network connections.   H    For installing and using OpenVMS, we've documented how to set up EFI 8 -- with or without the MP -- in the OpenVMS I64 manuals.   	--   -    re: one of the other replies in the thread   A    Yes, the ACPI device identification strings shown by EFI are,  E bluntly, really ugly -- text strings that only a BIOS engineer could  @ love.  It's one of the areas I'd personally like to upgrade the @ user-friendliness.  That written, if you follow the OpenVMS I64 G directions for configuration and installation of the operating system,  G you generally don't have to deal with the ACPI strings again except on  H very rare occasions, and you get GRUB-style boot aliases to select your A target boot disk.  (Once you get OpenVMS I64 V8.2-1 or later, we  0 automatically manage most of this for you, too.)   ------------------------------    Date: 15 Jun 2006 02:37:13 -0700 From: mcbill20@yahoo.com) Subject: Pathworks authentication problem C Message-ID: <1150364233.508586.325780@u72g2000cwu.googlegroups.com>   G Anyone out there using Pathworks DECnet client on Win 2003? I am having  an authentication problem.   Here's the layout:  E We have an NT 4.0 domain that unfortunately has to stay NT 4 forever. F We had one fileserver that was also NT 4 but I just replaced it with aF new one with Win 2003 Server. We have a building full of VAXen that doE automatic DECnet file copies to the windows file server, which is the F reason for the Pathworks client. Since it's not working yet on the newG server, I still have the DECnet node name and address on the old server 4 and the new server has a temporary name and address.  > Everything works fine in talking to the old server. I can do aG directory from the VAXen to the NT 4 machine (1.1004) and it works fine A but I get an authentication error when I try it to the new server 	 (1.1011).    Here's the output:   $ d 1011"user password":: C %DIRECT-E-OPENIN, error opening 1011"user password"::*.*;* as input / -RMS-E-FND, ACP file or directory lookup failed < -SYSTEM-F-INVLOGIN, login information invalid at remote node  D The username I am using is a domain user, which is supposed to work.A I've tried logging in to the server (windows login) with the same F username and it works fine.  I don't see anything in the windows event# viewer or the Pathworks log viewer.   D The VMS machines are running 5.5-2 and 7.2. The Pathworks version on6 the NT machine is 7.2 and 7.4 on the Windows 2003 box.  
 Any ideas?   Thanks.  Bill   ------------------------------  % Date: Thu, 15 Jun 2006 02:54:52 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> G Subject: Re: Slowin' machine while zipping or deleting big binary files , Message-ID: <44910413.7771BB76@teksavvy.com>   xxrmanza wrote:  >  > thank you all for your help. > % > The winner is    :  highwater mark!   + Beware of the security implication of this.   ? With highwater marking disabled, when you create a file with an G allocation of say 1000 blocks, you are able to read the former contents D that were physically located in the blocks that are now allocated to your file.    C When it is enabled, the system automatically zeroes a block that is H being accessed when that block is beyond the current end of file marker.   ------------------------------    Date: 15 Jun 2006 07:24:22 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) G Subject: Re: Slowin' machine while zipping or deleting big binary files 3 Message-ID: <ixUrlBZNwTkX@eisner.encompasserve.org>   c In article <YJEypI1TNzIB@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:  > @ > If ZIP is inefficient in the fact of highwatermarking, I think@ > there is a flaw in the coding of ZIP.  This seems likely since@ > many ZIP programs are ported from other systems.  To work on a? > highwater marking disk, write the file in strictly sequential > > order.  Otherwise, blocks will have to be zeroed in advance.  >    Although I've read that highwater marking should not make aB    significant impact on sequential writes, my experience has been
    otherwise.   @    That's based on tools I think are writing sequencially:  TPU,E    compilers, and LINK; and code we were writing that used sequential     Fortran or C RTL I/O.   ------------------------------    Date: 15 Jun 2006 05:42:47 -0700$ From: "AEF" <spamsink2001@yahoo.com>G Subject: Re: Slowin' machine while zipping or deleting big binary files C Message-ID: <1150375367.895938.201950@g10g2000cwb.googlegroups.com>    Larry Kilgallen wrote:d > In article <1150302397.812619.17100@f6g2000cwb.googlegroups.com>, "xxrmanza" <rrmj@gmv.es> writes:  > > thank you all for your help. > > ' > > The winner is    :  highwater mark!  > > F > > was enabled. As soon as I set it to nohighwater it works splendid. > @ > I do not see how highwater marking could affect file deletion,! > although erase-on-delete would.  > @ > If ZIP is inefficient in the fact of highwatermarking, I think@ > there is a flaw in the coding of ZIP.  This seems likely since@ > many ZIP programs are ported from other systems.  To work on a? > highwater marking disk, write the file in strictly sequential > > order.  Otherwise, blocks will have to be zeroed in advance.    G Wouldn't a SET RMS/EXTEND=big-number help when making a large zip file? 4 (big-number should be something like 5000 or larger)   AEF    ------------------------------  # Date: Thu, 15 Jun 2006 13:47:00 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>G Subject: Re: Slowin' machine while zipping or deleting big binary files 0 Message-ID: <oxdkg.1912$cT.948@news.cpqcorp.net>  
 AEF wrote:  I > Wouldn't a SET RMS/EXTEND=big-number help when making a large zip file? 6 > (big-number should be something like 5000 or larger)  A    Current zip provides appropriate extension sizes for its file  I operations, IIRC.  There are other fixes to zip (you want 2.31, or later  H as available) and unzip (get 5.52, or later as available) that make use * of the current revisions recommended, too.  #    Visit <http://www.info-zip.org.>   B    The next OpenVMS Freeware is shipping with these bits, as well.   ------------------------------  + Date: Thu, 15 Jun 2006 10:30:33 -0500 (CDT) * From: sms@antinode.org (Steven M. Schweda)G Subject: Re: Slowin' machine while zipping or deleting big binary files 2 Message-ID: <06061510303390_2022872F@antinode.org>  $ From: "AEF" <spamsink2001@yahoo.com> > Larry Kilgallen wrote:f > > In article <1150302397.812619.17100@f6g2000cwb.googlegroups.com>, "xxrmanza" <rrmj@gmv.es> writes:" > > > thank you all for your help. > > > ) > > > The winner is    :  highwater mark!  > > > H > > > was enabled. As soon as I set it to nohighwater it works splendid. > > B > > I do not see how highwater marking could affect file deletion,# > > although erase-on-delete would.  > > B > > If ZIP is inefficient in the fact of highwatermarking, I think) > > there is a flaw in the coding of ZIP.   D    There was, before Zip 2.31.  (And it wasn't the only one.  And it> probably wasn't the last one, either, but anyone is welcome to$ contribute complaints and/or fixes.)  D    Of course, as has been noted already, the original poster did not! mention the Zip version involved.    > >   This seems likely since 4 > > many ZIP programs are ported from other systems.  B    It would be more accurate to say that the Info-ZIP programs areG developed more or less simultaneously on multiple systems, according to H the preferences of the developers.  Unlike with the typical GNU program,G the Info-ZIP developers tend to be aware of code portability problems.  H In my limited travels, I have found no other freeware developers who are? more interested in accomodating VMS (features and limitations).    > >   To work on aA > > highwater marking disk, write the file in strictly sequential @ > > order.  Otherwise, blocks will have to be zeroed in advance.  D    And, more important, set the SQO (sequential access only) bit, toG inform the system that you'll be doing that, as merely writing strictly & sequentially does not fix the problem.  I > Wouldn't a SET RMS/EXTEND=big-number help when making a large zip file? 6 > (big-number should be something like 5000 or larger)  C    Yes, but a larger extend quantity also locks the disk for longer F periods when highwater marking is anabled, and the SQO bit is not set.  , From: Hoff Hoffman <hoff-remove-this@hp.com>B >    Current zip provides appropriate extension sizes for its fileJ > operations, IIRC.  There are other fixes to zip (you want 2.31, or laterI > as available) and unzip (get 5.52, or later as available) that make use , > of the current revisions recommended, too. > % >    Visit <http://www.info-zip.org.>  > D >    The next OpenVMS Freeware is shipping with these bits, as well.  H    Indeed.  It's nice to see that someone remembered.  For the original,F longer, more rambling discussion of [Un]Zip v. highwater marking, see, for example:  g       http://groups.google.com/group/comp.os.vms/browse_thread/thread/e40c7dbd70bab7c9/f8a01603c0ff49b3   F    Of course, "appropriate" is open to interpretation, but the currentF behavior (Zip 2.31 and up, subject to complaints) is to set the extendC quantity to 16384, subject to an override by way of SET RMS_DEFAULT G /EXTEND_QUANTITY.  The source code is available for inspection.  On the B other end, in UnZip 5.52 (and up, ...), because the file sizes areB stored in the archive, it's possible to allocate the whole of eachD extracted file when it's created, and that's what UnZIP does (now). H (And thanks to the miracle of the SQO bit, it no longer locks the targetB disk for extended periods when allocating space for a large file.)  C    Note that, for trivially small test cases, 16384 is too big, and E actually slows things down a little, but my inability to choose _the_ 2 perfect value is why the override was implemented.  H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------    Date: 15 Jun 2006 04:19:28 -0700  From: "Ian Miller" <ijm@uk2.net>/ Subject: Re: Sue Skonetski's Get Well Soon Gift B Message-ID: <1150370367.979692.138710@r2g2000cwb.googlegroups.com>  ) http://www.openvms.org/pages.php?page=Sue  has been updated. , 24 Contributors as of 1:30 am EST, June 15th   ------------------------------  % Date: Thu, 15 Jun 2006 16:48:17 +0200 , From: "Gooijen, Henk" <henk.gooijen@oce.com>$ Subject: want to get rid of an HSC70R Message-ID: <447524F844B59D48B8F7AE7F560935EE066817D4@OVL-EXBE01.ocevenlo.oce.net>   Hi all, ? I have an HSC70 that came with the VAX-11/750 that I collected. < However the interface nor the CI750 came with the system ...= I do not have the room or any use for the HSC70, but it seems < a waste to throw it away!  I have no knowledge on the HSC70,= but was told that the HSC70 was fairly equipped with "stuff". > I live in the south of The Netherlands, important as I can not> ship the HSC70 (too heavy, too big).  So, you must pick it up.> Would a trade for a UNIBUS or QBUS (disk) SCSI module be fair?( Old PDP-11 peripherals are also welcome!  See my website at  www.pdp-11.nl     kind regards,  - Henk.     L This message and attachment(s) are intended solely for the use of the addre=L ssee and may contain information that is privileged, confidential or otherw=3 ise exempt from disclosure under applicable law.  =   L If you are not the intended recipient or agent thereof responsible for deli=L vering this message to the intended recipient, you are hereby notified that=L  any dissemination, distribution, or copying of this communication is stric= tly prohibited.  =  L If you have received this communication in error, please notify the sender =7 immediately by telephone and with a "reply" message.  =    Thank you for your cooperation.    ------------------------------    Date: 15 Jun 2006 01:18:08 -0700- From: "Brucey" <Bruce.Goller@LCHClearnet.com> ! Subject: Re: XPO error messages ? C Message-ID: <1150359488.055402.132990@c74g2000cwc.googlegroups.com>   F Thanks, but I don't think the errors relate to their ACMS equivalents.  = e.g. from yesterday we had the following random(?) selection:   > %XPO-F-SCBWRITEFAIL, cannot add member due to failed SCB writeE %XPO-F-ONLYSRCMUSTSTAY, only existing source member cannot be removed 
 during a c- %XPO-F-NOTINPOOL, storage unit is not in pool ? %XPO-F-TRUSTCONF, trust conflict for privileged image execution E %XPO-F-MAXNAMPOL, maximum number of HBMM named policies already exist E %XPO-F-CANTDODDS, dissimilar device shadowing is not supported on all 
 systems wh    G Something seems to be "screwed up" somewhere. Maybe a bug in VMS or one B of the layered products ? Maybe the machine build (it's new) had a	 problem ?     D The Final Status Code (eg 30203444) translates into the relevant XPO: message for all the *msg.exe files - seems a bit strange ?  E e.g. If I use %x30203444 as the parameter to the following DCL. I get  the following:  ! @lme$utils:GET_MESSAGE %x30203444  .  .  .  >From : CLIUTLMSG E %XPO-F-CANTDODDS, dissimilar device shadowing is not supported on all + systems where shadow set is already mounted    >From : COSI$MSGE %XPO-F-CANTDODDS, dissimilar device shadowing is not supported on all + systems where shadow set is already mounted    >From : DBGTBKMSG E %XPO-F-CANTDODDS, dissimilar device shadowing is not supported on all + systems where shadow set is already mounted    >From : DBL$MSG E %XPO-F-CANTDODDS, dissimilar device shadowing is not supported on all + systems where shadow set is already mounted  .  .  .  etc.       With the DCL being as follows:  # $! P1 = Message number to translate  $! $ on error then continue $ write sys$output " " $top: - $ msg_file = f$search("sys$message:*msg.exe") & $ if msg_file .eqs. "" then goto endit% $ set message/nofac/noid/nosev/notext  $ set message 'msg_file  $ msg_stat = $status $ set message/fac/id/sev/text C $ if msg_stat .eqs. "%X10018292" then goto top ! not a message file  $ msg = f$message(p1) 3 $ if f$locate("NONAME",msg).lt.f$length(msg) .or. - :      f$locate("NOMSG",msg) .lt.f$length(msg) then goto top( $ op_start  = f$locate("]",msg_file) + 12 $ op_length = f$locate(".EXE",msg_file) - op_start4 $ op_file   = f$extract(op_start,op_length,msg_file)+ $ write sys$output "From : " + "''op_file'"  $ write sys$output msg $ write sys$output " "
 $ goto top $! $ endit:# $ set message sys$message:shrimgmsg  $ exit   ------------------------------  # Date: Thu, 15 Jun 2006 08:44:25 GMT   From: John Santos <john@egh.com>! Subject: Re: XPO error messages ? * Message-ID: <J59kg.6210$WM4.1822@trnddc01>  
 Brucey wrote: H > Thanks, but I don't think the errors relate to their ACMS equivalents. > ? > e.g. from yesterday we had the following random(?) selection:  > @ > %XPO-F-SCBWRITEFAIL, cannot add member due to failed SCB writeG > %XPO-F-ONLYSRCMUSTSTAY, only existing source member cannot be removed  > during a c/ > %XPO-F-NOTINPOOL, storage unit is not in pool A > %XPO-F-TRUSTCONF, trust conflict for privileged image execution G > %XPO-F-MAXNAMPOL, maximum number of HBMM named policies already exist G > %XPO-F-CANTDODDS, dissimilar device shadowing is not supported on all  > systems wh >  > I > Something seems to be "screwed up" somewhere. Maybe a bug in VMS or one D > of the layered products ? Maybe the machine build (it's new) had a > problem ?  >  > F > The Final Status Code (eg 30203444) translates into the relevant XPO< > message for all the *msg.exe files - seems a bit strange ? > G > e.g. If I use %x30203444 as the parameter to the following DCL. I get  > the following: >   E You might be looking at junk.  %x30203444 seems suspiciously texty to F me.  In ASCII, it would be "D4 0" which isn't very meaningful, but theF chances of getting 4 printable characters out of a random longword are@ pretty slim.  So maybe somthing is stepping on the stack, or R0?     --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  # Date: Thu, 15 Jun 2006 13:38:02 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>! Subject: Re: XPO error messages ? 1 Message-ID: <_odkg.1911$dS.1301@news.cpqcorp.net>   
 Brucey wrote:   D > We're running in an ACMS environment and have just upgraded to VMS1 > V7.3-2 along with a few other layered products.  > G > We're seeing "strange" final error statuses from $ ACCOUNTING/FULL on  > ACMS user processes e.g.7 > %XPO-F-DIRALLOC, allocation failure on directory file 2 > %XPO-F-DIRNOTCRE, !AS directory file not created) > %XPO-F-CONFQUAL, conflicting qualifiers ? > %XPO-F-PAGNOTINREG, page in the specified range is not within  > C >>From what I can gather XPO is an obsolete BLISS related product ?   F    That's almost certainly "stack junk", or a corruption somewhere in D the accounting data record(s).  The stack junk could be coming from H corruptions at various points up to when the record is written, or even G potentially after the record is written into the accounting data file.  I If this is only select process entries (and not new entries), this could  F be a block error underneath the accounting data record(s) involved --  this is unlikely, but possible.   H    The ACMS version and ECO, and the OpenVMS ECOs, would be the obvious I initial questions here.  I'd ensure the system is current on its updates.   D    I'd also look to see if something is writing into the accounting I data, as there have been third-party products that performed that action  D -- and if the structures being written aren't entirely correct, all I manner of accounting weirdness can ensue.  (The accounting records don't  F have individual checksums, so the corruptions can be silent.)  One of ? the utilities I recall seeing triggering accounting errors was  " performing charge-back accounting.  I    After verifying ECOs and ACMS version, I'd probably save the existing  H aside and then re-create the accounting database.  I'd also tend to get I into contact with the support center, as it might well be interesting to  H see what's actually present within the accounting data records involved * here, and to see if this problem persists.   ------------------------------   End of INFO-VAX 2006.331 ************************