1 INFO-VAX	Tue, 24 Oct 2000	Volume 2000 : Issue 594       Contents: Re: ">>>" what is this mode?% Re: $ show printer => %cli-f-syntax ? , AlphaServer 2100 upgrade from 4/233 to 5/2500 Re: AlphaServer 2100 upgrade from 4/233 to 5/2500 Re: AlphaServer 2100 upgrade from 4/233 to 5/2500 Re: AlphaServer 2100 upgrade from 4/233 to 5/2500 Re: AlphaServer 2100 upgrade from 4/233 to 5/2500 Re: AlphaServer 2100 upgrade from 4/233 to 5/250 Re: best way of deleting files? ' Re: Clsutering, What does it mean??????  F$GETQUI ON ALAPHA Re: F$GETQUI ON ALAPHA( Re: FS microvax 3100-85, 128mb, 6gb, 8mm Re: Galaxy doubt Re: Galaxy doubt Re: Galaxy doubt Galaxy QUESTIONS Gigabit Ethernet question  Re: Gigabit Ethernet question  Re: Gigabit Ethernet question  RE: Gigabit Ethernet question  Re: Handling oddball disks" Re: hex numbers with CLD + $NUMBER" Re: hex numbers with CLD + $NUMBER" HP4050 vs HP4050TN when using DCPS5 Re: PDF Generator for OpenVMS (was PDF under OpenVMS)  Re: PDF under OpenVMS  Re: PDF under OpenVMS  popquestion ' Re: Press Release from Process Software $ Re: Problem with COMPAQ 9.1GB drives$ Re: Problem with COMPAQ 9.1GB drives$ Re: Problem with COMPAQ 9.1GB drives$ Re: Problem with COMPAQ 9.1GB drives1 Question about running out of queue entry numbers 5 Re: Question about running out of queue entry numbers 5 Re: Question about running out of queue entry numbers 5 Re: Question about running out of queue entry numbers 5 Re: Question about running out of queue entry numbers 5 Re: Question about running out of queue entry numbers 5 Re: Question about running out of queue entry numbers  Record not current Re: Record not current" Show System (memory use) question.& Re: Show System (memory use) question." Re: Stockholm Exchange OM and VMS?" Re: Stockholm Exchange OM and VMS? Re: Sun "uptime" belly laugher Re: Sun "uptime" belly laugher Re: TCP/IP and load balancing  Re: VAX emulator vt520 music question Re: vt520 music question Re: What does DCPS really do ?  F ----------------------------------------------------------------------  # Date: Mon, 23 Oct 2000 18:28:10 GMT  From: zhoub@my-deja.com % Subject: Re: ">>>" what is this mode? ) Message-ID: <8t1vvf$csh$1@nnrp1.deja.com>    many thanks to all your reply!  : Yes, I had to reboot the machine, a lesson learned though,   Ben     ) In article <8t1ljl$35n$1@nnrp1.deja.com>,    zhoub@my-deja.com wrote: > Hi,  > F > during a session, I accidentally hit some keys and entered a command$ > line >>>, could not get out of it. > C > Can any VMS expert tell me what this is and how to get out of it?  > " > thanks a looooot for your reply. >  > Ben  > ( > Sent via Deja.com http://www.deja.com/ > Before you buy.  >     & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  % Date: Mon, 23 Oct 2000 16:53:11 -0700 5 From: "cstranslations" <cstranslations@email.msn.com> . Subject: Re: $ show printer => %cli-f-syntax ?) Message-ID: <#TTUEyUPAHA.324@cpmsnbbsa09>   6 John Santos <john.santos@verizon.net> wrote in message8 news:MPG.145dc127a700c8ce989684@news.bellatlantic.net...H > In article <uq0UaWGPAHA.254@cpmsnbbsa07>, cstranslations@email.msn.com	 > says...  > K > This is a known problem caused by the ECO VMS721_UPDATE-V0100.  According > > to the DIA article, contact Compaq support for a workaround.  0 In that case can I take the opportunity to rant?  J Wull I be damed Cleetus. vms721_update-v0100 don't fux wha it a suppose to= and it done broke some stuff that wazn't broke to begin with.    I'll stop ranting now.  - As someone did point out (off the news group)   %   $ set message sys$message:CLIUTLMSG    $ say f$message(%x0078B5BD) 1   %SHOW-?-ACME_SRV_LINE_0,    Logging status: !AS   I > I think it is caused by a mismatch between SET.EXE and DCLTABLES.  I am F > surprised it has taken this long to fix.  Maybe not many people have$ > parallel printers on their Alphas?  0 I figured there was a problem along those lines.  K In any event this is a hobbyist system so unless I go out and buy a support E contract I doubt Compaq support is going to want to talk to me. Maybe J there's an ECO I can down load hot off the presses? But then at the momentI I'd rather spend the two days or so that it would take to wipe the system L disk, install 6.2, and get that configured (for the way we're batting here).L Maybe they'll sell me $3 worth of cable with one end that will plug into theH parallel port on the 200 4/233  a MMJ6 on the other end to plug into theI LA70's serial port (for about $90 bucks) if such a thing exists. I better A stop at this point as I sense I'm getting a bit overly sarcastic.   J Guess it's time to dig the I/O Users Manual out of the closet and write my* own set printer and show printer commands.   Joe    ------------------------------  % Date: Mon, 23 Oct 2000 16:49:12 -0500 # From: "Mark E. Levy" <mark@fsi.net> 5 Subject: AlphaServer 2100 upgrade from 4/233 to 5/250 / Message-ID: <sv9cipob0j916d@corp.supernews.com>   H I'm upgrading an Alphaserver 2100 from two 4/233 CPUs to two 5/250 CPUs.J I'll probably have to change the firmware from the EV4 to the EV5 version.  , Is there anything else I need to know about?   TIA,   --E ---------------------------------------------------------------------  Mark E. Levy, President  FSINet, Inc. 800-827-6085 x202  847-753-6832 fax www.fsi.net  mark@fsi.netE ---------------------------------------------------------------------    ------------------------------   Date: 23 Oct 2000 22:50:40 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)9 Subject: Re: AlphaServer 2100 upgrade from 4/233 to 5/250 6 Message-ID: <8t2fc0$rjk$2@mailint03.im.hou.compaq.com>  U In article <sv9cipob0j916d@corp.supernews.com>, "Mark E. Levy" <mark@fsi.net> writes: I :I'm upgrading an Alphaserver 2100 from two 4/233 CPUs to two 5/250 CPUs. K :I'll probably have to change the firmware from the EV4 to the EV5 version.  : - :Is there anything else I need to know about?   H   You'll need an OpenVMS version with EV5 (or later) support.  (Duh. :-)J   Depending on what widgets are installed in the system, you will need at     least V6.2 and possibly later.  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 23 Oct 2000 19:53:40 -0500 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> 9 Subject: Re: AlphaServer 2100 upgrade from 4/233 to 5/250 - Message-ID: <39F4DD94.13ECB6E7@earthlink.net>    Hoff Hoffman wrote:  > W > In article <sv9cipob0j916d@corp.supernews.com>, "Mark E. Levy" <mark@fsi.net> writes: K > :I'm upgrading an Alphaserver 2100 from two 4/233 CPUs to two 5/250 CPUs. M > :I'll probably have to change the firmware from the EV4 to the EV5 version.  > : / > :Is there anything else I need to know about?  > J >   You'll need an OpenVMS version with EV5 (or later) support.  (Duh. :-)  D Well, actually it's a Tru64 box. On power up, the box hangs with theG front panel display reading "Starting CPU 0". We were wondering if this F is a firmware issue (EV4 Vs. EV5) or what we might be looking at here.  : Neither Mark nor I had expected this. We're kinda stumped.   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  % Date: Mon, 23 Oct 2000 20:35:44 -0500 ) From: "John E. Malmberg" <wb8tyw@qsl.net> 9 Subject: Re: AlphaServer 2100 upgrade from 4/233 to 5/250 / Message-ID: <sv9pnvftijrdae@corp.supernews.com>   B "David J. Dachtera" <djesys.nospam@earthlink.net> wrote in message' news:39F4DD94.13ECB6E7@earthlink.net...  > Hoff Hoffman wrote:  > > B > > In article <sv9cipob0j916d@corp.supernews.com>, "Mark E. Levy" <mark@fsi.net> writes:G > > :I'm upgrading an Alphaserver 2100 from two 4/233 CPUs to two 5/250  CPUs. F > > :I'll probably have to change the firmware from the EV4 to the EV5 version. > > : 1 > > :Is there anything else I need to know about?  > > L > >   You'll need an OpenVMS version with EV5 (or later) support.  (Duh. :-) > F > Well, actually it's a Tru64 box. On power up, the box hangs with theI > front panel display reading "Starting CPU 0". We were wondering if this H > is a firmware issue (EV4 Vs. EV5) or what we might be looking at here. > < > Neither Mark nor I had expected this. We're kinda stumped.  J Can the backplane for your Alphaserver 2100 support the higher speed CPUs?  L I would verify that the two CPU boards are of the same ECO revision and have( the same amount of cache memory on them.  K I would also try them one at a time, as if one of the processors is bad, or D you have a mismatch in the amount of onboard cache, it may cause the symptoms you are seeing.  K Also the insertion of an Alphaserver 2100 memory and CPU cards require that H firm and even pressure be placed all across the top of the board to makeI sure it is seated.  If you do not do this, the CPU board may malfunction. > Sometimes it will work for a few hours before it malfunctions.  J If this is a pedestal model, while it is down for maintenance, I recommendI removing the right side of the cabinet and inspecting the power supplies.  Dust tends to collect there.   -John  wb8tyw@qsl.network   ------------------------------  % Date: Mon, 23 Oct 2000 20:59:42 -0500 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> 9 Subject: Re: AlphaServer 2100 upgrade from 4/233 to 5/250 - Message-ID: <39F4ED0E.665C4E04@earthlink.net>    "John E. Malmberg" wrote:  [snip]L > Can the backplane for your Alphaserver 2100 support the higher speed CPUs?  ' Is there an easy way to determine this?    N > I would verify that the two CPU boards are of the same ECO revision and have* > the same amount of cache memory on them. > % > I would also try them one at a time    We did that - no schmae.   L > If this is a pedestal model, while it is down for maintenance, I recommendK > removing the right side of the cabinet and inspecting the power supplies.  > Dust tends to collect there.   Thanx for that note...   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  # Date: Tue, 24 Oct 2000 02:43:47 GMT ( From: Terry Kennedy <terry@gate.tmk.com>9 Subject: Re: AlphaServer 2100 upgrade from 4/233 to 5/250 ' Message-ID: <G2wy8z.LK8@spcuna.spc.edu>   7 David J. Dachtera <djesys.nospam@earthlink.net> writes: F > Well, actually it's a Tru64 box. On power up, the box hangs with theI > front panel display reading "Starting CPU 0". We were wondering if this H > is a firmware issue (EV4 Vs. EV5) or what we might be looking at here. > < > Neither Mark nor I had expected this. We're kinda stumped.  K   I've never done this, but there are apparently some funky things you need I to do with the firmware before swapping the CPU modules, or the box won't J start. The gorey details are found in Appendix H of the AS2100A/2x00 firm- ware release notes, at: a ftp://gatekeeper.dec.com/pub/Digital/Alpha/firmware/readmes/v5.8/doc/alpha2100_v53_fw_relnote.pdf   4         Terry Kennedy             http://www.tmk.com5         terry@tmk.com             Jersey City, NJ USA    ------------------------------  # Date: Tue, 24 Oct 2000 01:24:42 GMT * From: Alan E. Feldman <alan48@my-deja.com>( Subject: Re: best way of deleting files?) Message-ID: <8t2ocm$1tf$1@nnrp1.deja.com>   + In article <39EB88E5.B78C4B6@videotron.ca>, 0   JF Mezei <jfmezei.spamnot@videotron.ca> wrote:@ > Since the "delete files" topic does come up now and then, I am wondering if > this would be possible:  > G > Get a list of FILE IDs to be deleted. Then delete the directory file,  and thenD > delete individual files by file_id ? That would remove the need to
 update the% > directory file with every deletion.  > 3 > Is this possible ? Is this how DFU does its job ?   7 Yes. Yes, but in the opposite order. From DFU's manual:   A First all entries of a directory are deleted without removing the D directory entry [I assume this means resetting the bits in the index? file bitmap (in INDEXF.SYS) that correspond to the files in the F directory]; this saves a lot of unnecessary directory updates. FinallyG the directory file itself is deleted, unless the new /KEEP qualifier is  used.    [end of quote]  @ While this is much faster than DELETE, you'll have a mess if you  interrupt it before it finishes! -- Disclaimer: JMHO Alan E. Feldman  alan48  &-)  dellnet.com     & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  % Date: Mon, 23 Oct 2000 16:03:59 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> 0 Subject: Re: Clsutering, What does it mean??????, Message-ID: <39F499A7.809B2A9D@videotron.ca>   re: advantages of clustering  M It makes disk an tape devices of each machine  available to other machines in J the cluster. The disk interface is highly efficient and "complete". (locksK etc). If one node accesses a record in an indexed file, that record appears ) locked to all other nodes on the cluster.   I However, performance is enhanced because most of the work is done by your K node, and not the node that is physically hosting the drive. (this is where N there is a big difference with NFS or other file servers where the file serverL is the one that does most of the work, so the more nodes that connect to it,- the more overloaded the file server becomes).   K From a system management point of view, you can configure the system with a M single authorization file. So you can login on either machine and have access 2 to the same privileges and files and applications.  G From a load balancing point of view, you can setup your batch queues to K properly distribute the load. So if you are on node-A, you can submit a job M that will execute on Node-B if the later is not busy. Similarly, you can have N your print queues all shared. (although this is not too different from PC LANs1 that share print queues at the one server level).   K The tight integration of the disk drives allows you to shadow drives across L nodes. This means that node-1 would have an exact copy of the drive residingG on Node-2 and both can access/update the drive as they wish and changes M automatically sent to the drive on the other node. If one node goes down, the + drive remains accessible to the other node.   N Clusters also aloow you to create a cluster alias, a single node name that canK be used to connect to either of the machines. There is load balancing stuff M that give heavyly loaded nodes less of a chance of receiving new connections.   N On the surface, clustering appears to give you about the same stuff as PC LANsL do. But when you look a bit deeper, it has some key elements missing from PCN LANS (such as distributed locks) that allow VMS cluster to go well beyond whatN PC lans can do. And clusters are not dependent on a single central server that( acts as print/file server as do PC lans.  H And lastly, because of these added "behind the scenes" capabilities, theM clustering allows you to build disaster tolerant systems where a node located I in another building will continue to function after the first building is ! destroyed by wild giant termites.    ------------------------------  % Date: Mon, 23 Oct 2000 13:06:52 -0700 / From: Terry Marosites <TMarosites@unitedad.com>  Subject: F$GETQUI ON ALAPHA M Message-ID: <1137A4A23A51D311B2D600105A1D5213026FDFA0@seantexch.unitedad.com>   
 Hello all,  ; What is wrong with the file spec command, it worked before?   2 $ say f$getqui("DISPLAY_ENTRY","LOG_SPECIFICATION"  ,6274,"FREEZE_CONTEXT,ALL_JOBS")5 SEAALP$DKD201:[BACKMGR.LOG]00-10-23_DAILY_BACKUP.LOG;   3 $ say f$getqui("DISPLAY_ENTRY","FILE_SPECIFICATION"h  ,6274,"FREEZE_CONTEXT,ALL_JOBS")2 %JBC-F-INVITMCOD, invalid item code or option code   Thanks Terry     ------------------------------  # Date: Mon, 23 Oct 2000 23:44:44 GMT/ From: jbecker@ui.urban.org Subject: Re: F$GETQUI ON ALAPHA0) Message-ID: <8t2ihb$tkg$1@nnrp1.deja.com>o  
 In articleB <1137A4A23A51D311B2D600105A1D5213026FDFA0@seantexch.unitedad.com>,2   Terry Marosites <TMarosites@unitedad.com> wrote: > Hello all, >,= > What is wrong with the file spec command, it worked before?y >u4 > $ say f$getqui("DISPLAY_ENTRY","LOG_SPECIFICATION"" > ,6274,"FREEZE_CONTEXT,ALL_JOBS")7 > SEAALP$DKD201:[BACKMGR.LOG]00-10-23_DAILY_BACKUP.LOG;e >a5 > $ say f$getqui("DISPLAY_ENTRY","FILE_SPECIFICATION"R" > ,6274,"FREEZE_CONTEXT,ALL_JOBS")4 > %JBC-F-INVITMCOD, invalid item code or option code  5 I believe you're mis-remembering your previous usage.n  B First, you'd use DISPLAY_ENTRY with the WILDCARD flag to establishF context. Second, you'd use DISPLAY_FILE to get the FILE_SPECIFICATION.E To cover the general case, use DISPLAY_FILE repeatedly until the filei7 spec is null, indicating no further files in the entry.u  ( Here's your example with my adjustments:4 $ say f$getqui("DISPLAY_ENTRY", "LOG_SPECIFICATION", 6274, "WILDCARD,ALL_JOBS")A $ say f$getqui("DISPLAY_FILE", "FILE_SPECIFICATION",, "ALL_JOBS")s  C You don't need the entry number for the DISPLAY_FILE because you'vei already established a context.  F Going by your example, I'm thinking you might need some explanation ofB FREEZE_CONTEXT. If you leave it out, f$getqui advances to the nextF instance, in context, of whatever you're looking at (the next queue ifC it's DISPLAY_QUEUE, the next job if it's DISPLAY_JOB, etc.). If you B include FREEZE_CONTEXT, f$getqui stays on the same instance as theE previous call, in context. (If there was no previous call in context, 6 FREEZE_CONTEXT still lets you see the first instance.)  C In the DISPLAY_FILE above, using FREEZE_CONTEXT on the DISPLAY_FILEMD would work once; it would get you the first file spec in the job. IfF you looped until you got a null file spec though, FREEZE_CONTEXT wouldB cause you trouble. That is, you'd forever get the file spec of theD first file in the job. The only way to advance to the next file specA (or to get the null string at the end) is to omit FREEZE_CONTEXT.m   --
 Jim Becker+ The Urban Institute (http://www.urban.org/)i7 Encompass ESILUG (http://eisner.decus.org/lugs/esilug/)     & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  % Date: Tue, 24 Oct 2000 13:04:47 +1300 " From: Bill Eaton <fozzie@fp.co.nz>1 Subject: Re: FS microvax 3100-85, 128mb, 6gb, 8mm-( Message-ID: <39F4D21F.E109E4B3@fp.co.nz>   Bill Eaton wrote:t   > Available ex Auckland:A > Microvax 3100-85, 128mb memory, 2x 1.3GB disks, 2x 2.0GB disks,eF > vt420 console, TTi8510 tape (exabyte 8500 compatible).  VMS license." > Bill Eaton email fozzie@fp.co.nz  " Following up own message, sorry :(  2 In answer to some questions, the full details are:   Microvax 3100 model 85,c 128MB ECC memory, 
 RRD42 CD-ROM,w VT420 console, 2 x RZ58 disks (1.3GB each),$ 2 x Generic SCSI disks (2.0GB each), VMS license is unlimited users,a; Compaq expect a fee for registering transfer of the license " (NZ$250 as at sometime last year),D 8MM tape drive can be regarded as optional, capacity is about 4.5GB,/ VMS version currently installed is VMS 5.5-2H4.t  0 If anyone has a notion of how much (if anything)( this might be worth, please let me know!   tia   
 Bill Eaton   ------------------------------  # Date: Mon, 23 Oct 2000 18:27:22 GMT * From: Alan E. Feldman <alan48@my-deja.com> Subject: Re: Galaxy doubt ) Message-ID: <8t1vtv$crg$1@nnrp1.deja.com>.  ) In article <8t1smd$9nl$1@nnrp1.deja.com>,t.   Craig A. Berry <calepine@my-deja.com> wrote:8 > In article <8t1o13$n6t$1@mailint03.im.hou.compaq.com>,( >   hoffman@xdelta.zko.dec.nospam wrote: > ? > >   Yes, written American English is a rather interesting and 	 difficultrH > >   language to master.  (Difficult for even native speakers to truely > >   master, I might add.)r > A > ... as evidenced by the split infinitive and misspelling of thetD > word "truly" in that last sentence ;-).  (Yes, that was a sentence@ > fragment, and I'm not sure I spelled "misspelling" correctly.)  D THERE'S NOTHING WRONG WITH SPLITTING AN INFINITIVE. Check the FAQ at www.grammarlady.com, e.g.    Example:  - ...to boldly go where no man has gone before.a  G The alternatives sound ridiculous. Putting boldly between "to" and "go"eC puts the emphasis on it. Similarly, "to go boldly" puts emphasis on  "go".i   -- Disclaimer: JMHO Alan E. Feldman- alan48  &-)- dellnet.com,    & Sent via Deja.com http://www.deja.com/ Before you buy.n   ------------------------------   Date: 23 Oct 2000 19:49:29 GMT8 From: hammond@not@peek.ppb.cpqcorp.net (Charlie Hammond) Subject: Re: Galaxy doubtt6 Message-ID: <8t24o9$pko$1@mailint03.im.hou.compaq.com>  * In article <8t1vtv$crg$1@nnrp1.deja.com>, , Alan E. Feldman <alan48@my-deja.com> writes: ..E >THERE'S NOTHING WRONG WITH SPLITTING AN INFINITIVE. Check the FAQ at- >www.grammarlady.com, e.g. >y	 >Example:  >S. >...to boldly go where no man has gone before. >wH >The alternatives sound ridiculous. Putting boldly between "to" and "go"D >puts the emphasis on it. Similarly, "to go boldly" puts emphasis on >"go".  C IMHO splitting an infinitive should be avoided when it can be done c without becoming too awkward.   E In the case in point, if you want to emphasise "boldy" you should sayoD "boldy to go".  Personally, I think that "to go boldly" reads betterE than "to boldy go" -- but in the overal context  "to boldly go" scans3G better, so I grant poetic license.  But none of the three is bad enoughoI to be called a syntax error -- more a matter of opinion.  Writing is morea art than science.n   -- OK     Charlie Hammond -- Compaq Computer Corporation -- Pompano Beach  FL USAiF          (hammond@peek.ppb.cpqcorp.net -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------  % Date: Mon, 23 Oct 2000 21:23:50 -0000f- From: wspencer@ap.nospam.org (Warren Spencer)- Subject: Re: Galaxy doubtc/ Message-ID: <sv9b369vdqnsdf@news.supernews.com>   ; alan48@my-deja.com (Alan E. Feldman) wrote in <8t1vtv$crg$1p  
 -- snip --  E >THERE'S NOTHING WRONG WITH SPLITTING AN INFINITIVE. Check the FAQ atm >www.grammarlady.com, e.g. >v  
 -- snip --  7 This is off-topic banter up with which I shall not put.    ws   -- i3 << What if there were no hypothetical questions? >>5   ------------------------------  % Date: Mon, 23 Oct 2000 17:43:02 -0200E) From: fabio_compaq@ep-bc.petrobras.com.brs Subject: Galaxy QUESTIONS L Message-ID: <OFED880D23.2CA7EDDC-ON83256981.006B70B6@ep-bc.petrobras.com.br>  
 In articleA <OF8952D543.721D1211-ON83256981.0051820F@ep-bc.petrobras.com.br>,e+ fabio_compaq@ep-bc.petrobras.com.br writes:o :r: :I have "QUESTIONS"  about the Galaxy configuration:   :-)   :Of course  I'll need twoeF :Fibre Channel  adapters (one per instance) to connect the disk array.  C   Correct.  Multi-host SCSI and Fibre Channel can both be used as afD   storage interconnection within an OpenVMS Cluster, but neither canE   serve as a cluster communications interconnection.  In other words,iC   you can have as many or as few storage interconnections within anfG   OpenVMS Cluster as you want, but you need at least one communicationsrE   interconnection.  Within an OpenVMS Cluster operating across two or-D   more instances within an OpenVMS Galaxy configuration, you can use+   SMCI as your communications interconnect.A  H What means the FC adapter in each instance must see all the disks of the two instances ok ?E I am thinking in the case of using the EMC Symmetrix. Each FC adaptereG is for a group of disks (volumes). I am not sure if two FC adapters can . see all the disks - as a Storage Area Network.   Regards, Fabio Cardoso  * PS: My english is not really perfect ! :-)   ------------------------------  # Date: Mon, 23 Oct 2000 19:16:21 GMT / From: "John Nixon" <jorlnixon@worldnet.att.net>e" Subject: Gigabit Ethernet questionE Message-ID: <980J5.3738$UL.236569@bgtnsc07-news.ops.worldnet.att.net>i  D I have ordered some PCI gigabit ethernet adapters for a GS140 and anI Alphaserver 2100a (VMS 7.2-1).  We have had a communications failure (thenJ human kind) and I was under the impression we had gigabit capability. I amF told we do, but not enough.  We will have to order new modules for the- switches and run some new fiber optic cables.h  K I was then asked if Compaq will provide the new gigabit over copper that is L coming.  Supposedly that will be cheaper and easier for us to implement.  InJ my naievity, I was not aware that Compaq's gigabit ethernet required fiberJ optic cables.  The product description says it runs over existing ethernet
 technologies.t  L If anyone understands my confusion, can you shed some light?  (I sure wish I5 had a good ole S&O catalog to look this stuff up in).    ------------------------------  % Date: Mon, 23 Oct 2000 20:46:25 +0100e$ From: Andy Burns <andy@burns.uk.net>& Subject: Re: Gigabit Ethernet question8 Message-ID: <kb59vscjv0f92bgg7mkkbrfcg8ajvfrgpo@4ax.com>   John Nixon wrote:i  C >I sure wish I had a good ole S&O catalog to look this stuff up in.t   or even a DECdirect !    -- e
 Andy Burns   ------------------------------    Date: 23 Oct 2000 15:39:36 -0500- From: Graham Allan <allan@mnhep1.hep.umn.edu>0& Subject: Re: Gigabit Ethernet question0 Message-ID: <w53wvez8f7b.fsf@lanark.spa.umn.edu>  1 "John Nixon" <jorlnixon@worldnet.att.net> writes:g  F > I have ordered some PCI gigabit ethernet adapters for a GS140 and anK > Alphaserver 2100a (VMS 7.2-1).  We have had a communications failure (theCL > human kind) and I was under the impression we had gigabit capability. I amH > told we do, but not enough.  We will have to order new modules for the/ > switches and run some new fiber optic cables.t > M > I was then asked if Compaq will provide the new gigabit over copper that iswN > coming.  Supposedly that will be cheaper and easier for us to implement.  InL > my naievity, I was not aware that Compaq's gigabit ethernet required fiberL > optic cables.  The product description says it runs over existing ethernet > technologies.   J Asking more or less the same question in the Tru64 world recently revealedG that Compaq are currently testing gigabit over copper adaptors. I wouldiG guess/hope that if they plan to support this for Tru64, they are fairlyf likely to do so for VMS.   Graham -- aI -------------------------------------------------------------------------o: Graham Allan - I.T. Manager - gta@umn.edu - (612) 624-50409 School of Physics and Astronomy - University of Minnesota.I -------------------------------------------------------------------------D   ------------------------------  % Date: Mon, 23 Oct 2000 16:38:04 -0500k* From: WILLIAM WEBB <WWEBB1@email.usps.gov>& Subject: RE: Gigabit Ethernet question- Message-ID: <0033000007142581000002L012*@MHS>   H =0A     Sitting here looking at S&Os 4/93, 1/95, 5/96, 11/97, 4/98, 1/9= 9m  ;      It's really funny how often folks borrow the old ones.   H      Also, the OPEN DECconnect Applications Guide from Feb. 1993 gets l= ooked in;      quite a bit for its cabling and connector information.         WWWebb,   -----Original Message-----/ From: Info-VAX-Request@Mvb.Saic.Com at INTERNET1& Sent: Monday, October 23, 2000 3:54 PM6 To: Webb, William W; Info-VAX@Mvb.Saic.Com at INTERNET& Subject: RE: Gigabit Ethernet question     John Nixon wrote:e  C >I sure wish I had a good ole S&O catalog to look this stuff up in.    or even a DECdirect !-   -- Andy Burns=-   ------------------------------  % Date: Tue, 24 Oct 2000 01:23:43 -0400a2 From: rdeininger@mindspring.com (Robert Deininger)# Subject: Re: Handling oddball diskspL Message-ID: <rdeininger-2410000123430001@user-2ive68i.dialup.mindspring.com>  f In article <39F361CC.D674A6DB@earthlink.net>, "David J. Dachtera" <djesys.nospam@earthlink.net> wrote:    . > Does the term "fallback" mean anything here? > J > That is, if ddcu: says it supports (k,r,x) but doesn't act like it does,I > or logs errors on the attempt, fall back to (lowest common denominator) B > mode. If it still logs errors, then (MntVerify) with profuse andI > profusely verbose ERRLOG entries about what failed, what the driver did'D > to attempt to compensate, and the subsequent errors leading to the > MntVerify condition.  I Err, I think DKDRIVER already tries to do sane fallback.  But VMS doesn'tEK want to use a disk when it sees evidence that it DOESN'T work.  Those other J operating systems that "work" with cheapo disks have much lower standards.) They don't care if they squish your data.   I At some point, if dkdriver get conflicting information about a device, itsK has to rely on a specially-programmed rule, or it has to give up.  Guessingd' is not an option when data is at stake.t  L I have to agree with Glenn.  Dkdriver has gotten MUCH more versatile lately.N Sometimes we need to be clubbed over the head to get us to upgrade to a recent= version of VMS.  With SCSI devices, it's definitely worth it.?  Asking dkdriver to work properly with some of the trash disks on the market is just one step away from asking that it work when someone sticks a slice of buttered toast into a drive bay.  Some disks have more in common with buttered toast than they do with the SCSI standard.a  J > Can either of you list the criteria (those portions of the SCSI "spec.")H > to which DKDRIVER/MKDRIVER expect strict adherence, and how to inquire9 > of a vendor whether their device(s) meet such criteria?h  M If you ask a drive vendor, I'm sure you'll get an answer.  I wouldn't bank ons it being correct, however.   -- t Robert Deininger rdeininger@mindspring.comt   ------------------------------  # Date: Tue, 24 Oct 2000 03:40:03 GMTm From: lbohan9350@my-deja.com+ Subject: Re: hex numbers with CLD + $NUMBERi) Message-ID: <8t30ai$80t$1@nnrp1.deja.com>n  ) In article <8sqmdj$3g1$1@nnrp1.deja.com>, *   moi_is_me <moi_is_me@my-deja.com> wrote:  - >what about show proc/id=xxx ... where xxx isy) >a hex number, no radix is specified hereh  -  i believe that's because SHOW PROC/ID=<blah> 1  takes <blah> as a value, with $type unspecified;o  %  $ sh proc/id=xyz ! not caught by DCLi,   %SHOW-E-INVQUAVAL, value 'XYZ' invalid for    /IDENTIFICATION qualifier  .  (as opposed to %DCL-W-NUMBER, invalid numeric   value - supply an integer)  ,  maybe find Joe Meadows' VERB tool, and look&  at the generated *.cld for DCLTABLES,*  a good reference for *.CLD usages/idioms.  (  ftp://ftp.wku.edu/vms/fileserv/VERB.ZIP    define syntax SHOW_PROCESSi    ...)    qualifier IDENTIFICATION, nonnegatableo       value (required)    ...    & Sent via Deja.com http://www.deja.com/ Before you buy.o   ------------------------------  # Date: Tue, 24 Oct 2000 03:40:04 GMTt From: lbohan9350@my-deja.com+ Subject: Re: hex numbers with CLD + $NUMBER ) Message-ID: <8t30ak$80v$1@nnrp1.deja.com>n  ) In article <8sqmdj$3g1$1@nnrp1.deja.com>,g*   moi_is_me <moi_is_me@my-deja.com> wrote:  - >what about show proc/id=xxx ... where xxx ish) >a hex number, no radix is specified here(  -  i believe that's because SHOW PROC/ID=<blah> 1  takes <blah> as a value, with $type unspecified;s  %  $ sh proc/id=xyz ! not caught by DCLr,   %SHOW-E-INVQUAVAL, value 'XYZ' invalid for    /IDENTIFICATION qualifier  .  (as opposed to %DCL-W-NUMBER, invalid numeric   value - supply an integer)  ,  maybe find Joe Meadows' VERB tool, and look&  at the generated *.cld for DCLTABLES,*  a good reference for *.CLD usages/idioms.  (  ftp://ftp.wku.edu/vms/fileserv/VERB.ZIP    define syntax SHOW_PROCESSo    ...)    qualifier IDENTIFICATION, nonnegatablee       value (required)    ...    & Sent via Deja.com http://www.deja.com/ Before you buy.0   ------------------------------  # Date: Mon, 23 Oct 2000 23:01:06 GMTnL From: winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr")+ Subject: HP4050 vs HP4050TN when using DCPSX8 Message-ID: <009F2092.EA0C1BF0@SSRL04.SLAC.STANFORD.EDU>  	 VMSers --   A Environment: Alphaserver 2100 5/300, Multinet 4.2A-X, VMS 7.2-1, O$ same problems with DCPS 1.7 and 1.8.  N For about a year I've had an HP4050 which printed happily via DCPS, setup like" so (clipped from DCPS$STARTUP.COM)* ------------------------------------------% $ @sys$startup:DCPS$execution_queue -2>  bldg274hp4050 -                   ! P1 - Execution queue name?  "IP_RawTCP/bldg274hp4050.slac.stanford.edu:9100" -        ! P2TL       DCPS_LIB -                        ! P3 - Logical name for library(ies)G       ""-                               ! P4 - Default queue parameters"O       "/separate=(noreset,flag,notrailer)" -    ! P5 - Default queue qualifiersLI       ""-                               ! P6 - Communication speed(serialS<         -                               !      devices only)* ------------------------------------------  L Now the people in a remote building have a new HP4050TN(?); they swear to meH that this just the same as the other 4050 except that it has a duplexingK option.  So I cut and pasted the setup from the working printer and createdD a setup, like so:d  N ------------------------------------------------------------------------------% $ @sys$startup:DCPS$execution_queue - <  los3_hp4050 -                   ! P1 - Execution queue name=  "IP_RawTCP/los3-hp4050.slac.stanford.edu:9100" -        ! P2IL       DCPS_LIB -                        ! P3 - Logical name for library(ies)G       ""-                               ! P4 - Default queue parameters,O       "/separate=(noreset,flag,notrailer)" -    ! P5 - Default queue qualifiers I       ""-                               ! P6 - Communication speed(seriale<         -                               !      devices only)N ------------------------------------------------------------------------------  K Now when anybody tries to print to this printer, the DCPS cover sheet comessK out, and nothing else.  (So I've got the right node name and we can talk to K the printer, but it won't do anything useful.)  I tried upgrading DCPS fromo5 1.7 to 1.8; doesn't seem to have made any difference.b  M Is this printer sufficiently different from other 4000s to be an unrecognizeds0 printer?  Is there something hosed in the setup?  K Anyway, here's what showed up on my screen when I tried to print to it justp now:H ------------------------------------------------------------------------  8 SYSMGR>print/que=los3_hp4050/param=(sides=2,number_up=4)$ sys$startup:dcps$startup.com /notifyF Job DCPS$STARTUP (queue LOS3_HP4050, entry 203) started on LOS3_HP4050 SYSMGR>-  % %DCPS-I-USERDATA, @PJL USTATUS DEVICE,F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050r SYSMGR>-   %DCPS-I-USERDATA, CODE=10023F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050i SYSMGR>0  * %DCPS-I-USERDATA, DISPLAY="PROCESSING JOB"F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050l SYSMGR>a   %DCPS-I-USERDATA, ONLINE=TRUEpF -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050v SYSMGR>o   %DCPS-I-USERDATA, <0C> -LPS-I-IDLE, Idle F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050M SYSMGR>   % %DCPS-I-USERDATA, @PJL USTATUS DEVICE F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050e SYSMGR>n   %DCPS-I-USERDATA, CODE=10001F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050  SYSMGR>o  ! %DCPS-I-USERDATA, DISPLAY="READY"bF -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050  SYSMGR>o   %DCPS-I-USERDATA, CODE2=10024mF -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050t SYSMGR>n  * %DCPS-I-USERDATA, DISPLAY2="DATA RECEIVED"F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050n SYSMGR>i   %DCPS-I-USERDATA, ONLINE=TRUEfF -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050  SYSMGR>n   %DCPS-I-USERDATA, <0C>% -DCPS-I-USERDATA, @PJL USTATUS DEVICEnF -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050h SYSMGR>n   %DCPS-I-USERDATA, CODE=10023F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050n SYSMGR>   * %DCPS-I-USERDATA, DISPLAY="PROCESSING JOB"F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050o SYSMGR>    %DCPS-I-USERDATA, ONLINE=TRUErF -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050e SYSMGR>d   %DCPS-I-USERDATA, <0C>F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050l SYSMGR>dL %DCPS-I-JOBSTART, Job DCPS$STARTUP (queue LOS3_HP4050, entry 203) started on LOS3_HP4050y SYSMGR>-G SSRL::SYSTEM 15:48:11   (DCL)   CPU=00:00:02.37 PF=2302 IO=2442 MEM=112n SYSMGR>k  % %DCPS-I-USERDATA, @PJL USTATUS DEVICEcF -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050t SYSMGR>v   %DCPS-I-USERDATA, CODE=10023F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050N SYSMGR>V  6 %DCPS-I-USERDATA, DISPLAY="PROCESSING JOB FROM TRAY 3"F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050n SYSMGR>o   %DCPS-I-USERDATA, ONLINE=TRUEnF -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050  SYSMGR>l   %DCPS-I-USERDATA, <0C>3 -DCPS-I-SHEETSIZE, Current sheet size is lettertraytF -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050o SYSMGR>t  % %DCPS-I-USERDATA, @PJL USTATUS DEVICEoF -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050c SYSMGR>t   %DCPS-I-USERDATA, CODE=10001F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050  SYSMGR>   ! %DCPS-I-USERDATA, DISPLAY="READY" F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050  SYSMGR>(   %DCPS-I-USERDATA, CODE2=10024eF -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050l SYSMGR>o  * %DCPS-I-USERDATA, DISPLAY2="DATA RECEIVED"F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050  SYSMGR>R   %DCPS-I-USERDATA, ONLINE=TRUE9F -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP40501 SYSMGR>p  7 %DCPS-F-CONTERMINATED, Connection abnormally terminatedIF -DCPS-I-JOB_ID, for job DCPS$STARTUP (queue LOS3_HP4050, entry 203) on LOS3_HP4050 H ------------------------------------------------------------------------  < and then instructions on unholding the job and trying again.   What should I do?    Thanks,    -- Alan0    O ===============================================================================s0  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDUM  Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056eM  Physical mail to: SSRL -- SLAC BIN 69, PO BOX 4349, STANFORD, CA  94309-0210hO ===============================================================================w   ------------------------------  % Date: Mon, 23 Oct 2000 22:25:41 -0500 / From: Chris Scheers <chris@applied-synergy.com>a> Subject: Re: PDF Generator for OpenVMS (was PDF under OpenVMS)O Message-ID: <0F641D55A6047DE9.9D9659CB34F20765.DD187BF06CB6FF7E@lp.airnews.net>    JF Mezei wrote:  > M > I know I will eventually have to migrate to ghostscript since I am not eveneJ > sure Digital remembers it ever sold that product and I doubt it has been > ported to Alpha. > L > This is why I feel that the VMS group should pressure Adobe into releasingK > Distiller on VMS at the very least. It would make for a great utility foraP > on-the fly/automated PDF document production to be made instantly available onP > an intra/internet. Right now, documents produced on VMS have to be exported toJ > a MAC or worse, a WIndows PC to run Distiller and then sent back to VMS.    H Applied Synergy is currently soliciting the features that should be in a7 PDF generator for OpenVMS.  Suggestions can be sent to:-    	suggestions@applied-synergy.com  G -----------------------------------------------------------------------g$ Chris Scheers, Applied Synergy, Inc.  C Voice: 817-237-3360            Internet: chris@applied-synergy.com r   Fax: 817-237-3074t   ------------------------------   Date: 23 Oct 2000 12:27:57 PDTT From: Fairfield@SLAC.Stanford.EDU (Ken Fairfield; SLAC: 650-926-2924; FAX: 926-3515) Subject: Re: PDF under OpenVMS3 Message-ID: <vJEVXKMtRA2+@mccdev.slac.stanford.edu>n  - In article <8t0fnl$780@gap.cco.caltech.edu>, e8     mathog@seqaxp.bio.caltech.edu (David Mathog) writes: [...]eI > DCPS has its strong points but working with an arbitrary remote printerdI > isn't one of them.   The old MSAP printer function in Pathworks/Mac wassF > much more reliable, just plug in the PPD, and there was always a PPD             ^^^^^^^^  > available,  and you were done.  H         I think perhaps you chose the  wrong word above.  I'd agree thatH     MSAP was more _flexible_, but I'd strongly disagree that it was moreH     _reliable_.   I  had  nothing but headaches with  MSAP  with  queuesH     constantly getting in a state that I had to _reinitialize_ the queueH     to access the (Appletalk) printer.  Then again, MSAP did nothing forH     printers on TCP/IP, and lpr/lpd "works" but is bare bones  (I  don'tH     fancy  writing  lots  of  Postscript  setup modules to do relativelyH     simple things, like landscape or n-up...I prefer DCPS to do that for     me).           -Ken -- EM  Kenneth H. Fairfield            |  Internet: Fairfield@SLC.Slac.Stanford.Eduo:  SLAC, 2575 Sand Hill Rd, MS 46  |  Voice:    650-926-2924:  Menlo Park, CA  94025           |  FAX:      650-926-3515N  -----------------------------------------------------------------------------B  These opinions are mine, not SLAC's, Stanford's, nor the DOE's...   ------------------------------  % Date: Mon, 23 Oct 2000 22:09:45 -0500e/ From: Chris Scheers <chris@applied-synergy.com>t Subject: Re: PDF under OpenVMSO Message-ID: <381D0079763CB7C3.39B1E1CD3E96B16F.1CDA61D37A9CBCF3@lp.airnews.net>w   JF Mezei wrote:e > + > re: Widthdrawal of DPS support on VMS 7.3w > P > In exchange for dropping display postscript, I beleive that Compaq should haveP > negotiated with Adobe for Adobe to provide an official Adobe PDF reader on VMSD >  (Sorry Chris !), as well as porting the Acrobat Distiller to VMS.  G As I understand it, Adobe's official PDF reader for VMS is the Java PDF/ reader.   B I believe that Applied Synergy can provide a more "VMSish" (?) PDF3 Viewer for OpenVMS than Adobe can.  (Blatant plug!)-  G -----------------------------------------------------------------------a$ Chris Scheers, Applied Synergy, Inc.  C Voice: 817-237-3360            Internet: chris@applied-synergy.com -   Fax: 817-237-3074-   ------------------------------  % Date: Tue, 24 Oct 2000 11:45:53 +1300 9 From: "Antony Wardle" <antony.wardle@nnnoospam.met.co.nz>< Subject: popquestion2 Message-ID: <Y43J5.5218$SF5.107912@ozemail.com.au>    is the pop server multithreaded?  7 If 10 people all access at the same time, what happens?18 Does one person get in, and download 40 emails while the0 other nine people wait around and then time out?  6 We are getting a lot of time outs when we try it here.   Using 4.2 eco4 and 5.0a eco1   cheers   antony   ------------------------------  % Date: Mon, 23 Oct 2000 16:07:35 -0400X- From: JF Mezei <jfmezei.spamnot@videotron.ca>y0 Subject: Re: Press Release from Process Software, Message-ID: <39F49A7F.5E971CF1@videotron.ca>  K > In the agreement with Process, Innosoft will transition certain rights to N > development and responsibility for support of PMDF products on all platforms > to Process Software.  J So Innosoft retains onwership of PMDF then ? Is this because Innosoft with focus solely on SIMS ?  N What sort of freedom with Process have to develop PMDF into whatever they want4 ? Or will PMDF truly remain the base code for SIMS ?   ------------------------------  + Date: Mon, 23 Oct 2000 18:15:38 +0000 (GMT)i, From: Bill McLaughlin <mcbill20@hotmail.com>- Subject: Re: Problem with COMPAQ 9.1GB drivesa5 Message-ID: <LC7-LFD2095LZbuPCHX00000883@hotmail.com>    >-----Original Message-----f5 >From: Warren Spencer [mailto:wspencer@ap.nospam.org] ( >Sent: Monday, October 23, 2000 11:14 AM >To: Info-VAX@Mvb.Saic.Com. >Subject: RE: Problem with COMPAQ 9.1GB drives >e >i6 >hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) wrote in, ><8sqgm8$ha9$1@mailint03.im.hou.compaq.com>: >I > >kH > >In article <F161sE3jK8x3TEXcGwl00008be7@hotmail.com>, Bill McLaughlin! > ><mcbill20@hotmail.com> writes: F > >:Hoff, when I had first posted this problem, you mentioned that youI > >:weren't sure that the 9.1GB drives were supported in AlphaStation 500a& > >:boxes. Did you happen to find out? > >iI > >  AFAIK, no.  AFAIK, these Ultra2 RZ2DC-KA series SCSI disk drives areuG > >  not officially supported within most of (all of?) the older systema > >  enclosures. > > I > >  As I'd mentioned earlier, what you are seeing here could potentiallynJ > >  be caused by cooling that is insufficient for the requirements of the( > >  particular storage widget involved. > > 5 > > --------------------------- pure personal opinionh > > ---------------------------s2 > >   Hoff (Stephen) Hoffman   OpenVMS Engineering  > >   hoffman#xdelta.zko.dec.com > >  > >v >aJ >Are those 7200 rpm or 10000 rpm drives?  If so, Hoff correctly points out! >cooling issues.  Seen it before.  >  >wst >c >--i4 ><< What if there were no hypothetical questions? >> >E >K  K Thank you all for the info. It's much appreciated. Unfortunately, unless I  L want to say with old 2gig drives, I guess I must now purchase the obscenely " expensive Storageworks enclosures.   SET MODE/RANT=ON  M GRRRrrrrrrrrrrrrrrr!  This is SO frustrating. Face it, a 9 gig 7200RPM drive -J isn't exactly leading edge technology and alpha box isn't THAT old. (It's L still under the original warranty.) How difficult is it to build a box with M decent ventilation? It seems like the hardware engineers are in PeeCee mode: mL   "The drives available TODAY are...and surely no one would ever upgrade or M add more..." or "Drive technology won't improve much during the life of this P- box." or "No one will ever need more than..."$  I I just added a 20gig UDMA66 drive to my miserable Billybox for just over AF $100. I understand (and don't really mind) paying extra for the added J reliability of genuine Digital/Compaq parts (that's why this thread isn't L about problems with some generic drive). But, does the differential have to M be so much?  IMHO, the 9.1gig drives are the largest Compaq SCSI drives that /L are anywhere close to reasonable or affordable. But when you add a deskside G Storageworks rack ($500 used, if you're lucky), the $50 fast-wide SCSI pL external cable and then the $70(per drive) Storageworks drive enclosure, it M really adds up. For the same price, you could buy four fast 60gig drives for n	 a peecee!    SET MODE/RANT=OFFg    Well, thanks again for the info.   Bill McLaughlinmI _________________________________________________________________________wI Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.e  D Share information about yourself, create your own public profile at  http://profiles.msn.com.   ------------------------------  + Date: Mon, 23 Oct 2000 18:43:50 +0000 (GMT)v, From: Bill McLaughlin <mcbill20@hotmail.com>- Subject: Re: Problem with COMPAQ 9.1GB drivesd5 Message-ID: <F285nWwAeRaNgEpTX5V00001c5a@hotmail.com>o    Sorry to reply to my own reply--  K Does anyone know if the BA350 box supports these drives or do I need to go  
 with a BA356?u   Thanks.l Bill McLaughlin I _________________________________________________________________________aI Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com..  D Share information about yourself, create your own public profile at  http://profiles.msn.com.   ------------------------------   Date: 23 Oct 2000 21:24:52 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)- Subject: Re: Problem with COMPAQ 9.1GB drivesS6 Message-ID: <8t2ab4$qqk$1@mailint03.im.hou.compaq.com>  d In article <F285nWwAeRaNgEpTX5V00001c5a@hotmail.com>, Bill McLaughlin <mcbill20@hotmail.com> writes:L :Does anyone know if the BA350 box supports these drives or do I need to go  :with a BA356?  G   If a BA350-KA or BA350-SA has backplane H01 or later, it needs to be uG   upgraded to dual-speed fans and with some air baffles.  BA350-KB and "I   BA350-SB normally has the H01 backplane, as should the BA350-JA series.L  D   (The H01 revision of the backplane permits each fan to increase toG   high speed and take over should the other fan fail.  (This ECO dates     back to circa 1993.)  C   The upgrade kit itself is/was the BA35X-MJ upgrade.  This upgrade B   will provide the necessary baffles and a pair of BA35X-MD seriesC   dual-speed fans -- both together will the cooling requirements of-=   typical 7200 RPM series disks (such as the RZ29-VA series).a  G   If you want to load the box with seven 7200 RPM disks, you will need rD   the BA35X-HF 150 watt power supply upgrade -- the 131 watt supply E   found in many enclosures will typically support at most six of the -5   7200 RPM disks (again, such as the RZ29-VA series).-  F   The way to determine the backplane revision for the BA350 series is E   to look at the backplane near the SCSI connectors (JA1/JB1) -- you .G   will have to remove the brick in slot zero to see this.  Next to the  C   slot 0 connector (usually a white 3 by 32 connector) is the part  H   number 5021986-01-H1, and the suffix H1 indicates this backplane will J   accept dual-speed blower.  The earlier revision of the backplane is F1, G   and it is not designed for the dual-speed fans.  All of the BA35X-MD  G   series fans I've seen have big block letters that are visible on the -   back of the fan itself.-  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  + Date: Tue, 24 Oct 2000 01:08:56 +0000 (GMT)d, From: Bill McLaughlin <mcbill20@hotmail.com>- Subject: Re: Problem with COMPAQ 9.1GB drivesf5 Message-ID: <F12046t0OZl87RG700b00002371@hotmail.com>e   >-----Original Message-----g: >From: Hoff Hoffman [mailto:hoffman@xdelta.zko.dec.nospam]' >Sent: Monday, October 23, 2000 3:25 PM  >To: Info-VAX@Mvb.Saic.Com. >Subject: Re: Problem with COMPAQ 9.1GB drives >  >Y >RF >In article <F285nWwAeRaNgEpTX5V00001c5a@hotmail.com>, Bill McLaughlin ><mcbill20@hotmail.com> writes:PL >:Does anyone know if the BA350 box supports these drives or do I need to go >:with a BA356?T >DH >   If a BA350-KA or BA350-SA has backplane H01 or later, it needs to beH >   upgraded to dual-speed fans and with some air baffles.  BA350-KB andK >   BA350-SB normally has the H01 backplane, as should the BA350-JA series.M   What about a BA350-LA ?I  K Also, is there any way to find this documentation at the COMPAQ website? I ,= looked but I didn't see any. I hate to clutter the newsgroup.I  < Also, what's the difference between the BA350 and the BA356?   >tF >   (The H01 revision of the backplane permits each fan to increase toH >   high speed and take over should the other fan fail.  (This ECO dates >   back to circa 1993.) > E >   The upgrade kit itself is/was the BA35X-MJ upgrade.  This upgradeSD >   will provide the necessary baffles and a pair of BA35X-MD seriesE >   dual-speed fans -- both together will the cooling requirements ofu? >   typical 7200 RPM series disks (such as the RZ29-VA series).S >AH >   If you want to load the box with seven 7200 RPM disks, you will needE >   the BA35X-HF 150 watt power supply upgrade -- the 131 watt supply0F >   found in many enclosures will typically support at most six of the7 >   7200 RPM disks (again, such as the RZ29-VA series).2 >AG >   The way to determine the backplane revision for the BA350 series istF >   to look at the backplane near the SCSI connectors (JA1/JB1) -- youH >   will have to remove the brick in slot zero to see this.  Next to theD >   slot 0 connector (usually a white 3 by 32 connector) is the partI >   number 5021986-01-H1, and the suffix H1 indicates this backplane willtK >   accept dual-speed blower.  The earlier revision of the backplane is F1,OH >   and it is not designed for the dual-speed fans.  All of the BA35X-MDH >   series fans I've seen have big block letters that are visible on the >   back of the fan itself.O >H, >  --------------------------- pure personal$ >opinion ---------------------------1 >    Hoff (Stephen) Hoffman   OpenVMS Engineering, >t  * Thank you for the info and quick response.   Bill McLaughlinPI _________________________________________________________________________4I Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.y  D Share information about yourself, create your own public profile at  http://profiles.msn.com.   ------------------------------  # Date: Mon, 23 Oct 2000 17:50:18 GMTP* From: Alan E. Feldman <alan48@my-deja.com>: Subject: Question about running out of queue entry numbers) Message-ID: <8t1ton$ano$1@nnrp1.deja.com>    Hello,  D Suppose your queueing system entry numbers currently range from 1 toE 1000. If all 1000 of them are in use, and another job is submitted to ? the queueing system, the system expands the range, to 1-2000, IME believe. Okay. BUT, I was wondering if there is any safeguard againstA the following scenario:e  D All 1000 numbers are in use. The range is still 1 thru 1000. You runB SHOW ENTRY SOME_JOB and get output that gives the entry number andC shows that it is executing. You then decide that you want to deleteRB this job. But unbeknownst to you, it finishes before you enter the@ appropriate DELETE/ENTRY command. Meanwhile, another user starts> another job that gets the same entry number. Then you run your. DELETE/ENTRY command and delete the wrong job!  B So my question is, does the range of possible entry numbers expandF before all (or the very vast majority) of them are in use, say all but@ 50, or some reasonable percentage, so that the above scenario is, impossible (or at least extremely unlikely)?  D (Note, I don't have hundreds of jobs in my queues at any given time;2 I'm just curious if this could ever be a problem.)   TIA4 -- Disclaimer: JMHO Alan E. FeldmanR alan48  &-)- dellnet.comI    & Sent via Deja.com http://www.deja.com/ Before you buy.4   ------------------------------  % Date: Mon, 23 Oct 2000 18:09:56 +0000t From: SysAdmin <djesys@fsi.net>-> Subject: Re: Question about running out of queue entry numbers' Message-ID: <39F47EF4.DBAFA254@fsi.net>-   "Alan E. Feldman" wrote: >  > Hello, > F > Suppose your queueing system entry numbers currently range from 1 toG > 1000. If all 1000 of them are in use, and another job is submitted to=A > the queueing system, the system expands the range, to 1-2000, I-G > believe. Okay. BUT, I was wondering if there is any safeguard againsto > the following scenario:0 > F > All 1000 numbers are in use. The range is still 1 thru 1000. You runD > SHOW ENTRY SOME_JOB and get output that gives the entry number andE > shows that it is executing. You then decide that you want to deleteoD > this job. But unbeknownst to you, it finishes before you enter theB > appropriate DELETE/ENTRY command. Meanwhile, another user starts@ > another job that gets the same entry number. Then you run your0 > DELETE/ENTRY command and delete the wrong job! > D > So my question is, does the range of possible entry numbers expandH > before all (or the very vast majority) of them are in use, say all butB > 50, or some reasonable percentage, so that the above scenario is. > impossible (or at least extremely unlikely)? > F > (Note, I don't have hundreds of jobs in my queues at any given time;4 > I'm just curious if this could ever be a problem.)   Alan,v  F I've never had a problem with it. Even when entry numbers (on a system> that has only ever had a single queue manager) get up into the five-digit range.a  H In general, I wouldn't worry - entry numbers don't get re-used until theG previous job with that entry number disappears. Unless you "fat finger" H something or just type it wrong, it is unlikely that careful typing will> result in deleting the wrong entry. I usually cut-and-paste inA Reflection, PowerTerm or whatever. (KDE "Konsole" doesn't seem tosH support it, however.) That way I know what I'm entering is what I REALLY want to delete.2   FWIW...    David J. DachteraS   ------------------------------   Date: 23 Oct 2000 19:28:21 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)> Subject: Re: Question about running out of queue entry numbers6 Message-ID: <8t23gl$pft$1@mailint03.im.hou.compaq.com>  V In article <8t1ton$ano$1@nnrp1.deja.com>, Alan E. Feldman <alan48@my-deja.com> writes:E :Suppose your queueing system entry numbers currently range from 1 tohF :1000. If all 1000 of them are in use, and another job is submitted to> :the queueing system, the system expands the range, to 1-2000,  )   The entry number is an opaque longword.h  D   The entry number assignment algorithm is not documented, and it's E   not a linear expansion, and it is subject to change without notice.nE   There are some non-linear "jumps" in the entry allocation sequence.t  + :...You then decide that you want to delete C :this job. But unbeknownst to you, it finishes before you enter the A :appropriate DELETE/ENTRY command. Meanwhile, another user startsd? :another job that gets the same entry number. Then you run yourd/ :DELETE/ENTRY command and delete the wrong job!r  8   Yes, this sequence is possible.  Though very unlikely.  G   Currently (and this is subject to change), the entry number range is SG   from 1 to 99,999, with the expansion occuring when the current range  G   is at 90% full.  Note that certain configurations involve a couple of-G   extra digits in the "middle" of the entry number, digits that I will o   not get into here.  J   Treat it as an opaque longword, and all will be well.  Make assumptions I   on the entry allocation sequence and/or the queue file expansion schemer   at your peril.  C :So my question is, does the range of possible entry numbers expand1G :before all (or the very vast majority) of them are in use, say all butaA :50, or some reasonable percentage, so that the above scenario isy- :impossible (or at least extremely unlikely)?   9   Yes.  Currently, expansion occurs when at 90% capacity.e  0   Again, the entry number is an opaque longword.  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 23 Oct 2000 16:41:30 -0400a- From: JF Mezei <jfmezei.spamnot@videotron.ca>-> Subject: Re: Question about running out of queue entry numbers, Message-ID: <39F4A270.68A64544@videotron.ca>   Hoff Hoffman wrote:d2 >   Again, the entry number is an opaque longword.   Translation:  D The programmer that code that part is long gone and didn't leave anyM documentation. Nobody knows for sure because the code is a real mess and hard$ to understand.  & :-) :-) :-) :-) :-) :-) :-) :- :-) :-)   ------------------------------   Date: 23 Oct 2000 21:32:30 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)> Subject: Re: Question about running out of queue entry numbers6 Message-ID: <8t2ape$qqk$2@mailint03.im.hou.compaq.com>  \ In article <39F4A270.68A64544@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes: :Hoff Hoffman wrote:3 :>   Again, the entry number is an opaque longword.j ::
 :Translation:a :fE :The programmer that code that part is long gone and didn't leave any N :documentation. Nobody knows for sure because the code is a real mess and hard :to understand.p  &   Nope.   Please don't be opaque.  :-)  L   A more proper translation: we know full well what the current queue entry I   number format is, and we reserve the right to break any 's application fJ   that might make any assumptions about the entry allocation order, about J   the entry wrapping logic, and/or about the format or even the magnitude    of an individual entry.  1  I   The queue entry value is an opaque longword value, much like a context RJ   value used for a system service call.  If you look inside and then code J   your application(s) to depend on what you have observed, you can (will?)J   end up with a non-functional application at some current or future date.  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 23 Oct 2000 20:10:16 -0500h7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>r> Subject: Re: Question about running out of queue entry numbers- Message-ID: <39F4E178.6578EEAA@earthlink.net>    "Alan E. Feldman" wrote:  >Thanks for your rapid response.L >What if during your cut and paste the job finishes and another user submitsH >a job which then gets the same entry number because all the other entryG >numbers are in use? That is what I asked. I am not asking about makinga >typos.a) >Yeah, it's unlikely, but not impossible.   G Actually, I'm rather puzzled by the whole discussion. In 18+ years with E VMS, I can't recall nor can I imagine having, say 999 jobs waiting in-D print/batch queues (possible, but unlikely), having entry number 765G (for example) finish, having a user PRINT or SUBMIT a job and having itcC receive entry number 765 again, all within a span of a few seconds.,  H I'm quite sure that it's POSSIBLE. I'm also quite sure that it is HIGHLY	 unlikely.   F If you're worried about such a scenario, my guess is you've got bigger problems than that.c  F The FAR more likely scenario would be to have a user SUBMIT or PRINT aD job while 765 is still running, resulting in the entry numbers goingF into the four digit range if currently three, five digits if currently
 four, etc.  F I've never heard of or even considered entry numbers being a fixed setE or range (except within the limits of a longword). So, it's a foreign  concept to me.  G It wouldn't lose any sleep over it ... but that's just me. Your mileagee$ may vary (considerably!), as always.   -- a David J. Dachtera  dba DJE Systemsl http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/l  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  % Date: Mon, 23 Oct 2000 21:07:20 -0500s/ From: Chris Scheers <chris@applied-synergy.com>C> Subject: Re: Question about running out of queue entry numbersO Message-ID: <A53E1812957CEC6E.4DCBEB491730339E.2EA4047C493A11F4@lp.airnews.net>u   JF Mezei wrote:w >  > Hoff Hoffman wrote:a4 > >   Again, the entry number is an opaque longword. >  > Translation: > F > The programmer that code that part is long gone and didn't leave anyO > documentation. Nobody knows for sure because the code is a real mess and hard  > to understand.    3 Assuming that you are not being entirely facetious:   G Actually, what I have looked at of this code is pretty straight forward  and easy to understand.   @ In this case, "opaque" means: We reserve the right to change theH algorithm, possibly making the code a real mess and hard to understand.  <grin>  G ----------------------------------------------------------------------- $ Chris Scheers, Applied Synergy, Inc.  C Voice: 817-237-3360            Internet: chris@applied-synergy.com y   Fax: 817-237-3074w   ------------------------------  % Date: Tue, 24 Oct 2000 10:31:52 +1300u" From: "kevinf" <kevinf@gns.cri.nz> Subject: Record not current_- Message-ID: <8t2bb2$27a3$1@news.comnet.co.nz>o  J I am using ISAM files, performing a keyed read, deleting that record, thenI sequentially reading the next 'n' records and deleting them, too. UsuallyiC this is fine, but occasionally the delete trips up with "record not1= current", so far only on records that were read sequentially.   G Another process also accesses the same file with SHARED write access. IaK understand "next record" and "current record" pointers to be unique to each.J running process, so do not see how the other process should interfere with$ the delete sequence mentioned above.   Any ideas from the group?5   Many thanks, Kevin Fenaughty    K.Fenaughty@gns.cri.nz   ------------------------------   Date: 23 Oct 2000 22:48:12 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: Record not current36 Message-ID: <8t2f7c$rjk$1@mailint03.im.hou.compaq.com>  R In article <8t2bb2$27a3$1@news.comnet.co.nz>, "kevinf" <kevinf@gns.cri.nz> writes:K :I am using ISAM files, performing a keyed read, deleting that record, then J :sequentially reading the next 'n' records and deleting them, too. UsuallyD :this is fine, but occasionally the delete trips up with "record not> :current", so far only on records that were read sequentially.  5   OpenVMS platform, version, and exact error message?   H :Another process also accesses the same file with SHARED write access. IL :understand "next record" and "current record" pointers to be unique to eachK :running process, so do not see how the other process should interfere with-% :the delete sequence mentioned above.t  J   Is the "competing" application possibly adding or removing records from    the RMS indexed file?1  #   Does the code have status checks?h  G   Anything interesting in the secondary field -- RMS returns FAB$L_STS l5   and often some additional information in FAB$L_STV.2  H   Do you know what the other application is doing when the error arises?  H   The following is the error that is closest to the cited text -- please;   don't abbreviate errors -- that I can immediately locate:   ?  CUR,  no current record (operation not preceded by $GET/$FIND)e  7   Facility:     RMS, OpenVMS Record Management Services-  I   Explanation:  A program attempted an RMS $DELETE, $TRUNCATE, or $UPDATEaM                 operation without having performed a successful $GET or $FIND-                 operation.  L   User Action:  Check for a programming error. Modify the source program, ifB                 necessary, to detect and respond to the condition.    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 23 Oct 2000 19:32:00 -0400s- From: JF Mezei <jfmezei.spamnot@videotron.ca>0+ Subject: Show System (memory use) question.l, Message-ID: <39F4CA6C.53E09880@videotron.ca>  I When I do a SHOW system and it tells me that a process has a 5000 virtualDJ pages and a working set of 1000 pages, does this mean that the process has 1000 pages in physical memory ?n  G If I run 10 instances of TPU, whose image is installed/shared, to whicha1 process will the physical pages be "charged" to ?o   ------------------------------  % Date: Mon, 23 Oct 2000 22:12:47 -0400e( From: Jonas Lindholm <jlindholm@rcn.com>/ Subject: Re: Show System (memory use) question.o' Message-ID: <39F4F01F.817C53FD@rcn.com>    JF Mezei wrote:t  K > When I do a SHOW system and it tells me that a process has a 5000 virtualiL > pages and a working set of 1000 pages, does this mean that the process has! > 1000 pages in physical memory ?  > I > If I run 10 instances of TPU, whose image is installed/shared, to whichc3 > process will the physical pages be "charged" to ?l  N Every process will be "charged" the pages to its own working set but they will shareeL the same physical pages. So instead of using 10 x 1000 physical pages for 100 processes only 1000 physical pages will be used.   /Jonas Lindholme   ------------------------------   Date: 23 Oct 2000 15:54 -0400r From: hein@eps.zko.dec.c*m+ Subject: Re: Stockholm Exchange OM and VMS?s& Message-ID: <23OCT200015540601@miasys>  k In article <39F460B2.63CD29B6@gtech.com>, Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> writes...c >andrew harrison wrote:u) >> I don't hjave a clue. Neither probably   : tG >If you do not like the tone here, then feel free to leave this group !o >Arne)  J Unfair! Andrew is quoted out of context. He was provoked / teased to reactK by an earlier posting and did so with a reasonable attempt at humor, and a aE few smileys sprinkeled in for the humor impaired amongst the readers.   I I often dislike his messages, but some have core of thruth (can hurt) andlJ other messages (this) are basically because others asked for it. We shouldI all consider the silent treatment, or at least read on and see if someonefL already said what you were about to write. Some of his messages have blatant= misinformation and should be answered, non-emotionally, once._  ; Andrews 'clueless' message was clearly just in jest. Smile!r   Cheers,a 	Hein.   ------------------------------  # Date: Mon, 23 Oct 2000 20:59:02 GMTw From: jlhm@my-deja.com+ Subject: Re: Stockholm Exchange OM and VMS?-) Message-ID: <8t28qi$l66$1@nnrp1.deja.com>1  / The Saxess system is NOT running on OpenVMS, it ) use Sun servers, see www.omtechology.com.e1 We, OM Technology, are investigating the cause ofa1 the problem and we don't known at this moment thet exact reason for the problem.   + OpenVMS is used for the OMex Click Exchange  System used for option trading. + The OMex is used by several other exchanges,* worldwide such as the new ISE, Korea Stock& Exchange and Australia Stcok Exchange.  , Please contact OM at +46 8 405 6000 for more information.   /Jonas Lindholm ) This is NOT an official statement from OM 2 Technology or any other company owned by OM Group.0 The ONLY reason is to kill incorrect information in this group!!!!b. At this moment I don't have access to Internet, News from my desk and are therefore using my/ private Email address instead of my official OMg Group address.    * In article <39F424FC.72BA548D@uk.sun.com>,,   andrew harrison <andrew.nospam@uk.sun.com> wrote: > Curtis Rempel wrote: > >  > > Maybe we should ask Andrew.e > >  >t( > I don't hjave a clue. Neither probably1 > does anyone else on this newsgroup which almosto1 > certainly won't stop people making ill informedn > judgments. >,+ > I could make some inflamatory and totallyt	 unfoundedt > suggestions. >o1 > Perhaps along the lines of Rob or Kerry or eveni	 yourself.M > . > 1.	The exchange uses OpenVMS, must have been that* > 	thet caused to outage. We all know that OpenVMS & > 	is unreliable after all look at the multiple outages, > 	that etrade had for different reasons. Of course there is no, > 	evidence to support this but if I was Rob of Kerry( > 	I would stick to this even if all the evidence was that:$ > 	this point of view was incorrect. >n( > 2.	It must be the same thing as eTrade because the outage time,+ > 	2 hours is similar the the eTrade outagei times. Another% > 	totally idiotic theory but just as  plausible as other' > 	FUD posted on this newsgroup. :):):)f >e, > 3.	Perhaps they put one of the new special
 patches on* > 	the OpenVMS boxes ? :):):) Again almost certainly total1* > 	rubbish but entirely justifiable by the
 FUD standardse > 	on this group.a > 	 > Regardst > > "Peter Ljungberg"h- <peter.p.ljungberg@telia.se> wrote in message 1 > > news:HHnI5.1771$jv2.253581@newsc.telia.net...r > > >  > > >i) > > > I heard that it was a communicationr problem, not confirmed > > >t > > > /P.Lje > > >n > > >T2 > > > <richard_maher@my-deja.com> wrote in message) > > > news:8srpqk$sef$1@nnrp1.deja.com...e > > > > Hi,f > > > > * > > > > Does anyone know why the Stockholm! exchange's trading system crasheds. > > > > twice yesterday for a total of 2hours? Was VMS involved?o > > > >i > > > > Regards Richard Maher  > > > >  > > > >?. > > > > Sent via Deja.com http://www.deja.com/ > > > > Before you buy.m > > >' > > >c >o > -- > Andrew Harrisona > Enterprise IT Architecte >v      & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  # Date: Mon, 23 Oct 2000 19:10:51 GMTt+ From: Jordan Henderson <jordan@my-deja.com>t' Subject: Re: Sun "uptime" belly laugherr) Message-ID: <8t22fk$f71$1@nnrp1.deja.com>s  - In article <971974416.604379@sj-nntpcache-3>,e1   shawbrow@delilah.cisco.com (Shawn Brown) wrote: - > In article <MYnw451i3kbz@eisner.decus.org>,u- > Rob Young <young_r@eisner.decus.org> wrote:e > >DF > >The only thing that really matters is uptime.  Only bring it down a handfulrE > >of times in a year?  How about staying up a couple years?  ForeignS concept?H > >Better yet.... how about designing and selling machines that can stay > >up more than a month!!! >f
 > Nice troll.R  @ This must be some definition of troll with which I'm unfamiliar.  ; It would have been a troll if Rob had added comp.sys.sun oraB comp.os.solaris to the groups posted.  Here, it's just the sharing@ of some humor at the expense of Scott "I wish I were Bill Gates" McNealy.  ? Unlike certain employees of a Heliocentric computer company, we B OpenVMS advocates don't hang out in Sun newsgroups with the intentB of jeering at the failings of their favorite OS/hardware.  No, now THAT would be trolling.c   >eF > I've had production sun boxes with two year uptimes.  I think that's@ > actually negligent on my part, since I wasn't patching for the	 duration.u >eD > It's routine for our production sun boxes to have one or two month uptimes.5 > Not much more than that because we patch quarterly.D >T  A But, we've been told that you can patch Solaris with no downtime,e( just like you can with OpenVMS clusters.  $ What is it that you are doing wrong?   > Shawnr >  >e   -- -Jordan Hendersonb jordan@greenapple.coml    & Sent via Deja.com http://www.deja.com/ Before you buy.n   ------------------------------  % Date: Mon, 23 Oct 2000 15:46:33 -0400c+ From: "Chris Moore" <chris.moore@stelco.ca>c' Subject: Re: Sun "uptime" belly laugher-. Message-ID: <sv95d4spsob49@corp.supernews.com>  G It seems that Andrew only follows this newsgroup in order to "Oh Yeah?" I anything that might disparage Sun.  If he's so worried about such flames,o. maybe he should monitor the Sun Users group(s)    = "andrew harrison" <andrew.nospam@uk.sun.com> wrote in messageb$ news:39F06A69.C6FE3B6F@uk.sun.com... Arne Vajhj wrote: >i > Shawn Brown wrote:/ > > In article <MYnw451i3kbz@eisner.decus.org>,e/ > > Rob Young <young_r@eisner.decus.org> wrote: H > > >The only thing that really matters is uptime.  Only bring it down a handfulaG > > >of times in a year?  How about staying up a couple years?  Foreign- concept?J > > >Better yet.... how about designing and selling machines that can stay > > >up more than a month!!! > >o > > Nice troll.d > >mH > > I've had production sun boxes with two year uptimes.  I think that'sL > > actually negligent on my part, since I wasn't patching for the duration. > >nF > > It's routine for our production sun boxes to have one or two month uptimes.7 > > Not much more than that because we patch quarterly.q >lB > Not a troll - just the entire VMS community rolling on the floor > laughing,iG > because the SUN CEO say that it is SUN's goal to only have a handfulla > of downtime during a year. >n* > That is lower ambitions than MicroSoft ! > / > (but probably with better chances of success)0 >1J > And I do know that SUN sites do a lot of patching, which for some reason& > are much more rare in the VMS world. >n   Arne  = You need to read more of this newsgroup than just the threadsc# where people are trying to FUD Sun.J  9 If you had you would have realised the just at the moment 7 any discussion relating to patches is not going to be ad% painless one for an OpenVMS advocate.m  = I refer you if you hadn't been following it to the discussionm@ on this thread about Compaq OpenVMS patch quality (or otherwise) and the war stories.  B I particularly liked the duff patch which didn't cause the clusterC to crash but did require 1500 users to get kicked off the system toa escape from its deadly embrace.   G I think thats what the military call an acceptable level of casualties.r  : Seems to me that Sun "uptime" belly laughs could easily be< applied to OpenVMS as well. And that Rob's FUD could equally$ be described as OpenVMS botty burps.  G BTW the tread is called "Anybody else having bugchecks after installing  recent patches?"5 which is pretty difficult to miss though I assume youo7 must have from your confident attempt to FUD Sun's with = some kind of OpenVMS/Sun relative number of patches argument.d  : P.S This isn't an attempt to compare OpenVMS and Sun patch: quality just a suggestion that you are ill advised to fall7 into the normal OpenVMS advocate trap of throwing rocks- in your own glass house.     Regards  Andrew Harrison0 Enterprise IT Architecte   ------------------------------  % Date: Mon, 23 Oct 2000 17:51:09 +0000  From: SysAdmin <djesys@fsi.net>D& Subject: Re: TCP/IP and load balancing' Message-ID: <39F47A8D.B2800D31@fsi.net>r   Didier Morandi wrote:f >  > SysAdmin wrote:s > >e > ../..s > >n > > David J. Dachtera  > H > I would love to know why Mike has TCP answers from the Famous Datchera > Esquire and not me... :-(   8 %RQACP-W-RQCHK, Request check: unexpected context switchF -PERS-I-CTXUNREC, unrecognized context elements, attempting to resolve   Didier,s   I don't understand.    David J. Dachtera    ------------------------------   Date: 23 Oct 2000 17:56:25 GMT1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)5 Subject: Re: VAX emulatori+ Message-ID: <8t1u49$3g7$1@info.cs.uofs.edu>c  5 In article <mP6I5.130$Qz2.36868@typhoon.aracnet.com>,f5  "Zane H. Healy" <healyzh@shell1.aracnet.com> writes:a |>F |>                                                     What can I say,O |> even Hobbyists have a few legacy apps, and it would be nice to save a littlelA |> on the power bill by dropping my token VAX out of the cluster.   I Heresy!! Heresey!!  Someone get the stake set up I'll gather wood for thei fire!!   bill   -- rJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   .   ------------------------------  % Date: Tue, 24 Oct 2000 11:56:35 +1300 9 From: "Antony Wardle" <antony.wardle@nnnoospam.met.co.nz>e Subject: vt520 music questionl2 Message-ID: <0f3J5.5223$SF5.108657@ozemail.com.au>  2 anyone know why when you press the shift button on9 a vt520 five times you get a cute little three note scale.6 sound (going up) and when you press it five more times/ you get the same, but the notes are going down.a  ( It also draws a u shape and fills it in.  % I have no idea how i discovered this.-  0 Haven't found anything else, and haven't noticed2 it on any other vt devices. Tried it on excursion,2 but windows popped up something about sticky keys.     Antony.s   ------------------------------  % Date: Mon, 23 Oct 2000 19:49:11 -0500u7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>g! Subject: Re: vt520 music questionl- Message-ID: <39F4DC87.93B9DA56@earthlink.net>m   Antony Wardle wrote: > 4 > anyone know why when you press the shift button on; > a vt520 five times you get a cute little three note scaleo8 > sound (going up) and when you press it five more times1 > you get the same, but the notes are going down.t > * > It also draws a u shape and fills it in. > ' > I have no idea how i discovered this.s > 2 > Haven't found anything else, and haven't noticed4 > it on any other vt devices. Tried it on excursion,4 > but windows popped up something about sticky keys.  B That's exactly it! It's an accessibility feature for, for example,G quadraplegics who can do little more than manipulate a wand clenched in F their teeth. Obviously, such an example would make SHIFT+anykey rather$ difficult, if not for "sticky" keys.   -- f David J. Dachterac dba DJE Systemsr http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/e  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.a   ------------------------------  % Date: Mon, 23 Oct 2000 16:33:17 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> ' Subject: Re: What does DCPS really do ?e, Message-ID: <39F4A084.74106AFE@videotron.ca>   Paul Anderson wrote:H > There was an article in the Fall 1991 edition of the Digital Technical2 > Journal describing a lot about the guts of DCPS. > # >    http://www.digital.com/DTJ400/d   Thanks for the pointer.o  H > DCPS does not change the contents of a user's PostScript job, but addsI > PostScript code at the beginning and the end to control the printer andn, > select the options the user has requested.  M But in the case of n-UP printing (multiple pages on a single piece of paper),dN doesn't DCPS fiddle with the showpage operator to cause it scale and translateO (and possibly rotate) instead of just asking the printer to spit out the page ?   H The reason I ask is that on a Microvax II, DCPS seems to be taking largeI amounts of CPU time when I send postscript code that contains images. TheeK serial line is not defined as "binary capable". So i would assume that DCPSqE scans my postscript code to find any binary data and convert it to andN acceptable encoding ? Is it able to redefine "currentfile" to point to its new@ non-binrary filter without inserting code in my postscript job ?    M If DCPS only "worked" during print setup and termination, shouldn't it simply K copy data to the printer once the job is properly setup, thus not requiringnK large amounts of CPU (on a uVAX-II, any amount of CPU is a large amount :-)    ------------------------------   End of INFO-VAX 2000.594 ************************