1 INFO-VAX	Mon, 18 Oct 2004	Volume 2004 : Issue 578       Contents: BA353 configuration question  Re: BA353 configuration question  Re: BA353 configuration question1 Re: CC /MMS_DEPENDENCIES and related difficulties 1 Re: CC /MMS_DEPENDENCIES and related difficulties & Re: ERROR: unable to write header file& Re: ERROR: unable to write header file& Re: ERROR: unable to write header file& Re: ERROR: unable to write header file& Re: ERROR: unable to write header file Free Random password generator% Re: Humor   was Re: VMS for the blind # Re: Latest on Windoze Navy software # Re: Latest on Windoze Navy software & Re: Need Itanium2 (EPIC) Clarification RZ28B-VA drives wanted Re: VMS for the blind  Re: VMS for the blind 3 Re: VMS related water bound powerful mammal artwork   F ----------------------------------------------------------------------  % Date: Sun, 17 Oct 2004 16:35:03 -0700 , From: James Nykiel <jnykiel@access4less.net>% Subject: BA353 configuration question < Message-ID: <pan.2004.10.17.23.35.02.518042@access4less.net>  
 Greetings:    J I am interested in the BA353 and was wondering if the following is a validH configuration (1) RZ28-VA, (1) TLZ07-VA, (1) RRD43-VE.  Is there a mnualG or configuration guide for the BA353 in .PDF format available anywhere?      Thanks - Jim   ------------------------------  % Date: Sun, 17 Oct 2004 17:55:19 -0600 % From: Dan O'Reilly <dano@process.com> ) Subject: Re: BA353 configuration question A Message-ID: <6.1.2.0.2.20041017175446.02253fd8@raptor.psccos.com>   G My rule of thumb: plug them in and see.  I see nothing there that would 1 cause problems (usually heat-related in the 353).   + At 05:35 PM 10/17/2004, James Nykiel wrote:  >Greetings:  >  > K >I am interested in the BA353 and was wondering if the following is a valid I >configuration (1) RZ28-VA, (1) TLZ07-VA, (1) RRD43-VE.  Is there a mnual H >or configuration guide for the BA353 in .PDF format available anywhere? >  > 
 >Thanks - Jim    ------J +-------------------------------+----------------------------------------+J | Dan O'Reilly                  |  "There are 10 types of people in this |J | Principal Engineer            |   world: those who understand binary   |J | Process Software              |   and those who don't."                |J | http://www.process.com        |                                        |J +-------------------------------+----------------------------------------+   ------------------------------  % Date: Sun, 17 Oct 2004 23:37:12 -0400 ' From: Stuart Fuller <stufuller@usa.net> ) Subject: Re: BA353 configuration question 0 Message-ID: <8pdvkc.6a5.ln@dadsys2.fuller.local>   James Nykiel wrote:    > Greetings: >  > L > I am interested in the BA353 and was wondering if the following is a valid9 > configuration (1) RZ28-VA, (1) TLZ07-VA, (1) RRD43-VE.     No.   J The BA353 can accomodate 3 3.5-inch wide devices.  The RZ28 and the TLZ07 A are 3.5-inch wide devices, while the RRD43 is a 5.25-inch device.    --             Stu    ------------------------------  # Date: Sun, 17 Oct 2004 19:02:56 GMT 5 From: "Ed Vogel" <edward.vogel_stop_the_spam.@hp.com> : Subject: Re: CC /MMS_DEPENDENCIES and related difficulties1 Message-ID: <Alzcd.1010$tY1.693@news.cpqcorp.net>   G <sms@antinode.org> wrote in message news:04101620164825@antinode.org...  >    Is this a bug or not?  /     To quote from the help text (HELP CC /MMS):   0         " Note that the /OBJECT qualifier has no*            impact on the dependency file."  F     I believe this is what UNIX systems do for their corresponding -MD     switch.   K     You are not the first person to question this behavior, and it's a very G     valid question.  However,  the product has always behaved this way, B     and to change it now would probably cause a lot of trouble for-     users that rely on the existing behavior.    > H >    Is there some easy way I'm not seeing to get it to do what I'd like > (that is, something useful)? >   B     I would write a small script to modify the object file name in     the output .MMS file.        Ed Vogel     HP/Compaq C Engineering.   ------------------------------  + Date: Sun, 17 Oct 2004 22:05:23 -0500 (CDT)  From: sms@antinode.org: Subject: Re: CC /MMS_DEPENDENCIES and related difficulties) Message-ID: <04101722052347@antinode.org>       Thanks for the response ...5 From: "Ed Vogel" <edward.vogel_stop_the_spam.@hp.com>   1 >     To quote from the help text (HELP CC /MMS):  > 2 >         " Note that the /OBJECT qualifier has no, >            impact on the dependency file."  E    It'd be nice to change "impact" to "effect", as no one is actually F pounding on the dependency file, although I'm tempted every time I try  to get anything useful from one.  H >     I believe this is what UNIX systems do for their corresponding -MD
 >     switch.   4    Could be.  I'll check it if I get severely bored.  = >     You are not the first person to question this behavior,       I'm not amazed.   >  and it's a veryI >     valid question.  However,  the product has always behaved this way, D >     and to change it now would probably cause a lot of trouble for/ >     users that rely on the existing behavior.   H    One _could_ add a do-something-useful option which would preserve the9 current (near-useless) behavior by default.  For example, E /[NO]USEFUL_MMS_DEPENDENCIES [=file_spec], where the default would be @ /NOUSEFUL, and the optional file-spec would act like the /OBJECTF file-spec, which would be handy if /NOOBJECT were specified.  (Or else7 /NOOBJECT could accept a file-spec as well as /OBJECT.)   D >     I would write a small script to modify the object file name in >     the output .MMS file.   "    I wouldn't if I didn't need to.  H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode-org     Saint Paul  MN  55105-2547    ------------------------------  % Date: Sun, 17 Oct 2004 16:13:15 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> / Subject: Re: ERROR: unable to write header file + Message-ID: <4172D259.5A8FF12@teksavvy.com>    "R.A.Omond" wrote: >         $ exit %x54 3 >         %SYSTEM-F-CTRLERR, fatal controller error   L But woudln't this result in the error count dor the device going up ? The OP3 stated that the error count for the device is at 0.   ; (Or would the error count go up on the controller device ?)   N Does the error count in the SHOW DEV/FULL output get incrememented even if VMS- is unable to write to disk ? (the error log).    ------------------------------  % Date: Mon, 18 Oct 2004 10:17:50 +1000 # From: "Gremlin" <not-here@all.mate> / Subject: Re: ERROR: unable to write header file / Message-ID: <41730bab$1@duster.adelaide.on.net>    Hi All  L As I noted earlier, autogen had already decided the dump file size was fine I and I have run it a few times again just in case - I think the dump file  J message is a red herring.  The reason the error count doesn't increase is L that this ONLY occurs when shutting down - hence no opportunity to increase M the error count.  Fatal controller error sounds like a possibility, I wonder  * what could be causing it only at shutdown?  L Using a Seagate 20Gb drive in the standard IDE controller works fine except  at shutdown.........  ; "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  % news:4172D259.5A8FF12@teksavvy.com...  > "R.A.Omond" wrote: >>         $ exit %x544 >>         %SYSTEM-F-CTRLERR, fatal controller error > L > But woudln't this result in the error count dor the device going up ? The  > OP5 > stated that the error count for the device is at 0.  > = > (Or would the error count go up on the controller device ?)  > M > Does the error count in the SHOW DEV/FULL output get incrememented even if   > VMS 0 > is unable to write to disk ? (the error log).    ------------------------------  % Date: Sun, 17 Oct 2004 23:12:33 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> / Subject: Re: ERROR: unable to write header file , Message-ID: <41733491.58AF111F@teksavvy.com>   Gremlin wrote:K > message is a red herring.  The reason the error count doesn't increase is M > that this ONLY occurs when shutting down - hence no opportunity to increase N > the error count.  Fatal controller error sounds like a possibility, I wonder, > what could be causing it only at shutdown?  9 The dump file is not related to the error log dump file.    0 the error log is in disk:[SYS0.SYSERR]ERRLOG.SYS  D You can delete/rename this file and a new one gets created "fresh".   J Also, it might help if you could describe a bit more where in the shutdown  process the error message fails.  J You might also put a "SET VERIFY" in the shutdown.com file and then you'll- have a better idea of where the error occurs.    ------------------------------  % Date: Mon, 18 Oct 2004 13:42:59 +1000 # From: "Gremlin" <not-here@all.mate> / Subject: Re: ERROR: unable to write header file - Message-ID: <41733bbc@duster.adelaide.on.net>    OK. it goes roughly like this   * System is shutdown from the SYSTEM accountJ Shutdown procedure is activated and runs all the way through - nothing in  site specific shutdownH All usual and expected messages, no warning, error or fatal, everything  stops OKK Screen goes black, then blue, and stays that way with the hard drive light   "hard on" for about 5 minutes"I Then, these messages come up, about 2 minutes apart, followed by console   prompt- From there, I can init and everything is fine   ' Sho config and sho devices all looks OK     ; "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  & news:41733491.58AF111F@teksavvy.com... > Gremlin wrote:L >> message is a red herring.  The reason the error count doesn't increase isF >> that this ONLY occurs when shutting down - hence no opportunity to  >> increase I >> the error count.  Fatal controller error sounds like a possibility, I  	 >> wonder - >> what could be causing it only at shutdown?  > : > The dump file is not related to the error log dump file. > 2 > the error log is in disk:[SYS0.SYSERR]ERRLOG.SYS > E > You can delete/rename this file and a new one gets created "fresh".  > L > Also, it might help if you could describe a bit more where in the shutdown" > process the error message fails. > L > You might also put a "SET VERIFY" in the shutdown.com file and then you'll0 > have a better idea of where the error occurs.    ------------------------------   Date: 18 Oct 2004 05:20:15 GMT2 From: "Dave Weatherall" <djw-nothere@nospam.nohow>/ Subject: Re: ERROR: unable to write header file ? Message-ID: <DTiotGxQ0bj6-pn2-U5kcqeYCsoDt@dave2_os2.home.ours>   F On Sat, 16 Oct 2004 23:18:17 UTC, "Gremlin" <not-here@all.mate> wrote:   > Hi > K > All those issues are OK, I have been using the machine in production for  K > about a week and can add, delete etc without any problems.  I have about  O > 16Gb on the disk at the moment and have had no problems adding files.  Error  ! > count is zero.  Still confused!  >  > = > "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  ( > news:41715EE2.AC6EA923@teksavvy.com... > > Gremlin wrote: > >>. > >> VMS 7.2-2, DS10L, 20Gb Seagate IDE drive,? > >> "Error writing 2 blocks, buffer = FFFFFFFF.808B1E00, VBN 1 = > >>  Status code 00000054, 00000000 (Section = Header block) ? > >> Error writing 32 blocks, buffer = FFFFFFFF.809A0000, VBN 1 : > >> Status code 00000054, 00000000 (Section = Error logs) > >>K > >> So, is the first message indicating that VMS is bitching about a disk   > >> bigger  > >> than 2Gb? > > M > > I doubt that a DS10 with VMS 7.2-2 would have problems with a 2 gig disk.  > > C > > Seems to me more of a problem with the drive or the way it was   > > initialized. > > ? > > If you do SHOW DEV D/FULL does it show an error count > 0 ?  > > L > > Can you get to the $ sign ? If you try $PURGE device:[000000...]*.*/log  > > what > > does it say ?  > > L > > If the physical device is healthy, it could be something in the way the 	 > > drive ? > > was initialized, with an indexf.sys perhaps not big enough.  > > D > > SHOW DEV disk:/FULL tells you the maximum number of files on it.N > > $DIR dev:[000000...]*.*;*/grand  will tell you how many files are on your  > > drive.   >  >   F On Sat, 16 Oct 2004 23:18:17 UTC, "Gremlin" <not-here@all.mate> wrote:   > Hi > K > All those issues are OK, I have been using the machine in production for  K > about a week and can add, delete etc without any problems.  I have about  O > 16Gb on the disk at the moment and have had no problems adding files.  Error  ! > count is zero.  Still confused!  >  > = > "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  ( > news:41715EE2.AC6EA923@teksavvy.com... > > Gremlin wrote: > >>. > >> VMS 7.2-2, DS10L, 20Gb Seagate IDE drive,? > >> "Error writing 2 blocks, buffer = FFFFFFFF.808B1E00, VBN 1 = > >>  Status code 00000054, 00000000 (Section = Header block) ? > >> Error writing 32 blocks, buffer = FFFFFFFF.809A0000, VBN 1 : > >> Status code 00000054, 00000000 (Section = Error logs) > >>K > >> So, is the first message indicating that VMS is bitching about a disk   > >> bigger  > >> than 2Gb? > > M > > I doubt that a DS10 with VMS 7.2-2 would have problems with a 2 gig disk.  > > C > > Seems to me more of a problem with the drive or the way it was   > > initialized. > > ? > > If you do SHOW DEV D/FULL does it show an error count > 0 ?  > > L > > Can you get to the $ sign ? If you try $PURGE device:[000000...]*.*/log  > > what > > does it say ?  > > L > > If the physical device is healthy, it could be something in the way the 	 > > drive ? > > was initialized, with an indexf.sys perhaps not big enough.  > > D > > SHOW DEV disk:/FULL tells you the maximum number of files on it.N > > $DIR dev:[000000...]*.*;*/grand  will tell you how many files are on your  > > drive.    F If its any consolation, the IDE disk our DS20 did the same thing when B we first got it. I was using that disk to run all my Q/A tests on E before it went into day-to-day use. It was frustrating and worrying.  E However since the machine became the one used by everybody, I've not  F seen it happen. I am, however, its only, infrequent but intense, user.     --     Cheers - Dave W.   ------------------------------    Date: 17 Oct 2004 21:14:23 -07002 From: Spam2@Sharewareisland.com (FreewareTown.com)' Subject: Free Random password generator = Message-ID: <d4469d0d.0410172014.449ce992@posting.google.com>   ( here is a nice free you can run online. 3 http://www.sharewareisland.com/randompasswords.aspx 7  Its cool when there is nothing to download and install B  You can pick all diffrent kinds of opptions for the passwords too   ------------------------------  % Date: Sun, 17 Oct 2004 19:25:52 -0400 * From: Chuck Chopp <ChuckChopp@rtfmcsi.com>. Subject: Re: Humor   was Re: VMS for the blind< Message-ID: <XaDcd.178097$as2.169256@bignews3.bellsouth.net>   John Smith wrote:   J > When I saw the title of this thread "VMS for the blind", the first thing > that came to mind was: > E > Yes!!! Somebody has finally created a presentation for HP executive I > management about VMS at a simple enough level that even carly(tm) could A > understand - music, sing-along, follow the bouncing ball, .....   K LOL.... isn't this where that old marketing video titled "Educating Peter"  H would come in handy?  We were just discussing it in another thread here K recently and it would appear to be on the proper level required to educate   executives about VMS.      --   Chuck Chopp   8 ChuckChopp (at) rtfmcsi (dot) com http://www.rtfmcsi.com  @ RTFM Consulting Services Inc.     864 801 2795 voice & voicemail2 103 Autumn Hill Road              864 801 2774 fax Greer, SC  29651  , Do not send me unsolicited commercial email.   ------------------------------  # Date: Sun, 17 Oct 2004 19:06:57 GMT 5 From: "Ed Vogel" <edward.vogel_stop_the_spam.@hp.com> , Subject: Re: Latest on Windoze Navy software1 Message-ID: <lpzcd.1011$Y54.633@news.cpqcorp.net>   5 "Bill Gunshannon" <bill@cs.uofs.edu> wrote in message % news:2tdb8uF1v46k6U2@uni-berlin.de... F > No, the question is quite clear.  "Does any language use descriptors
 > natively ?"   A     I believe BASIC does.  BASIC strings are, by default, dynamic F     strings.  When passing strings, BASIC will pass the descriptor (by     reference).        Ed Vogel     HP/Compaq C Engineering )     (but worked on BASIC for many years).    ------------------------------   Date: 18 Oct 2004 05:20:10 GMT2 From: "Dave Weatherall" <djw-nothere@nospam.nohow>, Subject: Re: Latest on Windoze Navy software? Message-ID: <DTiotGxQ0bj6-pn2-4uTsVsIPNevB@dave2_os2.home.ours>   C On Sat, 16 Oct 2004 18:14:51 UTC, John Reagan <john.reagan@hp.com>   wrote:   > Dave Weatherall wrote: > H > > I had the same thought on the few occasions I have had to interface H > > Fortran with Pascal. The resulting Pascal prototypes look awful (or I > > awe-fully complex)  but they do work.  I always had the feeling that  J > > the counted string was a way of dealing with allocated/reserved length > > v current length.  > >  > H > Not to be mean, but you must not be writing them correctly.  They are  > rather easy to do. > @ > procedure pass_string_to_fortran ( p : [class_s] packed array % > [l..u:integer] of char ); external;  > D > procedure accept_string_from_fortran ( p : [class_s] packed array  > [l..u:integer] of char ); 
 >    begin >    writeln(p);+ >    pass_string_to_fortran('hello world'); 8 >    pass_string_to_fortran(p);  ! Pass along the string	 >    end;  > J > The "conformant array syntax" is how you tell Pascal that the parameter E > will be some length PACKED ARRAY OF CHAR (ie, string type) but the  I > length isn't known until runtime.  The '[CLASS_S]' attribute tells the  F > compiler what descriptor to use (by default, we would want to use a J > CLASS_A or CLASS_NCA to handle the cases where the lower bound wouldn't  > be 1).  E I don't take it mean :-). I can't check now how my defs compare with  E the one you show above, it appears very familiar. I'll look tomorrow  4 when I get in. I'm not sure I use the CLASS keyword.  D However, when you've got a procedure/function with 3 or more string F arguments, the protoype gets very long and awe- inspiring :-). WhetherE that's 'awful' is a matter for the beholder. I do try to ensure it's  F easy to read though. That said, most of my user's just take my exampleE code, blow it up to meet their purpose and never think about what it  D means. They strings involved mainly hold file-specs that get fed to  Fortran OPEN  statements.    --   Cheers - Dave.   ------------------------------  % Date: Sun, 17 Oct 2004 19:31:34 -0400 * From: Chuck Chopp <ChuckChopp@rtfmcsi.com>/ Subject: Re: Need Itanium2 (EPIC) Clarification < Message-ID: <igDcd.178114$as2.135993@bignews3.bellsouth.net>   Neil Rieck wrote:   M > In the past few weeks I've read several articles (including Terry Shannon's G > SKHPCV11N36) which mentioned the fact that "Itanium2 (Montecito) will J > shortly introduce multithreading". Here is a quote from Terry's article: > J > "Other enhancements to Montecito include multithreading. Debuting in theG > Xeon chip server line and already implemented in Pentium 4 processors B > and IBM POWER5 CPUs, multithreading allows a CPU to run multipleL > applications concurrently. This technology will be integrated into Itanium- > for the first time when Montecito arrives."   I This sounds like the "Hyper-threading" term that was introduced with the  M dual-core P4 CPUs.  It is one CPU package with dual processor cores so it is  G effectively a dual CPU system in an SMP configuration.  This gives you  I multi-processor SMP capabilities on a mother board that isn't equiped to  K support multiple separate processors on the board.  I don't recall whether  L or not the cache memory on the CPU was increased or if both cores share the K same cache memory that was previously dedicated to a single core, so there  J may be some performance-related issues that result in a dual-core CPU not K offering as large of a performance increase as what you'd get if you had a  + system with dual CPUs in separate packages.      --   Chuck Chopp   8 ChuckChopp (at) rtfmcsi (dot) com http://www.rtfmcsi.com  @ RTFM Consulting Services Inc.     864 801 2795 voice & voicemail2 103 Autumn Hill Road              864 801 2774 fax Greer, SC  29651  , Do not send me unsolicited commercial email.   ------------------------------  % Date: Sun, 17 Oct 2004 21:46:52 -0700 , From: James Nykiel <jnykiel@access4less.net> Subject: RZ28B-VA drives wanted < Message-ID: <pan.2004.10.18.04.46.51.139128@access4less.net>  
 Greetings:    G I am assembling a BA353 StorageWorks enclosure for use with my hobbyist F system and would like to obtain (2) RZ28B-VA drives.  Unfortunately myJ budget is fairly limited at this time so try and keep the price affordable- if you can.  Please email me with your offer.      Thanks - Jim   ------------------------------  % Date: Sun, 17 Oct 2004 20:47:06 -0700 % From: "Zachary" <Z_kline@hotmail.com>  Subject: Re: VMS for the blind+ Message-ID: <2tgslpF204pnsU1@uni-berlin.de>   ; "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  & news:4172D165.8D1B0603@teksavvy.com...H > Perhaps it would help if you could provide a lots of applications you  > intendG > or use on VMS, and whether you access it through a character cell or   > Xwindows interface.  >  > J > There is a xwindow utility called "Magnify screen" which is supposed to  > let K > you look at the screen with a magnifying glass. (although I can't get it   > toI > work properly right now). May not help if you are totally blind though.   H As it so happens, I am totally blind.  At this point, I am limited to a K character cell interface.  As for programs I intend using, I don't know at  K this point.  It depends what I can find.  Their seems to be a lot of stuff  D available, but deciding what I would want is hard, to say the least.   ------------------------------  % Date: Sun, 17 Oct 2004 21:33:23 -0700 % From: "Zachary" <Z_kline@hotmail.com>  Subject: Re: VMS for the blind+ Message-ID: <2tgvcgF20ds0mU1@uni-berlin.de>   ; "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  & news:4172D165.8D1B0603@teksavvy.com...H > Perhaps it would help if you could provide a lots of applications you  > intendG > or use on VMS, and whether you access it through a character cell or   > Xwindows interface.  >  > J > There is a xwindow utility called "Magnify screen" which is supposed to  > let K > you look at the screen with a magnifying glass. (although I can't get it   > toI > work properly right now). May not help if you are totally blind though.   L By the way, does anyone know what happened to the Deathrow OpenVMS cluster? M That is the cluster I signed up on.  It seems to have completely disappeared  J today.  At least for me.  This is odd, because other sites I've used have  also vanished without a trace.   ------------------------------  % Date: Mon, 18 Oct 2004 08:04:57 +0800  From: prep@prep.synonet.com < Subject: Re: VMS related water bound powerful mammal artwork- Message-ID: <877jpoopqu.fsf@prep.synonet.com>   - shoppa@trailing-edge.com (Tim Shoppa) writes:   c > JF Mezei <jfmezei.spamnot@teksavvy.com> wrote in message news:<416F4CA1.BBFE3037@teksavvy.com>...   I >> In the theoretical scenario where I would have an imaginary friend who P >> happened to have *THE* shark in vector format (resizeable, can change coloursQ >> etc), and such imaginary friend wanted to make that shark available to the VMS O >> community since it seems to be the de-facto logo to compete against the evil Q >> penguin, what would be the best format to distribute this so that it is usable  >> by the VMS community ?    
 >> PICT ?  >> DXF ? >> EPS ?
 >> Freehand ?  >> Illustrator ?   > Tek4014 vector graphics.  " MetaFish of course ;) What else...   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------   End of INFO-VAX 2004.578 ************************