1 INFO-VAX	Tue, 01 Nov 2005	Volume 2005 : Issue 610       Contents:N Re: Alphaserver 4100 and Mylex DAC960 RAID controller documentation/utilities?> Re: Finding out who is my Tape drive with Show devices command( Re: Poll: Web-based Chat on OpenVMS.org? TCPWare & Batteries? Re: TCPWare & Batteries? Re: TCPWare & Batteries? Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP Re: Writing an OpenVMS ACP  F ----------------------------------------------------------------------   Date: 1 Nov 2005 04:19:30 -0800  From: sampsal@gmail.com W Subject: Re: Alphaserver 4100 and Mylex DAC960 RAID controller documentation/utilities? C Message-ID: <1130847570.418944.110760@o13g2000cwo.googlegroups.com>   E Yeah noticed the 32 GB limit when making the logical drive. So I just A created a bunch of them. Everything seems to be running smoothly, B managed to get OpenVMS 7.3-1 up and running on it yesterday. Happy days, I have a VMS box.    Sampsa   Andy Bustamante wrote:M > There is a limit of 32 gb for any unit you create on this controller.  This N > works out to be up to 7 x 4.3 GB disk in a raid-5 set.  The hot spare and onK > the fly replacement isn't great, but this controller does work reasonably - > well.  I still some in productions systems.  >  > --   >  >  > Andy Bustamante ! > Remove the ASCII 95s for e-mail    ------------------------------   Date: 1 Nov 2005 07:22:47 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) G Subject: Re: Finding out who is my Tape drive with Show devices command 3 Message-ID: <gP9z$rjw8zWL@eisner.encompasserve.org>   n In article <1130789092.416214.182140@g14g2000cwa.googlegroups.com>, "pbritto" <britto.paulo@gmail.com> writes: > Bob,B >  I don't even know where to type in this script (it looks like aB > script), I tried the prompt but it complained at the second line >  Where should I use it?   C    To use labels the script must be in a file.  By convention these C    files use the extension .COM .  Use the @ command to execute the 
    script.  4    So if you put them in findtape.com, then you can:      $ @findtape  C    Where $ was the original VMS prompt, you may be using some other 
    prompt.   ------------------------------   Date: 1 Nov 2005 02:14:13 -0800  From: sampsal@gmail.com 1 Subject: Re: Poll: Web-based Chat on OpenVMS.org? C Message-ID: <1130840053.206204.210090@g49g2000cwa.googlegroups.com>    I would definitely use it.   ------------------------------   Date: 1 Nov 2005 04:47:43 -0800 % From: "issinoho" <issinoho@gmail.com>  Subject: TCPWare & Batteries? C Message-ID: <1130849263.818174.158030@f14g2000cwb.googlegroups.com>   * Anyone know what this OPCOM message means,  / TCPWARE_NTP-E-UNEXPCTD, can't sync battery time   & OpenVMS V7.3-2 & TCPWare 5.6 on Alpha.   ------------------------------  $ Date: Tue, 1 Nov 2005 09:12:53 -0500, From: "Richard Whalen" <WhalenR@process.com>! Subject: Re: TCPWare & Batteries? + Message-ID: <dk7t59$epm$1@news.process.com>   G The Time of Year clock in VAX and Alpha systems is powered by a battery L and runs independently of the system clock, which is maintained by software.L NTP regularly adjusts the software clock to help it keep more accurate time.G To avoid having the system revert to the unadjusted TOY clock time upon L reboot a SETIME system call is done periodically.  This will update the timeE in the TOY clock (and on the boot disk) so that when/if the system is  rebootedK the time will be pretty close to the actual time.  The TOY clock is updated  every 6 hours.  I The message means that an error was received when doing the SETIME system K call.  If you are only seeing this message occasionally, then it's probably  not J worth worrying about; but if it is showing up 3 or 4 times a day, then NTP isn't * able to do everything that it needs to do.    0 "issinoho" <issinoho@gmail.com> wrote in message= news:1130849263.818174.158030@f14g2000cwb.googlegroups.com... , > Anyone know what this OPCOM message means, > 1 > TCPWARE_NTP-E-UNEXPCTD, can't sync battery time  > ( > OpenVMS V7.3-2 & TCPWare 5.6 on Alpha. >    ------------------------------  % Date: Tue, 01 Nov 2005 17:44:33 +0300 N From: "Ruslan R. Laishev" <zzLaishev@zzDeltaTelecom.RU-remove.all-zz-to-reply>! Subject: Re: TCPWare & Batteries? 3 Message-ID: <D3D37E4722B6278B9627D72CF53607E1@nntp>   ! Is there DTSS up & running also ?    issinoho wrote:   , > Anyone know what this OPCOM message means, > 1 > TCPWARE_NTP-E-UNEXPCTD, can't sync battery time  > ( > OpenVMS V7.3-2 & TCPWare 5.6 on Alpha. >  >    --  F + WBR, OpenVMS [Sys|Net] HardWorker ............. Skype: SysMan-One  +9 Delta Telecom JSC, IMT-MC-450(CDMA2000) cellular operator E Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 716-3222 F +http://starlet.deltatelecom.ru ............. Frying on OpenVMS only +   ------------------------------  # Date: Tue, 01 Nov 2005 08:14:13 GMT   From: John Santos <john@egh.com># Subject: Re: Writing an OpenVMS ACP ( Message-ID: <ptF9f.1637$0d.323@trnddc08>  
 Max wrote:I > My thanks to everyone who has offered advice about porting a driver/ACP F > client/server arrangement from RSX to VMS. The message I'm receivingG > loud and clear is to steer clear of VMS ACPs; I suppose I should have I > guessed that from the fact that the standard VMS manuals don't tell you H > how to write an ACP. I have managed to download some source code for aH > VMS ACP, and of course it's in assembler, which is unhelpful since theE > machine I'm using at the moment is an Alpha but the eventual target G > machine will be an Integrity, presumably with different machine code.   C Actually, Macro-32 (the VAX assembler) exists as a compiler on both A Alpha and Itantium, so that shouldn't really be a barrier.  It is E possible to write Macro-32 source code that compiles and works on all B three architectures without too much trouble, and without too manyC ".if_def VAX"'s.  Macro-32 strongly resembles Macro-11, and the VAX C instruction set is basically an extended PDP-11 instruction set, so B if your original application is in Macro-11, that might be the way to go.  B I'm not recommending *against* using a higher level language, just) pointing out that it may not be required.     H > So I want to write everything in C. Anyway, I think I'll have a try atC > doing it with mailboxes. As someone pointed out, even the slowest I > Integrity server is a great deal faster than the fastest PDP11, so with E > any luck there won't be a performance problem. Thanks again, and if 3 > anyone needs any help with PDP11s, try me... Max.   C P.S.  Someone is sure to jump in at some point and mention a PDP-11 D emulator.  If you are stuck using Qbus hardware, this might actuallyC be the quickest (to implement) and fastest (in performance) option. E On modern CPUs, PDP-11 emulators are reputed to run many times faster F than any real PDP-11 ever ran, and some can directly interface to Qbus or Unibus peripherals.  8 I hope I've help here by making everything clear as mud!   --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  # Date: Tue, 01 Nov 2005 08:35:20 GMT   From: John Santos <john@egh.com># Subject: Re: Writing an OpenVMS ACP ( Message-ID: <cNF9f.1638$0d.807@trnddc08>   Dave Froble wrote: > Larry Kilgallen wrote: > I >> In article <cb19m1ledicofj64kac6eo7o8qjt7l6lfl@4ax.com>, Nigel Barker   >> <nigel@hp.com> writes:  >>< >>> On Sat, 29 Oct 2005 15:27:35 -0400, "Stanley F. Quayle"  >>> <squayle@insight.rr.com>
 >>> wrote: >>>  >>> ( >>>> On 29 Oct 2005 at 10:48, Max wrote: >>>>J >>>>> it's in assembler, which is unhelpful since the machine I'm using atG >>>>> the moment is an Alpha but the eventual target machine will be an 9 >>>>> Integrity, presumably with different machine code.   >>>> >>>>J >>>> True, but VAX Macro is supported on all 3 platforms.  On a VAX, it's H >>>> directly converted to machine code.  On Alpha and Integrity, Macro J >>>> is processed by an optimizing compiler, just like any other language 1 >>>> (C, Fortran, etc.), to produce machine code.  >>>>C >>>> And VAX Macro is the only language that comes "free" with VMS.  >>>  >>> @ >>> Java, PERL & PHP are all "free" with VMS on Alpha & Itanium. >> >> >>I >> I do not think so.  I looked into PERL and found that one must install + >> something else to put it onto a machine.  >>I >> And it is certainly unavailable to organizations that will not install  >> unsupported software. >  > H > 'Unavailable' is a rather strong word to use when an entity 'chooses' " > not to use a particular product. > @ > It's clear that Macro-32 is available on all 3 platforms, and  > distributed with the OS.  A But not necessarily present on all three.  It can be tailored off E on VAX, and appears to be optional on Alpha and Itanium.  (I actually . checked the Upgrade and Installation Manuals.)  B If you need a language that is absolutely guaranteed to be present6 on all 3 architectures, I think you're stuck with DCL.   > G > I believe Bliss is available on all 3 platforms, but not distributed  / > with the OS, rather it's on the Freeware CDs.  > J > Is Bliss also one of those unsupported products that some organizations ? > will not use?  If so, then they should stop using 1/3 of VMS.   E That 1/3 of VMS is supported by HP, even if the compiler itself isn't F supported.  If you encounter a VMS bug that is actually due to a BlissF compiler bug (how would you know?), HP would still be obligated to fixB it, and send you a new executable.  They could never get away withH saying "That's due to a bug in the Bliss compiler, which is unsupported,G so we won't fix it."  (Whether they fixed the compiler or worked around F it in their source code or re-implemented it in another language would be HP's choice.)     --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  $ Date: Tue, 1 Nov 2005 19:52:08 +08003 From: "Richard Maher" <maher_rj@hotspamnotmail.com> # Subject: Re: Writing an OpenVMS ACP 1 Message-ID: <dk7kvs$q8i$1@news-02.connect.com.au>    Hi Dan,   F > Over the years I've written many thousands of lines of MACRO32 code.G > Not only do I personally like MACRO32, but I'm also an expert MACRO32  coder   H Fair enough. I believe you, and neither do I care for false modesty. Any bits of VMS belong to you?  K > No doubt the only reason the MACRO32 _compiler_ was created for Alpha and H > Itanium was in support of the large amounts of _existing_ MACRO32 code  J So it would be ludicrous for me to suggest that any new features have beenK intoduced to Macro-32 since being ported first to Alpha and then to Itanium G (and then to the next architecture). I mean, why would one need VLM and L 64-bit addressing features if one was simply porting 32-bit code from VAX toC X? Still, I'm not an expert MACRO32 coder so you're probably right.   I > No doubt creating a compiler for it was much easier and far less risky.   G Does anyone else think it not a smidgin incongruous for someone of such G experience to find so little room for doubt? (I personally haven't been * certain about anything since my early 20s)  F > So if you'd like to write a few million _new_ lines of MACRO32 code, > please be my guest!   / Yep, that's what everyone's been talkin' about.   5 > Personally I'm not stupid enough to write any _new_ ! > MACRO32 source code unless. . .   K Well, just today I've added about 50 lines to a User-Written System Service I of mine to cater for a bollocks Microsoft DTC change, so the good news is K that I've achieved both "Blithering idiot" and "Stupid" status in one week. L And it's only Tuesday! But *most importantly* COV has once again lived up toK its reputation for reasoned debate of the highest calibre. Thanks for that!   0 > . . .writing it for the VAX platform and can'tI > conveniently accomplish the same task more productively using any other  > available language.   K So Dan, what would you recommend to the punters for writing inner-mode code E that must be linked /PROTECTed? No doubts about *all* of the bollocks < disclaimers and provisos contained in sys$examples:*uwss*.c?   Regards Richard Maher   L PS. I just had a thought that if I was unemployed and wanted to put my waresH in the HP street then I'd write a reply pretty much like yours. Nah no I	 wouldn't.   ' <danco@ns2.pebble.org> wrote in message + news:slrndmdei1.6jh.danco@ns2.pebble.org... H > In article <dk1p37$f3g$1@news-02.connect.com.au>, Richard Maher wrote: > D > >> Unless one has a large investment in _existing_ MACRO32 code toE > >> perpetuate, then I don't think it would be a good idea to create 
 > >> more. > > 6 > > Oh Really, why not? 'Cos Hoff (et al) told you so? > 2 > Honestly I have no idea what Mr. Hoffman thinks. > F > Over the years I've written many thousands of lines of MACRO32 code.G > Not only do I personally like MACRO32, but I'm also an expert MACRO32  coder.K > No doubt the only reason the MACRO32 _compiler_ was created for Alpha and I > Itanium was in support of the large amounts of _existing_ MACRO32 code. E > The task (and the risk) of re-writing all that code would have been  immense.I > No doubt creating a compiler for it was much easier and far less risky. F > I'm certainly very glad they did create a MACRO32 compiler for AlphaG > as it tremendously eased the porting of large amounts of my own code.  > F > So if you'd like to write a few million _new_ lines of MACRO32 code,J > please be my guest!  Personally I'm not stupid enough to write any _new_J > MACRO32 source code unless I'm writing it for the VAX platform and can'tI > conveniently accomplish the same task more productively using any other  > available language.  >  > - Dan    ------------------------------  # Date: Tue, 01 Nov 2005 16:00:19 GMT  From: danco@ns2.pebble.org# Subject: Re: Writing an OpenVMS ACP 1 Message-ID: <slrndmf0bc.6tk.danco@ns2.pebble.org>   F In article <dk7kvs$q8i$1@news-02.connect.com.au>, Richard Maher wrote:  M > So Dan, what would you recommend to the punters for writing inner-mode code G > that must be linked /PROTECTed? No doubts about *all* of the bollocks > > disclaimers and provisos contained in sys$examples:*uwss*.c?  C I have some inner mode code here that I wrote some 20 years ago and A which I still maintain.  It's almost all written in MACRO32, with ? some written in C.  If I was going to write any significant new   inner mode code, I'd do it in C.   - Dan    ------------------------------   End of INFO-VAX 2005.610 ************************                                                                                                                                                                =-T*7}JZ4|oo;G<HQ!\i]Aލ[	?-k]sʾq+gCLk5"ط̝f[Na#;YxPǙ\^T;C-\NrIfJG!FfXyd5(?3A.{(Jfo;EbJudfp≘iQj#lU%X$M5#vz_!ܓdͭ<rE
a}ߓ[PlSy8(8RҚJZF}mrsM"Ec|Y>UفeTlm>Fw_̼<lhaAq*kI[5G)ů H:]zJwi*#*ojBXx*1ђZ|%Z҈2~X8WaN|&1mpɨ;4o<yX#82e*.LN׫I2OnJO!-qj
mdl!͋|[QZwV5F$ꖋwG[

wrQt_B\0ێ삕(F(qΨ#CUZ7qWtO\Hܙ>cl@$]LA4qQ7b`bx&glW3XSzS'PkXԲc@Xj%+];t3ǉ׍,pAyD@Sq

*D[veLTl,CZ4Nuf*4OR 3qYhXmwNe%R-&?w-˹"Oh*xO̎a_j㖂&t*0,;MSqȫ7N@V[W
Xď
ZYKM9C~2Lvք9vq+|-z
D}*E\x2L I-\EW9 ÄN0z%RVaK`UP1j^U+mhƙO<ͧi-y!ȁIY7HHcڧ>쐴Zh{.+h}-Î,GY@-Vfu]j?cLD-rг$13R'
> ]lhĻc,Wup6yDgPا
2o+쯦w״}+/7ɥ1{No'5d;A>yFkݻJOV\$jۆݏ0&4~/tVG|!7@	 "vd4NJ"1'EPPPQ_vq0ɾ
Ay XRQ̺VtRF}X>"TтY,V
Fy&CUǢЂ6m;|7"==\DюA8 T_gAiu D(V0_i