1 INFO-VAX	Wed, 29 Oct 2003	Volume 2003 : Issue 599       Contents:. Re: backing up VMS files to PC based CD writer. Re: backing up VMS files to PC based CD writer. Re: Daylight to Standard Time Change via Batch. Re: Daylight to Standard Time Change via Batch Re: EV79 CANCELED !!!!!!!!! . forwarding routine in C - Alpha assembly help?$ Re: How are the sales of VMS going ?$ Re: How are the sales of VMS going ?0 ICONV, UTF-8, and language fun on OpenVMS - 0.624 Re: ICONV, UTF-8, and language fun on OpenVMS - 0.621 Re: LMF licence check has failed. Please help :-) 1 Re: LMF licence check has failed. Please help :-)  Mac OS X 10.3 & OpenVMS  Re: Mac OS X 10.3 & OpenVMS  Re: Mac OS X 10.3 & OpenVMS 2 Re: OpenVMS I64 ISV application count now over 5002 Re: OpenVMS I64 ISV application count now over 5002 Re: OpenVMS I64 ISV application count now over 5002 Re: OpenVMS I64 ISV application count now over 500 OpenVMS Pearl Computer Weekly ! Re: OpenVMS Pearl Computer Weekly ! Re: OpenVMS Pearl Computer Weekly P Reminder, NY Metro LUG meeting on Wed the 29th (some of my favorite people prese/ Re: Swan Song For The Alpha Processor - TechWeb < Re: Video "ringing" with PBXGA but not Mach64 or Elsa Gloria Re: VMS Text Files --> Unix . Re: [survey] why do you still use VAX systems?  F ----------------------------------------------------------------------   Date: 29 Oct 2003 00:50:29 GMT From: healyzh@aracnet.com 7 Subject: Re: backing up VMS files to PC based CD writer , Message-ID: <bnn2sl02euk@enews2.newsguy.com>  $ Hoff Hoffman <hoff@hp.nospam> wrote:S > In article <bnkfmm$6eb$1@inky.its.caltech.edu>, YYYlmhYYY@cco.caltech.edu writes:   M > :                                   I used a raw copy routine for the PC I  Q > :found on the web but got a file structure error when I tried to boot from the   > :subsequent disk file.]     B >   I'd not expect the disk to boot on OpenVMS unless the disk wasH >   configured for it -- a raw copy of a system disk typically won't be.  J I'm quite honestly not sure about the VAX version of SIMH, however, on theJ PDP-11 Version it is possible to take a SCSI disk from the PDP-11, hook itI up to a Linux box, use 'dd' to make a disk image of the SCSI HD, and then H boot the resulting image under SIMH.  The same image can be written to aG CD-R and booted on a the original PDP-11 if it is equiped with a CD-ROM  drive.  F >   I'd hope that one of the emulator websites has detailed directionsD >   on what is involved in building a bootable disk.  If not, you'llH >   have to see how OpenVMS VAX (in the case of SIMH) sets up the systemI >   disk based on the system management documentation, and replicate this F >   configuration into the LD partition and then perform the raw burn.  L I'm not sure if any of the emulator websites have instructions on building aI Bootable OpenVMS disk image.  I'm guessing that the only documentation is  whatever comes with SIMH.   K My website http://www.aracnet.com/~healyzh/decemu.html covers all emulation K of DEC systems that I'm aware of, and I'll be honest, while I've got a page H on VAX emulation, and it's got more info than some of the architectures,L it's still pretty limited (and I really need to update it).  The fact of theH matter is, I find VAX emulation rather boring, when as a Hobbyist I haveI about a dozen VAXen.  A nice VAXstation 4000 makes a lot more sense to me C than trying to emulate a VAX (actually I prefer a nice fast Alpha).    		Zane   ------------------------------  % Date: Wed, 29 Oct 2003 02:55:26 -0000 ! From: Z  <zarlenga@conan.ids.net> 7 Subject: Re: backing up VMS files to PC based CD writer / Message-ID: <vpub0ui9d4l7db@corp.supernews.com>     YYYlmhYYY@cco.caltech.edu wrote:@ : We have a couple of old VAXStations running VMS 5.5.  Our 8mm J : Exabyte doesn't work after being 'repaired'.  Is it possible to back up L : files by ftp'ing them (thru a Unix machine) to a PC and writing them on a  : CD ?   Yes.  = I usually ZIP my stuff up on the VMS box, FTP the ZIP file to > a PC (use binary or image mode) with a burner and burn the ZIP file(s) to CD(s).     P : by type).  However the .sav file would not work (either at default or minimum F : 2048 block size) and neither did the .obj file.  [Files transferred   > I have ALWAYS had trouble with VMS savesets ... something goes< wrong during the FTP and it become completely useless.  What= really stinks is that you won't find out until you try to use . BACKUP on the saveset to extract the contents.    = Since ZIP and UNZUP are available for VAX and ALPHA, and they  work fine, I use them instead.  = One word of caution: make sure you burn the CD as an ISO 9660 = CD and finalize the CD or you may not be able to read it on a  VMS machine.  1 PS: I use Nero Burning ROM for making my VMS CDs.    ------------------------------  % Date: Tue, 28 Oct 2003 15:07:30 -0500 & From: David M Smith <dsmit115@csc.com>7 Subject: Re: Daylight to Standard Time Change via Batch 8 Message-ID: <oiitpv826g2ot8j52diic3ucri02q81t0t@4ax.com>  K On Tue, 28 Oct 2003 12:50:46 -0500, David M Smith <dsmit115@csc.com> wrote:   L >On Tue, 28 Oct 2003 12:45:32 -0500, David M Smith <dsmit115@csc.com> wrote: > O >>I reviewed the code in UTC$TIME_SETUP.COM to try to answer this question, and # >>came up with something like this:  >>@ >>$ SUBMIT SYS$MANAGER:UTC$TIME_SETUP /AFTER=26-OCT-2003:02:00 -! >>	/PARAMETER=("","TDF","-300",0)  > Q >To be complete in my response, I will show you the entire set of code I ran from H >SYSMAN on the Alpha V7.3-1 system -- and which did not make any change: > . >$       say "Current TDF Information follows") >$       @sys$manager:utc$time_setup show ? >$       @sys$manager:utc$time_setup "" tdf 'new_tdf_minutes' 0 K >$       if f$trnlnm("SYS$TIMEZONE_RULE","LNM$SYSTEM_TABLE",,"executive") - C >            .nes. "" then $ deassign/system/exec sys$timezone_rule % >$       @sys$startup:tdf$utc_startup . >$       say "Updated TDF Information follows") >$       @sys$manager:utc$time_setup show  > F >I "deduced" this code from examination of UTC$TIME_SETUP.COM and alsoQ >DAYLIGHT_SAVINGS.COM. Here is the output I got when executed as a procedure from  >SYSMAN: > 3 >%SYSMAN-I-OUTPUT, command execution on node xxxxxx $ >TDF will be adjusted by -60 minutes  >Current TDF Information follows3 >    Configuring the Time Differential Factor (TDF)   >Updated TDF Information follows > I >Notice that the two messages I generated were output, and a message from Q >(apparently) the second call to UTC$TIME_SETUP. However, when I logged on Sunday M >morning the TDF was still -14400 (EDT). I executed (copy and paste) the same M >lines interactively and they worked as expected. Still looking to understand  >this...  K Experimentation and further examination of UTC$TIME_SETUP.COM has led me to N believe that I ran into two problems. First, UTC$TIME_SETUP.COM has two placesK in its execution where, to avoid possible DCL error or warning messages, it J "brackets" some code with DEFINE SYS$OUTPUT NLA0 / DEASSIGN SYS$OUTPUT andN similar for SYS$ERROR. I have discovered that, when run from SYSMAN, after theK DEASSIGN SYS$OUTPUT still refers to the null device -- this is apparently a P known issue in SYSMAN. Since it still exists in V7.3-1 it seems unlikely that itL will be fixed. I have submitted a problem report requesting that the code inE UTC$TIME_SETUP be revised (in the future) to eliminate this sequence.   < It turns out that the change to the TDF did take place, i.e.B SYS$TIMEZONE_DIFFERENTIAL does get modified when the "TDF" call toL UTC$TIME_SETUP was made. However, I then (using code modeled on the do_zone:M code in UTC$TIME_SETUP) deassigned the SYS$TIMEZONE_RULE logical and executed K the startup procedure TDF$UTC_STARTUP.COM -- the purpose of this code is to K force VMS to reset the other V7.3* specific SYS$TIME* logicals, which on my  system now look like this:  &   "SYS$TIMEZONE_DAYLIGHT_SAVING" = "0"(   "SYS$TIMEZONE_DIFFERENTIAL" = "-18000"   "SYS$TIMEZONE_NAME" = "EST" 7   "SYS$TIMEZONE_RULE" = "EST5EDT4,M4.1.0/02,M10.4.0/02"   M What I think happened is that, since all this ran at 2:00 EDT, once the clock L was set back to 1:00 the TDF$UTC_STARTUP.COM procedure (which runs a "magic"O image SYS$SYSTEM:TDF$SET_TIMEZONE.EXE) must have put things back to EDT because P it "appeared" to be an hour before the change (M10.4.0/02) -- this is conjectureM on my part, and I can't think of an easy way to test it (without a V7.3x test O system where I can "fiddle" with the time) until a year from now. if I'm right, P my code (which I wrote to handle a +1 hour change in the spring, and a -1 change. in the fall) should work correctly next April.I ------------------------------------------------------------------------- I David M. Smith 302.391.8533                       dsmit115 at csc dot com I Computer Sciences Corporation     (Opinions are those of the writer only) I -------------------------------------------------------------------------    ------------------------------  # Date: Tue, 28 Oct 2003 23:30:21 GMT # From: hoff@hp.nospam (Hoff Hoffman) 7 Subject: Re: Daylight to Standard Time Change via Batch 2 Message-ID: <h_Cnb.7947$ky4.7792@news.cpqcorp.net>  a In article <saatpvsncifud61vm3ij3l968ffv2aejbe@4ax.com>, David M Smith <dsmit115@csc.com> writes: 4 :On Mon, 27 Oct 2003 10:55:42 -0800, Rick Millhollin. :<rickm.REMOVE-THIS-NOSPAM@uoregon.edu> wrote: : A :>I'm running VMS 7.3-1 and MultiNet 4.4 on several clustered and D :>stand-alone systems.  In the past with 7.3 I've been able to run aG :>batch job that adjusts the time via a combination of MultiNet actions B :>and executing UTC$CONFIGURE_TDF.COM with no interactive input.      J   In concert with the OpenVMS Engineer that is maintaining the TDF commandI   procedures, I've tried to document how to do this stuff in the FAQ, and I   one of the key  pieces listed in the FAQ is a request to not (directly) .   invoke the UTC$CONFIGURE_TDF.COM procedure.      :> NowC :>with 7.3-1 that tells me to run UTC$TIME_SETUP.COM which has been E :>discussed here.  But it appears to require interaction.  Any way to ) :>change from a batch job now?  Thanks...  : N :I reviewed the code in UTC$TIME_SETUP.COM to try to answer this question, and" :came up with something like this: : ? :$ SUBMIT SYS$MANAGER:UTC$TIME_SETUP /AFTER=26-OCT-2003:02:00 -   :	/PARAMETER=("","TDF","-300",0) : P :This does seem to work, and resets (only) the SYS$TIMEZONE_DIFFERENTIAL logicalP :name to (in this example) -300 minutes or -18000 (for EST). The P4 = 0 disables :changing of the system clock. : K :Unfortunately, I tried to make the equivalent call executing from "within" Q :SYSMAN, via SYSMAN DO @SYS$MANAGER:UTC$TIME_SETUP ... and this did not work -- I N :have not yet figured out why. I assume that something is done inside the .COMO :file which (for some reason) does not work within SYSMAN DO context. I have to & :figure it out in the next 6 months...    G   Have you considered using the example DAYLIGHT_SAVINGS.COM procedure?     G   With V7.3 (get the TDF ECO for that release, too) and later releases, I   you can also choose to enable and use the automatic mechanism to change J   the DST setting, as all layered applications should defer to the OpenVMS4   DST and TDF mechanisms in V7.3 and later releases.  F   There's a substantial section on this and related topics in the FAQ.    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  % Date: Tue, 28 Oct 2003 23:49:12 -0500 * From: JF Mezei <jfmezei.spamnot@istop.com>$ Subject: Re: EV79 CANCELED !!!!!!!!!) Message-ID: <3F9F46BB.319A705A@istop.com>    jlsue wrote:K > Or, alternatively, unless of course the delay factor would put it out far J > enough that the current plans for IA64 migration overshadow the need for > it.   K Sorry, that isn't the point. Customers were told on June 25 2001 that Alpha N would continue to be developped with another 2 releases that would still raiseJ Alpha to impressive new heights. At that time, it was already planned that+ IA64 would be palatable during this period.   H As it turns out, we are still being told to wait for the next IA64 to beI impressive. So a delay in EV79 woudln't have changed the initial promise. N Remember that many customers will want to stay on Alpha for a long time before being forced to a new platform.   L When Alpha surpassed VAX performance, lots of customers continued to buy newK Vaxes. When/if IA64 surpasses Alpha, lots of customers will continue to buy J Alpha, especially if IA64 isn't seen as a viable platform in the long term+ since it may be replaced by a 64 bit 8086.    M I'd much rather HP fulfil its promises and deliver EV79 with maximum possible K speed. If IA64 is able to outspeed Alpha, then so be it. If not, then so be N it. The decision to kill Alpha is done, even if it was done on wrong premises.L To purposefully slow down Alpha because they lied to us 2 years ago is lame, and very bad business.  N The HP apologists are so quick to pounce on SPARC. I find it ironic. Their ownJ chip is purposefully being restrained from achieving full performance. AndN their new chip isn't quire ready for prime time yet. They aren't in a position to blast Sun.     I At least, if they had done EV7 and EV79 right, it would have helped build M badly needed trust between HP and its newsly acquired customers. Purposefully ? limiting Alpha to save Carly's butt is very bad for HP's image.    ------------------------------    Date: 28 Oct 2003 22:36:58 -08001 From: usenet_vms@lehrerfamily.com (Joshua Lehrer) 7 Subject: forwarding routine in C - Alpha assembly help? = Message-ID: <477e0934.0310282236.64277434@posting.google.com>   A VMS's Alpha version of fopen (from C) takes 2 or more parameters.   A I want to hook into all calls to fopen (which are really calls to B DECC$FOPEN) and instrument some logging, then call the real fopen.  E I was able to get my hook in, log, then call the real function, given B that I was called with two parameters.  However, as I said, on the@ Alpha, you can supply any additional parameters to fopen.  TheseA parameters are passed along to RMS.  For example, you can pass in 
 "shr=get".  B Is there a way, perhaps using inline assembly, that I can call theC real DECC$FOPEN, telling it to use all of the parameters that I was E passed?  Effectively, I'd like a jump statement to jump directly into E DECC$FOPEN, leaving the return address, argument count, etc... in all D of the appropriate registers and stack locations.  Is this possible?  E If not, I can always get the argument count (R25), and use va_args to D pull off each one, one at a time, then switch on the argument count, and call DECC$FOPEN:   switch(arg_count) { &  case 2: return DECC$FOPEN(name,mode);+  case 3: return DECC$FOPEN(name,mode,arg1); 0  case 4: return DECC$FOPEN(name,mode,arg1,arg2); };  " but that seems like the wrong way.  
 Any ideas?  
 joshua lehrer  factset research systems   ------------------------------  # Date: Tue, 28 Oct 2003 22:00:11 GMT 9 From: "Fred Kleinsorge" <my-last-name@stardotzko.dec.com> - Subject: Re: How are the sales of VMS going ? 2 Message-ID: <LFBnb.7940$iu4.7516@news.cpqcorp.net>   What is your first language?  L Bill and JF spread FUD over everything/anything, it's nothing new.  The factL that EV79 is now EV7z (it won't be in the process we planned) is pretty muchF a non-issue to most real customers.  Feedback on the current EV7 basedK systems from customers is that it has given them more performance than they 	 expected.    We are on plan.   I Nobody is trying to "shut anyone down" who we haven't wanted to leave for 3 years.  It's just the same old crap, different day.       ; "mist dragon" <mistdragon@zdnetonebox.com> wrote in message 7 news:7500353b.0310272251.454ee0ea@posting.google.com... E > I have seen a lot of activity lately from vendor to deny that there A > are problems of any kind on moving to Itanium. Even the regular G > posters like Bill and JF have got their part of flame and are claimed E > to spread FUD when they dislike the late news like cancelling EV79.  > @ > Officially everything looks fine from vendor and proceeding asF > planned. Alpha is EOL, last small tuning next year, iVMS is running,E > albait beta and slowly. Vendor is giving very clear message that no G > matter the arguments, this is the way it is gonna be - take it or cry  > and take it. > H > However, it seems that questions and opinions here carry larger weightH > than vendor would like to and they want to shut them down at any cost.A > Some of the answers from vendor seem to reflect desperately the / > 'truths' they have got from their management.  >  > I smell fear here. > ? > But fear for what ? If OpenVms is a hen laying golden eggs as E > represented in sales figures, then why would anyone kill it and not F > promote it ? Otoh, if the sales figures are not what they seem, thenA > there is really an actual fear in vendor of the future of iVMS,  > Itanium etc. > % > So how are the sales of VMS going ?    ------------------------------  % Date: Wed, 29 Oct 2003 00:06:31 -0500 * From: JF Mezei <jfmezei.spamnot@istop.com>- Subject: Re: How are the sales of VMS going ? ) Message-ID: <3F9F4AC9.A8980090@istop.com>    Fred Kleinsorge wrote:E > Bill and JF spread FUD over everything/anything, it's nothing new.    L You can blast me as much as you want.  But consider this: if all your formerL customers who were forced off VMS because of Digital/Compaq/HP policies wereB to come back to haunt you on this newsgroup, you'd be praising me.  J Not everyone has loyalty levels so high that we are willing to criticise a3 vendor for the good of the product we are loyal to.   L This is something HP management don't understand. Customers may have extremeM loyalty to VMS, but to transfer that loyalty to HP loyalty, it takes a lot of K work, and that is something which HP isn't doing. I have 0 loyalty to HP. I N still see them as a competitor to VMS, not a promoter of VMS. I still see them% as taking decisions that hinder VMS.    J Had HP been keen on making best use of Alpha to promote VMS and even Tru64J until IA64 was really better, then that would have helped build trust. ButJ because HP is seen is purposefully slowing down Alpha in order to not make- IA64 look so lame, then distrust of HP grows.   L Think again. Perhaps you should see me as the ghost of all the customers who! left VMS without telling you why.    ------------------------------  % Date: Tue, 28 Oct 2003 14:37:00 -0600 0 From: Patrick Spinler <spinler.patrick@mayo.edu>9 Subject: ICONV, UTF-8, and language fun on OpenVMS - 0.62 ' Message-ID: <3F9ED36C.3040805@mayo.edu>    Hi:   H I'm trying to use FreeTDS (www.freetds.org) on OpenVMS, since Sybase no I longer supplies a client and we need to upgrade to use our institutional  G sybase dbms server versions.  I was advised to stick with FreeTDS 0.61  % 'cause of various problems with 0.62.   G Unfortunately, it turns out that we need some functions only available  F in 0.62, specifically, the ct_param calls used to set up sp_regwatch, ! which is heavily used in our app.   E I compiled 0.62 with a few minor changes (if someone can tell me the  H preferred patch format and where to send it, I can try to send a patch).  B However, I immediately ran into the UTF-8 and ISO-8559-1 problems  discussed in this thread:   ? <http://lists.ibiblio.org/pipermail/freetds/2003q2/012650.html>   D In summary, there's two problems.  First the solvable one: VMS uses G 'ISO8559-1' instead of the 'ISO-8559-1' used in the FreeTDS source.  I  6 fixed this by, (as recommended by Craig Berry) putting       client charset = ISO8859-1  H in the [global] section of my FreeTDS.conf file, and by adding an alias B to the iconv_aliases structure in encoding.h for {"ISO8559-1", 0}.  D Now the hard one: tds_iconv_init wants to set up a translation from H UTF-8 (or an equivilent charset) to ISO-8859-1.  The default install of I VMS has no such translation available, only to ISO-8559-1 from UCS-2 and   UCS-4.   Help !  Should I:   B *) Find an appropriate language kit supporting UTF-8 charsets and H translations for OpenVMS ?  Where would I even begin looking for such a  thing ?   ? *) Try to copy the ct_param() functionality from 0.62 to 0.61 ?    *) Something else ?    Thanks,  -- Pat   ------------------------------  # Date: Wed, 29 Oct 2003 04:21:29 GMT 6 From: "Craig A. Berry" <craigberry@mac.com.spamfooler>= Subject: Re: ICONV, UTF-8, and language fun on OpenVMS - 0.62 @ Message-ID: <7c0ae2fea547c063d494ee0a7fca2af8@news.teranews.com>  G I won't repeat the entire answer I gave to your identical query on the  E FreeTDS list, but I will repeat this bit that may be of more general  ( interest to c.o.v. readers and googlers:    ' In article <3F9ED36C.3040805@mayo.edu>, 2  Patrick Spinler <spinler.patrick@mayo.edu> wrote:  D > *) Find an appropriate language kit supporting UTF-8 charsets and J > translations for OpenVMS ?  Where would I even begin looking for such a 	 > thing ?   G Right where the documentation tells you it is (but yes, it's harder to  G find than it should be).  You need the internationalization kit in the  E directory [VMSI18N_ALPHA07x] on the layered product CD with a volume  C label of ALP07xLP where "x" is your minor VMS version number.  And  D before anyone asks, yes, it is quite silly to have a perfectly good D iconv implementation but no UTF-8 translations available without an  additional installation.   ------------------------------    Date: 28 Oct 2003 15:38:52 -0800" From: cocacolaeisbaer@gmx.at (joe): Subject: Re: LMF licence check has failed. Please help :-)= Message-ID: <d627f19f.0310281538.10b4fe67@posting.google.com>    THANK YOU PEOPLE :-) !!!!!  D It is WORKING!! Now I have understand this license scheme and made aF new installation with also registering DW-MOTIF and now I'm looking to DecWindows the first Time.E This is realy realy motivating to me that with the help of you people E I have the possibility now to check out this great System and learn a  lot about this OS.  : I LOVE YOU PEOPLE, I LOVE VMS AND I LOVE THE USENET :-))))    ] hoff@hp.nospam (Hoff Hoffman) wrote in message news:<TZwnb.7910$MR3.2752@news.cpqcorp.net>... _ > In article <3F9E8E6E.49BFA4B0@sture.homeip.net>, Paul Sture <nospam@sture.homeip.net> writes:  > :David J. Dachtera wrote:  > :>   > :> joe wrote:  > :> >K > :> > Thank you realy much for your detailed posting but I think I already F > :> > registered the right PAK correctly and I have enabled it at the > :> > installation process.M > :> > I did act to your suggestion with the faq but it is like all the other ! > :> > faq's and google searches. L > :> > This license problem is realy confusing to me and I fear that I can'tG > :> > solve it and I never can check out this great OS because of this  > :> > stupid licensing.M > :> > This is the reason why I'm hopeing to get a good hint from usenet what L > :> > I exactly should do in my situation. In the meantime I will study the > :> > faq.  > M >   The FAQ exists to try to reduce the number of times that the usenet folks L >   answer the same question.  There are direct advantages to you -- you getM >   the answer more quickly -- and indirect advantages -- you avoid acquiring M >   an untoward reputation for the questions asked, and reduce the likelyhood K >   that your future questions will end up unseen; that your questions will M >   not be filtered by various newsreader killfiles.  No offense is intended.  > L >   There are also direct benefits to folks reading and answering questions,K >   in that a complete and detailed and oft-reviewed explanation is readily J >   available for citation, and the respondents have to spend the time andN >   effort involved in re-creating the answer.  Again, no offense is intended. >  > M > :> Well, what everyone seems to be trying to say is that there are two sets J > :> of licenses. One is just the operating system license. The other is aL > :> long list of licenses for pieces of software called "layered products".L > :> The part no one seems to explain fully is that the o.s. license is justK > :> that: a license for the o.s. The GUI is considered a "layered product"  > :> for this purpose. > :>  L > :> In addition to the OPENVMS-ALPHA license, you need the DW-MOTIF license* > :> from the layered product license set. > :>K > :> How do you load that now? Well, you gotta power up the machine without M > :> the keyboard connected, with a terminal or terminal program of some kind H > :> attached via the serial (console) port (the default is usually 9600J > :> baud, 8 bits, no parity, one stop bit). That should make it revert toH > :> the "serial console". Then you can log in and register the DW-MOTIFK > :> license, shutdown, re-attach the keyboard and power/boot up again. Now   > :> your GUI login should work. >  >  > H >   As for the question, please read the Frequently Asked Questions, andK >   specifically please read the three previously-cited sections.   Details I >   there include how to register the licenses when the failure arises on . >   a system with no available serial console. > K >   As for access to the serial console, you generally don't need to remove M >   the keyboard connection nor alter the workstation settings, you only need J >   trigger a conversational bootstrap.  This switch can normally be done G >   without access to and without altering the setting of the alternate M >   console -- if the particular system requires the selection at the console E >   environment prompt level, though resetting those systems with the K >   switch-based alternate console is obviously quite easy -- assuming that G >   the target box involved is a workstation with the graphics display  L >   enabled.  The switch mechanism itself is also discussed in the FAQ, BTW. > D >   Systems that are not workstations do not have the concept of the >   alternate console. > J >   Most (all?) boxes that have alternate (serial) consoles will honor theJ >   BREAK signal or similar input on the serial console and will switch toK >   the serial console -- without this, there would be no easy way to reset K >   the system to use the alternate (serial) console for situations such as 
 >   this one.  > H >   It is also possible to perform the conversational bootstrap from theL >   graphics head, BTW.  I've used that on more than a few occasions, thoughN >   the usual wrinkle with licensing -- with either the serial or the graphicsJ >   console -- is the scale of typing involved.  If you can't transfer theJ >   license PAKs on disk, then you can end up with having to type a few ofL >   the critical PAKs (DW-MOTIF, the core OpenVMS licenses, and probably theK >   UCX license for IP networking) and then use the network to transfer the 4 >   file containing the licenses over to the system. > K >   A core problem within OpenVMS here, unfortunately, involves the ease by G >   which folks can get into this no- or expired-license state, and the 8 >   relative difficulty of getting out of the situation. > P >  ---------------------------- #include <rtfaq.h> -----------------------------M >     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq P >  --------------------------- pure personal opinion ---------------------------G >         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  % Date: Tue, 28 Oct 2003 19:45:44 -0600 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> : Subject: Re: LMF licence check has failed. Please help :-)' Message-ID: <3F9F1BC8.10F9308A@fsi.net>    Hoff Hoffman wrote:  > [snip] >     If you can't transfer the J >   license PAKs on disk, then you can end up with having to type a few ofL >   the critical PAKs (DW-MOTIF, the core OpenVMS licenses, and probably theK >   UCX license for IP networking) and then use the network to transfer the 4 >   file containing the licenses over to the system.  F My trick of choice is to cut-and-paste between Notepad (or Eudora) and1 Reflection while hooked up to the serial console.    YMMV...    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------   Date: 28 Oct 2003 23:50:21 GMT From: healyzh@aracnet.com   Subject: Mac OS X 10.3 & OpenVMS, Message-ID: <bnmvbt01gqi@enews1.newsguy.com>  I I know there are a bunch of Mac users here, has anyone upgraded to 10.3?  J I'm wondering if the Termina.app (which I believe has been enhanced) playsI better with OpenVMS.  Specifically, does it support the keypad in MAIL or 	 EDIT now?   D Also has anyone run into any problems with 10.3 working with OpenVMS systems?   		Zane   ------------------------------    Date: 28 Oct 2003 22:40:46 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) $ Subject: Re: Mac OS X 10.3 & OpenVMS3 Message-ID: <RGWQ0utNftnK@eisner.encompasserve.org>   H In article <bnmvbt01gqi@enews1.newsguy.com>, healyzh@aracnet.com writes:K > I know there are a bunch of Mac users here, has anyone upgraded to 10.3?  L > I'm wondering if the Termina.app (which I believe has been enhanced) playsK > better with OpenVMS.  Specifically, does it support the keypad in MAIL or  > EDIT now?   L Mail was OK.  EDIT would depend on which editor you use - TECO should be OK.I As discussed here before, keypad emulation is incorrect and does not work  properly with ANUNEWS.   ------------------------------  % Date: Wed, 29 Oct 2003 00:08:08 -0500 % From: Howard Shubs <howard@shubs.net> $ Subject: Re: Mac OS X 10.3 & OpenVMS< Message-ID: <howard-C093CE.00080829102003@enews.newsguy.com>  G In article <bnmvbt01gqi@enews1.newsguy.com>, healyzh@aracnet.com wrote:   K > I know there are a bunch of Mac users here, has anyone upgraded to 10.3?    F I've begun the process of backing everything up.  After that, I'll do  the upgrade.   --  D You are what you eat, therefore, I'm a vegetable!  Cows and chickens and Pop Tarts are too.   ------------------------------  # Date: Tue, 28 Oct 2003 22:34:30 GMT & From: jlsue <jefflsxxxz@sbcglobal.net>; Subject: Re: OpenVMS I64 ISV application count now over 500 8 Message-ID: <0mrtpv899pk8v7p0d80j19cohlaqmtenic@4ax.com>  E On Tue, 28 Oct 2003 09:33:56 +0000, Andrew Harrison SUNUK Consultancy . <Andrew_No.Harrison_No@nospamn.sun.com> wrote:  
 >jlsue wrote: H >> On Fri, 24 Oct 2003 14:12:50 +0100, Andrew Harrison SUNUK Consultancy1 >> <Andrew_No.Harrison_No@nospamn.sun.com> wrote:  >>   >>   >>  B >>>Check my past posts I have also never suggested that OpenVMS is@ >>>crap, rubbish, terrible, slow, insecure etc all words used byB >>>members of the choir describe Solaris, Linux, UNIX. Mostly usedA >>>by people who have absolutely no experience of the system that  >>>they are describing.  >>> C >>>I am carefull not describe OpenVMS in these terms because I have = >>>no current experience of OpenVMS, I used VMS when I was at > >>>univercity and later when I used to install DECNET on SunOS@ >>>at Digital/Sun sites. Its a great pity that the vast majority? >>>of Solaris slaggers off who fall directly into this category * >>>as well don't follow the same strategy. >>   >>  J >> You have made claims about things like capabilities of VMSclusters thatL >> have been clearly wrong.  And you have argued with posts by others who doK >> have the real-world experience about those capabilities.  This, at best, 9 >> contradicts your first statement in paragraph 2 above.  >>   >  > > >Crap, I made not claims about OpenVMS cluster that were wrong= >I corrected a whole load of BS about the capabilites of UNIX = >clusters that periodically invaded this newsgroup from a few  >ill informed sources.   Check this entire string:   ; 	Subject:  Compaq: A simple, affordable clustering solution   G I tried repeatedly to explain to you that most of what Kerry said about I VMSclusters was true, and have been involved with many clusters as way of  showing my experience.  ( You choose to continue arguing about it.   > F >> And many of your discussions degenerate into trivializing, personalL >> attacks, and name-calling eventually; so don't get too high on that horse >> of self righteousness.  >>   > 	 >Really !  >   G Yes, really.  Check that string mentioned above.  Of the two of us, whoC1 resorted to condescension and name-calling first?r   ------------------------------  # Date: Tue, 28 Oct 2003 22:25:48 GMTn& From: jlsue <jefflsxxxz@sbcglobal.net>; Subject: Re: OpenVMS I64 ISV application count now over 500!8 Message-ID: <75rtpvkp8071nkn938n68di9ten29srr4b@4ax.com>  F On Mon, 27 Oct 2003 22:14:53 GMT, "John Smith" <a@nonymous.com> wrote:     >8L >Great flashing and waving of porcupine quills when HP is criticized or when8 >it is suggested that HP is 'economical with the truth'.  I More likely, just bored with this newsgroup's noise ratio being too high.pK Especially when you just don't know the truth, only the publically releasedM parts.  G The point is, decisions have been made and the company is going forward K with those decisions.  How successful it will be has  yet to be determined.    ------------------------------  % Date: Tue, 28 Oct 2003 19:34:46 -0600n1 From: "David J. Dachtera" <djesys.nospam@fsi.net>t; Subject: Re: OpenVMS I64 ISV application count now over 500o' Message-ID: <3F9F1936.F6B06220@fsi.net>S   jlsue wrote: > H > On Mon, 27 Oct 2003 22:14:53 GMT, "John Smith" <a@nonymous.com> wrote: >  > >eN > >Great flashing and waving of porcupine quills when HP is criticized or when: > >it is suggested that HP is 'economical with the truth'. > K > More likely, just bored with this newsgroup's noise ratio being too high.RM > Especially when you just don't know the truth, only the publically released. > parts.  A So, you admit it: what hp says and what it does are not the same.1  I > The point is, decisions have been made and the company is going forward M > with those decisions.  How successful it will be has  yet to be determined.   B Well, deception rarely begets ultimate success. History has provenG through the ages that honesty and integrity are always the best policy.V   -- s David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/o   ------------------------------  # Date: Wed, 29 Oct 2003 03:23:59 GMTd# From: "John Smith" <a@nonymous.com> ; Subject: Re: OpenVMS I64 ISV application count now over 500tG Message-ID: <jpGnb.48361$7B1.3651@news04.bloor.is.net.cable.rogers.com>    jlsue wrote:H > On Mon, 27 Oct 2003 22:14:53 GMT, "John Smith" <a@nonymous.com> wrote: >  >  >>F >> Great flashing and waving of porcupine quills when HP is criticizedB >> or when it is suggested that HP is 'economical with the truth'. >eE > More likely, just bored with this newsgroup's noise ratio being toos? > high. Especially when you just don't know the truth, only the  > publically released parts. >tA > The point is, decisions have been made and the company is goinguF > forward with those decisions.  How successful it will be has  yet to > be determined.     Let's see...   Plan of Record...v Committment...
 Roadmap...  G all these things which were made public by HP were used by customers infE their planning and purchasing decisions. To those who made purchasinggL Alpha's based on HP's Plan of Record and its (dare I say) solemn committmentK to Alpha/VMS customers and Alpha/Tru64 customers, should we now say that HP H cannot be trusted, that HP deserves to be punished in a court of law forK deceptive and misleading sales practices? I'm sure that some customers feelh	 that way.o  I Now to be fair, it's not often that companies (or people for that matter)-J tell the truth, the whole truth, and nothing but the truth. The reality isK that the usual state of affairs is that the truth is told, but only insofareL as 70% of the whole story is told. From where you sit it may be that you areF convinced that your employer is lily-white, having never mis-spoken toG customer and is adhering *faithfully* to the commitments it made to itsaF customers. Equally there are those who feel that this is not the case.  H It's a funny thing to see....people who were at one time the most ardentL defenders of their employers changing their tune once the pink slip arrives,2 and far too late for things they once believed in.  K Not to pick on any HP employee, there have been some simple questions askedaL in c.o.v. about what your immediate managers say about the lack of promotionG of VMS in the marketplace. Surely this subject come up around the watereJ cooler and in the cafeteria, however the silence here from HP employees isL deafening. But I can understand that...after all this is a public forum, and/ management might be watching - and probably is.e  H Each bone-head decision or inaction of HP's with respect to VMS makes itK more and more politically difficult for me to take the risk in recommendingaK VMS on any platform even if VMS suits the project better, and no matter how I much I personally believe that the efforts of you and your colleagues are J first-rate. Perception *IS* reality, and for a very large number of us whoK write here, and for a large number who merely lurk, that perception of HP'soK actions is negative. Despite all the financial difficulties that Sun is in,oJ Sparc/Solaris is a much more politically viable choice for me to recommendJ to my customer for a $20MM project. You say "How successful it will be hasI yet to be determined." - with fewer and fewer $20MM projects coming VMS'sS, way, I'd say the future is inevitably bleak.   ------------------------------    Date: 28 Oct 2003 11:51:58 -08001 From: susan_skonetski@hotmail.com (Sue Skonetski)n& Subject: OpenVMS Pearl Computer Weekly= Message-ID: <857e9e41.0310281151.7392b5ad@posting.google.com>r  S http://www.computerweekly.com/articles/article.asp?liArticleID=126004&liFlavourID=1$  C Hewlett Packard has launched a high-end Alphaserver and updated themC OpenVMS operating system with higher levels of system availability, , increased I/O and symmetric multiprocessing.  @ But users of the platform have been warned against making suddenE migration plans, even though HP only plans to ship the hardware for ao further three years.  D Alphaservers running OpenVMS are typically used for mission-criticalC applications in areas such as banking, aerospace and manufacturing.   C Martin Riley, HP's Alphaserver business manager for UK and Ireland,F@ said, "Because of their mission-critical applications, customers? cannot switch overnight - it will take them years of planning."T  C The company has pledged to support the Alphaserver range until 2012eA and users will be able to run OpenVMS on the machines until aboutC 2022.E  D Colin Butcher, board member of the HP User Group, said, "There is soA much at stake that you do not want to risk the disruption. MovingyD platforms in an operational mission-critical environment should only, be done after careful and thorough testing."  @ But Butcher urged users to get involved with HP's early adoptersF programme to gain experience of the new platform. A developer's kit toF enable users to examine OpenVMS on Integrity servers will be available in December.   ------------------------------  # Date: Tue, 28 Oct 2003 20:40:35 GMTi# From: "John Smith" <a@nonymous.com>a* Subject: Re: OpenVMS Pearl Computer WeeklyH Message-ID: <7vAnb.47944$7B1.20007@news04.bloor.is.net.cable.rogers.com>   Sue Skonetski wrote: > L http://www.computerweekly.com/articles/article.asp?liArticleID=126004&liFlav ourID=1t >eE > Hewlett Packard has launched a high-end Alphaserver and updated theeE > OpenVMS operating system with higher levels of system availability,.. > increased I/O and symmetric multiprocessing. >tB > But users of the platform have been warned against making suddenG > migration plans, even though HP only plans to ship the hardware for aM > further three years. >uF > Alphaservers running OpenVMS are typically used for mission-criticalE > applications in areas such as banking, aerospace and manufacturing.a > E > Martin Riley, HP's Alphaserver business manager for UK and Ireland,VB > said, "Because of their mission-critical applications, customersA > cannot switch overnight - it will take them years of planning.". >2E > The company has pledged to support the Alphaserver range until 2012cC > and users will be able to run OpenVMS on the machines until about( > 2022.s >"F > Colin Butcher, board member of the HP User Group, said, "There is soC > much at stake that you do not want to risk the disruption. Moving4F > platforms in an operational mission-critical environment should only. > be done after careful and thorough testing." >IB > But Butcher urged users to get involved with HP's early adoptersH > programme to gain experience of the new platform. A developer's kit toH > enable users to examine OpenVMS on Integrity servers will be available > in December.    ) Great. Alpha and VMS exposure in the U.K.   L When is Blatz going to get off his b*** and get some VMS 'buzz' happening inG North America? Or is North America too close to carly(tm) and hence too-8 visible to take the risk of advertising & marketing VMS?  I I have a funny feeling that HP Botswana will be doing VMS advertising and 3 marketing before HP does anything in North America.R   ------------------------------  + Date: Wed, 29 Oct 2003 06:52:39 +0000 (UTC)n3 From: "Richard Maher" <maher_rj@hotspamnotmail.com>l* Subject: Re: OpenVMS Pearl Computer Weekly2 Message-ID: <bnno3m$h85$1@hercules.btinternet.com>   Hi,R  F Made IT Weekly as well with even a half flattering quote from Gartner.   Regards Richard Maher.  < Sue Skonetski <susan_skonetski@hotmail.com> wrote in message7 news:857e9e41.0310281151.7392b5ad@posting.google.com...t >jL http://www.computerweekly.com/articles/article.asp?liArticleID=126004&liFlav ourID=1. > E > Hewlett Packard has launched a high-end Alphaserver and updated therE > OpenVMS operating system with higher levels of system availability,e. > increased I/O and symmetric multiprocessing. >tB > But users of the platform have been warned against making suddenG > migration plans, even though HP only plans to ship the hardware for aa > further three years. >SF > Alphaservers running OpenVMS are typically used for mission-criticalE > applications in areas such as banking, aerospace and manufacturing.  >IE > Martin Riley, HP's Alphaserver business manager for UK and Ireland,,B > said, "Because of their mission-critical applications, customersA > cannot switch overnight - it will take them years of planning."" >0E > The company has pledged to support the Alphaserver range until 2012IC > and users will be able to run OpenVMS on the machines until about  > 2022.. >eF > Colin Butcher, board member of the HP User Group, said, "There is soC > much at stake that you do not want to risk the disruption. MovingvF > platforms in an operational mission-critical environment should only. > be done after careful and thorough testing." >tB > But Butcher urged users to get involved with HP's early adoptersH > programme to gain experience of the new platform. A developer's kit toH > enable users to examine OpenVMS on Integrity servers will be available > in December.   ------------------------------    Date: 28 Oct 2003 11:50:55 -08001 From: susan_skonetski@hotmail.com (Sue Skonetski)uY Subject: Reminder, NY Metro LUG meeting on Wed the 29th (some of my favorite people preseo= Message-ID: <857e9e41.0310281150.6a7c6d2f@posting.google.com>e  A Please join us for the next NY Metro Local Users Group meeting.  h= Note: you must RSVP in advance for entrance to the building. -   "OpenVMS Update"   Wednesday, October 29th, 2003. 12:30-7 PM V HP Offices .. 2 Penn Plaza 8th Floor ( 7th Ave and 32nd St) , Directly above the entrance to Penn Station.  : 12:30 - 1:00     Check in and old-style DECUS Networking. / 1:00 - 1:10     Welcome and announcements, HP. -> 1:10 - 1:15     Gary McCready: LUG Business and Announcements : 1:15 - 2:30     Greg Jordan, HP "OpenVMS Technical Update"= 2:45 - 4:00     Greg Jordan, HP "OpenVMS Performance Update"  ? 4:15 - 5:00	    Edgar Zamora, HP "OpenVMS Implementation Updatei5 5:00 - 5:30     Break, Demonstrations and networking.gB 5:30 - 7:00	    Greg Jordan, HP "OpenVMS Technical Update" (repeat	 from 1pm)s  0  OpenVMS Technical Update and Product Road Maps   @ This session includes key highlights of the OpenVMS Alpha V7.3-1F release, the OpenVMS system support rollout plan for the EV7 platform,E a preview of upcoming OpenVMS releases, the rollout plans for OpenVMS D on ItaniumR architecture-based HP systems and the road map and plansB for the OpenVMS layered product suite. Discussion of the operating> system's new features will include such topics as performance,. security and system availability enhancements.   OpenVMS Performance Update e  E This session discusses details of the performance enhancements to thel= OpenVMS V7.3-1 operating system. A number of examples showing ? application performance improvements from both software and newtD hardware are presented. Information on performance work for the next1 release of the operating system is also provided.p     OpenVMS Implementationse  F Case studies of current and planned local OpenVMS implementations will
 be discussed.n    F Greg Jordan, Senior Member of Technical Staff, OpenVMS Engineering HP   C Greg Jordan: Greg is a Sr. Member of Technical staff in the OpenVMSaB Base OS Engineer Group. He has been working on the performance andC scaling of OpenVMS on large SMP systems for the last several years.aE Greg joined Digital Equipment Corporation in 1981 and has been a partn" of OpenVMS Engineering since 1991.    ) Edgar Zamora, BCS Solutions Architect, HP,  A Edgar is an HP VMS Ambassador and serves the NYC Metro area as ane OpenVMS resource for HP.  C To RSVP: send email to  NYMLUG-RSVP (at) yahoogroups.com, includingiF company name, when you plan to arrive and a way to contact you, if notB by your sending email address. You response, including the sending6 email address, will not be visible in any public list.  E You will be met by a HP employee at the security desk at the entrancesE to the building (now at the 7th Avenue side). Should you arrive late,t@ please call the HP reception desk at 212-856-2000 for an escort.E Please plan to arrive promptly as there is limited seating available.   C HP will provide light refreshments for the afternoon, and pizza for  those staying after 5pm.  F For further information on the group you may contact Gary McCready at @ NYMLUG(at)McCready.com or 201-556-3359. If you are interested inB suggesting a meeting topic please contact Gary to be placed on the Steering Committee email list.  E Apologies are in order if you have received multiple versions of thissD message. Feel free to forward this message to others who may have anD interest in attending - you do not have to be an Encompass member to attend.p  D If you did not receive an "original" version of this message, please? join our mailing list at  http://groups.yahoo.com/group/NYMLUG/l   ------------------------------  % Date: Tue, 28 Oct 2003 23:34:59 -0500D* From: JF Mezei <jfmezei.spamnot@istop.com>8 Subject: Re: Swan Song For The Alpha Processor - TechWeb) Message-ID: <3F9F4367.3AA4739E@istop.com>P   david20@alpha2.mdx.ac.uk wrote: O > Given Terry Shannon's flagwaving for IA64 that is a very interesting comment.sO > Unless I've missed some announcement from Intel IA64 will have no presence on ( > the desktop in the foreseeable future.  I isn't terry Shannon now just a semi-official HP spokesperson ?He's had to J build new relationships with 2 companies because his established ones withL Digital, built over a very long time vanished. And to get information duringN the relationship building phase, one must toe the corporate line otherwise one is not given any information.   L You can't blame him. He's caught between a rock and a hard place. However, I7 now take his comments/reports with a big grain of salt.    ------------------------------  % Date: Tue, 28 Oct 2003 18:05:08 -0800e3 From: Alan Frisbie <Usenet01REMOVE@Flying-Disk.com>eE Subject: Re: Video "ringing" with PBXGA but not Mach64 or Elsa Glorias. Message-ID: <3F9F2054.9050202@Flying-Disk.com>   Rich Jordan wrote:8 >> Alan Frisbie <Usenet01REMOVE@Flying-Disk.com> writes:  G >>> Since I did not see this problem on another Alpha with an ATI video G >>> card, I tried switching to an ATI Mach64 video card and the problem E >>> went away completely!  Just to complete the test, I also tried an A >>> Elsa Gloria Synergy II card and it also worked perfectly.  NosE >>> ringing, even with a cheap cable or going through the KVM switch.,  G >  The ZLXp-E2 card (maybe others in the series) reportedly originally  H > came with a monitor cable that grounded one of the three color signal K > grounds, or was used with a monitor that performed the same function. If lK > you scope the card, I believe two of the three color signal ground wires aE > (red and blue if I recall correctly) are grounded, while the third   > (green?) ground is floating.  F BINGO!   That was it!   Even though an ohmmeter showed zero resistanceB between the three analog grounds (pins 6, 7, & 8), a small wire (IB used 30ga wire-wrap wire) soldered across all three pins cured theF problem.   Now I can use the ZLXp-E2 at all 1280x1024 rates, including< the most "agressive", setting 13 (80 KHz Horiz, 75 Hz Vert).  D I am now using it through my Raritan KVM switch and cables without a trace of "ringing".,  B Hoff, do you suppose you could get this added to the FAQ or Wizard. answers in case anyone else hits this problem?  + Thank you all for your helpful suggestions.   H Now I have just one remaining question: Why does "Style Manager - Color"F not allow me to change colors (the "Modify" button is greyed out) with< the ZLXp-E2, but does allow it with the Elsa and ATI boards?   Alan   ------------------------------  % Date: Tue, 28 Oct 2003 19:38:02 -0600s1 From: "David J. Dachtera" <djesys.nospam@fsi.net>y$ Subject: Re: VMS Text Files --> Unix' Message-ID: <3F9F19FA.616DB72C@fsi.net>t  ( Andrew Harrison SUNUK Consultancy wrote: >  > David J Dachtera wrote:sz > > koehler@eisner.nospam.encompasserve.org (Bob Koehler) wrote in message news:<86B5B8hI2Iio@eisner.encompasserve.org>... > >iX > >>In article <e$+L0YWUD9Rr@eisner.encompasserve.org>, briggs@encompasserve.org writes: > >>C > >>>I don't see any support in my copy of dd for ANSI labelled magt
 > >>>tape. > >>L > >>   It's not built in.  You have to roll your own knowing how ANSI labels
 > >>   tapes.a > >e > > F > > In fact, little UN*X software supports ANSI labelled tapes. It's a! > > foreign concept in UN*X-land.r > >o > >e > F > Well except ansitar, ansitape, vmstp, tpmnt (UNICOS), ReelLibrarian,  > SAM-FS and a number of others.  $ How many of those ship with Solaris?   -- u David J. Dachtera- dba DJE Systems- http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/c   ------------------------------  % Date: Wed, 29 Oct 2003 06:11:45 +0100." From: Didier Morandi <no@spam.com>7 Subject: Re: [survey] why do you still use VAX systems?y2 Message-ID: <3f9f4c13$0$238$636a55ce@news.free.fr>   Chuck Graham wrote:u  F > The CHARON VAX emulator can be configured to be equivalent to a 7840H > by installing multiple copies of CHARON VAX on a multi-processor AlphaC > and clustering them together.  This has been tested on up to a 16aG > processor Alpha system with 15 instances of CHARON VAX with virtuallye; > linear increases in performance.  Results can be found onf > WWW.WinVMS.com.e  H Thanks, Chuck. Valuable input for the next VAX/VMS to Itanium Migration F Nwesletter, which will focus next month on emulation as a solution to % solve the VAX/VMS obsolescence issue.:  4 The October version of the letter may be found here:6 http://www.didiermorandi.com/vaxvms2itanium_200310.pdf   D.   ------------------------------   End of INFO-VAX 2003.599 ************************