1 INFO-VAX	Sat, 17 Aug 2002	Volume 2002 : Issue 452       Contents:< Re: Charon-VAX (was: [VAX] VMS to [Alpha] OpenVMS conversion Re: DCL question' Re: Fortune Magazine and a post-VMS rap  Re: Fortune Magazine wrapper Re: Fortune Magazine wrapper Free 19" New Monitor Re: Going 7.2-1 -> 7.3-1. Re: How can I format a SCSI RZ28M on VAX 4000?3 Re: JetDirect Printing through Pathworks from Win95 3 Re: JetDirect Printing through Pathworks from Win95 $ Re: keypad emulation in xterm window? RE: Oracle 9i rel 2 restricted to EV56 or later chips - why ??? . Re: Procedure to enlarge system name required.. Re: Procedure to enlarge system name required.B Re: Recompile applications when migrating from OpenVMS 7.1 to 7.3?  F ----------------------------------------------------------------------    Date: 17 Aug 2002 04:54:08 -0700) From: P.Young@unsw.EDU.AU (Patrick Young) E Subject: Re: Charon-VAX (was: [VAX] VMS to [Alpha] OpenVMS conversion = Message-ID: <55f85d77.0208170354.7504578b@posting.google.com>   \ David Froble <davef@tsoft-inc.com> wrote in message news:<3D5D2D52.4020103@tsoft-inc.com>... > Patrick Young wrote: > > G > > How about killing the Window(tm) version? It would be for the best.  > >   	 self snip   J > > I can't help thinking you are taking sales away from current Alpha and > > Future Itanic products.  >  > That's one perspective.  > L > But how about the original subject of this thread?  The move to Alpha VMS    Oh, I'm on topic.   B Charon VAX is a good thing - I'm really not trying to be weird, be? insulting to anyone, or otherwise producing a SPAM COV posting.   G I'm simply thinking "A Window(tm) version of the product might not be a D good thing". Sure it is a great thing for those "in the know" or forE someone in the know who needs "vax-on-a-laptop". It does however have I a dark side for OpenVMS when placed in the hands of commercial customers.   ? Dumping conversion to a Window(tm) based VAX is, well basically = dumping it. It still works maybe (is constrained to less than ? Window(tm) reliability - ie: stripped naked and made to perform B like some sort of stage act), then gets forgotten about. Until the> Borgbots(tm) break their borgbox(tm) and it becomes an issue -- then it becomes a Window(tm) broken(tm) mess.   > The OpenVMS Alpha version has no such evil overtones, and is aF righteous and valid choice for those  making the "[VAX] VMS to [Alpha] OpenVMS conversion".  @ On a PC, I would like to see it running in a stripped down LINUXB environment. IE: to the user it *is the OS* and installs as such -D there is no user level OS between Charon-VAX and the hardware. Would; need a nifty tool to install "off the shelf" LINUX drivers.    > R > If someone is determined to run windoz, then believe me (because I've seen it), S > they will find some way to reach their goal.  I've seen very good apps shut down  R > because they run on VMS, and the users on their third or fourth replacement for O > the app, and not very happy.  But the windoz/Unix bigots are very happy with  Q > their move, and if a user causes too much fuss, I've seen them also shut down,   > as in fired. >   K Too true. I've found the trick is to study that "solution", find the holes, H then make (it) look like a fool. You know when you are getting somewhere5 near where you want to be when you get a result like:   G "Following a discussion with my "Students record owner", We will change H the program to improve the way the program selecting the student. I will% send you the Test file in a few day."   H (result of a query into 1996 records - I had the 1996 download from "theG old system"- 25% were missing from a similar query to the "new" system, F which would be why I asked the question). The old system was a FujitsuF IBM look-alike, the new system is a Slowaris (and I mean **slow**) box/ with Peoplesoft/Citrix (window(tm)) everything.    ------------------------------  , Date: Sat, 17 Aug 2002 15:05:10 +0200 (CEST): From: "Gotfryd Smolik, VMS lists" <gotfryd@stanpol.com.pl> Subject: Re: DCL question J Message-ID: <Pine.LNX.4.21.0208171452230.28054-100000@irys.stanpol.com.pl>  * On Wed, 14 Aug 2002, Didier Morandi wrote: [...] M >+So, $ TELNET create_session and $ TELNET /create_session do the same thing?     You know the answe...  C >+This does not comply with DEC Human Engineering practices, to me.   :  May comply: know you the INSTALL two command modes, means? the "INSTALL command" (new [ermhm...] in VMS) where has defined A LIST, ADD, REPLACE etc. *commands* vs. "MCR INSTALL" (or foreign  = symbol $install:=$install "command") where uses LIST, REPLACE . etc. (AFAIR ADD is the default) *qualifiers* ?   "Nothing new under the sun" -:)    Regards - Gotfryd   --  E ===================================================================== F $ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") - 		THEN EXCUSE/OBJECT=ME . $!                        GS@stanpol.zabrze.plE =====================================================================    ------------------------------  # Date: Sat, 17 Aug 2002 12:07:55 GMT 1 From: "Terry C. Shannon" <terryshannon@attbi.com> 0 Subject: Re: Fortune Magazine and a post-VMS rap? Message-ID: <v0r79.150399$sA3.229763@rwcrnsc52.ops.asp.att.net>   < "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message! news:3D5DA8F7.94025A0D@fsi.net...  > "Terry C. Shannon" wrote:  > > ( > > [Delusional hallucinations snipped.]  2 (I assume the lucid hallucinations were retained?) > > E > > If these assumptions come to pass, does it really matter what the 
 underlying
 > > OS is? > > * > > Not a troll, just an idea to consider, > D > Hey, Terry? Where can I get a dime bag of whatever you're smokin'?  + I don't smoke. I do chew Nicorette, though.    > G > When ODS, RMS, DCL, VMScluster (including the DLM) and the entire VMS E > runtime library are ported to another non-VMS descendent o.s., I'll J > dance naked on stage at the (then current successor to) DECUS symposium. >  > There. You have it on record.  > , > ...and remember: you heard it here, first! >   : Indeed I did, but it isn't something I expect to see soon!   ------------------------------    Date: 17 Aug 2002 12:23:07 -00004 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>% Subject: Re: Fortune Magazine wrapper 6 Message-ID: <20020817122307.13236.qmail@nym.alias.net>  G On Fri, 16 Aug 2002, "Terry C. Shannon" <terryshannon@attbi.com> wrote:      >--  >Terry C. Shannon   >Consultant and Publisher, SKHPC   <snip>  K Terry, can you fix your M$ software to put the signature at the bottom, and D put in the separator properly as "-- "? It's bad enough that OutlookK Express tries to get people to top-post, but if it can't handle signatures,  I'd ask for a refund.      Doc. --  6 The bigger the humbug, the better people will like it.K ~ Phineas Taylor Barnum.                             https://vmsbox.cjb.net    ------------------------------    Date: 17 Aug 2002 12:39:01 -00004 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>% Subject: Re: Fortune Magazine wrapper 6 Message-ID: <20020817123901.32147.qmail@nym.alias.net>  K On Fri, 16 Aug 2002, "Sue Skonetski" <susan.skonetski@hp.nospam.com> wrote:  >Dear News Group,  > L >I just want to say something.  Maybe I just love VMS to much and I am happyD >when ever I see it in print (with the exception of large consultingG >companies who disregard any facts given them and use untruths to force K >trends that they predict).  I put things I find about VMS in print here so E >we can all share it.  I sure do not do it to make people upset and I  >apologize if that is the case.   F Don't take the criticism personally, I'm sure it isn't meant that way.  B Marketing *is* wanted by most people in the newsgroup, but what isH questioned is the target audience HP have selected. This target audienceE reflects the goals HP have for the product we're interested in - VMS.   E The reason some people seem to be critical, is there appears to be no K effort by HP to get new customers running VMS. From comments made, it would H appear that this Fortune wrapper campaign has been targetted at existing+ customers who have the systems it mentions.   F Now, had the "target audience" been selected from Fortune's subscriberI mailing list, instead of from HP's customer list, you could've expected a  much more positive response.     Doc. --  6 The bigger the humbug, the better people will like it.K ~ Phineas Taylor Barnum.                             https://vmsbox.cjb.net    ------------------------------  % Date: Sat, 17 Aug 2002 09:42:56 -0400 1 From: "Island (hpaq.net)" <dbturner@islandco.com>  Subject: Free 19" New Monitor / Message-ID: <ulskjpgir8b2b6@news.supernews.com>   H Get a free 19" Samsung Alpha Compatible .25 DP Monitor when you purchaseD an XP1000 667 Mhz special for $2995 from our website this month only   A $400 value free !!!      Limit 1 Monitor per customer   -- Island Computers US Corp.  2700 Gregory Street  Savannah GA 31404  Toll Free: 1-877 636 4332  International: 001 912 447 6622   Facsimile:      001 912 201 0096 dbturner@hpaq.net  www.hpaq.net   ------------------------------  % Date: Sat, 17 Aug 2002 01:49:15 -0400   From: John Santos <JOHN@egh.com>! Subject: Re: Going 7.2-1 -> 7.3-1 4 Message-ID: <1020817013251.415A-100000@Ives.egh.com>  G On Fri, 16 Aug 2002, Jan-Erik =3D?iso-8859-1?Q?S=3DF6derholm?=3D wrote:   5 > OK, now just so I'v understod everything correctly. 9 > This file ("VMS$REMEDIAL_OLD_FILES.TXT") is a file that 8 > exsists on the system *before* the upgrade !? Or is it. > some file that is inlcluded in the new kit ? >=20 > Jan-Erik S=F6derholm.  >=20 > "Mark D. Jilson" wrote:  > >=20I > > No reinstalling the RENAME kit will not fix this.  I do not know of a I > > new RENAME kit either.  Please log this to your local CSC.  I suspect > > > the workaround will be to edit VMS$REMEDIAL_OLD_FILES.TXT.  B I don't know if you start with an empty one or not.  PCSI ECO kitsB append text to it.  Apparently, it is a list of files each ECO has2 renamed and replaced, and the name of the ECO kit.  # All the legitimate lines look like: 4 [SYSEXE]MIME.EXE_OLD               VMS721_MIME-V0100  ) I think this file is used for two things:   E 1) To back out an ECO, all the files tagged with that ECO are renamed C with the _OLD removed from the file type.  (Usually also requires a H reboot.)  I don't know if a "PRODUCT REMOVE" will do this automatically,5 or if it just a guide to manually backing out an ECO.   = 2) All the files in the list are deleted during a VMS version ? upgrade, as they are detritus left around by no longer relevant  ECOs.   = Messing up the file names can break upgrades, e.g. by causing = your brand-new V7.3-1 APB.EXE to get deleted right before you ? try to boot your spiffy new V7.3-1 system disk, because it says @ [SYSEXE]APB.EXE                                 VMS721_SYS-V1200
 instead of@ [SYSEXE]APB.EXE_OLD                             VMS721_SYS-V1200   --=20  John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Sat, 17 Aug 2002 02:08:55 -0500 + From: "Charter" <ssj152 AT charter DOT net> 7 Subject: Re: How can I format a SCSI RZ28M on VAX 4000? / Message-ID: <ulrtk8p7aj2m53@corp.supernews.com>   I Nelson, if this is a workstation, like a 4000-60, connect the disk to the J system (using an unused SCSI ID), boot OpenVMS on another disk, and simply use the INIT command like:   $INIT DKA100: LABEL J --where you would use the actual device name where I placed dka100. DKA100K would be used if the new disk were set to a SCSI id of 1.  Note: you cannot  INIT a mounted disk.  K If this is not a workstation, some of the procedures will vary, but not the I VMS commands. You should be a little more explicit about the hardware for # best results in getting assistance.    Relevant commmands:   A at the console prompt (>>>), use SHOW CONFIG and / or SHOW DEVICE 1 -- to see memory, disks, etc installed in machine   # at a VMS prompt use $SHOW DEVICE DK K -- to see all SCSI disks seen by VMS, should match info from console prompt   J to mount a disk where the label is unknown use $MOUNT/OVER=ID DKA100: (use actual device name) 0 -- if it will not mount, needs to be initialized  G with disk mounted, at a VMS prompt use $SHOW DEVICE DKA100: / FULL (use ! actual device where I put DKA100) I -- to see detailed information about the disk, including the device type, 	 like RZ28   K OpenVMS disks do not use partitions or need low-level formatting unless the J disk is somehow damaged. I have moved disks back and forth between WindowsL 2000 and OpenVMS like this MANY times. As best I recall the RZ28M is OK with
 VMS 5.5H4.  7 Be careful as there is NOT a command to un-init a disk.    Regards, Stuart Johnson ssj152 AT charter DOT net   8 "Nelson" <nelson.deabreu@comsat.com.ve> wrote in message7 news:a6c2a2f4.0208162134.7eb8528b@posting.google.com... J > I need to format a SCSI HD RZ28M, but I dont khow what is the procedure. >  > I have the 5.5 H4 Version  >  > Thanks   ------------------------------  # Date: Sat, 17 Aug 2002 08:02:41 GMT . From: peter@langstoeger.at (Peter LANGSTOEGER)< Subject: Re: JetDirect Printing through Pathworks from Win955 Message-ID: <Bqn79.193565$cU1.6055579@news.chello.at>   [ In article <3D5DA51E.E4D3F6FE@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes:   E >Apologies up front for the tone of this. Guess I'm just "on the rag"  >this week.   G Sorry, David. I didn't want to upset you with hints given from the off. G I also didn't want to start a flame war and so I'd better kept my mouth C shut, but I try to explain my arguments one more time. I don't want K to continue this sensible discussion for any longer. Opinions are different : of course. And every opinion has it's arguments of course.  J >> >Problem occured in a *VERY* important production environment. DowntimeH >> >cannot be tolerated and version upgrades of core packages are not an( >> >option without a *VERY* good reason. >>  ' >> How about the coming IPF migration ? 2 >> You have to get as current as possible on Alpha0 >> before the next migration wave gets over you.. >> In my eyes, this *is* a *VERY* good reason. > G >....and that does exactly what to break down the barriers to upgrades?  > E >Does it magically move a VAX/VMS V5.3-1 application to OpenVMS-Alpha 9 >V7.3-1 with no source code and no problems with VESTing?   A Iff you have such an old application and you have no source code, A you already lost. But having no VEST problems bring hope back in.   B But unfortunately the time of VEST is officially over. It may workA of course, but you can't call HPQ for support. You are some years B too late for this. You may like it or not, but this is now a fact.  F >Does it magically make a recalcitrant vendor (of the app. or OpenVMS,* >your choice) co-operative and beneficent?  C Of course not. If you have problems like these, than you are forced G to do what you have done. But I know of people who like to 'never touch E a running system' until it's too late and their systems gets replaced 6 instead of upgraded and this means in 99% bye-bye-vms.  A >Does it magically make downtime an option to allow the upgrades?   L No. But if downtime is a problem (and this is exactly why VMS or VMSclustersJ were and still are the best solution) then such an upgrade takes very muchI time. With maybe two downtimes a year, you probably need some years to do ? your migration tests. So, I'd better start sooner than later...   I >> Folks are "stuck" at various versions of VMS and layered products for   >> a reason. > * >What part of that is in anyway ambiguous?  H It is not. And being "stuck" makes life much more complicated of course.G But to go on after the freeze time is over you have two options. Find a J replacement with VMS systems (how complicated this may be, you surely knowJ better than I do) or let someone do the replacement with something else...   >> Start ASAP.- >> Frozen systems are dead systems very soon.  > E >A couple of summers ago, I had to go to one of Mark's sites that was > >still using MicroVAX 2000s with touch screens in a productionH >environment. (notice: no clue as to identity, industry or anything elseD >that compromises their position, security or intellectual property!% >Didn't think I could do it, did ya?)t >AA >I don't see them moving to OpenVMS Alpha or IPF anytime soon. Ifd? >anything, they'd probably go Linux or *BSD (my guess - totallyi >unfounded).  
 Shit happens.r  ' >Things don't "die" until you let them.o  : You mean, you make your hardware spare parts on your own ?B What to do if HPQ does no longer offer maint for your old hardwareC and you tried to get spare parts on the used market and you've beeneH unsuccessful for over a year ? Then things are dead without your will...  D >Go ahead, guys - keep motivating me and others here to give up VMS,F >maybe even computing in general. It'd be the biggest favor you can do >for any of us.-  M Sorry, David, the opposite is true. I'd like to motivate everyone to use VMS. I It is the best operating system, it is a general purpose operating systemVL and it probably has all the features people need and like. The image and theI price of VMS (means, as you know, the treatment of it's owner) is not ok.s  I But, my experience has been, if you keep a system frozen for a long time, I it gets replaced and not upgraded. And this means, one VMS system less...    Good luck anyway   -- ' Peter "EPLAN" LANGSTOEGERi% Network and OpenVMS system specialist  E-mail  peter@langstoeger.atP A-1030 VIENNA  AUSTRIA              I'm looking for (a) Network _and_ VMS Job(s)   ------------------------------    Date: 17 Aug 2002 08:10:23 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) < Subject: Re: JetDirect Printing through Pathworks from Win953 Message-ID: <0e3hRc8VcUXq@eisner.encompasserve.org>f  f In article <Bqn79.193565$cU1.6055579@news.chello.at>, peter@langstoeger.at (Peter LANGSTOEGER) writes:  D > But unfortunately the time of VEST is officially over. It may workC > of course, but you can't call HPQ for support. You are some years D > too late for this. You may like it or not, but this is now a fact.  = I thought I read that a new version was shipping with V7.3-1.d   ------------------------------  + Date: Sat, 17 Aug 2002 08:18:55 +0000 (UTC)t% From: John Forkosh <john@invalid.com>t- Subject: Re: keypad emulation in xterm windowd+ Message-ID: <ajl0tf$vb$1@reader2.panix.com>d  1 Zane H. Healy <healyzh@shell1.aracnet.com> wrote: ( : John Forkosh <john@invalid.com> wrote:, : > I'm telnetting to a VS from a linux box., : > When I telnet directly from a shell, the- : > keypad emulation works real well -- I canr* : > edit using edt with very few problems./ : >      But if I startx, open an xterm window,s/ : > and telnet from there, the keypad emulationw* : > fails completely.  I guess I need some1 : > appropriate KP_xxx definitions in .Xdefaults, . : > but I don't know which ones.  Anybody have+ : > a list of them I can cut-and-paste into + : > my .Xdefaults?  (Or is there maybe somes : > other problem?)  Thanks.  8 : Try the following shell script to start up your xterm:* : ftp://zane.brouhaha.com/pub/vms/vt100.shG : Someone posted it here a few years ago, and it works like a charm for E : accessing OpenVMS, RT-11, RSTS/E, RSX-11M/M+, TOPS-10, and TOPS-20  K : systems!  The only downside is, you don't have all the function keys, butl6 : the important thing is the keybad works as expected!  C Thanks, Zane, works great.  Weirdly, the left- and right-arrow keys C on my pc keyboard perform the reverse functionality in edt (up- and F down-arrows work like you'd expect).  Of course, that shouldn't be tooF hard for me to flip.  Otherwise, seems perfect "right out of the box."
 Thanks again.r -- s> John Forkosh  ( mailto:  j@f.com  where j=john and f=forkosh )   ------------------------------  + Date: Sat, 17 Aug 2002 16:37:55 +0000 (UTC)e From: david20@alpha1.mdx.ac.ukH Subject: RE: Oracle 9i rel 2 restricted to EV56 or later chips - why ???+ Message-ID: <ajlu53$cke$1@aquila.mdx.ac.uk>t   In article <92EFB80E551BD511B39500D0B7B0CDCC0642C7A7@ohms.electric.ci.austin.tx.us>, "Stuart, Ed" <Ed.Stuart@austinenergy.com> writes:K >The restriction is Alpha based not VMS based.  This is cut and pasted from2 >an email I received.a >l? >	Oracle is de-committing support because of performance on the+J >pre-EV56 chips.  Pre-EV56 chips did not have byte or word instructions inL >hardware, they were emulated (by reading 32 bits and shifting or masking toJ >get 8 or 16 bits) in firmware.  EV56 was the first generation of Alpha to9 >put in hardware these needed byte and word instructions.  > F >	This restriction imposed by Oracle affects not only OpenVMS but alsoM >Tru64.  This is not an OpenVMS issue but an Alpha issue.  This affects AlphaI$ >chips that run slower than 400 MHz. >oB >	The new versions of Oracle will be optimized to run on the newerH >versions of the Alpha processor.  For additional information (including2 >support information) please see the following URL= >http://www.openvms.compaq.com/solutions/oracle/monthQs.html.S >a >EdzF >**Please apply a generous amount of all the usual disclaimers here.**    5 Yes I know it is an Alpha chip issue not a VMS issue. L Thats the point. There are lots of EV5 chip systems out there which with theL current uncertainty over VMS's future will not be upgraded to faster systemsK until probably sometime after VMS ships on Itanium. Any moves now by OraclenJ to restrict what Alphas Oracle runs on will result in movement off of VMS.L Given that TRU64 has even less of a future this would seem to be yet another< reason why people will be moving to non compaq/HP platforms.  O Also I would not think in general that CPU performance is the major performance K limiting factor on VMS systems - I'd think that would more likely be the IO  system.o  
 David Webb VMS and Unix team leader CCSS Middlesex University   ------------------------------  % Date: Sat, 17 Aug 2002 02:13:09 -0400e  From: John Santos <JOHN@egh.com>7 Subject: Re: Procedure to enlarge system name required. - Message-ID: <1020817020440.415B@Ives.egh.com>o  $ On Fri, 16 Aug 2002, JF Mezei wrote:   > Johno wrote: > >  > > Hi > > H > > Could someone show me how write a dcl routine that will read the vmsD > > system name and then output it to the screen enlarged, say 6 x 6H > > characters in size. What I would also like is if the system name is,E > > say, VMSSYS then the first enlarged letter is made up of V's, the3 > > second of M's and so on. >  > $myname = "VMSSYS" > $ESCAPE[0,8] = 27n& > $write sys$output escape,"#3",myname& > $write sys$output escape,"#4",myname > D > ESCAPE #3 writes the top half of a double width double height lineG > ESCAPE #4 writes the bottom half of double width, double height line.e > : > ESCAPE #5 will write a double width, single height line.  @ If someone wants to learn PERL, one of the c.o.v denizens posted< BANNER.PL which creates a vertical large-letter rendition of> its input text string, suitable for printing on a lineprinter, etc.  ; I'm sure it could easily be modified, or invoked from a DCL24 script, to print sys$node, or the IP host name, etc.  : However, it prints the wrong way, the letters are too big,: and it prints everything in Hash marks (#).  This is where. the small matter of Perl programming comes in.  6 I'm sure you can find the program in Google, but if it6 has vanished into the ozone, I'll post it here.  (It's a little big...)   -- i John Santosi Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  + Date: Sat, 17 Aug 2002 07:22:39 +0000 (UTC)d% From: John Forkosh <john@invalid.com> 7 Subject: Re: Procedure to enlarge system name required.t+ Message-ID: <ajktjv$e7$1@reader2.panix.com>h  ! John Santos <JOHN@egh.com> wrote:i& : On Fri, 16 Aug 2002, JF Mezei wrote: : > Johno wrote: : > >  : > > HiJ : > > Could someone show me how write a dcl routine that will read the vmsF : > > system name and then output it to the screen enlarged, say 6 x 6J : > > characters in size. What I would also like is if the system name is,G : > > say, VMSSYS then the first enlarged letter is made up of V's, them : > > second of M's and so on. : >  : > $myname = "VMSSYS" : > $ESCAPE[0,8] = 27a( : > $write sys$output escape,"#3",myname( : > $write sys$output escape,"#4",myname : > F : > ESCAPE #3 writes the top half of a double width double height lineI : > ESCAPE #4 writes the bottom half of double width, double height line.m : > < : > ESCAPE #5 will write a double width, single height line.  B : If someone wants to learn PERL, one of the c.o.v denizens posted> : BANNER.PL which creates a vertical large-letter rendition of@ : its input text string, suitable for printing on a lineprinter, : etc. :t= : I'm sure it could easily be modified, or invoked from a DCLD6 : script, to print sys$node, or the IP host name, etc. :m< : However, it prints the wrong way, the letters are too big,< : and it prints everything in Hash marks (#).  This is where0 : the small matter of Perl programming comes in. :u8 : I'm sure you can find the program in Google, but if it8 : has vanished into the ozone, I'll post it here.  (It's : a little big...)  ; There's also an extraordinarily comprehensive little system 6 called figlet, written in C, that can emit zillions of8 different sizes and fonts from input text, and which you< could run from within a dcl procedure to produce the desired: effect (if the double-width/double-height escape sequences don't do the trick).  SeeS           http://www.figlet.org  -- u> John Forkosh  ( mailto:  j@f.com  where j=john and f=forkosh )   ------------------------------  + Date: Sat, 17 Aug 2002 16:47:22 +0000 (UTC)a From: david20@alpha1.mdx.ac.ukK Subject: Re: Recompile applications when migrating from OpenVMS 7.1 to 7.3? + Message-ID: <ajlumq$d29$1@aquila.mdx.ac.uk>n  _ In article <3D5BDEE7.613E337A@Mvb.Saic.Com>, Mark Berryman <Mark.Berryman@Mvb.Saic.Com> writes:i+ >Alan Winston - SSRL Admin Cmptg Mgr wrote:k >> dG >> In article <KqL69.404$67l.181269504@news.telia.no>, "Steinar Botten"  >> <sbo@satcom.nera.no> writes:C >> s >> eN >> However, I believe you're going from EV5 to EV6 when you go from a 5/300 to@ >> a DS10.  If you wanted to recompile with /ARCHITECTURE=EV6 orN >> /ARCHITECTURE=HOST you might get more performance out of it, at the expenseE >> of having an image you couldn't count on taking back to your 4100.g >> i >[remainder deleted] > E >Why do people keep saying this?  An image built on any Alpha runningeG >OpenVMS will run on any other alpha running the same or higher versionrD >of OpenVMS, even if built with architecture-specific optimizations. >iB >OpenVMS emulates any instructions it uses on any of its supportedH >platforms that don't natively have that instruction.  So, while you mayF >impact performance, you will not build an image that you won't run on
 >some alphas.d >g  N Could someone tell Oracle this since as I mentioned in another thread they areL desupporting Oracle running on EV5 and earlier alphas precisely because they( have decided to use these optimisations.  
 David Webb VMS and Unix team leader CCSS Middlesex University             >Mark Berryman   ------------------------------   End of INFO-VAX 2002.452 ************************