1 INFO-VAX	Wed, 15 Mar 2006	Volume 2006 : Issue 148       Contents: Confused drives in RAID  DECterm performance  Re: DECterm performance  Re: DECterm performance  Re: DECterm performance  Re: DECterm performance 0 Re: Device Naming: (was OPA0 Console connection)0 Re: Device Naming: (was OPA0 Console connection)0 Re: Device Naming: (was OPA0 Console connection) Re: Eve - displaying ESC? % Re: FIPS 200 has now been promulgated  GLIB and GTK for OpenVMS ?1 Re: Image Backup and Restore of Bound Volume sets % Re: Itanium still not on alpha level!  Re: Mtools for VMS (?) Re: Mtools for VMS (?) Re: Mtools for VMS (?)? Re: Mysterious revision date changes caused by Advanced Server?  Re: rtvax300 revisions& SCT Banner software running on OpenVMS Re: VMS Updates  Re: VMS Updates  Re: VMS Updates  VXT 2000+ monitor options  Re: VXT 2000+ monitor options   F ----------------------------------------------------------------------  % Date: Wed, 15 Mar 2006 09:13:33 +0100 ( From: S <soterroatyahoodotcom@yahoo.com>  Subject: Confused drives in RAID6 Message-ID: <pan.2006.03.15.08.13.29.859000@yahoo.com>   Hi all,   G Somehow over the weekend location change (I'll spare the gory details), J the printed labels of my small 7 member RAID 5 set peeled off, and now I'mJ left with a bunch of identical drives only god knows which into which slot
 should go.  G The RAID configuration utility obviously shows everything as failed and J asks me to accept this new configuration. No way. I'd rather try to figure@ out, if possible, where was each drive situated. Is this kind ofE information readable somewhere or I'm just asking too much? (or there I might be the obvious and dumb way which I'm just missing being too tired)   G The machine is an AS2100, and the RCU is the latest one around I guess. A I know, I could just restore the stuff from the backup, but... :)   
 Thanks a lot,  S    ------------------------------  % Date: Wed, 15 Mar 2006 09:54:00 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>  Subject: DECterm performance, Message-ID: <44182A85.A086ED96@teksavvy.com>   BIKE: Vaxstation 3100  VELO: 4000-600  C In the past, (when VELO was the venerable all mighty Microvax II, I E would open a decterm on BIKE from which I did a SET HOST VELO and ran $ ALL-IN-1 on VELO, displayed on BIKE.  G Now, I tried to have VELO do the CREATE/TERM targetted at BIKE, and the E screen/window performance difference is extreme. Screen refreshes are 5 MUCH MUCH MUCH faster. Scrolling is extremely faster.   G I know that a 3100 is slow by today's standards, and I certaintly never G expected to be able to generate real time 3d renderings/animations on a C 3100. But I never realised that running the X server, DECTERM and a G CTERM session would be so much slower. Yet, I never found the CPU to be  that busy on the 3100.  D From the ethernet point of view, is it correct to state that a CTERMG (SET HOST) session would be far easier on the ethernet interface than a 0 remote DECTERM targetted at the 3100's display ?  H Is DECTERM really such a CPU hog that it becomes significantly slower on an older machine ?   ------------------------------  % Date: Wed, 15 Mar 2006 11:02:20 -0500 * From: "FredK" <fred.nospam@nospam.dec.com>  Subject: Re: DECterm performance, Message-ID: <44183a8d$1@usenet01.boi.hp.com>  : "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message& news:44182A85.A086ED96@teksavvy.com... > BIKE: Vaxstation 3100  > VELO: 4000-600 > E > In the past, (when VELO was the venerable all mighty Microvax II, I G > would open a decterm on BIKE from which I did a SET HOST VELO and ran & > ALL-IN-1 on VELO, displayed on BIKE. > I > Now, I tried to have VELO do the CREATE/TERM targetted at BIKE, and the G > screen/window performance difference is extreme. Screen refreshes are 7 > MUCH MUCH MUCH faster. Scrolling is extremely faster.  > I > I know that a 3100 is slow by today's standards, and I certaintly never I > expected to be able to generate real time 3d renderings/animations on a E > 3100. But I never realised that running the X server, DECTERM and a I > CTERM session would be so much slower. Yet, I never found the CPU to be  > that busy on the 3100. > F > From the ethernet point of view, is it correct to state that a CTERMI > (SET HOST) session would be far easier on the ethernet interface than a 2 > remote DECTERM targetted at the 3100's display ? > J > Is DECTERM really such a CPU hog that it becomes significantly slower on > an older machine ?  H You've cut out the middle man.  Including a couple buffer copies and theJ CTERM overhead.  Remember that ultimately for text mode operations DECtermJ sends draw text commands, clear area commands, and move area commands (andL all of which would have to be generated anyway regardless of if the commandsH are over a remote or local wire) - and none of which are CPU intensive -F they are graphics hardware intensive.  All of the drawing commands areK relatively compact and in terms of the data over the wire - not a whole lot  more than CTERM has to send.   ------------------------------  % Date: Wed, 15 Mar 2006 12:01:26 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>   Subject: Re: DECterm performance, Message-ID: <4418485B.C33B6A75@teksavvy.com>   FredK wrote:J > You've cut out the middle man.  Including a couple buffer copies and theL > CTERM overhead.  Remember that ultimately for text mode operations DECtermL > sends draw text commands, clear area commands, and move area commands (andN > all of which would have to be generated anyway regardless of if the commandsJ > are over a remote or local wire) - and none of which are CPU intensive -    H OK, another comparison: a DECTERM running on VELO but displaying on BIKEF is much faster than a decterm running on BIKE displayed on BIKE. (both doing a DCL "TYPE" command.)  A Does DECTERM itself involve heavy duty CPU processing ? Or is the D bottleneck the pseudo terminal communicatiosn between the actual DCLI process and the DECTERM controller ? Are FT devices very fast/efficient ?   G When I consider the CPU  horsepower needed for a  VT terminal, I didn't O expect DECTERM to require much CPU to rasterize the ANSI text/escape sequences.    ------------------------------  % Date: Wed, 15 Mar 2006 12:36:10 -0500 * From: "FredK" <fred.nospam@nospam.dec.com>  Subject: Re: DECterm performance, Message-ID: <4418508a$1@usenet01.boi.hp.com>  : "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message& news:4418485B.C33B6A75@teksavvy.com... > FredK wrote:L > > You've cut out the middle man.  Including a couple buffer copies and theF > > CTERM overhead.  Remember that ultimately for text mode operations DECterm I > > sends draw text commands, clear area commands, and move area commands  (andG > > all of which would have to be generated anyway regardless of if the  commandsL > > are over a remote or local wire) - and none of which are CPU intensive - >  > J > OK, another comparison: a DECTERM running on VELO but displaying on BIKEH > is much faster than a decterm running on BIKE displayed on BIKE. (both > doing a DCL "TYPE" command.) > C > Does DECTERM itself involve heavy duty CPU processing ? Or is the F > bottleneck the pseudo terminal communicatiosn between the actual DCLK > process and the DECTERM controller ? Are FT devices very fast/efficient ?  > I > When I consider the CPU  horsepower needed for a  VT terminal, I didn't F > expect DECTERM to require much CPU to rasterize the ANSI text/escape
 sequences.  K It is called distributed processing.  The VAX sucks for CPU power.  DECterm A itself isn't CPU hungry, but the VAX doesn't have a lot to spare.   K If you want faster scrolling (at least in the typical direction) change the A batch scroll parameter in the options to a number greater than 0.    ------------------------------  % Date: Wed, 15 Mar 2006 13:23:24 -0500 , From: Forrest Kenney <Forrest.Kenney@hp.com>  Subject: Re: DECterm performance& Message-ID: <44185B9C.1F8168FB@hp.com>  ? 	FTDRIVER has as little overhead as we could manage within the  A constraints of the O.S.  On the terminal side it the same as any  A terminal.  On the control side there are no buffer probes, extra  I buffer copies are avoided, context switches are avoided where possible.   G There is not need to wait for the system to get to IPL4 to complete an  I I/O.  There is no need to deliver and AST to fill in the IOSB.  When the  D orignal driver was tested the cost for a single character sent to a D terminal and the echo returned was 1/2 what it was when compared to # previous pseudo terminals for VMS.    @ 	Not free by any stretch but as fast as we could figure out how F to make it.  Much later buffer object, and other concepts used in the ' pseudo terminals showed up in Fast I/O.        Forrest  OpenVMS        JF Mezei wrote:  >  > FredK wrote:L > > You've cut out the middle man.  Including a couple buffer copies and theN > > CTERM overhead.  Remember that ultimately for text mode operations DECtermN > > sends draw text commands, clear area commands, and move area commands (andP > > all of which would have to be generated anyway regardless of if the commandsL > > are over a remote or local wire) - and none of which are CPU intensive - > J > OK, another comparison: a DECTERM running on VELO but displaying on BIKEH > is much faster than a decterm running on BIKE displayed on BIKE. (both > doing a DCL "TYPE" command.) > C > Does DECTERM itself involve heavy duty CPU processing ? Or is the F > bottleneck the pseudo terminal communicatiosn between the actual DCLK > process and the DECTERM controller ? Are FT devices very fast/efficient ?  > I > When I consider the CPU  horsepower needed for a  VT terminal, I didn't Q > expect DECTERM to require much CPU to rasterize the ANSI text/escape sequences.    ------------------------------  # Date: Wed, 15 Mar 2006 17:38:01 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>9 Subject: Re: Device Naming: (was OPA0 Console connection) 2 Message-ID: <ZhYRf.4735$h06.3645@news.cpqcorp.net>   Tom Linden wrote: J > I understand your comments, never-the-less  it should be possible to useK > names for the devices which are nmemonic,  after all VMS certainly knows  H > what it has, I shouldn't have to figure out which device is the CD andJ >  which the DVD or the Floppy or whatever.  IIRC, when Ultrix was replaceF > with OSF-1 similar changes were made in the /dev naming conventions.  I    Tell me how.  I don't know how to reliably identify all arbitrary I/O  F devices (only having looked at this closely for about ten years now), H and I don't know how to assign mnemonic names -- other than via logical D names, an approach which you've already rejected -- that reasonably I maintain the names, how to deal with multiple devices (DVD or otherwise)  I that can arise in most any non-trivial case, and I don't know how you or  E others will generally benefit from the effort involved in re-booting  ? some or all of the human-oriented device naming implementation.   H    Multi-path really makes this stuff interesting, too, as there can be 1 any number of paths to the particular I/O device.   I    Y'all won't be happy if we require device support for a user-settable  A device name, too, as that will eliminate various low-end widgets.   G    A local version of the MicroVAX subroutine from SYLOGICALS.TEMPLATE  E is about the only way I can see to set that up, at least not without  H greatly restricting what devices we can support within the (new) scheme.  D    Again, tell me how to do this -- I don't know of a reliable way. E (And I don't see how an overhaul in this area is going to have a big  C payoff for you and for other folks, which is the other requirement  ! involved in such a large effort.)    ------------------------------  % Date: Wed, 15 Mar 2006 12:07:38 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 9 Subject: Re: Device Naming: (was OPA0 Console connection) , Message-ID: <441849CF.C849F5C2@teksavvy.com>   Hoff Hoffman wrote: E >    Again, tell me how to do this -- I don't know of a reliable way.   C What exactly is wrong with the current VMS naming scheme that would  require a change ?  E My only complaint is the name of the ethernet devices that seem to be D random (which in term change the name of the TCPIP interface names).  H But I find the current naming scheme to be logical and quite acceptable.   ------------------------------    Date: 15 Mar 2006 19:24:45 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)9 Subject: Re: Device Naming: (was OPA0 Console connection) * Message-ID: <441869fd@news.langstoeger.at>  \ In article <441849CF.C849F5C2@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes:F >My only complaint is the name of the ethernet devices that seem to beE >random (which in term change the name of the TCPIP interface names).   H Make a LAN Failover Device 'virtualization' and you always have the sameL ifc names for the 'upper' layers (like TCPIP and DECnet) and you're done ;-)   --   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: Wed, 15 Mar 2006 09:47:29 -0500  From: norm.raphael@metso.com" Subject: Re: Eve - displaying ESC?Q Message-ID: <OF1BD82B27.E0E1560E-ON85257132.00511D44-85257132.005140A0@metso.com>   H "Peter Weaver" <newsonly@weaverconsulting.ca> wrote on 03/14/2006 08:14= :10  PM:   > > <mabbuttg@yahoo.ca> wrote in message news:1141963094.592037.' > 18970@u72g2000cwu.googlegroups.com... C > > Is there anyway to get Eve to display something where an escape H > > character occurs in a text file (not necessarily the escape itself = -  >  > D > EVE actually displays ASCII 26 instead of ASCII 27 for the escape,H > so if you have a terminal emulator that can translate 26 into somethi= ng. > that can be displayed then you will be fine.  F Pardon a question out of ignorance, but does EVE also display ASCII 26E for other "control characters?"  That would make the above suggestion  less than optimal.   > D > If you are running WRQ Reflection then it has "Translation Tables"D > built into it.  First you have to enable "Data Stream Translation"H > then define a key to open the Translation Tables (it is all in the he= lp, H > just search for Translation Tables Overview) then define character 1A=  H > (that is 26 in hex; TPU displays character 26 instead of 27 to make s= ure H > it does not do weird things to the display) to another character. I u= seH > A7 since that is a character I doubt I will ever need and it looks li= ke! > a suitable ESC character to me.  > B > To see what A7 looks like in your terminal emulator you can type >  > $ x[0,8]=3D%XA7  > $ show sym x >   X =3D "=15"  > H > Other terminal emulators may have the same thing built in, just remem= ber > > to change character 26 instead of 27 and you should be fine. > D > > I've read there are some issues with terminals interpreting themH > > instead of displaying them)?  I'm doing some work with printer form= s H > > and PCL escape codes and I'm finding the lack of them annoying when=  I > > go back to edit a file.  >  > >... > H > If you are working with PCL codes then this TPU code might help you o= ut;  >  > TRANSLATE_PCL.TPU;17 >  > ! H > !   This procedure copies the current buffer and replaces all PCL cod= e 1 > !   (we hope) with human readable descriptions.  > !  > !   29-SEP-2004  Peter Weaver  > ! - > PROCEDURE  translate_controls  (char_range)  >      LOCAL >          replace_text; > ! 7 > !  The  range  *must*  be  a  single  character  long  > ! & >      IF  LENGTH  (char_range)  <>  1 >      THEN RETURN  0;
 >      ENDIF;  > !  > !  > !     IF char_range =3D "@" 
 > !   THEN' > !      Select_start =3D SELECT(NONE);  > !      MOVE_HORIZONTAL (3);   > !      isPJL =3D SELECT_RANGE; > !      IF isPJL =3D "PJL"  > !         THEN > !  >      ERASE  (char_range);  >  > ! E > !    Loop until we see a termination character or a single chracter 
 > sequence > ! ! >      done_this_sequence :=3D 0;  >  >      loop * >         EXITIF done_this_sequence =3D 1; >         parse_sequence ; >      endloop;  >  >      RETURN  1;  >  > ENDPROCEDURE;  >  > PROCEDURE parse_sequence > 6 >      Parameterized_character :=3D CURRENT_CHARACTER; >      ERASE_CHARACTER (1);  > # >      CASE Parameterized_character  >         ["E"]: ! <ESC>E + >            COPY_TEXT ("{Printer Reset}"); ' >            done_this_sequence :=3D 1;  >         ["=3D"]: ! <ESC>=3D , >            COPY_TEXT ("{Half Line Feed}");' >            done_this_sequence :=3D 1;  >         ["9"]: ! <ESC>9 6 >            COPY_TEXT ("{Clear Horizontal Margins}");' >            done_this_sequence :=3D 1;  >         ["P"]: ! <ESC>P 5 >            COPY_TEXT ("{Device Control Sequence}"); ' >            done_this_sequence :=3D 1;  >         ["]"]: ! <ESC>] 7 >            COPY_TEXT ("{VMS Queue Manager Command}"); ' >            done_this_sequence :=3D 1;  >         ["\"]: ! <ESC>\ / >            COPY_TEXT ("{String Terminator}"); ' >            done_this_sequence :=3D 1;  >   >         ["(",")"]: ! <ESC>(?#?0 >            get_parameterized_escape_sequences;' >            get_termination_character; ! >            CASE group_character " >               ["I"]: ! <ESC>(i#?- >                  CASE termination_character + >                     ["D","d"]: ! <ESC>(ID 4 >                        COPY_TEXT ('{Symbol Set}'); >                  ENDCASE; " >               ["s"]: ! <ESC>(s#?- >                  CASE termination_character , >                     ["P","p"]: ! <ESC>(s#PH >                        COPY_TEXT ('{Spacing is: ' + value_string + '}= '); , >                     ["H","h"]: ! <ESC>(s#HH >                        COPY_TEXT ('{Pitch is: ' + value_string + '}')= ; , >                     ["V","v"]: ! <ESC>(s#VH >                        COPY_TEXT ('{Height is: ' + value_string + '}'= );, >                     ["S","s"]: ! <ESC>(s#SH >                        COPY_TEXT ('{Style is: ' + value_string + '}')= ; , >                     ["B","b"]: ! <ESC>(s#BH >                        COPY_TEXT ('{Stroke Weight is: ' + value_strin= g +  '}'); , >                     ["T","t"]: ! <ESC>(s#TH >                        COPY_TEXT ('{Typeface is: ' + value_string + '= }'); > ; >            ! If the end is W then if start is ) then Font @ >            ! If the end is W then if start is ( then character, >            ! otherwie ( and ) are the same >                   ENDCASE; >  >               [OTHERWISE]:@ >                  COPY_TEXT ('{**Unknown: ' + group_character +C >                      value_string + termination_character + '}');  >            ENDCASE;  >         ["%"]: ! <ESC>%?#?0 >            get_parameterized_escape_sequences; >  >         ["&"]: ! <ESC>&?#?0 >            get_parameterized_escape_sequences;' >            get_termination_character; ! >            CASE group_character " >               ["l"]: ! <ESC>&l#?- >                  CASE termination_character , >                     ["X","x"]: ! <ESC>&l#XH >                        COPY_TEXT ('{Print ' + value_string + ' copies= }');, >                     ["S","s"]: ! <ESC>&l#S* >                        CASE value_string. >                           ["0"]: ! <ESC>&l0S7 >                              COPY_TEXT ('{Simplex}'); . >                           ["1"]: ! <ESC>&l1SH >                              COPY_TEXT ('{Duplex, Long-Edge Binding}'= );. >                           ["2"]: ! <ESC>&l2SH >                              COPY_TEXT ('{Duplex, Short-Edge Binding}= '); ( >                           [OTHERWISE]:A >                              COPY_TEXT ('{**Unknown Duplex: ' + @ >                                           value_string + '}');! >                        ENDCASE; , >                     ["U","u"]: ! <ESC>&l#UH >                        COPY_TEXT ('{Long-edge Offset Registration: ' = + @ >                                           value_string + '}');, >                     ["Z","z"]: ! <ESC>&l#ZH >                        COPY_TEXT ('{Short-edge Offset Registration: '=  +@ >                                           value_string + '}');, >                     ["T","t"]: ! <ESC>&l#TH >                        COPY_TEXT ('{Job Separation: ' +value_string +=   '}'); , >                     ["G","g"]: ! <ESC>&l#GH >                        COPY_TEXT ('{Output Bin: ' +value_string + '}'= );, >                     ["A","a"]: ! <ESC>&l#AH >                        COPY_TEXT ('{Page Size: ' +value_string + '}')= ; , >                     ["H","h"]: ! <ESC>&l#H? >                        COPY_TEXT ('{Paper (Media) Source: ' + A >                                            value_string + '}'); , >                     ["P","p"]: ! <ESC>&l#PA >                        COPY_TEXT ('{Page Length (Obsolete): ' + A >                                            value_string + '}'); , >                     ["O","o"]: ! <ESC>&l#OH >                        COPY_TEXT ('{Orientation: ' +value_string + '}= '); , >                     ["E","e"]: ! <ESC>&l#EH >                        COPY_TEXT ('{Top Margin: ' +value_string + '}'= );, >                     ["F","f"]: ! <ESC>&l#FH >                        COPY_TEXT ('{Text Length: ' +value_string + '}= '); , >                     ["L","l"]: ! <ESC>&l#LH >                        COPY_TEXT ('{Perforation Skip: ' +value_string=  + '}'); , >                     ["C","c"]: ! <ESC>&l#C@ >                        COPY_TEXT ('{Vertical Motion Index: ' +B >                                             value_string + '}');, >                     ["D","d"]: ! <ESC>&l#DH >                        COPY_TEXT ('{Line Spacing: ' +value_string + '= }'); >  > " >                     [OTHERWISE]:F >                        COPY_TEXT ('{**Unknown: ' + group_character +< >                                             value_string +H >                                             termination_character + '= }'); >                  ENDCASE;  > " >               ["u"]: ! <ESC>&u#?- >                  CASE termination_character , >                     ["D","d"]: ! <ESC>&u#DH >                        COPY_TEXT ('{Unit of Measure: ' +value_string = +  '}'); " >                     [OTHERWISE]:F >                        COPY_TEXT ('{**Unknown: ' + group_character +< >                                             value_string +H >                                             termination_character + '= }'); >                  ENDCASE;  > # >                ["a"]: ! <ESC>&a#? - >                  CASE termination_character , >                     ["G","g"]: ! <ESC>&a#GE >                        COPY_TEXT ('{Duplex Page Side Selection: ' + B >                                             value_string + '}');, >                     ["P","p"]: ! <ESC>&a#PH >                        COPY_TEXT ('{Print Direction: ' +value_string = +  '}'); , >                     ["L","l"]: ! <ESC>&a#LH >                        COPY_TEXT ('{Left Margin: ' +value_string + '}= '); , >                     ["M","m"]: ! <ESC>&a#MH >                        COPY_TEXT ('{Right Margin: ' +value_string + '= }');, >                     ["C","c"]: ! <ESC>&a#CH >                        COPY_TEXT ('{Horizontal Cursor Positioning: ' = + H >                                             value_string + ' Columns}= '); , >                     ["H","h"]: ! <ESC>&a#HH >                        COPY_TEXT ('{Horizontal Cursor Positioning: ' = + > >                                             value_string + ' Decipoints}');, >                     ["R","r"]: ! <ESC>&a#RF >                        COPY_TEXT ('{Vertical Cursor Positioning: ' +H >                                             value_string + ' Rows}');=  , >                     ["V","v"]: ! <ESC>&a#VF >                        COPY_TEXT ('{Vertical Cursor Positioning: ' +> >                                             value_string + ' Decipoints}');" >                     [OTHERWISE]:F >                        COPY_TEXT ('{**Unknown: ' + group_character +< >                                             value_string +H >                                             termination_character + '= }'); >                  ENDCASE;  >  >        ["c"]: ! <ESC>&c#? & >           CASE termination_character& >               ["T","t"]: ! <ESC>&c#T; >                  COPY_TEXT ('{Character Text Direction: '  > +value_string + '}');  >               [OTHERWISE]:@ >                  COPY_TEXT ('{**Unknown: ' + group_character +< >                                             value_string +H >                                             termination_character + '= }'); >           ENDCASE; >  >        ["t"]: ! <ESC>&t#? & >           CASE termination_character& >               ["P","p"]: ! <ESC>&t#PF >                  COPY_TEXT ('{Text Parsing Method: ' +value_string + '}');  >               [OTHERWISE]:@ >                  COPY_TEXT ('{**Unknown: ' + group_character +< >                                             value_string +H >                                             termination_character + '= }'); >           ENDCASE; >  >        ["k"]: ! <ESC>&k#? & >           CASE termination_character& >               ["H","h"]: ! <ESC>&k#HH >                  COPY_TEXT ('{Horizontal Motion Index: ' +value_strin= g +  '}'); & >               ["G","g"]: ! <ESC>&k#HH >                  COPY_TEXT ('{Line Termination: ' +value_string + '}'= ); >               [OTHERWISE]:@ >                  COPY_TEXT ('{**Unknown: ' + group_character +< >                                             value_string +H >                                             termination_character + '= }'); >           ENDCASE; >  >        ["f"]: ! <ESC>&f#? & >           CASE termination_character& >               ["S","s"]: ! <ESC>&f#S; >                  COPY_TEXT ('{Push/Pop Cursor Position: '  > +value_string + '}');  >               [OTHERWISE]:@ >                  COPY_TEXT ('{**Unknown: ' + group_character +< >                                             value_string +H >                                             termination_character + '= }'); >           ENDCASE; >        ENDCASE;  >      ["*"]: ! <ESC>*?#? . >          get_parameterized_escape_sequences;% >          get_termination_character; ! >            CASE group_character " >               ["p"]: ! <ESC>*p#?- >                  CASE termination_character , >                     ["X","x"]: ! <ESC>*p#X: >                        COPY_TEXT ('{Units of measure ' +< >                                             value_string +E >                                             ' for Horizontal Motion 
 Index:}');, >                     ["Y","y"]: ! <ESC>*p#Y: >                        COPY_TEXT ('{Units of measure ' +< >                                             value_string +? >                                         ' for Vertical Cursor  Positioning:}');" >                     [OTHERWISE]:F >                        COPY_TEXT ('{**Unknown: ' + group_character +< >                                             value_string +H >                                             termination_character + '= }'); >                  ENDCASE;  >            ENDCASE;  >  >      [OTHERWISE]: 0 >          COPY_TEXT ("{**Unknown Sequence**}");% >          done_this_sequence :=3D 1;  >          RETURN;
 >    ENDCASE;  >  >    SPLIT_LINE; >  >      RETURN; > ENDPROCEDURE;  > . > PROCEDURE get_parameterized_escape_sequences, >    group_character :=3D CURRENT_CHARACTER; >    ERASE_CHARACTER(1); >    get_value; 2 >    termination_character :=3D CURRENT_CHARACTER; >    ERASE_CHARACTER(1); > ENDPROCEDURE;  > % > PROCEDURE get_termination_character , >    IF (termination_character >=3D "@") and( >       (termination_character <=3D "^") >       THEN% >          done_this_sequence :=3D 1;  >       ELSE. >          COPY_TEXT(Parameterized_character);& >          COPY_TEXT(group_character);  >          MOVE_HORIZONTAL (-2);% >          done_this_sequence :=3D 0;  >       ENDIF; > ENDPROCEDURE;  >  > PROCEDURE get_value  >  >    value_string :=3D "";! >    IF CURRENT_CHARACTER =3D "-"  >       then! >          value_string :=3D "-";  >          erase_character (1);  >       else$ >       IF CURRENT_CHARACTER =3D "+" >          then $ >             value_string :=3D "+";" >             erase_character (1); >          ENDIF;  >    ENDIF;  > 	 >    LOOP H >    IF ((CURRENT_CHARACTER <=3D "9") and (CURRENT_CHARACTER >=3D "0"))=  or # >       (CURRENT_CHARACTER =3D ".")  >       THEN> >          value_string :=3D value_string + current_character; >          erase_character (1);  >       ELSE >          EXITIF 1 
 >       ENDIF 
 >    ENDLOOP;  > > >    IF value_string =3D "" THEN value_string :=3D "0" ENDIF ; > 
 >    RETURN ;  >  > ENDPROCEDURE;  >  > ! H > !  This  procedure  controls  the  outer  loop  search  for  the  spe= cial3 > !  control  characters  that  we  want  to  view.  > !  > PROCEDURE  translate_pcl >      CONSTANT  > ! = > !   PCL commands start with ESC, PJL commands start with @.  > ! 6 >          Special_Chars  :=3D ASCII   (27) !  +  "@"; >      LOCAL >          ctrl_char_pattern,  >          ctrl_char_range;  > ! ) >      source_buffer :=3D current_buffer;  > ! B > !  Create  the  translation  buffer  and  window,  if  necessary3 >      IF  translate_buffer  =3D  TPU$K_UNSPECIFIED C >      THEN translate_buffer  :=3D  CREATE_BUFFER  ("translation"); . >          SET  (NO_WRITE,  translate_buffer);
 >      ENDIF; 3 >      IF  translate_window  =3D  TPU$K_UNSPECIFIED @ >      THEN translate_window  :=3D  CREATE_WINDOW (1,  17,  ON);
 >      ENDIF;  > ! 9 > !  Make  a  copy  of  the  buffer  we  are  translating ! >      ERASE  (translate_buffer); $ >      POSITION  (translate_buffer);" >      COPY_TEXT  (source_buffer); > @ >      SET (EOB_TEXT, translate_buffer, "[END OF TRANSLATION]"); > ! A > !  Search  for  any  control  characters  and  translate  them. > > !  If  a  control  character is  not  found,  SEARCH_QUIETLY > !  will  return  a  0.4 >      ctrl_char_pattern  :=3D  ANY (Special_Chars);4 >      POSITION  (BEGINNING_OF  (translate_buffer));F >      LOOP ctrl_char_range  :=3D  SEARCH_QUIETLY  (ctrl_char_pattern, > FORWARD); + >          EXITIF  ctrl_char_range  =3D  0; ' >          POSITION  (ctrl_char_range);  >          !H >          !  If  we  did  not  translate  the  character,  move  past =  it  >          !9 >          IF  NOT  translate_controls  (ctrl_char_range) % >          THEN MOVE_HORIZONTAL  (1);  >          ENDIF;  >      ENDLOOP;  > ! ' > !  Now  display  what  we  have  done 4 >      POSITION  (BEGINNING_OF  (translate_buffer));2 >      MAP  (translate_window,  translate_buffer); > ENDPROCEDURE;  >  > 9 > DEFINE_KEY ("translate_pcl;", CTRL_D_KEY, "CTRLD_KEY");  >  >=   ------------------------------    Date: 15 Mar 2006 11:58:29 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) . Subject: Re: FIPS 200 has now been promulgated3 Message-ID: <OYea1khgfgtN@eisner.encompasserve.org>   f In article <1142443913.173183.130160@u72g2000cwu.googlegroups.com>, "Ian Miller" <ijm@uk2.net> writes:   > when did this happen?   L The announcement went out March 14, but the FIPS document itself says it wasI approved by the Secretary of Commerce on March 9.  Those who are affected B had an opportunity to comment on the public draft last July or so,B meaning they probably have not been taken by surprised that it did finally get approved.   E FIPS 200 itself is actually a short overview which makes it mandatory G for the affected folk to follow the more detailed NIST 800-53, released  February 28, 2005.   ------------------------------  % Date: Wed, 15 Mar 2006 17:52:40 +0100 ' From: "Klaus-D. Bohn" <info@it-bcsb.de> # Subject: GLIB and GTK for OpenVMS ? 6 Message-ID: <44184663$0$8735$9b622d9e@news.freenet.de>   Hello together,   I does everybody tried to move these libraries (www.gtk.org) to the OpenVMS 	 systems ? * I mean the new version (2.x), not the old.   Experience will be welcome.   	     Klaus    ------------------------------  % Date: Wed, 15 Mar 2006 05:23:57 -0800 ( From: Jeff Cameron <roktsci@comcast.net>: Subject: Re: Image Backup and Restore of Bound Volume sets0 Message-ID: <C03D556D.1D440%roktsci@comcast.net>  J On 3/14/06 7:07 PM, in article dv80ct$pmc$2@newslocal.mitre.org, "Keith A.& Lewis" <klewis@OMEGA.MITRE.ORG> wrote:  6 > Jeff Cameron <roktsci@comcast.net> writes in articleM > <C03CC0FF.1D414%roktsci@comcast.net> dated Tue, 14 Mar 2006 18:50:39 -0800: M >> I have a customer who is having troubles performing image backups of bound E >> volume sets then restoring. I do not have sufficient free disks to K >> experiment on my system, and the VMS documentation only describes how to J >> mount bound volume sets. We cannot seem to locate information on how to+ >> restore bound sets from an image backup.  >>  K >> When we do the image backup of a bound volume set it seems to work fine, I >> however when we attempt to do an image restore it gives us "Device not  >> mounted" error messages.  >>  M >> Do we have to do image backups of each constituent volume and restore them  >> individually? >>  0 >> Can someone briefly outline the proper steps. > 0 > No, you don't have to back them up separately. > N > I never figured out how to do an image restore on a bound set.  Luckily, youK > can do a non-image restore.  First, re-do your INIT and MOUNT/BIND.  Then N > use the BACKUP command to restore the files.  The files will not necessarilyJ > go to the same volume where they originally resided; hopefully that's OK > with you.  > 2 > --Keith Lewis              klewis {at} mitre.org@ > The above may not (yet) represent the opinions of my employer.  J Unfortunately this bound volume set has Shelved files, and the only way to> maintain it's shelved status is to do an image backup/restore.   ------------------------------  # Date: Wed, 15 Mar 2006 19:26:26 GMT 1 From: Keith Parris <keithparris_NOSPAM@yahoo.com> . Subject: Re: Itanium still not on alpha level!2 Message-ID: <CTZRf.4739$d46.4008@news.cpqcorp.net>   bob@instantwhip.com wrote:  > what about a single cpu box?    H You can buy single-CPU Itanium boxes today: the rx16x0 and rx26x0. Just H because the rx16x0 allows for 2-CPU expansion at the same low price and 7 the DS15 didn't shouldn't make the rx16x0 unattractive.   H Go to an HP/Intel porting seminar for $2K and get an rx2620. Can't beat F that price (and get help with porting your applications as well)! See b http://h21007.www2.hp.com/dspp/bus/bus_BusDetailPage_IDX/1,1252,6045,00.html?jumpid=reg_R1002_USEN   ------------------------------  # Date: Wed, 15 Mar 2006 17:16:26 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com> Subject: Re: Mtools for VMS (?) 2 Message-ID: <KZXRf.4731$FX5.2941@news.cpqcorp.net>   Steven M. Schweda wrote:5   Does anyone know if the IO$_DIAGNOSE stuff works on : > an IDE/ATAPI drive through the DQ driver?  I sure don't.  E   The IO$_DIAGNOSE interface works for the current DQDRIVER (ATAPI),  G DKDRIVER (SCSI), DGDRIVER (FC), and DNDRIVER (USB) drivers, and for at  I least with V7.3-2 and later.  (I use the IO$_DIAGNOSE API heavily within  B the CD and DVD recording code, but I haven't been pounding on any F drivers prior to V7.3-2 in quite a while.  Do ensure you have current I drivers, as I did encounter a couple of driver bugs, and these have been   fixed via ECO.)   H   There will be discussions of FAT tools and the EFI partition (and the C DVD recording code) at the boot camp, if you are interested.  (The  E OpenVMS I64 bootstrap partition is a FAT volume, and there are tools   around to maintain it.)   F   There's also an older MTOOLS port around, and there are a couple of > discussions of reading Windows FAT volumes in the OpenVMS FAQ.  I   If you have a FREEWARE_README.TXT file for it, I can queue this MTOOLS  ! port for the next Freewaree, too.    ------------------------------    Date: 15 Mar 2006 17:34:07 +0100C From: vaxinf@chclu.chemie.uni-konstanz.de (Eberhard Heuser-Hofmann)  Subject: Re: Mtools for VMS (?) 2 Message-ID: <441841ff$1@merkur.rz.uni-konstanz.de>  ? In article <KZXRf.4731$FX5.2941@news.cpqcorp.net>, Hoff Hoffman ! <hoff-remove-this@hp.com> writes:  >Steven M. Schweda wrote: 6 >  Does anyone know if the IO$_DIAGNOSE stuff works on; >> an IDE/ATAPI drive through the DQ driver?  I sure don't.  > F >  The IO$_DIAGNOSE interface works for the current DQDRIVER (ATAPI), H >DKDRIVER (SCSI), DGDRIVER (FC), and DNDRIVER (USB) drivers, and for at J >least with V7.3-2 and later.  (I use the IO$_DIAGNOSE API heavily within C >the CD and DVD recording code, but I haven't been pounding on any  G >drivers prior to V7.3-2 in quite a while.  Do ensure you have current  J >drivers, as I did encounter a couple of driver bugs, and these have been  >fixed via ECO.) > I >  There will be discussions of FAT tools and the EFI partition (and the  D >DVD recording code) at the boot camp, if you are interested.  (The F >OpenVMS I64 bootstrap partition is a FAT volume, and there are tools  >around to maintain it.) > G >  There's also an older MTOOLS port around, and there are a couple of  ? >discussions of reading Windows FAT volumes in the OpenVMS FAQ.  > J >  If you have a FREEWARE_README.TXT file for it, I can queue this MTOOLS " >port for the next Freewaree, too. >   8 IO$_DIAGNOSE for DNDRIVER (USB) under V7.3-2? How to get this driver version?   Eberhard   ------------------------------  % Date: Wed, 15 Mar 2006 13:11:13 -0500 , From: Forrest Kenney <Forrest.Kenney@hp.com> Subject: Re: Mtools for VMS (?) & Message-ID: <441858C1.3E63E621@hp.com>  > 	I give Steve Hoffman drops of new DNDRIVER every now and thenD and when he gets a chance he puts them onthe freeware site.  Having G said that what is on the freeware site is generally a good ways behind  G the latest driver.  I am still trying hard to make sure that the driver G can be built and work on every version that supports USB.  But that is  E getting harder and harder to do all the time.  If you need something  F that is not in the driver on the freeware site contact me directly andG I will see about getting you an image.  No promises if I have code that $ will help I will try and release it.   Forrest Kenney
 OpenVMS group    Eberhard Heuser-Hofmann wrote: > A > In article <KZXRf.4731$FX5.2941@news.cpqcorp.net>, Hoff Hoffman # > <hoff-remove-this@hp.com> writes:  > >Steven M. Schweda wrote: 8 > >  Does anyone know if the IO$_DIAGNOSE stuff works on= > >> an IDE/ATAPI drive through the DQ driver?  I sure don't.  > > G > >  The IO$_DIAGNOSE interface works for the current DQDRIVER (ATAPI), I > >DKDRIVER (SCSI), DGDRIVER (FC), and DNDRIVER (USB) drivers, and for at K > >least with V7.3-2 and later.  (I use the IO$_DIAGNOSE API heavily within D > >the CD and DVD recording code, but I haven't been pounding on anyH > >drivers prior to V7.3-2 in quite a while.  Do ensure you have currentK > >drivers, as I did encounter a couple of driver bugs, and these have been  > >fixed via ECO.) > > J > >  There will be discussions of FAT tools and the EFI partition (and theE > >DVD recording code) at the boot camp, if you are interested.  (The G > >OpenVMS I64 bootstrap partition is a FAT volume, and there are tools  > >around to maintain it.) > > H > >  There's also an older MTOOLS port around, and there are a couple ofA > >discussions of reading Windows FAT volumes in the OpenVMS FAQ.  > > K > >  If you have a FREEWARE_README.TXT file for it, I can queue this MTOOLS $ > >port for the next Freewaree, too. > >  > : > IO$_DIAGNOSE for DNDRIVER (USB) under V7.3-2? How to get > this driver version? > 
 > Eberhard   ------------------------------  # Date: Wed, 15 Mar 2006 13:46:07 GMT  From: d_gillbilly@hotmail.com H Subject: Re: Mysterious revision date changes caused by Advanced Server?8 Message-ID: <uq4g12d58r2b7ncf6s51tebl109u5plckr@4ax.com>  F On Mon, 13 Mar 2006 22:01:33 GMT, hoff@hp.nospam (Hoff Hoffman) wrote:  Y >In article <blmb12d4cnpikniamu7nf97gksl1mj5umv@4ax.com>, d_gillbilly@hotmail.com writes:  > G >  I've done a little more digging.  Something on the client is opening G >  the files, and Advanced Server is updating the ACE -- it may well be F >  that the client is retrieving an icon, or other such bits, from the >  file(s) involved. > O > ---------------------------- #include <rtfaq.h> ----------------------------- L >    For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqO > --------------------------- pure personal opinion --------------------------- H >       Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[\0100]hp.com   Slaps fingers.  F As long as I keep VMS and Windows away from each other, I don't have a3 problem :-) But everyone here already knows that...   + It reminds me of a problem from long ago...   B Technical Writer: Duane, a lot of our word documents have a virus! Me: ??? We don't use word.C TW: Well, I just did a virus scan on the documentation directory!!! G I could only chuckle as I REMOVE SHARE and reached for the backup tape.   7 I think she still believes that Micro$ invented .DOC's.    Back to the present.  ? While the invasive read nature of Windoze is annoying, it's the D selective updates that bother me. For now, I will revert to an olderA (but still works) distribution model. This will limit my exposure  to this kind of problem.  G As long as something from the collective doesn't lay claim to .BCK's, I 
 should be ok.   0 Now to get my packet trace decoder ring working.3 Trace logs are not the easiest of things to read...   '    Thanks to those that have responded. 
      Duane   ------------------------------  # Date: Wed, 15 Mar 2006 17:27:56 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com> Subject: Re: rtvax300 revisions 2 Message-ID: <w8YRf.4733$f06.3513@news.cpqcorp.net>   Mehrdad Ardavan wrote:  E > I fased a problem with rtvax300 cpu spare , after I changed the old B > card with a new one , this message comes up: VAXELN-F-BOOT ERROR > module rev out of range , 2 > would you please let me know about this problem.  H    You'll probably end up likely rebuilding your VAXeln application, or L finding an rtVAX KAV30-series module with a revision closer to the original.   ------------------------------    Date: 15 Mar 2006 08:24:02 -0800 From: schortingh_j@mercer.edu / Subject: SCT Banner software running on OpenVMS C Message-ID: <1142439842.719283.166840@i40g2000cwc.googlegroups.com>   A We are currently running SCT Plus suite on OpenVMS Alpha and I am C interested in hearing from anyone running the SCT Banner product on G OpenVMS.   Area's of interest would be migration,  possile list serv of 9 universities running Banner on OpenVMS, how well it runs.    Thanks.    Jim Schortinghouse VMS Systems Manager  Mercer University  schortingh_j@Mercer.edu    ------------------------------  # Date: Wed, 15 Mar 2006 15:07:56 GMT  From: Jim Duff <jim@127.0.0.1> Subject: Re: VMS UpdatesD Message-ID: <g5WRf.4458$tW2.1699@bgtnsc04-news.ops.worldnet.att.net>   dan.ryan@cgha.com wrote:I > I apologize if this is posted somewhere already, but I am fairly new at I > VMS administrator.   I know there are updates to VMS, but is there some G > notification of updates that are sent out when there are new releases H > I know Microsoft had it where if there was an update, especially if itI > was critical or serious, they would send out an email.  However, I have F > not heard if there is one from HP, that one can sign up for.  I knowI > the updates are out on HP's ftp site, but I though I would ask if there  > was an easier way. >  > Appreciate any advice. >     ; My attempt at a syndicated versions of the ftp.itrc.hp.com:   0 http://www.eight-cubed.com/patches/patches.shtml  C Wouldn't it be nice if HP published an XML document with each patch F containing things such as version, reboot requirements, prerequisites,C install level, etc?  Then someone could make a stab at *automating* # patch retrieval and installation...    Jim.   ------------------------------    Date: 15 Mar 2006 07:19:31 -0800 From: dan.ryan@cgha.com  Subject: Re: VMS UpdatesC Message-ID: <1142435971.365229.226620@p10g2000cwp.googlegroups.com>   ' I appreciate your help.  This is great.   ; Jim, totally agree with you.  Thanks to all for the advice.    Dan    ------------------------------  % Date: Wed, 15 Mar 2006 12:27:22 -0500  From: norm.raphael@metso.com Subject: Re: VMS UpdatesQ Message-ID: <OF7D028187.045DDBD3-ON85257132.005F169F-85257132.005FE3F5@metso.com>   ? Graham Burley has constructed a DCL procedure to run on OpenVMS A that can be used to email about the HP OpenVMS ftp patch site(s).    The last version I have is:   J $! FTP_NEW.COM - check an ftp directory for new, changed, or removed files $!4 $!  Author: Graham Burley <burley@encompasserve.org> $! $!<snip>- $!      V0.15   10-Feb-2004     Graham Burley   = This and the notification list from OpenVMS.org do it for me. D One warns me of impending ECO's and the other notifies me of changes to the FTP site, with text.    -Norm   I David J Dachtera <djesys.nospam@comcast.net> wrote on 03/14/2006 10:18:03  PM:    > dan.ryan@cgha.com wrote: > > K > > I apologize if this is posted somewhere already, but I am fairly new at K > > VMS administrator.   I know there are updates to VMS, but is there some I > > notification of updates that are sent out when there are new releases J > > I know Microsoft had it where if there was an update, especially if itK > > was critical or serious, they would send out an email.  However, I have H > > not heard if there is one from HP, that one can sign up for.  I knowK > > the updates are out on HP's ftp site, but I though I would ask if there  > > was an easier way. > >  > > Appreciate any advice. > B > In addition to the other posters' advice, ITRC is accessible via > anonymous FTP: > ( > ftp://ftp.itrc.hp.com/openvms_patches/ > / > Check this periodically on your own for ECOs.  > G > The main OpenVMS website provides info about current releases (but no / > download links): http://www.hp.com/go/openvms  > D > As another poster mentioned, the support organization does provide  > notification of urgent issues. >  > -- > David J Dachtera > dba DJE Systems  > http://www.djesys.com/ > ( > Unofficial OpenVMS Marketing Home Page# > http://www.djesys.com/vms/market/  > * > Unofficial Affordable OpenVMS Home Page:! > http://www.djesys.com/vms/soho/  > $ > Unofficial OpenVMS-IA32 Home Page:! > http://www.djesys.com/vms/ia32/  > + > Unofficial OpenVMS Hobbyist Support Page: $ > http://www.djesys.com/vms/support/   ------------------------------  % Date: Wed, 15 Mar 2006 14:31:17 +0000 / From: "R.A.Omond" <Roy.Omond@BlueBubble.UK.Com> " Subject: VXT 2000+ monitor options4 Message-ID: <dv98fm$n36$1$8300dec7@news.demon.co.uk>   Gentle colleagues,  @ one of my clients has a number of VXT 2000 X-terminals for which> the monitors (PCXAV 20") are slowly but surely dying a natural; death (understandably).  They'd like to keep the VXT's, but < replace the old monitors with 19" (or greater) flat-screens.  ; Has anyone gone through this process ?  What was involved ?   < My initial thoughts would be to replace the entire equipment; with thin-clients (possibly with embedded Linux), since the < extra cost in the base unit compared to the price of a large9 flat-screen by itself is likely relatively insignificant.   # Any advice/recommendations welcome,    thanks in advance,  	 Roy Omond  Blue Bubble Ltd.   ------------------------------    Date: 15 Mar 2006 07:53:14 -0800( From: "Rich Jordan" <jordan@ccs4vms.com>& Subject: Re: VXT 2000+ monitor optionsB Message-ID: <1142437994.444248.69200@j52g2000cwj.googlegroups.com>   Roy,G      when I was looking for the same, I was told (and to a very limited > extent found in testing) that a monitor that would work with aG VAXstation 3100 SPX board would work with the VXT2000s.  That meant BNC * connectors, with sync-on-green capability.  D      I've tested an older NEC 18" on both in the past and it worked.F However finding BNC connectors on current panels is hard, and a lot ofG them have discontinued support for sync-on-green as well.  You can make A do with a VGA connector, but the adapters will cause some loss of G quality in the signal (and I don't know where to get those adapters any  more).   ------------------------------   End of INFO-VAX 2006.148 ************************                                                                                                                                                                                        