1 INFO-VAX	Fri, 13 May 2005	Volume 2005 : Issue 266       Contents: Re: /TRANS=TERMINAL  Re: /TRANS=TERMINAL  Re: /TRANS=TERMINAL / Ann Livermore loves Opteron but perhaps not VMS 3 Re: Ann Livermore loves Opteron but perhaps not VMS 3 Re: Ann Livermore loves Opteron but perhaps not VMS 3 Re: Ann Livermore loves Opteron but perhaps not VMS  Re: BACKUP A:[...]*.* B:[...]  Re: BACKUP A:[...]*.* B:[...]  Re: BACKUP A:[...]*.* B:[...]  Re: BACKUP A:[...]*.* B:[...]  Re: BACKUP A:[...]*.* B:[...]  Re: BACKUP A:[...]*.* B:[...] * Re: BACKUP A:[...]*.* B:[...] missing root* Re: BACKUP A:[...]*.* B:[...] missing root# Re: DECterm oddity (mangled output) # Re: DECterm oddity (mangled output) , Re: DO HLP HLD BRK PRN and other keymappings( Re: DUMP /ASCII - Request for Guy Peleg?( Re: DUMP /ASCII - Request for Guy Peleg?J Re: INFO-VAX 2005.262Re: Powerstorm graphics w/ VMS -- and OpenGL, anyone?J Re: INFO-VAX 2005.262Re: Powerstorm graphics w/ VMS -- and OpenGL, anyone?& Re: Info-Zip VMS to PC password needed& Re: Info-Zip VMS to PC password needed& Re: Info-Zip VMS to PC password needed Re: KZPBA-CA Scsi Card, license problem with openvms-alpha need help0 Re: license problem with openvms-alpha need help0 Re: license problem with openvms-alpha need help0 Re: license problem with openvms-alpha need help0 Re: license problem with openvms-alpha need help0 Re: license problem with openvms-alpha need help0 Re: license problem with openvms-alpha need help Re: OpenVMS and Mac OS X 10.4 B Re: OpenVMS IA64 Pilot Program site doesn't have the pilot programB Re: OpenVMS IA64 Pilot Program site doesn't have the pilot programB Re: OpenVMS IA64 Pilot Program site doesn't have the pilot program+ Re: OT: Only slightly off-shore programming 7 Re: Slow screen update with cobol generated executables 7 Re: Slow screen update with cobol generated executables 7 Re: Slow screen update with cobol generated executables 7 Re: Slow screen update with cobol generated executables 7 Re: Slow screen update with cobol generated executables  Re: Strange PINGing ? " Re: The continuing saga of the VAX" Re: The continuing saga of the VAX" Re: The continuing saga of the VAX" Re: The continuing saga of the VAX" Re: The continuing saga of the VAX" Re: The continuing saga of the VAX VT525 TFT Monitor   F ----------------------------------------------------------------------    Date: 13 May 2005 07:46:34 -0500 From: briggs@encompasserve.org Subject: Re: /TRANS=TERMINAL3 Message-ID: <bUbMs$XrW4se@eisner.encompasserve.org>   w In article <d60er2$44p$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: J > In article <1115918678.155557.56380@g14g2000cwa.googlegroups.com>, "AEF"# > <spamsink2001@yahoo.com> writes:   > F >> No. /NAME=NOALIAS is to prevent a user from superseding the logicalE >> name. You can still define the equivalence name as another logical  >> name. >>  & >> $ DEFINE DISK DSA100: /NAME=NOALIAS >> $ DEFINE DSA100 DSA200: >>  * >> This will make DISK point to DSA200: !. >  > Right. > E >> If you used /TRAN=TERM instead then DISK would point to DSA100: !.  > 1 > Yes.  But is that WHY /TRANS=TERM was invented?  > C You presumably get a small performance boost by suppressing a final F failed logical name lookup.  And bear in mind that failed name lookups/ tend to be more expensive than successful ones.    	John Briggs   ------------------------------    Date: 13 May 2005 08:03:05 -0500 From: briggs@encompasserve.org Subject: Re: /TRANS=TERMINAL3 Message-ID: <LulhyZPoSE+L@eisner.encompasserve.org>   w In article <d60er2$44p$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: 1 > Yes.  But is that WHY /TRANS=TERM was invented?  > B The real reason that /TRANS=TERM was invented was that the leadingB underscore convention and the leading double-underscore convention were kluges.   	John Briggs   ------------------------------  % Date: Fri, 13 May 2005 10:20:26 -0700 , From: Ken Fairfield <my.full.name@intel.com> Subject: Re: /TRANS=TERMINAL+ Message-ID: <d62nkr$i84$1@news01.intel.com>   / Phillip Helbig---remove CLOTHES to reply wrote: , > What is the purpose of /TRANS=TERM?  [...]  =     My recollection is that this was the only way to define a > rooted logical name when they were first invented.  Vague (and= volatile!) memories, etc...  A whole bunch of qualifiers were : added to DEFINE in the V5 time frame, but clusters and theB definition of SYS$SYSROOT, etc., which were necessary for clustersA were V4 creations.  There was simply no other way to get a rooted & logical without /Translation=Terminal.   	-Ken  --  6 I don't speak for Intel, Intel doesn't speak for me...  
 Ken Fairfield ! D1C Automation VMS System Support " who:   kenneth dot h dot fairfield where: intel dot com   ------------------------------    Date: 13 May 2005 05:04:00 -0700( From: greigaln@netscape.net (Alan Greig)8 Subject: Ann Livermore loves Opteron but perhaps not VMS= Message-ID: <d391276d.0505130404.379d7ba8@posting.google.com>   Q http://www.computerworld.com/hardwaretopics/hardware/story/0,10801,101410,00.html    Couple of quotes:   D "I recently spoke with Ann Livermore, executive VP of the technologyE solutions group at HP, about what must have been two tough decisions: C to pull out of that 10-year Itanium co-development pact with Intel, D and to suck it up and offer the Opteron-based systems that customersC wanted. Livermore's position was characteristically straightforward C and down to earth: Citing "some great price/performance" with AMD's D technology, she basically said HP needed to give customers what they want."   ---   2 And whay does this Galaxy codename sound familiar?  C "What's interesting about all this is that since his return to Sun, A Bechtolsheim has been shepherding a hush-hush project, code-named < Galaxy, to develop a next generation of servers. What I findD particularly eyebrow-raising is that this entire line will be devoidF of Sun's Sparc microprocessor technology. It will be based entirely on5 Opteron microprocessors from Advanced Micro Devices."  ---    --  
 Alan Greig   ------------------------------    Date: 13 May 2005 07:38:43 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) < Subject: Re: Ann Livermore loves Opteron but perhaps not VMS3 Message-ID: <9ll4yYqvPVAG@eisner.encompasserve.org>   h In article <d391276d.0505130404.379d7ba8@posting.google.com>, greigaln@netscape.net (Alan Greig) writes: >  > Couple of quotes:  > F > "I recently spoke with Ann Livermore, executive VP of the technologyG > solutions group at HP, about what must have been two tough decisions: E > to pull out of that 10-year Itanium co-development pact with Intel, F > and to suck it up and offer the Opteron-based systems that customersE > wanted. Livermore's position was characteristically straightforward E > and down to earth: Citing "some great price/performance" with AMD's F > technology, she basically said HP needed to give customers what they > want."  I    Somebody tell Ann customers want VMS running on their Pentium laptops.    ------------------------------    Date: 13 May 2005 16:08:52 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)< Subject: Re: Ann Livermore loves Opteron but perhaps not VMS, Message-ID: <4284d114$1@news.langstoeger.at>  q In article <9ll4yYqvPVAG@eisner.encompasserve.org>, koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: i >In article <d391276d.0505130404.379d7ba8@posting.google.com>, greigaln@netscape.net (Alan Greig) writes:  >> Couple of quotes: >>  G >> "I recently spoke with Ann Livermore, executive VP of the technology H >> solutions group at HP, about what must have been two tough decisions:F >> to pull out of that 10-year Itanium co-development pact with Intel,G >> and to suck it up and offer the Opteron-based systems that customers F >> wanted. Livermore's position was characteristically straightforwardF >> and down to earth: Citing "some great price/performance" with AMD'sG >> technology, she basically said HP needed to give customers what they 	 >> want."  > J >   Somebody tell Ann customers want VMS running on their Pentium laptops.  B Almost. Customers want VMS running on their Turion64 Notebooks ;-)   --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------    Date: 13 May 2005 08:22:14 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com> < Subject: Re: Ann Livermore loves Opteron but perhaps not VMSC Message-ID: <1115997734.389369.207420@g44g2000cwa.googlegroups.com>     Peter 'EPLAN' LANGSTOEGER wrote:5 > In article <9ll4yYqvPVAG@eisner.encompasserve.org>, = koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: @ > >In article <d391276d.0505130404.379d7ba8@posting.google.com>,* greigaln@netscape.net (Alan Greig) writes: > >> Couple of quotes:  D > >> technology, she basically said HP needed to give customers what they > >> want."  > > C > >   Somebody tell Ann customers want VMS running on their Pentium  laptops. > D > Almost. Customers want VMS running on their Turion64 Notebooks ;-) >  > -- > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialist  > E-mail  peter@langstoeger.at@ > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   D I wouldn't complain if VMS was running beneath Aqua on a G4/G5 Power Mac either... ;-)    ------------------------------  + Date: Fri, 13 May 2005 05:54:49 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)& Subject: Re: BACKUP A:[...]*.* B:[...]$ Message-ID: <d61ff9$3f1$1@online.de>  < In article <42841714.314986B7@comcast.net>, David J Dachtera$ <djesys.nospam@comcast.net> writes:   G > > What are other instances when, from a user point of view, B doesn't K > > behave the same as C[D.]?  One that I can think of is that one can't do @ > > DEFINE E B:[F.] if B is defined as above.  Are there others? > I > May I assume that "C[D.]" (apparently, colon(":") is missing) is just a 8 > transcription typo and not what's causing the problem?   Yes.   ------------------------------  + Date: Fri, 13 May 2005 06:52:16 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)& Subject: Re: BACKUP A:[...]*.* B:[...]$ Message-ID: <d61ir0$70k$1@online.de>  C In article <1115954868.447894.103470@g14g2000cwa.googlegroups.com>, ' "AEF" <spamsink2001@yahoo.com> writes:    D > I meant the backup a:[...] b:[...], etc., works for me. The second' > thing, define e b:[f.] does not work.   ; OK.  Below I have a test procedure to explain what I meant.   D Actually, I think it CAN SOMETIMES work.  It depends on the default F directory at the time the BACKUP command is executed.  If the default H directory is itself e = b:[f.] and one has [...] as the target, then it H won't.  What happens is that a bogus 000000.DIR is created, and in that I the subdirectories are created, but the non-directory files try to go to  4 [f.*] and the corresponding directories don't exist.  
 > Others?  > . >     BACKUP /IMAGE rooted_device: output-spec >  > does not work.  G Right, but that's not generally something a non-priviledged user would   do.   E ---------8<----------------------------------------------------------   
 $  SET VERIFY  $  SET NOON 4 $  USERNAME = F$EDIT(F$GETJPI("","USERNAME"),"TRIM") $  SET DEF SYS$SCRATCH $  SHOW DEFAULT ! $  SHOW LOGICAL DISK$SCRATCH/FULL - $  CREATE/DIR DISK$SCRATCH:['USERNAME'.A.B.C]  $  CREATE [.A]A.TXT  $  CREATE [.A.B]B.TXT  $  CREATE [.A.B.C]C.TXT  $  CREATE/DIR [.D] $  CREATE/DIR [.E]7 $  BACK/LOG [.A...]*.* [.D...] ! this works as expected  $  DIR [.A...] $  DIR [.D...]9 $  DEFINE/TRANS=CONC TEST_DISK DISK$SCRATCH:['USERNAME'.] ! $  SET DEFAULT TEST_DISK:[000000]  $  SHOW DEFAULT  $  DIR E.DIRK $! the following line should do essentially the same as the previous BACKUP 5 $  BACK/LOG DISK$SCRATCH:['USERNAME'.A...]*.* [.E...]  $  DIR TEST_DISK:[E] $  DIR [.E...] $  SET DEFAULT SYS$SCRATCH $  SET NOVERIFY  $  EXIT    ------------------------------  % Date: Fri, 13 May 2005 10:46:11 +0200 ( From: "Rudolf Wingert" <win@fom.fgan.de>& Subject: Re: BACKUP A:[...]*.* B:[...]3 Message-ID: <002501c55798$36da9f70$994614ac@wat153>    Hello,  F if you have defined the logical correct (C:[d.]), did you also specify> all the translation attribute (AFAIK: CONCEALED and TERMINAL).   Best regards R. Wingert    ------------------------------    Date: 13 May 2005 07:37:05 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) & Subject: Re: BACKUP A:[...]*.* B:[...]3 Message-ID: <L7ysW0d8nkIV@eisner.encompasserve.org>   j In article <1115954868.447894.103470@g14g2000cwa.googlegroups.com>, "AEF" <spamsink2001@yahoo.com> writes:
 > Others?  > . >     BACKUP /IMAGE rooted_device: output-spec  F    Yes it does.  It makes an image of the disk.  It always goes to theH    disk that a logical name points to, whether it points to the physical    disk or some location on it.   8    There's no such thing as an /IMAGE of part of a disk.   ------------------------------    Date: 13 May 2005 07:05:52 -0700$ From: "AEF" <spamsink2001@yahoo.com>& Subject: Re: BACKUP A:[...]*.* B:[...]C Message-ID: <1115993152.494385.264830@g49g2000cwa.googlegroups.com>    Bob Koehler wrote:E > In article <1115954868.447894.103470@g14g2000cwa.googlegroups.com>, & "AEF" <spamsink2001@yahoo.com> writes: > > Others?  > > 0 > >     BACKUP /IMAGE rooted_device: output-spec > D >    Yes it does.  It makes an image of the disk.  It always goes to the A >    disk that a logical name points to, whether it points to the  physical! >    disk or some location on it.  > : >    There's no such thing as an /IMAGE of part of a disk.  F Well, if someone typed that I'd think the intent would be to just makeG a "functional copy" of the files under rooted_device:[000000...], which G it doesn't do. So just because it runs without errors, doesn't mean "it G works". I gave it a quick try to NL:, aborting it rather early, and all F the files were reported (from /LOG) to be from []. So does it actuallyA make a proper image backup that is usable, preserving aliases and C directory structure? I may try it out another time when I have more  time.    ------------------------------    Date: 13 May 2005 12:38:19 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) & Subject: Re: BACKUP A:[...]*.* B:[...]3 Message-ID: <RW+QrMJIfsT4@eisner.encompasserve.org>    > H > Well, if someone typed that I'd think the intent would be to just makeI > a "functional copy" of the files under rooted_device:[000000...], which I > it doesn't do. So just because it runs without errors, doesn't mean "it 	 > works".   D    It does what it is documented to do:  makes an image of the disk.    To me that means it works.   A > I gave it a quick try to NL:, aborting it rather early, and all H > the files were reported (from /LOG) to be from []. So does it actuallyC > make a proper image backup that is usable, preserving aliases and E > directory structure? I may try it out another time when I have more  > time.   H    I don't actualy do it often, but the last time I tried it, it worked.      ------------------------------  % Date: Fri, 13 May 2005 05:25:13 -0700 ( From: Jeff Cameron <roktsci@comcast.net>3 Subject: Re: BACKUP A:[...]*.* B:[...] missing root / Message-ID: <BEA9EAB9.DE1A%roktsci@comcast.net>   @ On 5/12/05 10:06 AM, in article d602e3$ejj$2@online.de, "PhillipJ Helbig---remove CLOTHES to reply" <helbig@astro.multiCLOTHESvax.de> wrote:  J > I'm sure it is a known bug that BACKUP A:[...]*.* B:[...] doesn't behaveJ > as expected if B: is not a real device but rather B = C[D.] [concealed].+ > I think this has been around for a while.  > ' > Is there any chance it will be fixed?  > E > What are other instances when, from a user point of view, B doesn't I > behave the same as C[D.]?  One that I can think of is that one can't do > > DEFINE E B:[F.] if B is defined as above.  Are there others? > G If I am not Mistaken, [...] means the current default directory and all L subdirectories, so I think that A:[...] would depend greately on the currentI default definition. In so far as the output specification B:[...] it gets A the root definition from whatever was found and used in the input J definition. So this could have very different outcomes depending on if theE current default root directory does or does not exist on the A drive.   L Even with you logical name translation of B being C:[E.], the syntax you are7 looking for is: BACKUP A:[000000...]*.*;* B:[000000...]    Jeff   ------------------------------  % Date: Fri, 13 May 2005 09:22:07 -0400  From: norm.raphael@metso.com3 Subject: Re: BACKUP A:[...]*.* B:[...] missing root Q Message-ID: <OFD06CF391.BB4C0093-ON85257000.00495993-85257000.00494746@metso.com>   C Jeff Cameron <roktsci@comcast.net> wrote on 05/13/2005 08:25:13 AM:   B > On 5/12/05 10:06 AM, in article d602e3$ejj$2@online.de, "PhillipE > Helbig---remove CLOTHES to reply" <helbig@astro.multiCLOTHESvax.de>  wrote: > E > > I'm sure it is a known bug that BACKUP A:[...]*.* B:[...] doesn't  behave? > > as expected if B: is not a real device but rather B = C[D.]  [concealed].- > > I think this has been around for a while.  > > ) > > Is there any chance it will be fixed?  > > G > > What are other instances when, from a user point of view, B doesn't K > > behave the same as C[D.]?  One that I can think of is that one can't do @ > > DEFINE E B:[F.] if B is defined as above.  Are there others? > > I > If I am not Mistaken, [...] means the current default directory and all F > subdirectories, so I think that A:[...] would depend greately on the current K > default definition. In so far as the output specification B:[...] it gets C > the root definition from whatever was found and used in the input H > definition. So this could have very different outcomes depending on if the G > current default root directory does or does not exist on the A drive.  > J > Even with you logical name translation of B being C:[E.], the syntax you are 9 > looking for is: BACKUP A:[000000...]*.*;* B:[000000...]   F $ BACKUP A:[*...]*.*;* B:[*...]  !? to avoid a redundant 000000.dir  ?   >  > Jeff >    ------------------------------    Date: 13 May 2005 07:32:24 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) , Subject: Re: DECterm oddity (mangled output)3 Message-ID: <O2LyB7eg6JQY@eisner.encompasserve.org>   ] In article <42841987.35003F1F@teksavvy.com>, JF Mezei <jfmezei.spamnopt@teksavvy.com> writes:   N <ESC>[m<SO>qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq > qqqqqqqqqqqqq   C    That looks like the escape sequence to shift to the line drawing F    character set, followed by "q" which does a horizontal line in that    set.   B    Quite possibly the escape seqnuence to shift back to the normal    character set was not seen.  C    On a DECterm, the menu entry Commands->Reset Terminal will clear     this.   ------------------------------  % Date: Fri, 13 May 2005 11:17:07 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> , Subject: Re: DECterm oddity (mangled output), Message-ID: <4284C4EE.99DE06E9@teksavvy.com>   Bob Koehler wrote: > _ > In article <42841987.35003F1F@teksavvy.com>, JF Mezei <jfmezei.spamnopt@teksavvy.com> writes:  > P > <ESC>[m<SO>qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq > > qqqqqqqqqqqqq  > E >    That looks like the escape sequence to shift to the line drawing H >    character set, followed by "q" which does a horizontal line in that	 >    set.   G Actually this one was part of the FMS data stream to display the allin1 , index form. the line drawing is expected :-)    C The escape sequences in the spam subject cause DECTERM to then have E problems handling stuff, even as simple as output from SHOW TERM. And F when you type, characters sometimes don't get displayed, and sometimesC go on the next line (but the compuet receives the right chartacters H without any problems, so while on the screen it looks lolke you mistyped+ a command, the host sees the right command.    ------------------------------  % Date: Fri, 13 May 2005 10:22:44 -0000 / From: Thomas Dickey <dickey@saltmine.radix.net> 5 Subject: Re: DO HLP HLD BRK PRN and other keymappings 0 Message-ID: <1188vvk2kfs9qbe@corp.supernews.com>  E In comp.terminals David J Dachtera <djesys.nospam@comcast.net> wrote:   F > If you have access to a VMS system, look at SYS$SYSTEM:SMGTERMS.TXT.J > There in, you'll find descriptions of the escape sequence transmitted byF > the active function keys. (Roughly equivalent to the termcap file in8 > UN*X-land, but must be "compiled" into TERMTABLE.EXE.)  H It's analogous, but contains less information (at least I've not seen itF describing the color escape sequences, and iirc, is rather limited forA the line-drawing).  It does, as you note, list the function-keys.    --   Thomas E. Dickey http://invisible-island.net  ftp://invisible-island.net   ------------------------------  # Date: Fri, 13 May 2005 13:56:35 GMT ( From: "Hein" <hein.nomail@hp.nomail.com>1 Subject: Re: DUMP /ASCII - Request for Guy Peleg? 2 Message-ID: <nm2he.5355$CV7.2822@news.cpqcorp.net>  ( <elementyl@hotmail.com> wrote in message; news:1115953280.753293.5540@g43g2000cwa.googlegroups.com... 
 > Hein wrote: 	 > > [...] < > > open (FILE,"<$file") or die "Failed to open file $file"; > > binmode FILE; [...]  > I > While this should default to raw, with the default 5.6.1 installation I I > tried this on this missed the record control bytes in the variable file   C You are absolutely right. I glanced over my test output too quickly 
 yesterday.I I now see it tried to 'help' by replacing the nice variable length record # structur to lf terminated nonsense. ' Changing read to sysread is even worse. K Adding an explicit discipline (layer) ":raw" (the default?!) to binmode did ! not help either (on  perl v5.6.0) . I may have to check out VMS::Stdio  after all.   ------------------------------  # Date: Fri, 13 May 2005 14:04:27 GMT ( From: "Hein" <hein.nomail@hp.nomail.com>1 Subject: Re: DUMP /ASCII - Request for Guy Peleg? 2 Message-ID: <Lt2he.5356$eY7.2703@news.cpqcorp.net>  ( <elementyl@hotmail.com> wrote in message; news:1115953280.753293.5540@g43g2000cwa.googlegroups.com... 
 > Hein wrote: 	 > > [...] < > > open (FILE,"<$file") or die "Failed to open file $file"; > > binmode FILE; [...]  > I > While this should default to raw, with the default 5.6.1 installation I I > tried this on this missed the record control bytes in the variable file   & [sorry to re-reply, I missed one line]    5 The workaround for that is:   $ set file/attr=rfm=udf  :-(    Hein.    ------------------------------  % Date: Fri, 13 May 2005 10:42:29 +0200 ( From: "Rudolf Wingert" <win@fom.fgan.de>S Subject: Re: INFO-VAX 2005.262Re: Powerstorm graphics w/ VMS -- and OpenGL, anyone? 3 Message-ID: <002401c55797$b2881c70$994614ac@wat153>    Hello,  D The PowerStorm 4D20 is an excellent but expensive 3D graphic adapter; with an connector for shutter classes for 3d visualization.    Best regards R. Wingert    ------------------------------  # Date: Fri, 13 May 2005 14:55:38 GMT * From: "FredK" <fred.nospam@nospam.dec.com>S Subject: Re: INFO-VAX 2005.262Re: Powerstorm graphics w/ VMS -- and OpenGL, anyone? 2 Message-ID: <Kd3he.5361$B_7.2642@news.cpqcorp.net>  J You can put the card into 24-bit mode.  Edit DECW$PRIVATE_SERVER_SETUP.COM (rename from .TEMPLATE)  and add   3 define/exec/system/nolog decw$server_pixel_depth 24   K The ELSA is not fast.  But I'm not sure that newer cards will work for your  system (I don't recallG what you said it was, but I seem to remember it being an older system).     > "Christopher Smith" <csmith@stu.parkland.edu> wrote in message1 news:1115952791.dfd60fccsmith@stu.parkland.edu... K Well, it was worth a shot.  They seem very nice cards from the specs, but I 7 can't be bothered to run NT on something to find out ;)   E I guess the next question is, what's the best route for good (PCI) 3d G performance on VMS -- if there is one?  Otherwise, what's a good 24-bit J framebuffer.  I've got an 8-bit board in there now, and it works, but it's somewhat offensive to my eye.   & Elsa Gloria Synergy keeps coming up...   Chris   # Date: Wed, 11 May 2005 10:22:21 GMT * From: "FredK" <fred.nospam@nospam.dec.com>  ( VMS does not support those cards. Sorry.   ------------------------------  % Date: Fri, 13 May 2005 09:30:18 -0400 & From: "Donald Plugge" <plugge@usa.net>/ Subject: Re: Info-Zip VMS to PC password needed 3 Message-ID: <RZ1he.293$fZ5.624@mencken.net.nih.gov>   K The VMS system is a VAX 4000 running VMS 6.2.  On the PC side I'm using the L XP Professional version of unzip that is built into the system (so I believeK it would be InnerMedia's DynaZip DLL).  I'll try another version of zip, to L see if it is zip specidfic.  The files that ask for a password are not largeH files, not even a MB.  And the entire zip archive is 27MB, therefore the size wouldn't be an issue.  G Is password locking built-into the Info-Zip file?  Perhaps a few header  bytes are causing the problem.   Don   7 "Steven M. Schweda" <sms@antinode.org> wrote in message , news:05051208111862_2860027B@antinode.org...( > From: "Donald Plugge" <plugge@usa.net> > 	 > > [...] L > > I downloaded the most recent version of Info-Zip, as I had problems with myL > > older version of Zip crashing on certain binary files.  Info-Zip versionC > > 2.31 (March 8th 2005) worked like a dream on ALL the data files 	 including 3 > > the binary files.  I ran it with the qualifiers  > > 1 > > $ ZIP -ruv {user}.zip {device}:[{user}...]*.*  > J >    "Didn't explode" and "worked like a dream" may _look_ similar without > actually _being_ similar.  > G > > I was able to download the resultant zipped folder to the PC and it  lookedK > > fine.  I could traverse the folders while in zip format and see all the  dataG > > in a hierarchical fashion.  However, when I went to extract all the  data, I H > > got about half way through the data and then began getting "password needed" I > > messages.  Obviously, something in the structure of some of the files  mostI > > have fooled Info-Zip into thinking they were password protected.  Has  anyoneB > > run into this problem when going from VMS to PC with Info-Zip? > H >    I haven't heard of this one, but if you went past the 2GB file sizeI > barrier, then almost anything could go wrong.  How big is that archive? B > Which version of which UnZip program on the PC?  VMS environment6 > (VAX/Alpha/IA64, VMS version, ...)?  PC environment? > F >    Does UnZip on the VMS system do any better (or even differently)? > J > ------------------------------------------------------------------------ > 6 >    Steven M. Schweda               (+1) 651-699-98185 >    382 South Warwick Street        sms@antinode-org  >    Saint Paul  MN  55105-2547    ------------------------------  + Date: Fri, 13 May 2005 08:58:07 -0500 (CDT) * From: sms@antinode.org (Steven M. Schweda)/ Subject: Re: Info-Zip VMS to PC password needed 2 Message-ID: <05051308580734_2860027B@antinode.org>  & From: "Donald Plugge" <plugge@usa.net>  M > The VMS system is a VAX 4000 running VMS 6.2.  On the PC side I'm using the N > XP Professional version of unzip that is built into the system (so I believeM > it would be InnerMedia's DynaZip DLL).  I'll try another version of zip, to N > see if it is zip specidfic.  The files that ask for a password are not largeJ > files, not even a MB.  And the entire zip archive is 27MB, therefore the > size wouldn't be an issue.  =    To me, it sounds like some defect in the PC's unzip (where G incompatibility with Info-ZIP is considered a defect).  I'd verify that G Info-ZIP UnZip works on VMS, and then try Info-ZIP UnZip for Windows on @ the PC.  (I'm not a significant Windows user, but traffic on theF Info-ZIP complaint list suggests a quick caution to be sure to get theB Info-ZIP kit for Windows, not the one for DOS, if you're really on	 Windows.)   I > Is password locking built-into the Info-Zip file?  Perhaps a few header   > bytes are causing the problem.  E    I haven't used it, but there is an encrypt option in Info-ZIP Zip, H and it seems reasonable to deduce that your PC unzip program thinks thatG it's seeing encrypted stuff.  As I recall, owing to export regulations, C Zip 2.x needed special build options to enable the feature, so it's G unlikely that your Zip was trying to do the extra stuff.  If you're not F using Zip "-V", I'd expect little or no weird stuff in the archive, so? I'd tend to blame your unzip's confusion on your unzip, pending ' production of evidence to the contrary.   3 > > > $ ZIP -ruv {user}.zip {device}:[{user}...]*.*   D    If you get _very_ desperate for straws at which to grasp, does itF make any difference to leave out the "-ru" (and start with no existingH "{user}.zip" file)?  The "..." should obviate "-r" on VMS.  I know of no= problems with "-u", but it's one more potential complication.   H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode-org     Saint Paul  MN  55105-2547    ------------------------------  % Date: Fri, 13 May 2005 07:56:05 -0700 # From: "Tom Linden" <tom@kednos.com> / Subject: Re: Info-Zip VMS to PC password needed ( Message-ID: <opsqpyfrj9zgicya@hyrrokkin>  C If you install cygwin on your PC you get a bash shell with a lot of ! useful stuff like gzip, tar, etc.   J IOn Fri, 13 May 2005 09:30:18 -0400, Donald Plugge <plugge@usa.net> wrote:  K > The VMS system is a VAX 4000 running VMS 6.2.  On the PC side I'm using    > the H > XP Professional version of unzip that is built into the system (so I  	 > believe L > it would be InnerMedia's DynaZip DLL).  I'll try another version of zip,   > toJ > see if it is zip specidfic.  The files that ask for a password are not   > large J > files, not even a MB.  And the entire zip archive is 27MB, therefore the > size wouldn't be an issue. > I > Is password locking built-into the Info-Zip file?  Perhaps a few header   > bytes are causing the problem. >  > Don  > 9 > "Steven M. Schweda" <sms@antinode.org> wrote in message . > news:05051208111862_2860027B@antinode.org...) >> From: "Donald Plugge" <plugge@usa.net>  >>
 >> > [...]J >> > I downloaded the most recent version of Info-Zip, as I had problems   >> with  > myG >> > older version of Zip crashing on certain binary files.  Info-Zip   
 >> versionD >> > 2.31 (March 8th 2005) worked like a dream on ALL the data files > including 4 >> > the binary files.  I ran it with the qualifiers >> >2 >> > $ ZIP -ruv {user}.zip {device}:[{user}...]*.* >>K >>    "Didn't explode" and "worked like a dream" may _look_ similar without  >> actually _being_ similar. >>H >> > I was able to download the resultant zipped folder to the PC and it > lookedJ >> > fine.  I could traverse the folders while in zip format and see all   >> the > dataH >> > in a hierarchical fashion.  However, when I went to extract all the	 > data, I I >> > got about half way through the data and then began getting "password 	 > needed" J >> > messages.  Obviously, something in the structure of some of the files > mostJ >> > have fooled Info-Zip into thinking they were password protected.  Has > anyoneC >> > run into this problem when going from VMS to PC with Info-Zip?  >>I >>    I haven't heard of this one, but if you went past the 2GB file size J >> barrier, then almost anything could go wrong.  How big is that archive?C >> Which version of which UnZip program on the PC?  VMS environment 7 >> (VAX/Alpha/IA64, VMS version, ...)?  PC environment?  >>G >>    Does UnZip on the VMS system do any better (or even differently)?  >>K >> ------------------------------------------------------------------------  >>7 >>    Steven M. Schweda               (+1) 651-699-9818 6 >>    382 South Warwick Street        sms@antinode-org  >>    Saint Paul  MN  55105-2547 >  >    ------------------------------  % Date: Fri, 13 May 2005 13:17:28 -0400 > From: "Chris Moore" <paynoattentionto@themanbehindthe.curtain> Subject: Re: KZPBA-CA Scsi Card 1 Message-ID: <Ii5he.5656$5u4.19894@nnrp1.uunet.ca>   J Be prepared for the added card to upset the bus definitions.  Might not onJ the box in question, but a similar addition that I did to an older AS1000AK assigned the new card as A, and dropped the internal to B (i.e. boot deviceoG had to be changed to DKB0 from DKA0, with attendant changes required inh! startup mounts, assignments, etc.e    ; "Peter Harper" <peter.harper@uk.bosch.com> wrote in messageu. news:d62fa9$m4g$1@ns2.fe.internet.bosch.com... > Hi Group,P >[# > Thanks for all the valuable info.. >:L > I will add a new scsi card at the weekend and move the tape drive to that. >P6 > Will let you know the results (many fingers crossed) > 	 > Cheers,A >P > Peter Harper > "i >n >o   ------------------------------    Date: 13 May 2005 08:43:57 -0700 From: dgahling@gmail.com5 Subject: license problem with openvms-alpha need help C Message-ID: <1115999037.329210.232510@g49g2000cwa.googlegroups.com>X  9 I've been trying this many times and cant get it to work.?E no matter what I do I get the same error, even trying other licenses.y5 I think I tried 6 or 8 times with different licenses.Z  ( I'm using the openvms hobbyist licenses,9 on a DEC 3000 300LX, entered the serial # and everything,r3 with the checksum and it always says the same errore6 "license checksum does not validate for openvms-alpha"   i'm running openvms 7.2e  @ I am not sure about the policy of posting this type of sensitiveD information in the newsgroup so I'll leave that for email if someone wants to help me with it.e   maybe I am doing this wrong-B I have a keyboard and mouse hooked up to the dec with a monitor as well.  i do a "boot -flag 0,1"e6 then do the following (some information is not shown):   $ set /startup opa0: $ set window_system 0o $ set writesysparams 0
 $ continue ...y" $ license register openvms-alpha -
 /activity=a -p+ /authorization=decus-can-#########-766515 -l /date=12-may-2006 -  /hardware_id=AB42401809 - 
 /issuer=dec -e /optinos=(no_share) -e /produder=dec -  /termination=12-may-2006 -
 /units=0 - /checksum=1-LAHN-NCOK-PHAN-OONKe  1 that is only one of 6 different licenses I tried.gC any suggestions? I'm thinking its because of the way I start up thes system.eF if I let it boot into xwindows (er whatever) try to login it says "lmf license check failed"g$ i hope someone can help with this...   ------------------------------    Date: 13 May 2005 09:05:04 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com>79 Subject: Re: license problem with openvms-alpha need help/C Message-ID: <1116000304.863877.186450@g49g2000cwa.googlegroups.com>    dgahl...@gmail.com wrote:l$ > $ license register openvms-alpha - > /activity=a -g- > /authorization=decus-can-#########-766515 -c > /date=12-may-2006 -6 > /hardware_id=AB42401809 -c > /issuer=dec -a  D Issuer should be "decus", not "dec". Tripped me up a couple of times too.   > /optinos=(no_share) -l  + Should be "/options" but it might not care.    > /produder=dec -a > /termination=12-may-2006 - > /units=0 -! > /checksum=1-LAHN-NCOK-PHAN-OONKD >0   ------------------------------  # Date: Fri, 13 May 2005 16:02:03 GMT>  From: John Santos <john@egh.com>9 Subject: Re: license problem with openvms-alpha need help % Message-ID: <%b4he.18$rI1.3@trnddc02>    dgahling@gmail.com wrote:m; > I've been trying this many times and cant get it to work.pG > no matter what I do I get the same error, even trying other licenses.h7 > I think I tried 6 or 8 times with different licenses.- > * > I'm using the openvms hobbyist licenses,; > on a DEC 3000 300LX, entered the serial # and everything,L5 > with the checksum and it always says the same error 8 > "license checksum does not validate for openvms-alpha"  6 This indicates a problem with the license registration7 command.  (You only need to do this once, successfully, 8 to enter the license into the license database, and then7 you're good to go until the license expires, next year.b6 So you don't want to put this in your system startup.)   >  > i'm running openvms 7.2  > B > I am not sure about the policy of posting this type of sensitiveF > information in the newsgroup so I'll leave that for email if someone > wants to help me with it.  >  > maybe I am doing this wrong-D > I have a keyboard and mouse hooked up to the dec with a monitor as > well.a > i do a "boot -flag 0,1"d8 > then do the following (some information is not shown): >  > $ set /startup opa0: > $ set window_system 0b > $ set writesysparams 0 > $ continue > ...e$ > $ license register openvms-alpha - > /activity=a -$- > /authorization=decus-can-#########-766515 -s > /date=12-may-2006 -h > /hardware_id=AB42401809 -o > /issuer=dec -o > /optinos=(no_share) -n > /produder=dec -  > /termination=12-may-2006 - > /units=0 -! > /checksum=1-LAHN-NCOK-PHAN-OONK   9 My license for my home Alpha looks just like this, exceptt8 for two things.  Mine was issued by DECUS-USA instead of5 DECUS-CANADA, and the /ISSUER= is "DECUS", not "DEC".i  9 (Of course, the authorization serial number, hardware ID,O. termination dates and checksum also differ...)  ! Double-check your license e-mail.c  8 The text has to match exactly or the checksum won't work% and the license won't get registered.e  < ("/optinos" is also obviously a typo, but shouldn't actually: matter since it is correct in the 1st 4 characters, and it9 would have complained of a parsing error, rather than thea7 checksum error, since DCL has to parse it before it cant compute the checksum.)   > 3 > that is only one of 6 different licenses I tried.nE > any suggestions? I'm thinking its because of the way I start up them	 > system.cH > if I let it boot into xwindows (er whatever) try to login it says "lmf > license check failed"a& > i hope someone can help with this...   HTH.     -- f John SantosW Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------    Date: 13 May 2005 09:24:17 -0700/ From: "dgahling@gmail.com" <dgahling@gmail.com>n9 Subject: Re: license problem with openvms-alpha need helphC Message-ID: <1116001457.815653.231910@g47g2000cwa.googlegroups.com>h  . ahh crap. yer right. it is decus not dec. doh! i'll try that and post back.  5 if it works i'm going to feel awefully stupid.....!!!- I've been using vms since 1976 must be one of those days...   Thanks!n   ------------------------------    Date: 13 May 2005 09:37:53 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com>n9 Subject: Re: license problem with openvms-alpha need help7A Message-ID: <1116002273.742753.9340@g47g2000cwa.googlegroups.com>e   dgahling@gmail.com wrote: 0 > ahh crap. yer right. it is decus not dec. doh! > i'll try that and post back. >n7 > if it works i'm going to feel awefully stupid.....!!!o  > I've been using vms since 1976 > must be one of those days... > 	 > Thanks!n  / Since 1976?  Must have been an early version...    ------------------------------  % Date: Fri, 13 May 2005 12:34:13 -0400g' From: Dave Froble <davef@tsoft-inc.com>s9 Subject: Re: license problem with openvms-alpha need help 0 Message-ID: <1189lmd4ccbd3d5@corp.supernews.com>   dgahling@gmail.com wrote:e; > I've been trying this many times and cant get it to work. G > no matter what I do I get the same error, even trying other licenses.m7 > I think I tried 6 or 8 times with different licenses.c > * > I'm using the openvms hobbyist licenses,; > on a DEC 3000 300LX, entered the serial # and everything,t5 > with the checksum and it always says the same errori8 > "license checksum does not validate for openvms-alpha" >  > i'm running openvms 7.29 > B > I am not sure about the policy of posting this type of sensitiveF > information in the newsgroup so I'll leave that for email if someone > wants to help me with it.  >  > maybe I am doing this wrong-D > I have a keyboard and mouse hooked up to the dec with a monitor as > well.- > i do a "boot -flag 0,1",8 > then do the following (some information is not shown): >  > $ set /startup opa0: > $ set window_system 0  > $ set writesysparams 0 > $ continue > ... $ > $ license register openvms-alpha - > /activity=a -D- > /authorization=decus-can-#########-766515 -  > /date=12-may-2006 -t > /hardware_id=AB42401809 -e > /issuer=dec -t > /optinos=(no_share) -  > /produder=dec -p > /termination=12-may-2006 - > /units=0 -! > /checksum=1-LAHN-NCOK-PHAN-OONK  > 3 > that is only one of 6 different licenses I tried.sE > any suggestions? I'm thinking its because of the way I start up the 	 > system.oH > if I let it boot into xwindows (er whatever) try to login it says "lmf > license check failed" & > i hope someone can help with this... >   + The license you've listed is a VMS license.v  H To run DECwindows, you need additional license(s).  The VMS license PAK ( is not enough to run a windowing system.   -- E4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Roadc Vanderbilt, PA  15486.   ------------------------------    Date: 13 May 2005 12:43:31 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)>9 Subject: Re: license problem with openvms-alpha need helpr3 Message-ID: <csDbfuDOEWb2@eisner.encompasserve.org>t  ^ In article <1115999037.329210.232510@g49g2000cwa.googlegroups.com>, dgahling@gmail.com writes:; > I've been trying this many times and cant get it to work.tG > no matter what I do I get the same error, even trying other licenses.a7 > I think I tried 6 or 8 times with different licenses.a > H    I've had the same problem.  Then I very carefully typed in each line,A    letter by letter and it worked.  Never did figure out my typo.o  H    Using @sys$update:vmslicence is better for fixing typos than entering    the license command by hand.g  D    Transfering most of the licenses electronically after you get the2    VMS and network licenses in is by far the best.   ------------------------------    Date: 13 May 2005 08:35:22 -0700' From: "toby" <toby@telegraphics.com.au>D& Subject: Re: OpenVMS and Mac OS X 10.4B Message-ID: <1115998522.164536.55260@z14g2000cwz.googlegroups.com>   toby wrote: 5 > ...You can bet that minor 'vulnerability' was fixedsF > within hours of the public announcement and is being qualified for a  > Software Update as we speak...  G http://apple.slashdot.org/article.pl?sid=05/05/13/1423240&tid=179&tid=3t   >  > --Toby >  > > 
 > > 		Zane   ------------------------------  % Date: Fri, 13 May 2005 07:49:12 -0400-# From: "John Smith" <a@nonymous.com>tK Subject: Re: OpenVMS IA64 Pilot Program site doesn't have the pilot programn, Message-ID: <jIidnQygv-uhCRnfRVn-1w@igs.net>   Soterro wrote: > Hello, >kG > I just tried to order the VMS IA64 SDK media kits for that DSPP Pilotl- > program somewhere on http://www.hp.com/dsppa > L (http://h21007.www2.hp.com/dspp/bus/bus_BusDetailPage_IDX/1,1252,4689,00.htm l)H > So you log in as DSPP member, the page gives you the username and passE > for the kiosk where you're supposed to get it, and after using them C > you're left on a page which says 'No kiosk associated with user'.  >d" > If it's a joke it's not funny :(    G You probably have to be using a Window's-based machine running Internet K Explorer, with an attached HP inkjet printed with HP-original equipment ink # cartridges in order for it to work.      --F OpenVMS - The never advertised operating system with the dwindling ISV base.-   ------------------------------  % Date: Fri, 13 May 2005 13:11:58 -0400O4 From: "Peter Weaver" <newsgroup@weaverconsulting.ca>K Subject: Re: OpenVMS IA64 Pilot Program site doesn't have the pilot programL+ Message-ID: <3ek5f2F3ibv1U1@individual.net>B   Soterro wrote: > Hello, >CG > I just tried to order the VMS IA64 SDK media kits for that DSPP PilotT- > program somewhere on http://www.hp.com/dsppi >oH (http://h21007.www2.hp.com/dspp/bus/bus_BusDetailPage_IDX/1,1252,4689,00 .html)H > So you log in as DSPP member, the page gives you the username and passE > for the kiosk where you're supposed to get it, and after using themaC > you're left on a page which says 'No kiosk associated with user'.] > " > If it's a joke it's not funny :( >[ > S]  F It worked last night, but now I see what you see. I think the usernameH they gave last night was different from what they are showing now, but IE can not recall exactly what it was then. Maybe you should give them as phone call?0   -- $ Peter Weaver Weaver Consulting Services Inc.h Canadian VAR for CHARON-VAXc www.weaverconsulting.cas   ------------------------------  # Date: Fri, 13 May 2005 17:37:50 GMT % From: "John Vottero" <John@mvpsi.com>-K Subject: Re: OpenVMS IA64 Pilot Program site doesn't have the pilot programn; Message-ID: <OB5he.2079$j17.615@newssvr33.news.prodigy.com>:  / "Soterro" <soterroatyahoocom> wrote in message e3 news:42845c45$0$294$4d4ef98e@read.news.ch.uu.net...0 > Hello, >cH > I just tried to order the VMS IA64 SDK media kits for that DSPP Pilot - > program somewhere on http://www.hp.com/dspppP > (http://h21007.www2.hp.com/dspp/bus/bus_BusDetailPage_IDX/1,1252,4689,00.html)M > So you log in as DSPP member, the page gives you the username and pass for rI > the kiosk where you're supposed to get it, and after using them you're a< > left on a page which says 'No kiosk associated with user'. >0" > If it's a joke it's not funny :( >a   It worked for me.    ------------------------------  % Date: Fri, 13 May 2005 15:58:34 +0800w From: prep@prep.synonet.como4 Subject: Re: OT: Only slightly off-shore programming- Message-ID: <87d5rviml1.fsf@prep.synonet.com>2  ) Dave Froble <davef@tsoft-inc.com> writes:   B > Defined contribution is a much better idea.  Once committed, theF > money is yours, and is not dependant upon the employer.  Much betterD > if you change jobs also.  I guess one argument for defined benefit? > is employee retention, but the other side of that is employern > retention.  B The name `Maxwell' ring a faint bell? As in bob, bob, Bod Maxwell,. late of the Mercury(?) pension fund and paper?     -- r< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.a@                                              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.   ------------------------------  + Date: Fri, 13 May 2005 09:48:02 +0000 (UTC)-3 From: "Richard Maher" <maher_rj@hotspamnotmail.com>i@ Subject: Re: Slow screen update with cobol generated executables? Message-ID: <d61t4h$1uo$1@nwrdmz03.dmz.ncs.ea.ibs-infra.bt.com>e   Hi,   E Don Braffit usually wanders around about once a month to answer COBOL 7 questions so it's probably worth waiting for his reply.i  G But in the mean time, something in the back of my mind tells me that onrD Alpha, when one uses the SCREEN-SECTION, the compiler translates theH ACCEPT/DISPLAY verbs into SMG$ calls. (Which may explain why we get thatG annoying screen clearing thing happening.) Anyway, I too prefer FMS andiK haven't used the screen-section in anger so this could be completely wrong.o  K However, if it does use SMG$ then it would be nice if one could control the?J smg$*_display_update stuff. Maybe the COBOL manual is full of all sorts of" useful advice. Has anybody looked?   Regards Richard Maher   = PS. When you say COBOL appears slow, I assume that you have a52 BASIC,PL/I,Fortran etc example that just flies by?  > "Dr. Dweeb" <NOSPAM_5msg0h202@sneakemail.com> wrote in message7 news:42840174$0$78288$157c6196@dreader1.cybercity.dk...6 > anguel@web.de wrote: > > JF Mezei wrote:l > >> anguel@web.de wrote: H > >>> I have real DEC text terminals (VT220) attached to a ALPHA machineH > >>> running OpenVMS 7.3. The serial speed is 9600, and all screens are > >>> built as expected. > >>> D > >>> But, when running an executable built from a cobol source, theD > >>> screenis built up like with a 600 baud connection - very slow. > >>C > >> The VT220 terminal is actually a fairly slow terminal in termsD$ > >> of processing escape sequences. > >n > > Oh - nice to know. > >B= > >> Have you tried putting the VT220 into display of controlk > >> characters to see ? > >a" > > No, not yet, but I'll try now. > >oE > >> Do you know which package is being used to generate the output ?i2 > >> is it a forms management system such as FMS ? > >>@ > >> Or does the program draw the screen completely on its own ? > > H > > The latter one. The screen layout is defined in a SCREEN SECTION and > > DISPLAYed as a whole.r > >y >eL > Wow, I never saw anyone try and actually use that functionality, prefering0 > FMS, TDMS, DECForms in chronological sequence.K > I guess it displays about thesame as aDCL programdoing the same thing :-)- >-2 > But hey, I never tried it, so what would I know. >  > Dr. Dweeb. >oL > ps: There is doubtless a COBOL compiler guy somewhere who knows the answer
 > to this. >O
 > > Anguel >9 >8   ------------------------------  # Date: Fri, 13 May 2005 13:27:53 GMTo( From: "Hein" <hein.nomail@hp.nomail.com>@ Subject: Re: Slow screen update with cobol generated executables2 Message-ID: <tX1he.5351$_W7.3164@news.cpqcorp.net>  > "Richard Maher" <maher_rj@hotspamnotmail.com> wrote in message9 news:d61t4h$1uo$1@nwrdmz03.dmz.ncs.ea.ibs-infra.bt.com...s > Hi,r > G > Don Braffit usually wanders around about once a month to answer COBOLu9 > questions so it's probably worth waiting for his reply.f  L I just pinged him, hoping (but not promissing) a better response time than a	 month :-)     I > But in the mean time, something in the back of my mind tells me that onEF > Alpha, when one uses the SCREEN-SECTION, the compiler translates the' > ACCEPT/DISPLAY verbs into SMG$ calls.    Use debugger to check?  K > Maybe the COBOL manual is full of all sorts of useful advice. Has anybodyn looked?a  	 Right on!n  ? > > >> Have you tried putting the VT220 into display of controlt > > >> characters to see ? > > > $ > > > No, not yet, but I'll try now.  J Yes, you may find the screen image is calculates are a 24*80 array and all  bytes, all spaces are send over?K Many PC based terminal emulators also have a 'data scope' setting which may  help.:   fwiw,  Hein.y   ------------------------------  % Date: Fri, 13 May 2005 10:10:53 -0400A- From: William Webb <william.w.webb@gmail.com>n@ Subject: Re: Slow screen update with cobol generated executables7 Message-ID: <8660a3a1050513071011bffa24@mail.gmail.com>i  C On 12 May 2005 05:02:22 -0700, anguel@web.de <anguel@web.de> wrote:t > JF Mezei wrote:  > > anguel@web.de wrote:G > >> I have real DEC text terminals (VT220) attached to a ALPHA machine,G > >> running OpenVMS 7.3. The serial speed is 9600, and all screens areq > >> built as expected.q > >>C > >> But, when running an executable built from a cobol source, theeC > >> screenis built up like with a 600 baud connection - very slow.l > >bB > > The VT220 terminal is actually a fairly slow terminal in terms# > > of processing escape sequences.a >=20 > Oh - nice to know. >=20< > > Have you tried putting the VT220 into display of control > > characters to see ?  >=20  > No, not yet, but I'll try now. >=20D > > Do you know which package is being used to generate the output ?1 > > is it a forms management system such as FMS ?l > >t? > > Or does the program draw the screen completely on its own ?  >=20F > The latter one. The screen layout is defined in a SCREEN SECTION and > DISPLAYed as a whole.t >=20 > Anguel >=20 >=20    E I worked at an agency where certain small locations used satellite asqB a backup means of communication.  And for character-based input onC VTs, EACH CHARACTER had to go up to the satellite, back down to thezD VMS system, back up to the satellite, and then down to the VT in the remote location.  B There should be another word for this as it goes beyond latency...   :^)a   WWWebb   --=20 C NOTE: This email address is only used for noncommerical VMS-relatede correspondence.tC All unsolicited commercial email will be deemed to be a request fore8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------    Date: 13 May 2005 07:14:11 -0700* From: "Don Braffitt" <don.braffitt@hp.com>@ Subject: Re: Slow screen update with cobol generated executablesC Message-ID: <1115993651.423435.309530@g49g2000cwa.googlegroups.com>u   Richard Maher wrote:F > But in the mean time, something in the back of my mind tells me thatE > on Alpha, when one uses the SCREEN-SECTION, the compiler translates>+ > the ACCEPT/DISPLAY verbs into SMG$ calls.t  C Richard is correct. When SCREEN-SECTION was implemented in COBOL onoE OpenVMS Alpha in 1992, SMG$ calls were used. This same implementationRG is what is available today with COBOL V2.8 on OpenVMS Alpha and OpenVMSl I64.  E The programmer control of what escape sequences are issued is limitede! to modifications to SMGTERMS.TXT:e  ; http://h71000.www7.hp.com/doc/82final/6296/6296pro_065.htmli -----i@ 11.  On OpenVMS, control sequences from SMGTERMS.TXT are used toD accomplish cursor positioning, screen erasure, and video attributes.D Refer to the Support for Non-HP Terminals chapter of the OpenVMS RTLF Screen Management (SMG$) Manual if you wish to customize SMGTERMS.TXT. -----e  G The mapping of SCREEN-SECTION statements to SMG$ calls by the COBOL RTLe  is not under programmer control.   - Don BraffittE   project leader, HP COBOL, SORT32, Hypersort for OpenVMS, Tru64 UNIX.   ------------------------------  % Date: Fri, 13 May 2005 11:22:46 -0400m- From: JF Mezei <jfmezei.spamnot@teksavvy.com>l@ Subject: Re: Slow screen update with cobol generated executables, Message-ID: <4284C641.38B1A3C7@teksavvy.com>   Don Braffitt wrote:   = > http://h71000.www7.hp.com/doc/82final/6296/6296pro_065.htmlt > ----- B > 11.  On OpenVMS, control sequences from SMGTERMS.TXT are used toF > accomplish cursor positioning, screen erasure, and video attributes.F > Refer to the Support for Non-HP Terminals chapter of the OpenVMS RTLH > Screen Management (SMG$) Manual if you wish to customize SMGTERMS.TXT.    2 Interesting use of global search and replace here.  C HP terminals are quite different beasts , using very different flowi control and escape sequences.D  ! VMS never supported HP terminals.   G One more reason HP needs to keep the words Digital, VMS, VAX etc in itsm< portfolio. Really silly to call DEC-C  -> HP-C for instance.   ------------------------------    Date: 13 May 2005 11:15:37 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: Strange PINGing ?, Message-ID: <42848c59$1@news.langstoeger.at>  a In article <1115954857.310860.102340@g43g2000cwa.googlegroups.com>, elementyl@hotmail.com writes:eB >The -t option is for timeout, so I would guess ping was patiently >waiting as specified.   AAARRRGGGGGHHH.- Thanks for not blaming me ;-)eG Indeed, I have mixed the (NT and UCX) syntax (and not noted for hours).dF Too bad that I have (at least) three different PINGs (M$, HPQ, PSC)...   --   Peter "EPLAN" LANGSTOEGER0% Network and OpenVMS system specialiste E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------   Date: 13 May 2005 14:01:50 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)+ Subject: Re: The continuing saga of the VAXf+ Message-ID: <3ejqaeF3gvvaU1@individual.net>-   OK, on to the next problem.h  ? I can now see devices.  But apparently, not boot from them. :-)2  D Here is some output.  I have repeated this about a half dozen times.2 It sure isn't like booting one of ny VS3100's  :-)  
 P00>>> sh deve, polling for units on cixcd0, slot 3, xmi0...1 dua1.2.0.3.0       $1$DUA1 (HSJ002)          HSX1w1 dua41.2.0.3.0      $1$DKA41 (HSJ002)        RRD46l P00>>> boot dua41.2.0.3.0  Initializing...r  F F   E   D   C   B   A   9   8   7   6   5   4   3   2   1   0   NODE #C                             A   M   .   .   .   P   P   P   P   TYPuC                             o   +   .   .   .   +   +   +   +   ST1sC                             .   .   .   .   .   E   E   E   B   BPD C                             o   +   .   .   .   +   +   +   +   ST2)C                             .   .   .   .   .   E   E   E   B   BPDdC                             +   +   .   .   .   +   +   +   +   ST3wC                             .   .   .   .   .   E   E   E   B   BPD   H     +   .   .   .   .   .   +   .   .   .   .   +   .   +       C0 XMI +B .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   C1B .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   C2B .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   C3  C                             .  A0   .   .   .   .   .   .   .   ILV6E                             . 512   .   .   .   .   .   .   .   512MB2  H Firmware Rev = S4.4-4857      SROM Rev = S3.1-0      SYS SN = NI525N9935 P00>>>  
 Booting...' Connecting to boot device dua41.2.0.3.0n Created device: dua41.2.0.3.0r/ block 0 of dua41.2.0.3.0 is  a valid boot blocke$ reading 87 blocks from dua41.2.0.3.0 bootstrap code read in base = 154000, start = 200  boot device name = dua41.2.0.3.0 boot flags  0,2,0  boot device type = 20n controller ID = af unit number = 41 node ID = 2e channel = 0  slot = 3 hose = 0 jumping to bootstrap at 154200  % -------------------------------------s  0 And there it sits.  Until I hit ^P.  Then I get.      + CPU:0 Console entry reason: ^P or Node Halt   ) Entry PC: 00154E07     Entry PSL:041F0200Z  	 P00>>> ^Cp
 P00>>> sh devy, polling for units on cixcd0, slot 3, xmi0... Resetting IO subsystem...r P00>>>   sh deva, polling for units on cixcd0, slot 3, xmi0...1 dua1.2.0.3.0       $1$DUA1 (HSJ002)          HSX1n1 dua41.2.0.3.0      $1$DKA41 (HSJ002)        RRD46r  / Well, at least my devices are still there.  :-(p  C Is there some bootflag I need to add either because of the model or_# maybe because it's booting from CI?t   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>   t   ------------------------------  % Date: Fri, 13 May 2005 11:39:40 -0400O* From: "Marty O'Connor" <moconnor@dvfs.com>+ Subject: Re: The continuing saga of the VAXp+ Message-ID: <3ek00lF3f0vgU1@individual.net>   6 "Bill Gunshannon" <bill@cs.uofs.edu> wrote in message % news:3ejqaeF3gvvaU1@individual.net...n > OK, on to the next problem.u >nA > I can now see devices.  But apparently, not boot from them. :-)w >gF > Here is some output.  I have repeated this about a half dozen times.4 > It sure isn't like booting one of ny VS3100's  :-)  M I seem to recall that the VS3100 could not boot off a disk larger than 1 GB. o. I may be wrong but it'd be something to check.   Marty    ------------------------------    Date: 13 May 2005 09:30:09 -0700 From: sean@obanion.us-+ Subject: Re: The continuing saga of the VAX C Message-ID: <1116001809.391465.240280@g47g2000cwa.googlegroups.com>-  A I think the 1GB limitation as for booting from a local SCSI disk,m4 because the firmware couldn't count blocks past 1GB.  @ I would check the cluster related parameters like EXPECTED_VOTES7 (probably should be 1 at the moment) and VOTES (ditto).e  D You will probably want to do a conversational boot, which will allowA you to SHOW and SET these values between the boot command and VMS  actually starting.  F The boot command flags that need to be set to do this, and a few otherG things, are system specific and can be found in the on-line doc and theoD FAQ.  Once you find the details you need, print it out and keep in aA folder ... you always need them when the Internet is slow or yourt connection is down.e     Sean       Marty O'Connor wrote:b7 > "Bill Gunshannon" <bill@cs.uofs.edu> wrote in messaget' > news:3ejqaeF3gvvaU1@individual.net...e > > OK, on to the next problem.o > >hC > > I can now see devices.  But apparently, not boot from them. :-)Z > >mA > > Here is some output.  I have repeated this about a half dozenP times.6 > > It sure isn't like booting one of ny VS3100's  :-) >.C > I seem to recall that the VS3100 could not boot off a disk largerf
 than 1 GB.0 > I may be wrong but it'd be something to check. >  > Martyh   ------------------------------   Date: 13 May 2005 16:43:39 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)+ Subject: Re: The continuing saga of the VAXc+ Message-ID: <3ek3pqF3k0fbU1@individual.net>e  + In article <3ek00lF3f0vgU1@individual.net>,e- 	"Marty O'Connor" <moconnor@dvfs.com> writes:o > 8 > "Bill Gunshannon" <bill@cs.uofs.edu> wrote in message ' > news:3ejqaeF3gvvaU1@individual.net...e >> OK, on to the next problem. >>B >> I can now see devices.  But apparently, not boot from them. :-) >>G >> Here is some output.  I have repeated this about a half dozen times. 5 >> It sure isn't like booting one of ny VS3100's  :-)  > O > I seem to recall that the VS3100 could not boot off a disk larger than 1 GB. i0 > I may be wrong but it'd be something to check. > D I was comparing it to the ease with which I can boot and install VMSH on a 3100.  This machine is a 6640 with disks on CI from a StorageWorks.F box.  I thought that would be obvious from the info I posted.  Nothing at all like 3100.  :-(   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: 13 May 2005 16:45:24 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)+ Subject: Re: The continuing saga of the VAXl+ Message-ID: <3ek3t3F3k0fbU2@individual.net>t  C In article <1116001809.391465.240280@g47g2000cwa.googlegroups.com>,  	sean@obanion.us writes:C > I think the 1GB limitation as for booting from a local SCSI disk,d6 > because the firmware couldn't count blocks past 1GB. > B > I would check the cluster related parameters like EXPECTED_VOTES9 > (probably should be 1 at the moment) and VOTES (ditto).d  ? I think you need VMS installed first.  I am just trying to boota" from the install CD at the moment.   Must be because it's friday.   bill f   -- eJ 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>   h   ------------------------------    Date: 13 May 2005 09:52:52 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com> + Subject: Re: The continuing saga of the VAXhB Message-ID: <1116003172.090334.85340@g14g2000cwa.googlegroups.com>   Bill Gunshannon wrote: > OK, on to the next problem.> >$A > I can now see devices.  But apparently, not boot from them. :-)l >"F > Here is some output.  I have repeated this about a half dozen times.4 > It sure isn't like booting one of ny VS3100's  :-) >n > P00>>> sh devo. > polling for units on cixcd0, slot 3, xmi0...3 > dua1.2.0.3.0       $1$DUA1 (HSJ002)          HSX1 3 > dua41.2.0.3.0      $1$DKA41 (HSJ002)        RRD46v > P00>>> boot dua41.2.0.3.0l > Initializing...> >gF > F   E   D   C   B   A   9   8   7   6   5   4   3   2   1   0   NODE #dE >                             A   M   .   .   .   P   P   P   P   TYPtE >                             o   +   .   .   .   +   +   +   +   ST1sE >                             .   .   .   .   .   E   E   E   B   BPDrE >                             o   +   .   .   .   +   +   +   +   ST2tE >                             .   .   .   .   .   E   E   E   B   BPDcE >                             +   +   .   .   .   +   +   +   +   ST3iE >                             .   .   .   .   .   E   E   E   B   BPD, >.D >     +   .   .   .   .   .   +   .   .   .   .   +   .   +       C0 XMI +rD > .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   C1D > .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   C2D > .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   C3 >oE >                             .  A0   .   .   .   .   .   .   .   ILV-G >                             . 512   .   .   .   .   .   .   .   512MB  >y? > Firmware Rev = S4.4-4857      SROM Rev = S3.1-0      SYS SN =i
 NI525N9935 > P00>>> > Booting...) > Connecting to boot device dua41.2.0.3.0h > Created device: dua41.2.0.3.0i1 > block 0 of dua41.2.0.3.0 is  a valid boot blocks& > reading 87 blocks from dua41.2.0.3.0 > bootstrap code read in > base = 154000, start = 200" > boot device name = dua41.2.0.3.0 > boot flags  0,2,0r > boot device type = 20h > controller ID = at > unit number = 41
 > node ID = 2 
 > channel = 0"
 > slot = 3
 > hose = 0  > jumping to bootstrap at 154200 >4' > -------------------------------------o >P2 > And there it sits.  Until I hit ^P.  Then I get. >l >d >n- > CPU:0 Console entry reason: ^P or Node Haltr > + > Entry PC: 00154E07     Entry PSL:041F0200  >n > P00>>> ^Cs > P00>>> sh devs. > polling for units on cixcd0, slot 3, xmi0... > Resetting IO subsystem...e > P00>>>   sh dev:. > polling for units on cixcd0, slot 3, xmi0...3 > dua1.2.0.3.0       $1$DUA1 (HSJ002)          HSX1D3 > dua41.2.0.3.0      $1$DKA41 (HSJ002)        RRD46c >X1 > Well, at least my devices are still there.  :-(t > E > Is there some bootflag I need to add either because of the model ore% > maybe because it's booting from CI?t >i > bill >e > --E > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Threer wolvesF > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > University of Scranton   |@ > Scranton, Pennsylvania   |         #include <std.disclaimer.h>  F It's been a while since I've played with CI connected stuff (2001) butG I didn't know you could boot from a CD across the CI.  I've booted from @ a local CD of course and from a CD on an Infoserver, but never aC HSJ/HSC.  The fact that the console lists the CD as "dua41.2.0.3.0"-C rather than a DK device makes me wonder a bit.  Also the boot flags D being "0,2,0" doesn't seem right either.  Either it's trying to boot? SYS2 or passing a flag to sysboot (I don't have the list of bit @ definitions handy).  It may be a red herring but just seems odd.   ------------------------------  % Date: Fri, 13 May 2005 18:19:09 +0100p< From: "John Griffiths" <john_ngNO_SPAM_PLEASE@btconnect.com> Subject: VT525 TFT Monitor4 Message-ID: <d62nhq$t0i$1$8302bc10@news.demon.co.uk>   Hi  L I am trying to replace CRT monitors connected to a VT525 terminal with a 17"F TFT monitor. I have tried one monitor (difusion) but it fails to work,  something to do with wrong sync.  J The VT525 uses 37.8Khz and 72Hz, however most manufactures quote the rangeG of vertical and horizontal frequencies they cover, but the one I tested7L seemed to have a table within the quoted range that the monitor works (foundG in user guide after purchase), this excludes the configuration that them
 VT525 covers.i  B Have any of the members of this group been successful if finding aH manufacturer whose monitor will work, or is there a way of modifying the< VT525 to operate on the frequency settings as used by TFT's.  L Have also searched web looking for circuit diagram for the 525, but no luck.   Thanks in anticipation   John   ------------------------------   End of INFO-VAX 2005.266 ************************