1 INFO-VAX	Tue, 08 Jul 2003	Volume 2003 : Issue 373       Contents:1 =?ISO-8859-1?Q?Re:_Assign_9.1_GB_HD=B4s_to_8_GB?=  Re: APC UPS control for VMS  Re: APC UPS control for VMS  Re: APC UPS control for VMS  Re: Are HP listening?  Re: Are HP listening? 1 Re: Assign 9.1 GB =?iso-8859-1?Q?HD=B4s?= to 8 GB 1 Re: Assign 9.1 GB =?ISO-8859-1?Q?HD=B4s_to_8_GB?= % Re: Backup Software for VMS and Linux  Re: Basics of attaching a PC Re: Basics of attaching a PC Re: Basics of attaching a PC Re: Basics of attaching a PC; beta software of new Legato NetWorker Client & Storage Node  Cannot see disk drives Re: Cannot see disk drives Re: DHCP startup problems  Good code profilers on VMS?  Re: Good code profilers on VMS? I Re: HP Webcast this morning on Next-Generation Intel Itanium 2 processors # Re: HP World (was HP to drop hpux?) + Re: HP World: Why Alpha's Omega Makes Sense + Re: HP World: Why Alpha's Omega Makes Sense + Re: HP World: Why Alpha's Omega Makes Sense  KVM switches Re: KVM switches Re: KVM switches Re: KVM switches Re: KVM switches Re: KVM switches" Re: OpenVMS 7.3.1 Install problem." Re: OpenVMS 7.3.1 Install problem." Re: OpenVMS 7.3.1 Install problem." Re: OpenVMS 7.3.1 Install problem.< OpenVMS Technical Update Day in Chicago - Only 10 days away!@ Re: OpenVMS Technical Update Day in Chicago - Only 10 days away!@ Re: OpenVMS Technical Update Day in Chicago - Only 10 days away! Porting VAX Object Libraries  Re: Porting VAX Object Libraries  Re: Porting VAX Object Libraries RDB V7.1 Re: RDB V7.1* Re: Recursive copy between nodes using LAT* Re: Recursive copy between nodes using LAT Re: Rethinking  V.M.S  Re: Rethinking  V.M.S  Re: Running VMS off CD Re: Running VMS off CDP Re: SNMP Commands (was Re: How do I monitor the CPU temperature in  an         EP Re: SNMP Commands (was Re: How do I monitor the CPU temperature in an         ESP Re: SNMP Commands (was Re: How do I monitor the CPU temperature in an         ESP Re: SNMP Commands (was Re: How do I monitor the CPU temperature in an         ESP Re: SNMP Commands (was Re: How do I monitor the CPU temperature in an         ESH Re: Subject: Reading long files in BASIC that appears to be "recordless"0 Re: Sybase Migrations External Website available0 Re: Sybase Migrations External Website available0 Re: Sybase Migrations External Website available0 Re: Sybase Migrations External Website available+ Re: SYS$SPECIFIC and SYS$COMMON not enough? + Re: SYS$SPECIFIC and SYS$COMMON not enough? ! Re: Upcoming release of VMS 7.3-2 $ Re: Using ArcServe to backup VAX/VMS8 Re: VAX Vup Listing not available on HP - where is it ??8 Re: VAX Vup Listing not available on HP - where is it ??1 vms security model - does it still exist on IA64? 5 Re: vms security model - does it still exist on IA64? 5 Re: vms security model - does it still exist on IA64? 5 Re: vms security model - does it still exist on IA64? 5 Re: vms security model - does it still exist on IA64? 5 Re: vms security model - does it still exist on IA64? 5 Re: vms security model - does it still exist on IA64? , Re: What Tape Library for VMS and FC cluster, Re: What Tape Library for VMS and FC cluster  F ----------------------------------------------------------------------   Date: 7 Jul 2003 18:35:50 -0000 4 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>: Subject: =?ISO-8859-1?Q?Re:_Assign_9.1_GB_HD=B4s_to_8_GB?=1 Message-ID: <Karls-Ghost.20030707@cyberspace.nil>   = On 5 Jul 2003, contracer11@uol.com.br (Shiva MahaDeva) wrote: K >In my job Im using a MicroVAX 3100-98 (Personal Workstation), VMS V5.5-2. K > In this machine I have ~60 GB in SCSI HDs (a tower with 7 9.1 GB HDs).  ; > Looking behind this tower , I see BA35X-VA storage model. I > I want assign all 9.1 GB Hds from 9.1 to 8 GB, to avoit constant crash J > in this system. Id like to get a procedure to make this modifications,  > in details. Can you help me ?  > Thanks in advance...  N Should you choose to peruse the appropriate documentation you may discover theN rather shocking fact that your selected version of VMS will only support disks up to 8Gb in size.  G This is unfortunate, and investment in replacement disks may be costly.   N However, if you are prepared to try a rather hackerish solution, you will needH the specifications for the drives, a set of accurate torque wrenches forF dismantling, and reassembly, plus access to some precision engineeringH equipment.  Armed with these tools you can physically reduce the storageH capacity of the disks to that appropriate to your chosen version of VMS.  H First you must remove the platters from the casings.  Check and note theK torque settings of all nuts, bolts, and screws.  It is highly unlikely that H the manufacturer will provide these details in the drive specifications.  H Secondly, you must take each platter and carefully measure the diameter.K Check this twice, because if the calculations you make are in error you may  render the platter unusable.  H Calculate 87.9121% of this value - the difference between 9.1Gb and 8Gb.  J Take the two figures and program them into a computer controlled lathe, ifL you're lucky this will be an old machine which is still controlled by a VAX.  H Mount the platter in the lathe and proceed to reduce the diameter to the/ appropriate value from your calculations above.   D Repeat for each platter from a disk casing, reassemble, and you haveK successfully converted your disks from 9.1Gb to 8Gb.  Your problems are now  over.      Doc. --  K OpenVMS.         Eight out of ten hackers prefer *other* operating systems.    ------------------------------   Date: 7 Jul 2003 21:40:30 +0200 2 From: "Lars Holmstrm" <lars.holmstrom@flysta.net>$ Subject: Re: APC UPS control for VMS( Message-ID: <3f09ccaa$1@news.wineasy.se>  , We use the Powercute for VMS. Works perfect.. Can you describe your problem more in detail ? /Lars   / "Alfred Falk" <falk@arc.ab.ca> wrote in message 3 news:Xns93B1686F98B98falkarcabca@205.233.108.180... 2 > Kilgallen@SpamCop.net (Larry Kilgallen) wrote in- > news:E8A1TtoJwPr3@eisner.encompasserve.org:  > I > > In article <Xns93B16004BC898falkarcabca@205.233.108.180>, Alfred Falk  > > <falk@arc.ab.ca> writes:E > >> Has anyone developed software to control APC SmartUPS from OVMS? J > >> The Powerchute catalog does list a VMS version, which is no longer inH > >> development but still supported.  Assuming it's like PowerChute forF > >> Windows, I think I will have a hard time getting it to do exactly > >> what I want.  > > ? > > I believe Brian Schenkenberger has a product in this space.  > > A > > Use Google to search this newsgroup for posts containing both  > > "Schenkenberger" and "APC".  > ) > Looks promising.  Thanks for your help.  >  > --  B > ----------------------------------------------------------------B >   A L B E R T A         Alfred Falk               falk@arc.ab.caB > R E S E A R C H         Information Systems Dept   (780)450-5185- >   C O U N C I L         250 Karl Clark Road 3 >                         Edmonton, Alberta, Canada ! > http://www.arc.ab.ca/   T6N 1E4 " > http://www.arc.ab.ca/staff/falk/   ------------------------------  % Date: Mon, 07 Jul 2003 20:17:19 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> $ Subject: Re: APC UPS control for VMS' Message-ID: <3F0A1B9F.C52EA0D9@fsi.net>    "Lars Holmstrm" wrote:  > . > We use the Powercute for VMS. Works perfect.0 > Can you describe your problem more in detail ?  : How recent is your Powerchute release (date, not version)?   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Mon, 07 Jul 2003 21:29:12 -0500 ( From: Rich Jordan <duodec@speakeasy.net>$ Subject: Re: APC UPS control for VMS2 Message-ID: <UF2dnT6fFN-os5eiXTWc-g@speakeasy.net>   http://www.tmesis.com/upshot  I This is Brian's product for SmartUPS systems and OpenVMS.  We have it in  F use at one customer site; its a lot more versatile than the APC code, F which I believe only uses the 'dumb' relay mode, not the smart serial H mode.  UPShot also provides a web interface that you can use to monitor 9 and partly manage the UPS remotely (with authentication).   F I had planned on getting it for home, but I just couldn't justify the H cost of a SmartUPS in the range I needed when Sams Club put BackUPS Pro  1100s on sale recently....  E Good product, and Brian worked with us to get it going under TCPware  D (which at that time, ~2 years ago, he hadn't been able to test with " much) so the support is there too.   Rich   ------------------------------  % Date: Mon, 07 Jul 2003 10:45:18 -0700 " From: Eric Bruno <eric@ebruno.org> Subject: Re: Are HP listening?) Message-ID: <3F09B1AE.9020406@ebruno.org>   & --------------0306000705060102000600039 Content-Type: text/plain; charset=us-ascii; format=flowed  Content-Transfer-Encoding: 7bit        David J. Dachtera wrote:   >Eric Bruno wrote: >    > > >>"David J. Dachtera" <djesys.nospam@fsi.net> wrote in message# >>news:3F07A23A.6C67B8A8@fsi.net...  >>     >>J >>>Re: the subject, "Are HP Listening?", experience to date indicates that >>>they are/do not.  >>>  >>>"Doc.Cypher" wrote:	 >>>        >>> 
 >>>>[snip]1 >>>>Here's my correspondent's list of suggestions  >>>>A >>>>1.  Get a major application such as SAP running on VMS again.  >>>>         >>>>I >>>Get major packages back, like Polycenter. The current poor excuses for K >>>system management tools are, at the very least, albatrosses: an absolute 9 >>>disgrace and, at the very best, an industry-wide joke.  >>> 	 >>>        >>> 3 >>PolyCenter would compete with HP OpenView, [snip]  >>     >> > C >Not directly. PolyCenter wasn't a client/server solution, with the B >possible exception of PCM, and was VMS-only: it didn't attempt to= >encompass non-VMS systems and/or their management paradigms.  >    > I We used Polycenter to manage the NASA Science Internet for 7 years which   was primarly Unix G systems and SNMP with some VMS.  We had to drop it when NSI was merged   in with NISN which andG the Ames NOC closed and moved to Huntsville, AL since Marshall Used HP  	 OpenView.   G There are plug-ins for HP Openview to manage VMS systems so be it good    bad or indifferent HP ManagementB can claim there is an existing solution.  How does that ad go "HP  OpenView works right now" :-).   >    >     & --------------030600070506010200060003) Content-Type: text/html; charset=us-ascii  Content-Transfer-Encoding: 7bit   ? <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">  <html> <head>   <title></title>  </head>  <body> <br> <br> David J. Dachtera wrote:<br>< <blockquote type="cite" cite="mid3F087B3D.162AAFB5@fsi.net">    <pre wrap="">Eric Bruno wrote:   </pre>   <blockquote type="cite">     <pre wrap="">"David J. Dachtera" <a class="moz-txt-link-rfc2396E" href="mailto:djesys.nospam@fsi.net">&lt;djesys.nospam@fsi.net&gt;</a> wrote in messagel <a class="moz-txt-link-freetext" href="news:3F07A23A.6C67B8A8@fsi.net">news:3F07A23A.6C67B8A8@fsi.net</a>...
     </pre>     <blockquote type="cite">Z       <pre wrap="">Re: the subject, "Are HP Listening?", experience to date indicates that they are/do not.   "Doc.Cypher" wrote:        </pre>       <blockquote type="cite">         <pre wrap="">[snip] - Here's my correspondent's list of suggestions   = 1.  Get a major application such as SAP running on VMS again.          </pre>       </blockquote> Y       <pre wrap="">Get major packages back, like Polycenter. The current poor excuses for H system management tools are, at the very least, albatrosses: an absolute6 disgrace and, at the very best, an industry-wide joke.         </pre>     </blockquote> B     <pre wrap="">PolyCenter would compete with HP OpenView, [snip]
     </pre>   </blockquote>    <pre wrap=""><!---->B Not directly. PolyCenter wasn't a client/server solution, with theA possible exception of PCM, and was VMS-only: it didn't attempt to < encompass non-VMS systems and/or their management paradigms.   </pre>
 </blockquote> H We used Polycenter to manage the NASA Science Internet for 7 years which was primarly Unix<br> N systems and SNMP with some VMS. &nbsp;We had to drop it when NSI was merged in with NISN which and<br> T the Ames NOC closed and moved to Huntsville, AL since Marshall Used HP OpenView.<br> <br>J There are plug-ins for HP Openview to manage VMS systems so be it good bad  or indifferent HP Management<br>O can claim there is an existing solution. &nbsp;How does that ad go "HP OpenView  works right now" :-).<br>  <br>< <blockquote type="cite" cite="mid3F087B3D.162AAFB5@fsi.net">   <pre wrap="">    </pre>
 </blockquote>  <br> </body>  </html>   ( --------------030600070506010200060003--   ------------------------------  # Date: Mon, 07 Jul 2003 19:29:49 GMT # From: "John Smith" <a@nonymous.com>  Subject: Re: Are HP listening?H Message-ID: <NSjOa.72940$a51.54078@news02.bloor.is.net.cable.rogers.com>   <Dave Brennan> wrote in message 2 news:ov1egv4rifn1ahguk5otplu7a6s44j2o38@4ax.com...7 > Doc.Cypher <Use-Author-Address-Header@[127.1]> wrote:  > > 0 > >Here's my correspondent's list of suggestions > > @ > >1.  Get a major application such as SAP running on VMS again. > > : > >2.  Get Oracle to treat VMS with a little more respect. > > ) > >3.  Market outside the installed base.  > > + > >4.  Invest in the Educational Programme.  > > C > >5.  Reintroduce lower-cost hardware and offer a low-cost turnkey 
 web server > >    platform. > >  > B > I agree with the analysis. I would however bundle as many of the/ > layered products as possible into the system.  > F > This would produce packages such as "VMS for developers" which would, > have all the development products bundled. > 2 > "VMS for Enterprise" a cheap VMS cluster option. > C > What I am saying is that given that most users are migrating from  VMS,) > why not make it easy to migrate to VMS.  > B > The development costs of the layered products have been recoverd years F > ago. Why keep the DEC model for selling layered products, who buys a C * > compiler at the price HP sell it on VMS. > C > The real problem is that VMS is still run by people who live in a  DEC D > world. The time has come to move out of the 1970's and think about% > packaging VMS for the next century.     E Try www.sun.com/software/sunone/starterkit   for an example of a well / run program similar to what has been suggested.   E Some of the products have only 90-day licenses, but most products are B 1-year right-to-develop licenses. The CD/DVD set is shipped 4x per; year and costs $49 for a 1-year subscription (DVD version).   D But also recognize that Sun ships a lot of true value-added productsE that HP doesn't have in its software parade - integration servers and C the like.....which Digital/Compaq/HP have for the most part decided E don't belong in a hardware vendor's portfolio, hence the sell-offs to  outfits like BEA, et. al.   @ HP would be well advised to 'partner' with BEA, Oracle, IBM, and@ others, to get VMS versions of products on a DVD to include in a similar programme.   ------------------------------  % Date: Mon, 07 Jul 2003 20:03:49 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> : Subject: Re: Assign 9.1 GB =?iso-8859-1?Q?HD=B4s?= to 8 GB' Message-ID: <3F0A1875.93A1D8DD@fsi.net>    Hoff Hoffman wrote:  > [snip]H >   You do realize that one of the particular problems involved here wasJ >   resolved over a decade ago, with V6.0?  (Isn't it time to upgrade to aE >   more recent OpenVMS VAX release?  Please?  ...V7.3 is current...)   H Applications issues frequently make this impossible, due to loss of ISVsA and/or loss of ISV support for OpenVMS. The best way to get these G customers onto newer VMS is to probably to raise these issues with your  management.    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Mon, 07 Jul 2003 21:13:51 +0200 $ From: Michael Unger <unger@decus.de>: Subject: Re: Assign 9.1 GB =?ISO-8859-1?Q?HD=B4s_to_8_GB?=5 Message-ID: <bech66$3ggsh$1@ID-152801.news.dfncis.de>   ' On 07-Jul-2003 20:35, Doc.Cypher wrote:   ? > On 5 Jul 2003, contracer11@uol.com.br (Shiva MahaDeva) wrote: L >>In my job Im using a MicroVAX 3100-98 (Personal Workstation), VMS V5.5-2.L >> In this machine I have ~60 GB in SCSI HDs (a tower with 7 9.1 GB HDs). < >> Looking behind this tower , I see BA35X-VA storage model.J >> I want assign all 9.1 GB Hds from 9.1 to 8 GB, to avoit constant crashK >> in this system. Id like to get a procedure to make this modifications,    >> in details. Can you help me ? >> Thanks in advance...  > P > Should you choose to peruse the appropriate documentation you may discover theP > rather shocking fact that your selected version of VMS will only support disks > up to 8Gb in size. >  > [...]  > J > Calculate 87.9121% of this value - the difference between 9.1Gb and 8Gb. >  > [...]   K Did you consider the different data densities on inner and outer cylinders?    Michael   	 PS: SCNR!    --  B OpenVMS: See <URL: http://www.pointsecure.com/pdf/Defconwhite.pdf>@ Please do *not* send "Security Patch Notifications" or "SecurityA Updates"; this system isn't running a Micro$oft operating system. = And don't annoy me <mailto:postmaster@[127.0.0.1]> please ;-)    ------------------------------   Date: 7 Jul 2003 11:57:20 -0700 % From: sellis@legato.com (Shaun Ellis) . Subject: Re: Backup Software for VMS and Linux; Message-ID: <1faa9425.0307071057.5534bf@posting.google.com>    "CHANGE username to westes" <DELETE_westes@uscsw.com> wrote in message news:<QuQHa.52919$Io.5007556@newsread2.prod.itd.earthlink.net>...J > I was told today that VMS cannot use an LTO-1 tape drive because of someL > limitation around writing odd-byte writes on LTO.   What options are there  > for using LTO-1 drives on VMS? > H > What backup applications implement good agents for both VMS and Linux?M > Could we run the LTO-1 drives on a Linux backup server, and then backup and F > restore data for VMS through a VMS agent that works with that backup > application? >   > What other options do we have?  E Legato NetWorker supports both Linux and OpenVMS. There is the issue, F you mentioned, about using LTO-1 drives on OpenVMS. Networker actuallyC uses even bytes when it writes to tape, so should work. However, we E have never tested it as it is not supported by OpenVMS itself. If you * would like to know more, please contact me   Shaun Ellis  OpenVMS product manager  Legato Systems Inc sellis@legato.com    ------------------------------  # Date: Mon, 07 Jul 2003 18:35:30 GMT # From: hoff@hp.nospam (Hoff Hoffman) % Subject: Re: Basics of attaching a PC 2 Message-ID: <S3jOa.4039$9H7.1716@news.cpqcorp.net>  W In article <3F09A059.F83B6750@yahoo.com>, Rodney Carter <rtcarter401@yahoo.com> writes: F :I am a lowly Microsoft/Novell admin who has been thrown into the deepG :end. I don't mind doing my homework but I need some basic help. Please 7 :don't say RTFM because I can find no FM in this shop.    C   Um, RTFM?  :-)  Seriously.  :-)  You do have access to a website  A   with HTML-format manuals for OpenVMS and DECwindows.  You have  ?   access to most of (all of?) the Fine Manuals, in other words.   B   You will want to acquire at least CD copies of the manuals, too.F   It's difficult to run most any non-trivial software platform withoutC   having local copies of the relevent documentation and/or manuals.    And you waste more time.  2 :..The openVMS version is 6.2 and the transport isE :TCP/IP and use Humingbird Exceed.... We have bought upgrade PCs and  C :I have tried to mirror the setups of the old systems. There are no F :new user accounts--just the old ones. Logging on with an old account, :I get the following error:  : , :%DECW-E-CANT_OPEN_DISPL, Can't open display/ :INTERnet ACP AUXS failure Status=%DECW-E-NOMSG   >   SHOW DISPLAY will display the target display for DECwindows.:   This should be the X Windows Server; the Exceed IP host.  E :I can telnet to the server and login OK with an existing account but @ :when the application tries to access a drawing I get the error: : ) :Error while initializing graphics device   D   Use ICO (RUN DECW$EXAMPLES:ICO.EXE) for troubleshooting X Windows C   displays, as ICO provides some fairly reasonable X Windows error     messages.   D :From my research, I understand that I need to define the new PCs in4 :Security. But I haven't figured out just how, yet.   A   The setting is usually one in the X Windows server (Exceed), as A   the security is set up in the X Windows server.  Look around in A   the session manager menus, or whatever Exceed calls this stuff.   H :Can someone layout the basic steps I need to take to install a PC node L :into the VAX system? Just general--I'll work hard at finding the specifics. :Something like:& :1. Define the PC in the VMS security.  6   Nope.  Configure at the X Windows server; in Exceed.  % :2. Define the VMS servers in Exceed.   B   Nope.  Usually SET DISPLAY on OpenVMS, either directly or in theC   LOGIN.COM or SYLOGIN.COM command procedure, or in a site-specific ,   or application-specific command procedure.  B   X Windows applications are clients of the server, and the serverB   (usually) runs on the appliance or host controlling and local to   the X Windows display itself.   " :3. Assign new PC to user account.  F   Eh?  Usually, the reverse is what you need and want -- the X WindowsF   Server (Exceed) needs to map to the remote hosts and username(s) andC   transport(s) that will be establishing incoming X Windows display    sessions.   D   Sometimes the most difficult part of this can be matching the caseB   or username syntax, and the X Windows server log files can be an@   invaluable resource for troubleshooting failed connections andC   security errors.  And again, these are in the Exceed environment.   & :4. Whatever the next step would be...  F   The DECwindows manuals are on the documentation website.  Start withE   the OpenVMS FAQ (qv: sig) and the documentation -- particularly the E   DECwindows documentation, and then the system management and user's F   guides within the OpenVMS manual set -- at the OpenVMS documentation
   website.  F :I want to learn and I want this project so I've got to get some solidI :steps to show my boss progress. Can anyone help me or am I really out of  :my league with this?     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: Mon, 07 Jul 2003 20:48:54 +0200 9 From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com> % Subject: Re: Basics of attaching a PC ' Message-ID: <3F09C096.48E1DADB@aaa.com>    Hoff Hoffman wrote:  > D >   You will want to acquire at least CD copies of the manuals, too.H >   It's difficult to run most any non-trivial software platform withoutE >   having local copies of the relevent documentation and/or manuals.     A What's wrong with copying the manuals from the web ? Are they any   different from the "CD copies" ?  	 Jan-Erik.    ------------------------------  % Date: Mon, 07 Jul 2003 19:27:48 -0400 + From: Rodney Carter <rtcarter401@yahoo.com> % Subject: Re: Basics of attaching a PC ) Message-ID: <3F0A01F4.A11A0CAF@yahoo.com>   Y Thank you for pointing me to the web for docs. I found them and will be reading all nite. X Now, the ones I found at the DEC/HP site are for version 7.2/7.3. In my Microsoft world,Y exact identical functions are given different names as they change versions each year--it Y is crazy because you have to learn the same thing 5 different ways. Is this going to be a T consideration in that I am using open VMS version 6.2? Am I wasting time reading 7.3 manuals for a 6.2 OS?   W Sorry about the RTFM remark but I had seen several answers to questions in a forum with [ knowledgeable people being arrogant I'm tired and stressed and just don't need that type of V response. I need  help (from gracious people such as I have found here) and not people[ pointing out the fact that I don't know what I'm doing. If I can find the answers myself, I * will but if I ask a question, I need help.   Hoff Hoffman wrote:   Y > In article <3F09A059.F83B6750@yahoo.com>, Rodney Carter <rtcarter401@yahoo.com> writes: H > :I am a lowly Microsoft/Novell admin who has been thrown into the deepI > :end. I don't mind doing my homework but I need some basic help. Please 8 > :don't say RTFM because I can find no FM in this shop. > D >   Um, RTFM?  :-)  Seriously.  :-)  You do have access to a websiteB >   with HTML-format manuals for OpenVMS and DECwindows.  You haveA >   access to most of (all of?) the Fine Manuals, in other words.  > D >   You will want to acquire at least CD copies of the manuals, too.H >   It's difficult to run most any non-trivial software platform withoutE >   having local copies of the relevent documentation and/or manuals.  >   And you waste more time. > 4 > :..The openVMS version is 6.2 and the transport isF > :TCP/IP and use Humingbird Exceed.... We have bought upgrade PCs andE > :I have tried to mirror the setups of the old systems. There are no H > :new user accounts--just the old ones. Logging on with an old account, > :I get the following error:  > : . > :%DECW-E-CANT_OPEN_DISPL, Can't open display1 > :INTERnet ACP AUXS failure Status=%DECW-E-NOMSG  > @ >   SHOW DISPLAY will display the target display for DECwindows.< >   This should be the X Windows Server; the Exceed IP host. > G > :I can telnet to the server and login OK with an existing account but B > :when the application tries to access a drawing I get the error: > : + > :Error while initializing graphics device  > E >   Use ICO (RUN DECW$EXAMPLES:ICO.EXE) for troubleshooting X Windows D >   displays, as ICO provides some fairly reasonable X Windows error
 >   messages.  > F > :From my research, I understand that I need to define the new PCs in5 > :Security. But I haven't figured out just how, yet.  > C >   The setting is usually one in the X Windows server (Exceed), as C >   the security is set up in the X Windows server.  Look around in C >   the session manager menus, or whatever Exceed calls this stuff.  > I > :Can someone layout the basic steps I need to take to install a PC node N > :into the VAX system? Just general--I'll work hard at finding the specifics. > :Something like:( > :1. Define the PC in the VMS security. > 8 >   Nope.  Configure at the X Windows server; in Exceed. > ' > :2. Define the VMS servers in Exceed.  > D >   Nope.  Usually SET DISPLAY on OpenVMS, either directly or in theE >   LOGIN.COM or SYLOGIN.COM command procedure, or in a site-specific . >   or application-specific command procedure. > D >   X Windows applications are clients of the server, and the serverD >   (usually) runs on the appliance or host controlling and local to! >   the X Windows display itself.  > $ > :3. Assign new PC to user account. > H >   Eh?  Usually, the reverse is what you need and want -- the X WindowsH >   Server (Exceed) needs to map to the remote hosts and username(s) andE >   transport(s) that will be establishing incoming X Windows display 
 >   sessions.  > F >   Sometimes the most difficult part of this can be matching the caseD >   or username syntax, and the X Windows server log files can be anB >   invaluable resource for troubleshooting failed connections andE >   security errors.  And again, these are in the Exceed environment.  > ( > :4. Whatever the next step would be... > H >   The DECwindows manuals are on the documentation website.  Start withG >   the OpenVMS FAQ (qv: sig) and the documentation -- particularly the G >   DECwindows documentation, and then the system management and user's H >   guides within the OpenVMS manual set -- at the OpenVMS documentation >   website. > H > :I want to learn and I want this project so I've got to get some solidK > :steps to show my boss progress. Can anyone help me or am I really out of  > :my league with this?  > 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: Mon, 07 Jul 2003 20:49:42 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> % Subject: Re: Basics of attaching a PC ' Message-ID: <3F0A2336.26BE7678@fsi.net>    Jan-Erik Sderholm wrote:  >  > Hoff Hoffman wrote:  > > F > >   You will want to acquire at least CD copies of the manuals, too.J > >   It's difficult to run most any non-trivial software platform withoutG > >   having local copies of the relevent documentation and/or manuals.  > C > What's wrong with copying the manuals from the web ? Are they any " > different from the "CD copies" ?  A The CDs use a proprietary format known as BookReader. Not bad for H OpenVMS+DECwindows, but the PC/Windows version of BNU is a beta and doesH not print. Also, I've had problems with some of the .PDFs being corrupt.    The old ways are still the best:   - Text + - PS + - BKR +  - PDF   G That way, you're bound to find SOMEthing that will get you the info you  need.   , Personally, though, I still prefer hardcopy.   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------   Date: 7 Jul 2003 12:43:40 -0700 % From: sellis@legato.com (Shaun Ellis) D Subject: beta software of new Legato NetWorker Client & Storage Node= Message-ID: <1faa9425.0307071143.74e71018@posting.google.com>    Hello,  @ in August, we will start the Beta of the new version of Legato's+ Client & Storage Node for OpenVMS on Alpha.   F We have  aunique offering in the market as the only fully endorsed, by@ OpenVMS engineering, 3rd party backup solution. We were first to@ market with tape drive and library sharing in a heterogeneous FCF environment. With this new version, we will be keeping up the pressureD on our competition, it will be a pre-requisite for soon to be coming Oracle and Oracle RDB module.   = If you are interested in being in the beta, please contact me 	 directly.    regards    Shaun Ellis  OpenVMS Product manager  Legato Systems Inc sellis@legato.com    ------------------------------  % Date: Mon, 07 Jul 2003 16:57:41 -0400 * From: BoylesA <alan.boyles@mindspring.com> Subject: Cannot see disk drives / Message-ID: <vgjo0t9t09up8e@corp.supernews.com>    I have an AlphaStation 500/500 with  1 internal drive ( currently the system drive ) a KZPCM-DA with a BA356-KD with 6 RZ!CB (4.3 
 gig ) drives.  The BA356 has a narrow SE (-MH).  From the SRM prompt I can see all the drives in the cabinet but when VMS boots it see none of the  external drives..   + I have run IO AUTOCONFIG and still nothing.   
 Any ideas?   Alan   ------------------------------  % Date: Mon, 07 Jul 2003 17:06:50 -0400 . From: Alan Boyles <alan.boyles@mindspring.com># Subject: Re: Cannot see disk drives / Message-ID: <vgjoi286oekfa0@corp.supernews.com>    BoylesA wrote:H > I have an AlphaStation 500/500 with  1 internal drive ( currently the K > system drive ) a KZPCM-DA with a BA356-KD with 6 RZ!CB (4.3 gig ) drives. J > The BA356 has a narrow SE (-MH).  From the SRM prompt I can see all the G > drives in the cabinet but when VMS boots it see none of the external  
 > drives.. > - > I have run IO AUTOCONFIG and still nothing.  >  > Any ideas? >  > Alan >  The BA35X-MG is the single bus shelf, and right now I have the cable going to the left 50 ping connector and the right connector is 7 empty.  Do you need termination on the right connector?    ------------------------------  # Date: Mon, 07 Jul 2003 23:04:53 GMT 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)" Subject: Re: DHCP startup problems3 Message-ID: <p0nOa.10734$1F6.199674@news.chello.at>   j In article <slrnbgjbr9.2fne.steve@h68-144-58-171.cg.shawcable.net>, Steve Young <sdyoung@well.com> writes:J >  I'm having a weird problem with DHCP on my VMS 7.3-1 box running CompaqH >TCP/IP.  The problem is that when TCP/IP starts during boot time, it isL >unable to get a DHCP lease and starts the machine up without an IP address.G >However, if I log in immediately afterwards and deassign SE0 and then e= >re-create the interface with /DHCP/PRIMARY, it works fine.     C I found so far three annoyances with TCPIP V5.3 (ECO2) DHCP client.p  H 1) What you found. You won't get a lease, if you start DHCP client afterL DECnet (or LAT, which has DECnet comptible addresses as default). I "solved"L it, by starting TCPIP in SYSMAN (CONFIG phase) _before_ DECnet gets started.F I have so far no explaination why you can get a lease at your 2nd try. It never worked here.o  G 2) You get a wrong subnet mask. You don't get the subnet mask which theIK DHCP server offers, you get the default subnet mask of the offered address.d  9 	eg. 10.1.2.3	offered, with 255.255.255.0, gets 255.0.0.0m    I 3) You get only one DNS path set. If you want to use more than one searcheM paths in your DNS client, you have to set them per hand (eg. in SYSTARTUP_VMSw$ with TCPIP SET NAME/SYSTEM/PATH=xxx)  K Maybe some time, TCPIP closes up with TCPware, but until then, I know whiche is still the better IP stack...    --   Peter "EPLAN" LANGSTOEGERc% Network and OpenVMS system specialiste E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------   Date: 7 Jul 2003 12:39:14 -0700L) From: ejohnson@factset.com (Eric Johnson) $ Subject: Good code profilers on VMS?= Message-ID: <ef79676b.0307071139.475257da@posting.google.com>u  B Am I the only one to find DEC PCA to be largely useless?  Its onlyE capable of handling one image at a time *AND* to top it off, it can't D even deal with any images that happen to be loaded dynamically.  ItsE rather tragic that their code performance tool can't deal with two ofaA OpenVMS's best features - (1) multiple images and (2) dynamically  loaded ones too.  C So, if you're like me, and you find that tool useless, the questionP' is, what do *YOU* do to deal with that?P  @ We've explored DCPI to some extent, but it seems more suited forE analyzing everything on a box.  That's certainly useful and good, butb" its not quite what I'm hoping for.  C I'd really love to have a way to collect a ton of PC samples from aaC process and dump those out to a file.  My idea of a ton is a coupleCA thousand a second.  Once I have the PC samples, I can do some SDAoD magic and get the layout of the images in memory.  From there, I canC stitch it all back to source code given that I have all of the .map  and .lis files.i  ? Once I have all of that, I can produce reports that can given aeE developer a more informed viewpoint about where their code is chewingtB up all its cpu cycles, or at least, where it appears their program went while it was executing.  F Are there *good* 3rd party tools for this?  What do others do inhouse?  
 -Eric Johnsone   ------------------------------   Date: 7 Jul 2003 14:53:26 -0500-- From: Kilgallen@SpamCop.net (Larry Kilgallen)i( Subject: Re: Good code profilers on VMS?3 Message-ID: <SzHfe$6jtGBN@eisner.encompasserve.org>-  i In article <ef79676b.0307071139.475257da@posting.google.com>, ejohnson@factset.com (Eric Johnson) writes:sD > Am I the only one to find DEC PCA to be largely useless?  Its onlyG > capable of handling one image at a time *AND* to top it off, it can't F > even deal with any images that happen to be loaded dynamically.  ItsG > rather tragic that their code performance tool can't deal with two of C > OpenVMS's best features - (1) multiple images and (2) dynamicallyD > loaded ones too. > 8 > So, if you're like me, and you find that tool useless,   I don't find it useless, but...B  6 > the question is, what do *YOU* do to deal with that?  C When measuring performance I create a slightly different version ofp- my program that does not use dynamic linking.o  1 I have not seen the problem with dynamic linking.i  ? I _have_ seen the problem that PCA cannot deal with DECthreads.w  E Certainly HP needs to put a _lot_ more emphasis on bringing PCA up tov date.    ------------------------------  # Date: Mon, 07 Jul 2003 18:44:36 GMTr& From: Rick Jones <foo@bar.baz.invalid>R Subject: Re: HP Webcast this morning on Next-Generation Intel Itanium 2 processors2 Message-ID: <ocjOa.4041$PF7.2765@news.cpqcorp.net>  ) Bill Todd <billtodd@metrocast.net> wrote:t5 > "Rick Jones" <foo@bar.baz.invalid> wrote in message - > news:YE_Ma.3909$Yn3.865@news.cpqcorp.net...r > ... E >> I'd probably hold that 10% was not noise but would agree that very H >> small single digits would be. 3% would probably be my limit; the lineG >> being somehwat fuzzy.  We'll just have to see if AMD comes up with aeE >> 2.0 GHz Opteron system with a SPECweb99_SSL result that closes theu >> gap.a  D > A leak pounced upon by The Inquirer suggests that it may appear in. > early August - just too late for that lunch.  B OK, we'll modify things a bit - if it does appear in early August,A with SPECweb99_SSL scores that evaporate the lead, I'll buy you ad) snack and a soda instead of lunch then :)d  c rick -- iG oxymoron n, Hummer H2 with California Save Our Coasts and Oceans platesdF these opinions are mine, all mine; HP might not want them anyway... :)A feel free to post, OR email to raj in cup.hp.com  but NOT BOTH...    ------------------------------  % Date: Mon, 07 Jul 2003 20:15:13 -0500o1 From: "David J. Dachtera" <djesys.nospam@fsi.net> , Subject: Re: HP World (was HP to drop hpux?)' Message-ID: <3F0A1B21.42A733EC@fsi.net>-   "Main, Kerry" wrote: > A > > > I suspect Linux will simply continue to provide a low-cost,e2 > > > lower-capability entry point for Unix users. > >0= > > ...as well as eventually achieving greater acceptance and = > > greater penetration into the commercial computing market.  > >A > > -- > > David J. Dachterao > > dba DJE SystemsX > > http://www.djesys.com/ > >3, > > Unofficial Affordable OpenVMS Home Page:# > > http://www.djesys.com/vms/soho/r > >n >  > David, > G > Fwiw, my personal $.02 is that there is a lot of hype and speculationlJ > about how big vendors like HP/IBM can add value to an OS like Linux, butH > the reality is that if you do not own the kernel, then it is extremely? > difficult to ship any add-on product like clustering that mayl$ > potentially impact data integrity.  F Well, sort of. Even VMS Engineering makes statements about how certainH pieces are validated. Case in point: the tri-architecture cluster thread! currently going on in this forum.   G If code *MUST* go poking around in the kernel (save that as a dead lasteD resort, IMHO), then state very clearly that it was validated against> only certain kernel code, and will only be "supported" in such environment(s).    --   David J. Dachterar dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Mon, 07 Jul 2003 20:18:31 -0500t1 From: "David J. Dachtera" <djesys.nospam@fsi.net>t4 Subject: Re: HP World: Why Alpha's Omega Makes Sense& Message-ID: <3F0A1BE7.9ACA459@fsi.net>   Keith Parris wrote:v > E > There was an interesting article in the July 2003 issue of HP WorldVA > Magazine, page 34. The article is available online via the linko5 > http://hpworldnews.c.tclk.net/maabedKaaY0bda4e8YPe/. > E > (Note: The online copy of the article is accessible only by Interexw= > members, but a free level of membership is available -- see  > http://www.interex.org.)  F Any rebuttal available from frustrated / confused / enraged customers?   -- / David J. Dachtera- dba DJE Systems- http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/R   ------------------------------  % Date: Tue, 08 Jul 2003 06:43:12 +0200e From: Dirk Munk <munk@home.nl>4 Subject: Re: HP World: Why Alpha's Omega Makes Sense2 Message-ID: <bediko$jsd$1@news3.tilbu1.nb.home.nl>   David J. Dachtera wrote: > Keith Parris wrote:c > E >>There was an interesting article in the July 2003 issue of HP WorldUA >>Magazine, page 34. The article is available online via the linkn5 >>http://hpworldnews.c.tclk.net/maabedKaaY0bda4e8YPe/  >>E >>(Note: The online copy of the article is accessible only by Interex = >>members, but a free level of membership is available -- seek >>http://www.interex.org.) >  > H > Any rebuttal available from frustrated / confused / enraged customers? > M If someone would be so kind to publish an extract of this article here ? Not e3 everyone is a member of the US part of Interex ....-   ------------------------------  % Date: Mon, 07 Jul 2003 22:05:35 -0700c& From: Greg Cagle <gregc@gregcagle.com>4 Subject: Re: HP World: Why Alpha's Omega Makes Sense/ Message-ID: <vgkk92p9keq708@corp.supernews.com>e   Dirk Munk wrote:  K > If someone would be so kind to publish an extract of this article here ? c9 > Not everyone is a member of the US part of Interex ....a   Here you go:   ----------------   Why Alpha's Omega Makes Sense71 Farewell to the "Fastest Processor on the Planet"A by Terry Shannon  I In my last HP World Magazine article ("Dj vu All Over Again," April HP rH World Magazine, page 33), I discussed in detail prior migrations on DEC F and Compaq platforms. A close read of the article rendered it evident H that I was a bona-fide Alpha adherent, which in fact was the case. Less G than two months before the decision to terminate the Alpha program was  F made public on June 25, 2001, I was on the road in the United States, 8 Europe and the Pacific Rim touting the virtues of Alpha.  H But there are two sides to every coin, and such is the case with Alpha. H Since its introduction in November 2002, the "architecture for the next I 25 years" has begun to lose some of its initially compelling performance SF differentiation. In fact, former DEC CEO Bob Palmer's "we're twice as I fast as any competitive processor" lost credence relatively early in the i game.t  B While the infamous 023.eqntott benchmark mistake rendered Intel's G Pentium Pro about 16 percent slower than Intel originally claimed, the iF fact that a low-cost, high-volume commodity processor could present a H serious challenge to Alpha's supremacy-at least with respect to integer C performance-was the cause of considerable concern at DEC and was a pB contributing factor in DEC's decision to sell its misbegotten and C ill-fated FAB-6 facility-not to mention a license to produce Alpha -H processors and gain carte blanche to Alpha intellectual property-to the  aforementioned Intel Corp.   Great ExpectationsE The original Alpha road map proved to be exceedingly optimistic. The kI second-generation EV5 processor materialized as advertised, albeit a few  G months late, but the third-generation EV6 processor-thought by some to iH be Alpha's chance to regain supremacy-was at least 18 months late. (The A delay was due to the implementation of out-of-order execution, a aH technology designed to dramatically increase processor performance, but H one which proved to be daunting to implement. Rival vendor IBM ran into F similar problems and release date delays with its very capable POWER4  architecture.)  " Megahertz Don't Matter-or Do They?E When EV6 eventually materialized, it ran at a clock speed of 100 MHz "H less than the then-incumbent EV56 processor. In fact, during the course H of about a year, Intel boosted processor frequency by 500 MHz while DEC A managed to eke out an improvement of perhaps 100 MHz. Senior DEC cF processor architects who previously disregarded Intel as a competitor B had a sudden change of opinion and concluded that Intel's process I technology was emerging as a daunting-if not insurmountable-challenge to a Alpha's long-term future.t  F Adding to Alpha's problems was a 21-month delay in the release of the H AlphaServer GS320 "Wildfire" enterprise server, whose extremely complex D infrastructure ensured that the enterprise server never lived up to F performance or reliability expectations. Meanwhile, the vaunted Intel F marketing machine did a superlative job convincing customers that MHz : did matter and that Intel was the Master of the Megahertz.   Terminate Alpha? Never!tF As did rival vendors such as IBM and HP, DEC microprocessor engineers C concentrated on microprocessor architecture and implementation and bB resolved many of the issues surrounding the fourth-generation EV7 D processor. EV7 consisted of an EV68 core with 1.75 MB of seven-way, I associative, on-chip cache, as well as a new "glueless SMP" interconnect  D that enabled Alpha hardware developers to dispense with much of the ) complexity that hobbled the GS320 series./  H EV7 booted in July 2001, soon after the Itanium Transition decision was H announced, and began shipping in systems in 2002. Thus far, EV7 has met 0 or exceeded Compaq/HP and customer expectations.  1 EV7 Birth Approaches, While EV8 Begins to GestateaE While EV7 was approaching "first silicon" status at DEC's Palo Alto, iG Calif., facility in 2000, a separate group of engineers in Shrewsbury, hI Mass., were hard at work on the next-generation EV8 processor. While IBM nI opted for "chip multiprocessing" (CMP), or the incorporation of multiple PB CPUs on a single die, DEC, which had investigated CMP through its > "Piranha" advanced research project, decided that symmetrical F multi-threading, or SMT, would provide performance equivalent to that G offered by CMP technology, but with a mere 10 percent increase in chip rJ size or "real estate" vis--vis the 100 percent increase required for CMP.  I Given the expense and complexity of CMP real estate (a single wafer that  F can yield 100 SMT chips might yield 55 CMP processors, and wafers are F not cheap!), the technology was duly relegated to EV9 or future Alpha  processors.u  / Great Expectations to Late Summer Night's DreamtE In fall 2000, a team of senior Alpha architects and system designers rD held a summit to determine the future of Alpha. According to a lead E architect who chooses to remain nameless, it was discovered that SMT eE technology was far easier to implement in PowerPoint than in working   silicon.  D Not only would a quantum leap in compiler technology be required to F fully exploit SMT-allowing a single EV8 processor to deliver at least I 3.4 times the performance of an EV7 processor-it was determined that EV8 rE would have to be delivered on time, on spec and completely bug free. nG Attempting to satisfy these requirements would necessitate incremental pA human and financial resources, which Compaq's bean counters were h unwilling to supply.   Bad News for Alpha AdvocatesH Concurrently, the trio of Alpha advocates were invited to sign ironclad I PIDs with Intel in order to get a glimpse of Intel's Itanium plans. Even oH though the much-maligned Merced had yet to materialize, Intel disclosed G an extended five-year-plus road map that convinced the Alpha team that -H Itanium would surpass Alpha in every metric before EV8 saw the light of F day. (At least one of the Intel briefers was a former PRISM and Alpha ? developer, whose several years at Intel proved instrumental in -A convincing the Alpha team that Itanium and its EPIC architecture d  ultimately would trounce Alpha.)  H Armed with this information-much of which became available to attendees H at the recent Intel Developers Forum in San Jose, Calif.-the Alpha team G drafted a white paper articulating the respective futures of Alpha and oG Itanium. Given Intel's market share, superior process technology (more oH than 90 percent wafer yields are the order of the day at Intel) and the F tight relationship between fab technology and processor capabilities, I the paper concluded that it would be in Compaq's best interests to begin nI a transition from Alpha to Itanium within the next year. Contrary to the  H claims of some, the research and the resulting decision were arrived at H by the best and the brightest on the Alpha team, not by Compaq's senior  management team or financiers.   The Die Is CastuH Compaq CEO Michael Capellas decided in March 2001 to abdicate Alpha and G adopt Itanium over an estimated three- to four-year period. The public $H announcement of the decision was withheld until June 25, 2001, close to # the end of Compaq's fiscal quarter.m  G A variety of factors went into the decision and the timing thereof: it sH was financially beneficial to Compaq to take the Alpha write-off during G a lackluster quarter, Intel gained a heavy-weight Itanium partner, and BG Compaq immediately began to realize financial benefits by transferring ,G Alpha architects and the GEM compiler team to Intel. No less important tF is the fact that, due to low and declining production volumes, Compaq = was losing more or less $800 on every Alpha chip it produced.i   The Right ChoiceF Not unexpectedly, Alpha advocates were stunned-if not outraged-by the G June 25 announcement. But hindsight reveals that Compaq made the right aF choice. The economics were obvious, and the Compaq/Intel relationship 1 was vastly improved by the removal of the "other  G architecture"-Alpha-from the playing field. Intel and Compaq were able  D to forge a much tighter HPTC (high performance technical computing) H alliance, an alliance that will benefit both partners since they have a ' common interest in this market segment.p  I Compaq's system production costs would decline dramatically as Alpha was -E replaced by the high-volume, lower-cost Itanium architecture. Compaq  C already had planned to base future Himalaya NSK systems on Itanium eG (which, as a result, incorporates the requisite lock-stepping hardware e required by NonStop systems).e  E The decision to base future NSK systems on Alpha was a by-product of 7H Compaq's acquisition of DEC and the Alpha franchise. Compaq already had I demonstrated the "Bravo" variant of Tru64 Unix on a Merced emulator, and -I it's safe to assume that the NSK team will find it relatively easy to go MH "back to the [Itanium] future." As noted in my previous column, OpenVMS H has successfully booted on Itanium, and an initial software developer's G kit should be available late this year. Linux-a growing contributor to tI the HP revenue stream-performs well on Itanium. And of equal importance, NI the Itanium adoption simplified the merger of Compaq and Hewlett-Packard.e  E Finally, Itanium performance increased dramatically from the initial eF Itanium I to the incumbent Itanium II "McKinley" processor. A similar E performance increase is expected this summer when Intel releases the nB Itanium "Madison" processor, and annual performance increases are * projected for the remainder of the decade.  C Being enhanced with compiler technology, glueless SMP and "special  F sauce" derived from 15 years of Alpha development can only accelerate I the performance increases of future Itanium processors, both at the high 9F end and, ultimately, on the desktop and even laptops. ISV adoption of D Itanium already exceeds the ISV adoption rate enjoyed by Alpha, and H hardly a day passes that another ISV doesn't announce its allegiance to  Itanium.  F HP customers face an architectural migration, but migrations are part E and parcel of the IT world. The good news is that HP-like most other nD vendors-is betting on the right horse. Far better to go the Itanium I route (and perhaps eat some crow with a side dish of humble pie) than to eG relentlessly rely on an aging microprocessor such as PA-RISC or Alpha. tI Only one major system vendor continues to eschew Itanium, and the future uG of that vendor is dubious at best. So, at the end of the day, and with vG the crow and apple pie digested, I submit that history will prove that  E Compaq made the correct-albeit difficult-decision to phase out Alpha.   ( An Architecture for the Next 25 Years...B At the time of its introduction, Alpha ran only a handful of UNIX B applications, and VMS support wasn't scheduled to materialize for D another six months. It would be another six months before the Alpha D version of VMS achieved parity with VAX/VMS and before a reasonable G number of Alpha/VMS applications became available. Nevertheless, Alpha  H was the first microprocessor to run at speeds of 100 MHz or greater and 3 to be dubbed "the fastest processor on the planet."i  G Unfortunately for VMS users, however, Alpha imposed an immediate sales l@ freeze on VAX systems, which had undergone a phenomenal 13-fold H performance increase in just 39 months. The freeze kept the massive VAX B user base in limbo for nearly a year, while the Alpha design team E devoted nearly one-third of an estimated $10 billion budget to Alpha  F research, development and implementation cost to address the dramatic A differences in the VAX and Alpha architectures. VAX and VMS were aH produced in a collaborative effort that literally wed the VMS operating I system to the VAX architecture, thus ensuring maximum compatibility. The iE Alpha architecture, on the other hand, had no "knowledge" of the VMS c operating system.C  D To enable native VAX/VMS applications to run on Alpha hardware, the D Alpha engineering team developed a binary code translation facility F dubbed "VEST" (VAX to Alpha Executable Translator), which allowed the C majority of VAX/VMS binary applications to run on Alpha platforms, dI albeit at significantly reduced speeds. Developers of custom or in-house sH VAX/VMS applications were forced to rewrite and recompile their code to G run in native mode on Alpha systems. Needless to say, the VAX-to-Alpha eC migration was a painful experience for many customers and a golden eA opportunity for IBM and other vendors to migrate disgruntled VAX t# customers to competitive platforms.i    Stymied by Marketing MalfeasanceG Despite its modern design and projected architectural longevity, Alpha eG proved to be a costly effort that contributed to DEC's downfall. While rH Alpha retained its performance advantage over rival RISC architectures, D the architecture was briefly outpaced by IBM and Hewlett-Packard on  several occasions.  F The mid-1990s debut of Intel's Pentium Pro, which implemented many of E the design features that gave Alpha its performance advantage, was a  I watershed moment in the architecture's history. Not only did DEC fail to uH aggressively market and promote Alpha and to attract a critical mass of I ISV applications, the far less expensive Intel IA32 architecture-and its lD portfolio of tens of thousands of applications-caused customers and I prospects to have second thoughts about Alpha adoption. Internal DEC and eH Compaq numbers indicate that the firms produced slightly in excess of 1 F million Alpha microprocessors, which served as the engines of perhaps 2 500,000 Alpha systems over the course of a decade.  G Significantly, Alpha sales began to slump almost immediately after the  E consummation of Compaq's purchase of DEC. The Compaq sales force was  D intimately familiar with the Intel product set but had virtually no F knowledge of Alpha; hence, Compaq more often than not would recommend / Intel solutions to prospective Alpha customers.o   Itanium RisingH Jointly announced by Intel and Hewlett-Packard on June 3, 1994, Itanium G (a.k.a. P7 or Merced) was Intel's first foray into the world of 64-bit oI computing. Rather than relying on RISC technology, Intel and HP opted to m@ implement their new microprocessor in EPIC (Explicitly Parallel G Instruction Computing) technology, a derivative of the VLIW (Very Long 4A Instruction Word) technology developed by Brandford, Conn.-based :H MultiFlow Computer, Inc., one of the numerous failed computer companies  of the 1980s and early 1990s.e  F Originally slated to debut in 1997, Itanium proved easier to announce G than to develop and deliver. Even though many of the MultiFlow migrs ,@ ended up at Hewlett-Packard, both the EPIC architecture and the A compilers necessary to fully exploit a VLIW-based machine proved sA extremely difficult to implement and coordinate with one another.n  E Not unexpectedly, the Itanium delivery schedule slipped, slipped and uC slipped again, much to the glee of rival vendors and the trade and rF business press. Finally, Itanium I was "platform-launched" on May 29, H 2001, ending an extended development cycle and a chorus of "It'll never > fly, Orville" assertions among the press and industry pundits.  B The performance of the new microprocessor left a great deal to be C desired, however, and the architecture was not widely adopted. The  F majority of the several thousand Itanium 1 machines were relegated to 6 seed system status in development labs and among ISVs.  
 Alpha's Omega H As Itanium slipped, Compaq Computer began to have second thoughts about F Alpha. Two iterations of the architecture experienced delays of their = own, and the senior developers of the much-vaunted Alpha EV8  < microprocessor, originally due in 2004, began investigating F alternatives. Given declining sales, increasing R&D costs, budget and A resource constraints and a dependency on IBM Microelectronics to oE actually fabricate the Alpha chips, the future of Alpha was becoming s
 murky indeed.u  C Faced with a net loss of around $800 on every Alpha microprocessor eD produced, along with the daunting issues associated with EV8, three H high-level Alpha designers and corporate executives decided in November F 2000 to have a heart-to-heart-and highly confidential-discussion with H their Intel counterparts. It soon became evident that the Alpha program H would devolve into a full-blown catastrophe if EV8 was not delivered on @ time and proved unable to perform as advertised. It was further I discovered that the addition of symmetrical multi-threading to EV8 would WD reduce the processor's target clock speed by 1 GHz, and incremental > resources were not available to address this and other issues.  C The final nail in the Alpha coffin was a glimpse at Intel's highly  I confidential, long-term Itanium road map. Based on the road map, Itanium wG would surpass Alpha in virtually every dimension before 2005 and prior OG to the introduction of a next-generation enterprise server designed to f; run multiple processor architectures and operating systems.   I The Gang of Three-who all hailed from the Alpha development group in New BH England-issued a report to Compaq's CTO and senior management: the most H viable solution to Compaq's growing Alpha problem was a strategic shift F that would consolidate all of the firm's 54-bit enterprise servers on F Itanium at the conclusion of the Alpha EV7 life cycle. The report was I issued in November 2000, and by May 2001 Compaq CEO Michael Capellas had n; concluded that the firm would make a major-and undoubtedly lI disruptive-strategic announcement prior to the end of the second quarter.    Spilling the BeansB This earth-shattering information was closely held until mid-June H 2001-fewer than a dozen people at Compaq were privy to the information. F About a week later, at a heavily attended June 25 press conference in I New York City, Capellas and Intel CEO Craig Barrett announced that Alpha iI would reach its production Omega with the 2004 introduction of the Alpha hC 21364 EV79 part. Compaq subsequently would base all its enterprise  H systems on forthcoming members of Intel's Itanium microprocessor lineup.  B Under the terms of the non-exclusive agreement between Compaq and H Intel-an agreement that represented an undeniable coup for Intel-Compaq B would consolidate its entire 64-bit platform and OS lineup on the G Itanium architecture beginning in 2004. New Alpha systems and upgrades rE would be rolled out through 2004, and all incumbent systems would be a supported through 2013.l  G Compaq immediately began porting its NSK, Tru64 Unix and VMS operating eG systems to Itanium while transferring key Alpha processor and compiler .C technology, tools and engineering resources to Intel. Both vendors tA agreed to pursue a joint engineering program focused on advanced r5 parallelism for high-performance technical computing.t  * Architectural Aftershocks: Minimal at BestF While the initial customer reaction to the announcement was less than D overwhelmingly positive, large customers who buy mass quantities of G Compaq enterprise iron reacted favorably. For example, health care ASP  F Cerner Corp., which has bet its business on OpenVMS, was upbeat about  the transition.t  E Oracle Corp., which has licensed key elements of Compaq's TruCluster eH software for Oracle 9i Real Application Clusters-and thus has more than F a passing interest in the continued success of Tru64 Unix-thought the @ deal was good news. Oracle will continue to rely on Tru64-based I AlphaServers as the development platform for future iterations of Oracle dA 9i RAC. In fact, Oracle CEO Larry Ellison was an early and vocal c= proponent of the Compaq-Intel Itanium Processor Family (IPF) k architectural partnership.  < Compaq's most demanding customers-those in the Himalaya NSK A community-seemed satisfied with the new architectural game plan. aE Enterprise e-payment software purveyor ACI Worldwide opined that the tB deal was great news for the firm's Himalaya customers. "Continued G investment by Compaq in the Himalaya product line and a clear movement DG to industry-standard technology only strengthens the value proposition aH for our solutions in the mission-critical e-payments environment," said G ACI President Mark Vipond. Large Himalaya end users, including Brown & oH Company Securities Corp. and the London Stock Exchange, also weighed in 0 with day-one Alpha-to-IPF strategy endorsements.  I Statements of ISV allegiance and customer confidence aside, Compaq got a rF strong endorsement for its Alpha-to-IPF strategy from Stockholm-based F telco giant Ericsson. As previously reported in SKHPC ("Shannon Knows D HPC" newsletter), Ericsson and Compaq in October 2000 signed a deal H though which Ericsson would base its next-generation AXE telco switches H on Tru64-based Alpha technology. (Ericsson and other vendors heretofore = have based their switches on custom processors and software.),  E Asked about the impact of the Alpha-IPF transition, Ericsson CTO Jan NG Uddenfeldt said that Compaq's decision to switch to IPF would have few tG consequences, financial or otherwise, for the Swedish firm. "Of course nF we have an agreement with Compaq to handle the gradual move over from F Alpha chips to Itanium. When it comes to money, I don't think it will ! have an impact," said Uddenfeldt.t  G Ericsson's endorsement is a boon to Compaq, because the Swedish firm's eD strategy hinges on the success of the next-generation Alpha chip, a I smooth transition from Alpha to IPF and the continued viability of Tru64 sI Unix. Ericsson's willingness to stay the course reflects high confidence ,G in Compaq's ability to execute the transition to Itanium. The decision  H to merge Tru64 Unix and HP-UX into a "Consolidated Enterprise UNIX" has H created few problems, even though the consolidation will be a difficult  and extended exercise.   Uh-Oh, ANOTHER MigrationH The Alpha-to-Itanium migration should pose few problems for NSK or UNIX G customers. Compaq's original game plan was to migrate NonStop Himalaya iH systems from MIPS processors to Itanium technology, and Itanium already I contains the requisite lock-stepping hardware. For NSK users, therefore, e5 the consolidation is a "back to the future" strategy.aE As for HP-UX, it has booted on Itanium, and several years ago Compaq gG booted Tru64 Unix on an Itanium emulator under the now-defunct "Bravo"   program.   What About OpenVMS?rI HP's OpenVMS team faced a somewhat different task, but HP's efforts will hF be a boon to Alpha/OpenVMS customers who migrate to Itanium/ OpenVMS. D During the VAX-to-Alpha transition a decade ago, OpenVMS developers A re-coded a number of OS components, including device drivers and IA executive modules, in C, thus rendering a subsequent port a less  5 daunting exercise for developers and customers alike.a  I HP announced on Feb. 4 that, following a successful initial boot on Jan.  E 31, its OpenVMS operating system is now running on the Intel Itanium -B architecture. This feat represents a significant milestone toward F completing the port of OpenVMS to Itanium. HP expects that an initial G port will be available to early developers in June, followed by a more tG complete port by the end of the year and a full production version for  ( VMS customers in the first half of 2004.  A "We are committed to enable our customers to move to the Itanium .C architecture on their own schedule and to make the transition from aF OpenVMS on AlphaServer systems to the Intel Itanium-based platform as = seamless and as risk-free as possible," said Mark Gorham, HP  F vice-president of OpenVMS Systems. "We are using a single source-code I base so that we can release future versions of OpenVMS on both platforms  F simultaneously. Paramount in this transition will be that the OpenVMS I enterprise fundamentals of scalability, data integrity, availability and l@ reliability will remain at the forefront of all our development  efforts," he said.  I "We are very excited about the boot and are moving ahead aggressively to rB meet our road map targets," an exuberant Gorham added. "I am very C confident that VMS on the Itanium systems will offer our customers tF significant performance and price-performance advantages. Many of the H key contributors to the VAX-to-Alpha port of OpenVMS are working on the F current port. This previous experience has helped greatly in creating F the strategy and in helping us to meet the road map schedule," Gorham G said. (SKHPC believes that HP remains on track to deliver two SDKs and  9 early adopter releases of VMS 8.n for Itanium this year.)L  F Another key has been the knowledge and experience of the HP engineers H involved with Itanium right from the get-go in 1994. "The pre-merger HP @ engineering teams have made the porting process easier than was E anticipated," said Gorham, who noted the early and close buy-in from o Itanium-adept HP developers.  , The OpenVMS Porting Process: Fast If Not FunH According to Gorham, the Alpha-to-Itanium port was much easier than the G VAX-to-Alpha port. In porting from VAX to Alpha, nearly all components aE of the VMS OS underwent significant change. In porting from Alpha to IG Itanium, the code changes involve a few concentrated areas such as the aB boot path, the transition of Alpha PALcode functions into OpenVMS H itself, and software interrupts. The vast majority of the OS transition I can be summarized as "recompile, re-link and go" from a common code base.d  C This means a far less expensive project and also a shorter time to gE market, both for HP in bringing VMS to Itanium and for customers and IF ISVs in bringing their apps to Itanium. In addition, extensive use of G Linux on Itanium was used in the early porting process. Before the VMS sI development tools were in place, new code to support Itanium was written D? and debugged on Linux and then later moved into the VMS kernel.,  E As for the estimated 18-month duration of the porting process, Clair aC Grant, Base Operating System technical architect for HP, said, "We sE intentionally lengthened the boot schedule in order to move to using i< industry standards such as the Intel Calling Standard (with H OpenVMS-specific extensions) and the ELF/DWARF object, image and symbol E formats. This will allow much easier porting of many apps as well as e; development and analysis tools between VMS and other OSes."2  I Finally, OpenVMS is being ported to the now-proven Itanium architecture, oF not the nascent Alpha platform. All of this bodes well for HP and its 1 hundreds of thousands of loyal OpenVMS customers.i     -- .
 Greg Cagle gregc at gregcagle dot com   ------------------------------  % Date: Mon, 07 Jul 2003 19:48:48 +0100 / From: Tim ffrench-Lynch <nospam@baesystems.com>A Subject: KVM switchesa. Message-ID: <3F09C090.51C9DD71@baesystems.com>  F Does anyone know of any affordable KVM switches that will work with anH AlphaStation 255? It's the old business of the Alpha using scanset 3 and the PC something else.  D It looks like what is needed is a KVM with a keyboard controller forE each computer connection which then talks to the keyboard in whateveraG way it prefers. It looks like a Raritran switch would work, but they're , a bit pricey for a 92 AlphaStation at home.   Timn   ------------------------------  % Date: Mon, 07 Jul 2003 15:30:43 -0400g. From: Mike Bartman <omni@foolie.omniphile.com> Subject: Re: KVM switchese8 Message-ID: <v5ijgvo832ed9j3ileff7mjsh62kih5g7n@4ax.com>  5 On Mon, 07 Jul 2003 19:48:48 +0100, Tim ffrench-Lyncha <nospam@baesystems.com> wrote:  G >Does anyone know of any affordable KVM switches that will work with anrI >AlphaStation 255? It's the old business of the Alpha using scanset 3 and$ >the PC something else.>  > I've got an AlphaStation 200 using a Belkin F1D074.  Handles 4E computers, and worked fine with a couple of NT boxes when I was usingqE it to handle all three inputs (I've since found a proper keyboard foroE the Alpha, so that part isn't on the Belkin anymore...I like the feely@ of a proper keyboard better, and the keys are where the softwareC expects them.  I still use the Belkin to switch the mouse and videow though.)  C I'm running my NT screen at 1280x1024, and the video is fine.  I'veeF set it much higher than that just to see if it works, and it does, but9 1280x1024 is as high as my eyes can take on a 19" screen.a  D The keyboard I'm using is programmable, and the fact that the BelkinF uses keyboard codes to switch inputs allowed me to program a couple of? extra blank function keys on the keyboard to select between theaA inputs...I just hit a button and the screen jumps to the system IeE want.  Takes a second to lock the new video signal, but only a secondO8 or two.  The keyboard is otherwise a normal PC keyboard.  C I don't know if a 200 and a 255 differ enough to matter, but that'sf, what I've got here, and it's working for me.   -- Mikee@ ----------------------------------------------------------------=   To reply via e-mail, remove the 'foolie.' from the address.o%   I'm getting sick of all the SPAM...t@ ----------------------------------------------------------------   ------------------------------  % Date: Mon, 07 Jul 2003 17:08:03 -0400 * From: "Stanley F. Quayle" <stan@stanq.com> Subject: Re: KVM switches / Message-ID: <3F09A8F3.18494.107B9919@localhost>f  0 On 7 Jul 2003 at 19:48, Tim ffrench-Lynch wrote:  H > Does anyone know of any affordable KVM switches that will work with anJ > AlphaStation 255? It's the old business of the Alpha using scanset 3 and > the PC something else. > 9 > It looks like a Raritran switch would work, but they'reh0 > a bit pricey for a =A392 AlphaStation at home.  B Actually, Raritran boxes turn up frequently on eBay for less than < $100, including cables.  The one I bought works perfectly...  
 --Stan Quaylei Quayle Consulting Inc.  
 ----------C Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-1671 1 8572 North Spring Ct. NW, Pickerington, OH  43147v= Preferred address:  stan@stanq.com       http://www.stanq.comt   ------------------------------   Date: 7 Jul 2003 20:51:22 GMTl3 From: gartmann@immunbio.mpg.de (Christoph Gartmann)a Subject: Re: KVM switchesy0 Message-ID: <becmga$1ta$1@n.ruf.uni-freiburg.de>  ` In article <3F09C090.51C9DD71@baesystems.com>, Tim ffrench-Lynch <nospam@baesystems.com> writes:G >Does anyone know of any affordable KVM switches that will work with anpI >AlphaStation 255? It's the old business of the Alpha using scanset 3 and- >the PC something else..  I The UltraView series of Rose Electronics does a good job (www.rosel.com).u  E >It looks like what is needed is a KVM with a keyboard controller for F >each computer connection which then talks to the keyboard in whateverH >way it prefers. It looks like a Raritran switch would work, but they're- >a bit pricey for a 92 AlphaStation at home.i  M The Rose switches aren't cheap either :-( Perhaps you find an older ServeView  model on ebay?   Regards,    Christoph Gartmann    -- .E  Max-Planck-Institut fuer      Phone   : +49-761-5108-464   Fax: -452r  ImmunbiologieA  Postfach 1169                 Internet: gartmann@immunbio.mpg.de-  D-79011  Freiburg, Germany 9                http://www.immunbio.mpg.de/home/menue.htmlc   ------------------------------  % Date: Mon, 07 Jul 2003 16:28:33 -0700e, From: Ken Fairfield <My.Full.Name@intel.com> Subject: Re: KVM switchesc) Message-ID: <3F0A0221.EE8EB8A3@intel.com>    Tim ffrench-Lynch wrote: > H > Does anyone know of any affordable KVM switches that will work with anJ > AlphaStation 255? It's the old business of the Alpha using scanset 3 and > the PC something else. > F > It looks like what is needed is a KVM with a keyboard controller forG > each computer connection which then talks to the keyboard in whatevereI > way it prefers. It looks like a Raritran switch would work, but they'reo. > a bit pricey for a 92 AlphaStation at home.  D Interesting you should bring this topic up since I'm about to be in ? a similar situation (thanks to Dave Turner at Islandco.Com :-).c  D I Googled for old c.o.v discussions, and I spent a good deal of timeC on the web researching (to the extent I could) KVMs.  The good newsmA is that both Rose and Raritan have models that officially supportaD OpenVMS.  That bad news is they are VERY expensive: the ones offeredC are in the US$680 range. :-(  The not-quite-so-bad news is that thelE CompuSwitch series KVMs are about half the price of the MasterConsolenE series and officially support OpenVMS, but US$360 is still a LOT for u a home system.  C It's precisely what you said, "the old business of the Alpha using rB scanset 3 and the PC something else", that is at issue.  I haven'tA been able to get a technical person to tell me whether either the C Rose or the Raritan can manage the switch between a live VMS/Alpha iA and a live PC.  If it can't, one might as well use a cheap, e.g.,n@ Belkin switch, and be resigned to rebooting the Alpha (or PC) in@ order to use the keyboard (it would still save space at home and? allow sharing the k, v, and m...just not simultaneously...sigh.e  0 Good luck and let us know what you come up with!   	-Ken	 --6 I don't speak for Intel, Intel doesn't speak for me...  
 Ken Fairfield " D1C Automation VMS System Support , kenneth[dot]h[dot]fairfield[at]intel[dot]com   ------------------------------  % Date: Tue, 08 Jul 2003 00:17:00 -04000* From: "Stanley F. Quayle" <stan@stanq.com> Subject: Re: KVM switchesr. Message-ID: <3F0A0D7C.9509.12045020@localhost>  , On 7 Jul 2003 at 16:28, Ken Fairfield wrote:M > I haven't been able to get a technical person to tell me whether either therE > Rose or the Raritan can manage the switch between a live VMS/Alpha t > and a live PC.  D I have a Raritan switch working between Windows 2000, Red Hat Linux B 7.3 on Intel, OpenVMS 7.3-1 Alpha, and OpenVMS 7.3 VAX.  It works F perfectly.  There are no problems with the keyboard, unlike other KVM  switches I've tried.  D And, as I said in an earlier posting, I was able to get a Raritan 4- port for about $100 on eBay.  
 --Stan QuayleV Quayle Consulting Inc.  
 ----------C Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-1671-1 8572 North Spring Ct. NW, Pickerington, OH  43147u= Preferred address:  stan@stanq.com       http://www.stanq.come   ------------------------------  % Date: Mon, 07 Jul 2003 10:47:33 -0700a" From: Eric Bruno <eric@ebruno.org>+ Subject: Re: OpenVMS 7.3.1 Install problem.i) Message-ID: <3F09B235.6070808@ebruno.org>a  & --------------0007010406070708000601029 Content-Type: text/plain; charset=us-ascii; format=floweda Content-Transfer-Encoding: 7bita       David J. Dachtera wrote:   >Eric Bruno wrote: >  s >a >>[snip]H >>Someone was generous enough to put an iso image of  7.2-1 up for me to >>download.pJ >>I downloaded the image, burnt the CD installed 7.2-1 with out a problem. >>     >> >ME >Interesting that it worked at all. AFAIK, VMS's loaders can't handle ; >ISO-9660 media. I suspect it was an ODS image, not an ISO.d >    >eB It was ISO as far as the buring software was concerned  (the file # extension) it was image of  the CD.r4 The actual format I'll have to take your word on it.   >    >t    & --------------000701040607070800060102) Content-Type: text/html; charset=us-asciip Content-Transfer-Encoding: 7bit   ? <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">y <html> <head>I   <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">n   <title></title>  </head>  <body> <br> <br> David J. Dachtera wrote:<br>< <blockquote type="cite" cite="mid3F08747C.D73DA36D@fsi.net">    <pre wrap="">Eric Bruno wrote:   </pre>   <blockquote type="cite">     <pre wrap="">[snip]mF Someone was generous enough to put an iso image of  7.2-1 up for me to	 download. H I downloaded the image, burnt the CD installed 7.2-1 with out a problem.
     </pre>   </blockquote>l   <pre wrap=""><!---->D Interesting that it worked at all. AFAIK, VMS's loaders can't handle: ISO-9660 media. I suspect it was an ODS image, not an ISO.   </pre>
 </blockquote>0Q It was ISO as far as the buring software was concerned &nbsp;(the file extension)n! it was image of &nbsp;the CD.<br> 8 The actual format I'll have to take your word on it.<br>< <blockquote type="cite" cite="mid3F08747C.D73DA36D@fsi.net">   <pre wrap="">f   </pre>
 </blockquote>E <br> </body>i </html>   ( --------------000701040607070800060102--   ------------------------------   Date: 7 Jul 2003 14:21:03 -0500 - From: Kilgallen@SpamCop.net (Larry Kilgallen)t+ Subject: Re: OpenVMS 7.3.1 Install problem.u3 Message-ID: <IDM53ySni6ui@eisner.encompasserve.org>i  N In article <3F09B235.6070808@ebruno.org>, Eric Bruno <eric@ebruno.org> writes: > ( > --------------000701040607070800060102; > Content-Type: text/plain; charset=us-ascii; format=flowedt! > Content-Transfer-Encoding: 7bit  >  >  >   @ The quoted material above was all extraneous and there were 1394C more bytes at the end which I have excised for the sake of brevity.a  B Please do not post MIME in newsgroups or mailing lists that do notA specifically permit it.  If the documentation that came with your D software is unclear regarding the method for avoiding MIME creation, contact your software vendor.e   > David J. Dachtera wrote: >  >>Eric Bruno wrote:e >>   >>	 >>>[snip]iI >>>Someone was generous enough to put an iso image of  7.2-1 up for me toi >>>download.K >>>I downloaded the image, burnt the CD installed 7.2-1 with out a problem.i >>>    n >>>i >>F >>Interesting that it worked at all. AFAIK, VMS's loaders can't handle< >>ISO-9660 media. I suspect it was an ODS image, not an ISO. >>   >>D > It was ISO as far as the buring software was concerned  (the file % > extension) it was image of  the CD.v  C Software just burning a CDROM does not check whether it is ISO9660, D Files11, Macintosh HFS or anything else.  What you had was an image, but not an ISO9660 image.    ------------------------------   Date: 7 Jul 2003 17:28 CDT' From: carl@gerg.tamu.edu (Carl Perkins)h+ Subject: Re: OpenVMS 7.3.1 Install problem.I, Message-ID: <7JUL200317283416@gerg.tamu.edu>  5 "David J. Dachtera" <djesys.nospam@fsi.net> writes...e }Eric Bruno wrote: }>  = }> Well I think I found the line that is hanging the install.iD }> If reboot the system after the install locks up and boot the diskB }> it does an autogen complains about some missing files but runs. }> wL }> If I try to manually install products they complain VMS is not installed.L }> Digging around the forums/newsgroups using information from various posts5 }> I determined that a PCSI database was not present.t }> n }> So I did the following: }> a+ }>  $DIRECTORY/DATE/SIZE SYS$SYSTEM:*.PCSI*e }> s }>  This showed show NO files. }> t3 }>  $DIRECTORY/DATE/SIZE SYS$COMMON:[000000]*.PCSI*v }> u! }>  This showed these four files:I }> s6 }>     DEC-AXPVMS-OPENVMS-V0703-1-5.PCSI$DESCRIPTION;1. }>     DEC-AXPVMS-OPENVMS-V0703-1-5.PCSI$TLB;12 }>     DEC-AXPVMS-VMS-V0703-1-2.PCSI$DESCRIPTION;1* }>     DEC-AXPVMS-VMS-V0703-1-2.PCSI$TLB;1 }  }Try:c } 8 }$ RENAME SYS$COMMON:[000000]*.PCSI* SYS$COMMON:[SYSEXE] } I }That should put the files into the correct path and get you going again.i } A }FWIW, installing VMS on "unsupported" hardware tends to be a bityI }challenging. Not sure why - most of this should be "don't care" stuff toa
 }such things.f }  }--  }David J. Dachtera  + I wouldn't count on that being a good idea.2  * Have you checked your system to see what a  ! $ DIR SYS$SYSROOT:[000000]*.PCSI*i  
 gives you?  ? You'll probably find 4 files much like the above ones, possiblyc> differing in VMS version number. I certainly have 4 such filesD there on my fully functional system (it came that was via FIS, too).  : Note that these are .PCSI$DESCRIPTION and .PCSI$TLB files,= not .PCSI$DATABASE files. (There should be two files matchingtA the file names of the above files but with names ending in -1 andb. of type .PCSI$DATABASE located in SYS$SYSTEM.)  < I have no idea if moving them would ever cause a problem wit anything, but it might.o   --- Carl   ------------------------------  % Date: Mon, 07 Jul 2003 19:56:36 -0500i1 From: "David J. Dachtera" <djesys.nospam@fsi.net>a+ Subject: Re: OpenVMS 7.3.1 Install problem.e' Message-ID: <3F0A16C4.76FA5D93@fsi.net>h   > Eric Bruno wrote:t >  > David J. Dachtera wrote: >  > > Eric Bruno wrote:l > >t > >i > >> [snip]yE > >> Someone was generous enough to put an iso image of  7.2-1 up forp
 > >> me to > >> download.D > >> I downloaded the image, burnt the CD installed 7.2-1 with out a
 > >> problem.  > >> > >>H > > Interesting that it worked at all. AFAIK, VMS's loaders can't handle> > > ISO-9660 media. I suspect it was an ODS image, not an ISO. > >d > >iC > It was ISO as far as the buring software was concerned  (the files% > extension) it was image of  the CD.d  B My guess is you're using a piece of software that burns the image,E regardless of its content. AFAIK, Gear and Nero will do this, as willu others (cdrecord?).m  6 > The actual format I'll have to take your word on it.  H Don't take my word for it - ask OpenVMS Engineering if VMS can be booted from an ISO-9660 format medium.t   -- v David J. Dachtera  dba DJE Systemse http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/t   ------------------------------   Date: 7 Jul 2003 12:03:05 -0700u1 From: susan_skonetski@hotmail.com (Sue Skonetski)rE Subject: OpenVMS Technical Update Day in Chicago - Only 10 days away! = Message-ID: <857e9e41.0307071103.3f99c32a@posting.google.com>m  D It is only 10 calendar days until the one and only OpenVMS TechnicalE Update Day to be held in North America occurs. The event is scheduledsC for Thursday, July 17. All the details for this FREE event (and them# registration page) can be found at:   f, http://www.hp.com/large/events/2003/openvms/  e  eC Currently we have 61 individuals registered (out of a planned eventr? size of 150). The time is now to insure that the entire OpenVMSnD customer base in the Great Lakes area is aware of this event and has an opportunity to register.   eD Please note that HP employees and HP Business Partner employees needB to register as well. Lunch will be provided to those who register. Walk-ins will be on their own.  o0 Thanks for your support. Let's get the word out!  o
 Best Regards,n   ------------------------------  # Date: Tue, 08 Jul 2003 00:12:31 GMTt# From: "John Smith" <a@nonymous.com>aI Subject: Re: OpenVMS Technical Update Day in Chicago - Only 10 days away!dH Message-ID: <P%nOa.80968$x4o.57023@news04.bloor.is.net.cable.rogers.com>  > "Sue Skonetski" <susan_skonetski@hotmail.com> wrote in message7 news:857e9e41.0307071103.3f99c32a@posting.google.com...tF > It is only 10 calendar days until the one and only OpenVMS Technical= > Update Day to be held in North America occurs. The event isu	 scheduledtE > for Thursday, July 17. All the details for this FREE event (and theh% > registration page) can be found at:  >t. > http://www.hp.com/large/events/2003/openvms/ >- >eE > Currently we have 61 individuals registered (out of a planned eventeA > size of 150). The time is now to insure that the entire OpenVMSaF > customer base in the Great Lakes area is aware of this event and has > an opportunity to register.  >wF > Please note that HP employees and HP Business Partner employees needD > to register as well. Lunch will be provided to those who register.  > Walk-ins will be on their own. >,2 > Thanks for your support. Let's get the word out! >  > Best Regards,a    ? Is this the date of the annual Chicago summer heat wave??   :-)o   ------------------------------  % Date: Mon, 07 Jul 2003 20:45:44 -0500e1 From: "David J. Dachtera" <djesys.nospam@fsi.net>3I Subject: Re: OpenVMS Technical Update Day in Chicago - Only 10 days away! ' Message-ID: <3F0A2248.58C07C1E@fsi.net>r   John Smith wrote:i > @ > "Sue Skonetski" <susan_skonetski@hotmail.com> wrote in message9 > news:857e9e41.0307071103.3f99c32a@posting.google.com...oH > > It is only 10 calendar days until the one and only OpenVMS Technical? > > Update Day to be held in North America occurs. The event isl > scheduled G > > for Thursday, July 17. All the details for this FREE event (and theb' > > registration page) can be found at:o > >h0 > > http://www.hp.com/large/events/2003/openvms/ > >C > >oG > > Currently we have 61 individuals registered (out of a planned event C > > size of 150). The time is now to insure that the entire OpenVMSdH > > customer base in the Great Lakes area is aware of this event and has > > an opportunity to register.o > >oH > > Please note that HP employees and HP Business Partner employees needF > > to register as well. Lunch will be provided to those who register." > > Walk-ins will be on their own. > >o4 > > Thanks for your support. Let's get the word out! > >i > > Best Regards,u > A > Is this the date of the annual Chicago summer heat wave??   :-)   E August is usually our hottest, mostly mid-August, but it varies. ThisfE year's been kinda weird: cool right up until the Solstice, then quiten warm - and stormy!   -- o David J. Dachterar dba DJE Systemsl http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/i   ------------------------------  * Date: Mon, 7 Jul 2003 21:06:01 +0000 (UTC)! From: "Code Monkey" <me@here.com> % Subject: Porting VAX Object Librariesm/ Message-ID: <becnbo$lro$1@titan.btinternet.com>u  @ Have an application that I would like to port to Alpha from VAX.  H Whilst I have the C code for the application it has to link against some3 object libraries which I don't have the source for.a  G I have read about VEST DECmigrate e.t.c but this seems to translate VAXd .EXE's to Alpha .EXE's??  I Is there are way to translate these VAX object libraries so I can link tot them on the alpha platform ??n   Many Thanks,   C.Mq   ------------------------------  # Date: Mon, 07 Jul 2003 21:43:01 GMTo# From: hoff@hp.nospam (Hoff Hoffman) ) Subject: Re: Porting VAX Object Librariesy2 Message-ID: <FPlOa.4057$DS7.2391@news.cpqcorp.net>  S In article <becnbo$lro$1@titan.btinternet.com>, "Code Monkey" <me@here.com> writes:rA :Have an application that I would like to port to Alpha from VAX.h :eI :Whilst I have the C code for the application it has to link against some 4 :object libraries which I don't have the source for. :pH :I have read about VEST DECmigrate e.t.c but this seems to translate VAX :.EXE's to Alpha .EXE's??e : J :Is there are way to translate these VAX object libraries so I can link to :them on the alpha platform ??     Nope.g  G   These objects need to be linked into a shareable image (if possible),eD   and that image can then be translated via DECmigrate.  Or find theF   source code.  Or rewrite the source code in the libraries.  Or use aC   VAX hardware emulator, and continue operating as if the code and t<   libraries involved were operating native OpenVMS VAX code.  E   There is no object-code translation tool available, in other words.a    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqeN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comn   ------------------------------  % Date: Mon, 07 Jul 2003 17:24:04 -0400e* From: "Stanley F. Quayle" <stan@stanq.com>) Subject: Re: Porting VAX Object Librariesm/ Message-ID: <3F09ACB4.21379.108A3F91@localhost>d  J > Whilst I have the C code for the application it has to link against some5 > object libraries which I don't have the source for.t >nK > Is there are way to translate these VAX object libraries so I can link toc > them on the alpha platform ??    You have two approaches:  / 1. Build the image on VAX, then use DECmigrate.s> 2. Build the object libraries into a shareable image, then use;    DECmigrate on it.  You'll have to compile your C modulest    with the /TIE option.  C Neither of these is a great choice.  Make sure you have the latest t> version of DECmigrate, which is now called "OpenVMS Migration > Software for VAX to Alpha".  Check the HP OpenVMS site for it.  ? Alternatively, you could run CHARON-VAX on your Alpha [Another e/ Shameless Plug(tm) from a CHARON-VAX reseller.]n  
 --Stan Quayley Quayle Consulting Inc.  
 ----------C Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-1671a1 8572 North Spring Ct. NW, Pickerington, OH  43147d= Preferred address:  stan@stanq.com       http://www.stanq.comi   ------------------------------  $ Date: Mon, 7 Jul 2003 23:34:18 +0100" From: "Rolona" <nospam@nospam.com> Subject: RDB V7.1c9 Message-ID: <yBmOa.22$Pg7.5@news-binary.blueyonder.co.uk>e  D Anyone know where I can download a copy of RDB 7.1 for Vax? I have a6 legitimate license but I've lost the distribution kit.   ------------------------------  # Date: Tue, 08 Jul 2003 01:02:17 GMTy/ From: "Jeff Goodwin" <jgoodwin@maine.rrr-r.com>t Subject: Re: RDB V7.1l7 Message-ID: <tKoOa.25002$ma.22942@twister.nyroc.rr.com>a  I My recollection is that V7.0 was the last version of RDB for VAX and thatf V7.1 is Alpha only.n   -Jeffh      - "Rolona" <nospam@nospam.com> wrote in message 3 news:yBmOa.22$Pg7.5@news-binary.blueyonder.co.uk...rF > Anyone know where I can download a copy of RDB 7.1 for Vax? I have a8 > legitimate license but I've lost the distribution kit. >e >o   ------------------------------   Date: 7 Jul 2003 13:07:03 -0500  From: briggs@encompasserve.org3 Subject: Re: Recursive copy between nodes using LATa3 Message-ID: <HZcqkEr$giCE@eisner.encompasserve.org>t  [ In article <CaiOa.1942$Fy1.91859@localhost>, "Jeff Barnes" <barnesjw@dfo-mpo.gc.ca> writes: L > OK, OK both are running DECnet (I can set host from one to the other).  MyM > problem is still the same and your solution, unlike most on this newsgroup, < > is not very helpful.  Why do you bother responding at all?  B Well, Bob's response got you to admit that you had DECnet running.  : Given that, one obvious possibility would be to use DECnet< to transfer a BACKUP save set from one machine to the other.  ? machine1$ backup source-disk:[source-dir...] machine2::save.seti  9 machine2$ backup save.set /save /select=[source-dir...] -  	target-disk:[target-dir...]  F If you don't have enough disk space to hold a save set, your available@ options diminish considerably.  Task to task DECnet could do the job, but it would be painful.t   	John Briggs   ------------------------------  # Date: Mon, 07 Jul 2003 18:41:29 GMTr# From: hoff@hp.nospam (Hoff Hoffman) 3 Subject: Re: Recursive copy between nodes using LATn2 Message-ID: <t9jOa.4040$9H7.1129@news.cpqcorp.net>  [ In article <5GhOa.1938$Fy1.91872@localhost>, "Jeff Barnes" <barnesjw@dfo-mpo.gc.ca> writes:   J :I am trying to copy a directory structure (a recursive copy) from one VMSM :node running LAT to another running LAT and TCP/IP.  Any assistance would be0
 :appreciated.i  J   LAT is not a storage transport -- you can certainly do this using KermitJ   or other such serial file transport over a LAT or serial connection, butK   folks seek to have IP or DECnet installed on both systems (a more typicaliF   network configuration), or the folks use media-based data transfers.  K   The usual (but not the only) tool for directory tree transfers is BACKUP.lJ   You can create a BACKUP saveset containing the desired files, and unpack   it on the remote host.  G   COPY/FTP and other DCL commands can also be used, though FTP and suchyH   will typically work with (only) one directory at a time -- you'll need1   to transfer the files one directory at a chunk.   H   If you can cluster, then you can use cluster disk servers and there isG   no need to explicitly transfer the files.  (NFS can provide somethingaE   rather similar, but without various of the features of clustering.)l    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: Mon, 07 Jul 2003 20:48:46 GMTd' From: Don Sykes <anonymous@pacbell.net>  Subject: Re: Rethinking  V.M.S+ Message-ID: <3F09DCB7.AC23377E@pacbell.net>w   Bob Koehler wrote: > W > In article <3F03225E.AC8837D3@pacbell.net>, Don Sykes <anonymous@pacbell.net> writes:  > >aG > > In spite of what others have said this deserves some consideration.pC > > While it's true it would not be practical in all situations, invL > > environments where there are not a lot of processes running, this may beI > > possible. As you stated, paging, swapping, related to disk I/O delay,wG > > could be eliminated, but so could all the cycles related to addresss+ > > translation, working sets and the like.i > I >   If you have enough RAM, there isn't any paging or swapping except forhE >   initially paging in the program when it starts.  So you don't getnD >   any advantage by taking out the capability (you still have to do- >   I/O somehow to get the program into RAM).s > H >   There aren't really cycles used up for address translation.  AddressJ >   translation happens in the pipeline parallel to instruction execution.I >   And you still have to track working sets and the like unless you want H >   my process to clobber data in your process' space.  Like MS-DOS.  No >   thanks.f >   C I don't know enough about cpu design to argue that. I was under theeA impression that EVERY virtual address had to be de-referenced andrG checked against page tables to see if the subject address's page was inwH memory or not. Then page it in to the appropriate location. If the AlphaH is doing all that in a parallel stream in hardware, I guess that part ofC the advantage would be minimized. Is the IA64 also doing all that? t  G As far as working sets and system page tables, IIRC they are maintainedtC to track the physical pages in memory assigned to a process. If alleE pages were already physical, you might still need to track which pagenE belonged to which process, but not which pages are physical (no one'ss, suggesting a return to an MS DOS style OS!).   --     Have VMS, Will Travel  Wire paladin, San Francisco    (paladinATalphaseDOTcom)   ------------------------------  * Date: Mon, 7 Jul 2003 16:27:35 -0700 (PDT). From: Fabio Cardoso <fabiopenvms@yahoo.com.br> Subject: Re: Rethinking  V.M.S@ Message-ID: <20030707232735.80058.qmail@web20210.mail.yahoo.com>  @ --- Bob Koehler <koehler@eisner.nospam.encompasserve.org> wrote:H > In article <20030702222109.54536.qmail@web20202.mail.yahoo.com>, Fabio, > Cardoso <fabiopenvms@yahoo.com.br> writes: > > * > > Memory --> Memory (PAGEnn:  / SWAPnn:) > & >    Now that's a waste of CPU cycles.  5 So there is no escape about the trinity (IO/Mem/CPU).o9 Let's wait for the Quantic Computer ! May be we can have e: OpenVMQS  (Virtual Memory Quantic System)running in these A kind of processors (or any name the scientists will give them) ! s   Regards    FC d   =====d ========================== Fbio dos Santos Cardoso OpenVMS System Manager Rio de Janeiro - Brazils fabiopenvms@yahoo.com.br ==========================  " __________________________________ Do you Yahoo!?+ SBC Yahoo! DSL - Now only $29.95 per month!t http://sbc.yahoo.com   ------------------------------  % Date: Mon, 07 Jul 2003 19:51:05 -0500g1 From: "David J. Dachtera" <djesys.nospam@fsi.net>  Subject: Re: Running VMS off CDt' Message-ID: <3F0A1579.6C922670@fsi.net>    John Smith wrote:  > [snip]H > Or watchdog process could monitor the <listener> and restart it should	 > it die.2  , What happens when the watchdog process dies?   -- v David J. Dachtera  dba DJE Systemsh http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/u   ------------------------------  # Date: Tue, 08 Jul 2003 03:53:55 GMTo# From: "John Smith" <a@nonymous.com>  Subject: Re: Running VMS off CDoH Message-ID: <nfrOa.94401$2ay.26712@news01.bloor.is.net.cable.rogers.com>  < "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message! news:3F0A1579.6C922670@fsi.net...n > John Smith wrote:i
 > > [snip]C > > Or watchdog process could monitor the <listener> and restart ito should > > it die.  >f. > What happens when the watchdog process dies?    - Damn...it's always the details, isn't it? ;-)t   ------------------------------  # Date: Tue, 08 Jul 2003 01:21:07 GMT  From: Rob.Buxton@wcc.govt.nzY Subject: Re: SNMP Commands (was Re: How do I monitor the CPU temperature in  an         Ey$ Message-ID: <3f0a1bbc.19584109@news>  7 On Sun, 06 Jul 2003 14:30:22 -0500, "David J. Dachtera"  <djesys.nospam@fsi.net> wrote:  
 >Verne wrote:e >>   >> >
 >> >[snip] >> > >>  G >> Don't know if this would help, but once I tried some SNMP stuff, and F >> from the on-line help (HELP MULTI SHOW /SNMP) and the Info-MultinetF >> mailing list archives at www.process.com, I came up with (perhaps a >> trivial example): >> e9 >>   mul show /snmp=11.22.33.44/mib=mib-2.43.10.2.1.4.1.1" >> r >> and >>  K >>   mul show /snmp=11.22.33.44/mib=enterprises.11.2.3.9.4.2.2.10.2.1.4.1.1, >> dG >> to see the lifetime page counter on a printer... at least this worksvG >> on newer HP JetDirect-attached printers, such as the LJ5, LJ4000 andr. >> the LJ2100 (would not work on a III or IV). >> hB >> Sorry, but I forget where I got the MIB variable 'id' from  :-( >n# >Yeah - discovered those ages ago. c > 3 >$ MULT SHOW/CONN/SNMP=x.x.x.x/MIB_VAR/OUT=filespec  >nD >...will list out all the MIB varaibles on the target node and their >current values. >o" >O.k. Let me try this another way: > G >I'm looking for a way - from a VMS system running Multinet - to send aaD >SNMP trap to a "foreign" system monitoring center (at work, they're >trying to use Cisco's CIC). >c >Does *THAT* help? >mG >I *DON'T* want to use the VMS system examine other systems, I want theaC >VMS system to be able to alert a "foreign" system when some bit ofuF >system administrivia goes awry (disk fills up, shadow-set member gets" >dropped, backup job fails, etc.). >c >Does *THAT* help? >I >--  >David J. Dachtera >dba DJE Systems >http://www.djesys.com/  > ) >Unofficial Affordable OpenVMS Home Page:t  >http://www.djesys.com/vms/soho/  6 Have you looked at the Insight Manager Agents for VMS?D They're only available for Alpha, but they will send SNMP Traps to a Server.v7 http://h71000.www7.hp.com/openvms/products/mgmt_agents/g  D Alas, a lot of what you seem to be after is beyond the current range of the IM Agents.    ------------------------------  % Date: Mon, 07 Jul 2003 20:08:49 -0500e1 From: "David J. Dachtera" <djesys.nospam@fsi.net>eY Subject: Re: SNMP Commands (was Re: How do I monitor the CPU temperature in an         ES ' Message-ID: <3F0A19A1.5E60E19A@fsi.net>   
 dooley wrote:t > b > "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message news:<3F0878CE.889AB110@fsi.net>... > > Verne wrote: > > >- > > > > 
 > > > >[snip]  > > > >1 > > > J > > > Don't know if this would help, but once I tried some SNMP stuff, andI > > > from the on-line help (HELP MULTI SHOW /SNMP) and the Info-Multinet I > > > mailing list archives at www.process.com, I came up with (perhaps at > > > trivial example):p > > >g< > > >   mul show /snmp=11.22.33.44/mib=mib-2.43.10.2.1.4.1.1 > > >d	 > > > andi > > >yN > > >   mul show /snmp=11.22.33.44/mib=enterprises.11.2.3.9.4.2.2.10.2.1.4.1.1 > > >eJ > > > to see the lifetime page counter on a printer... at least this worksJ > > > on newer HP JetDirect-attached printers, such as the LJ5, LJ4000 and1 > > > the LJ2100 (would not work on a III or IV).0 > > >rE > > > Sorry, but I forget where I got the MIB variable 'id' from  :-(e > >s% > > Yeah - discovered those ages ago.5 > >a6 > > $ MULT SHOW/CONN/SNMP=x.x.x.x/MIB_VAR/OUT=filespec > >cG > > ...will list out all the MIB varaibles on the target node and their  > > current values.l > > % > > O.k. Let me try this another way:l > >iJ > > I'm looking for a way - from a VMS system running Multinet - to send aG > > SNMP trap to a "foreign" system monitoring center (at work, they'rer > > trying to use Cisco's CIC).s > >  > > Does *THAT* help?d > >lJ > > I *DON'T* want to use the VMS system examine other systems, I want theF > > VMS system to be able to alert a "foreign" system when some bit ofI > > system administrivia goes awry (disk fills up, shadow-set member getse% > > dropped, backup job fails, etc.).  > >h > > Does *THAT* help? : > Your "foreign" system admin should be able to tell you -9 > the ip address of the system that will receive the trapb > the community name to usey > the port to use (162?)/ > the "enterprise" (compaq is 1.3.6.1.4.1.232.) = > the oid to use within 232 to indicate disk full or whateveru) > use this link to identify "enterprises" 4 > http://www.alvestrand.no/objectid/1.3.6.1.4.1.html > Phil  5 ...and the command to do that is ___________________.s (Fill in the blank.)  D (Actually, wasn't there a musical group: "Phil 'n' the The Blanks"?)   --   David J. Dachteraa dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/r   ------------------------------  % Date: Mon, 07 Jul 2003 20:12:05 -0500-1 From: "David J. Dachtera" <djesys.nospam@fsi.net>fY Subject: Re: SNMP Commands (was Re: How do I monitor the CPU temperature in an         ES-& Message-ID: <3F0A1A65.739D8E2@fsi.net>   "Bradford J. Hamilton" wrote:- > o > In article <1YgOa.82$1c6.15462519@newssvr14.news.prodigy.com>, "James Gessling" <jgessling@yahoo.com> writes:e > |-? > |"David J. Dachtera" <djesys.nospam@fsi.net> wrote in message8$ > |news:3F0878CE.889AB110@fsi.net... > |>K > |> I'm looking for a way - from a VMS system running Multinet - to send a5H > |> SNMP trap to a "foreign" system monitoring center (at work, they're  > |> trying to use Cisco's CIC). > |> > |cD > |Back when we could actually spend money on our VMS systems we got > |a product from these guys:x > |r* > |http://www.comtekservices.com/index.htm > |lM > |We've been using is for quite a while and as I remember, it's quite cheap.n > O > We used their services at my previous job, and I can recommend them.  Product4 > support was good and fast.  F Thanx for the testimonials. If BMC Patrol leaves any holes unfilled, I will certainly look into this.   -- - David J. Dachtera  dba DJE Systems2 http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/g   ------------------------------  % Date: Mon, 07 Jul 2003 20:11:00 -0500@1 From: "David J. Dachtera" <djesys.nospam@fsi.net>mY Subject: Re: SNMP Commands (was Re: How do I monitor the CPU temperature in an         ESA' Message-ID: <3F0A1A24.E0F86055@fsi.net>    briggs@encompasserve.org wrote:e > e > In article <1ca82fc6.0307061815.45694de9@posting.google.com>, dooleys@snowy.net.au (dooley) writes:od > > "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message news:<3F0878CE.889AB110@fsi.net>... > >> Verne wrote:a > >> > > >> > > > >> > >[snip] > >> > > > >> >K > >> > Don't know if this would help, but once I tried some SNMP stuff, and J > >> > from the on-line help (HELP MULTI SHOW /SNMP) and the Info-MultinetJ > >> > mailing list archives at www.process.com, I came up with (perhaps a > >> > trivial example): > >> >= > >> >   mul show /snmp=11.22.33.44/mib=mib-2.43.10.2.1.4.1.11 > >> >
 > >> > and > >> >O > >> >   mul show /snmp=11.22.33.44/mib=enterprises.11.2.3.9.4.2.2.10.2.1.4.1.1w > >> >K > >> > to see the lifetime page counter on a printer... at least this works K > >> > on newer HP JetDirect-attached printers, such as the LJ5, LJ4000 andc2 > >> > the LJ2100 (would not work on a III or IV). > >> >F > >> > Sorry, but I forget where I got the MIB variable 'id' from  :-( > >>& > >> Yeah - discovered those ages ago. > >>7 > >> $ MULT SHOW/CONN/SNMP=x.x.x.x/MIB_VAR/OUT=filespec3 > >>H > >> ...will list out all the MIB varaibles on the target node and their > >> current values. > >>& > >> O.k. Let me try this another way: > >>K > >> I'm looking for a way - from a VMS system running Multinet - to send a H > >> SNMP trap to a "foreign" system monitoring center (at work, they're  > >> trying to use Cisco's CIC). > >> > >> Does *THAT* help? > >>K > >> I *DON'T* want to use the VMS system examine other systems, I want theeG > >> VMS system to be able to alert a "foreign" system when some bit ofrJ > >> system administrivia goes awry (disk fills up, shadow-set member gets& > >> dropped, backup job fails, etc.). > >> > >> Does *THAT* help?< > > Your "foreign" system admin should be able to tell you -; > > the ip address of the system that will receive the trapp > > the community name to usea > > the port to use (162?)1 > > the "enterprise" (compaq is 1.3.6.1.4.1.232.)U? > > the oid to use within 232 to indicate disk full or whatever + > > use this link to identify "enterprises"g6 > > http://www.alvestrand.no/objectid/1.3.6.1.4.1.html > B > The key piece that David is missing is not the community string,= > MIB variable or UDP port number.  It is a piece of software 6 > that would allow _traps_ to be _sent_ from Multinet.  9 *AT* *LAST*!!!!  SOMEone who understands the question!!!!t  E > One way to go would be to write a program to format the UDP datagaml? > and send it yourself.  Once you come up to speed on the ASN.1tA > coding conventions, this would not be much work.  But coming up  > to speed can be a pain.o > ? > David -- I have some very old software that I wrote in C that @ > does SNMP gets and sets under Multinet ($QIO interface).  It's= > "roll your own" code and includes pieces which do the ASN.10E > formatting for the outbound SNMP requests and ASN.1 parsing for the G > resulting responses.  It's huge, site specific and pretty ugly but it>C > should have most of the support routines you would need to use tol> > craft a trap datagram.  And the comments contain pretty much? > everything I know about ASN.1.  E-mail me if you want a copy.t  D A very gracious and generous offer. Many thanx. See Richard Whalen's( reply at another point in this thread...   -- l David J. Dachtera3 dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/a   ------------------------------  % Date: Mon, 07 Jul 2003 20:59:00 -0500o1 From: "David J. Dachtera" <djesys.nospam@fsi.net>nY Subject: Re: SNMP Commands (was Re: How do I monitor the CPU temperature in an         ES ' Message-ID: <3F0A2564.E8CC0195@fsi.net>H   Richard Whalen wrote:s > > > "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message# > news:3F0878CE.889AB110@fsi.net...3 > >7% > > O.k. Let me try this another way:n > >>J > > I'm looking for a way - from a VMS system running Multinet - to send aG > > SNMP trap to a "foreign" system monitoring center (at work, they'ree > > trying to use Cisco's CIC).t > >e > > Does *THAT* help?c > >:J > > I *DON'T* want to use the VMS system examine other systems, I want theF > > VMS system to be able to alert a "foreign" system when some bit ofI > > system administrivia goes awry (disk fills up, shadow-set member gets1% > > dropped, backup job fails, etc.).I > >s > > Does *THAT* help?a > >F > > -- > > David J. Dachtera  > > dba DJE Systemss > > http://www.djesys.com/ > >n, > > Unofficial Affordable OpenVMS Home Page:# > > http://www.djesys.com/vms/soho/  > G > If you have a support contract with Process Software, then you shouldo- > contact support for help with this problem.0 > * > The basic steps that you need to do are:I > 1) add a COMMUNITY name ip-address TRAPS to MULTINET:SNMP.CONF for eachIC > address that you want to send the trap to. (see chapter 23 in the ' > Installation & Administrator's Guide)t > 7 > 2) define the symbol: trap_gen :== $multinet:trap_gen> > L > 3)                  $ trap_gen <enterprise> <generic_trap> <specific_trap>0 >                   [<trap_specific_values>....] > J >           <enterprise> identifies the location in the MIB tree that this2 >           trap pertains to. An example would be: > " >                 1.3.6.1.4.105.3, > N >           which denotes a location in Process Software Corporation's portion >           of the MIB tree. > M >           <generic_trap> is an integer representing the generic trap value.  > H >           <specific_trap> is an integer representing the specific trap > value. > L >           <trap_specific_values> are arbitrary strings separated by spacesM >           that are passed to the agent receiving the trap as octet strings.b > K >           The TRAP_GEN program uses the trap community definitions in the/I >           MULTINET:SNMPD.CONF file to determine where to send the trap.7    Thanx so much for that, Richard.  1 I suppose this is undocumented / unsupported, eh?m   -- l David J. Dachterar dba DJE Systemsu http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/n   ------------------------------   Date: 7 Jul 2003 11:57:31 -0700w' From: dennisb@wvhmhc.org (Dennis Baker)7Q Subject: Re: Subject: Reading long files in BASIC that appears to be "recordless"-= Message-ID: <6f29699e.0307071057.68c1c1a2@posting.google.com>v   Jeff, and Jeff Morgan -eB Those solutions won't work, because I'll never be able to know theD maximum record size (i.e., total file size) but I DO know that it'llF be at least 1,000,000.  Looks like some manner of QIO(W) is necessary.C  Thanks to Randy Park and Milan Jercic for examples.  I think I canE get what I need from them. - Dennis Baker  e "Jeff Morgan" <vmswiz@geonospamcities.com> wrote in message news:<be5ssb$fls5$1@news3.infoave.net>...u	 > Dennis:n > L >    See if this code snippet works for you. It should handle any record and# > file type up to a 4K record size.o > ? >                                                          JeffK >  >  >  >  DECLARE LONG EOF_SW, SS >  >  DECLARE STRING WORK_RECORDg >  >  RECORD WW_RECORD   >         STRING WW_DATA = 4096%
 >  END RECORDn >  MAP (WW_MAP) WW_RECORD WW >  >  WHEN ERROR IN >         OPEN "INPUT_FILE:" &3 >                 FOR INPUT AS FILE #FILE_CHANNEL,&1+ >                 ORGANIZATION UNDEFINED, &h# >                 RECORDTYPE ANY, &i >                 MAP WW_MAP, &-  >                 ACCESS READ, & >                 ALLOW MODIFY >         SS = 0%c	 >     USEV >         SS = 1%o >  END WHENg >  >  IF SS = 1% THENA >         PRINT "CAN'T OPEN INPUT_FILE: " + STR$(ERR) + ERT$(ERR)s >         EXIT PROGRAM	 >  END IFW >  >  GOSUB READ_RECORD >  WHILE EOF_SW = 0% >  >         GOSUB DO_SOMETHING >  >         GOSUB READ_RECORDb >  >  NEXT  >  >  CLOSE FILE_CHANNELa >  >  EXIT PROGRAMg >  > READ_RECORD: >  >  WHEN ERROR IN >         GET #FILE_CHANNELo2 >         WORK_RECORD = LEFT$(WW::WW_DATA,RECOUNT) >         EOF_SW = 0% 	 >     USE  >         WORK_RECORD = "" >         EOF_SW = 1%a >  END WHENp > 	 >  RETURN  >  > 6 > "Dennis Baker" <dennisb@wvhmhc.org> wrote in message9 > news:6f29699e.0306271111.2720c9f0@posting.google.com... F > > I have a BASIC program that lists files matching numerous wildcardF > > patterns, sorted in descending date order, and prompts the user toH > > select one for processing.  It opens each file and reads a few linesH > > to try to figure out what kind of contents are in them.  Previously,J > > it just used LINPUT to get each line of the file.  The problem is someB > > files I've just started receiving are what I believe have beenI > > referred to as "unix-like" files: they don't have individual records,d > > so a GET results ini >  > . . .w >  > > There should bebI > > an easier way to read any file in BASIC block by block, regardless of * > > it's file attributes, but I'm stumped. > >e$ > > Dennis Baker, Programmer/Analyst > > Wabash Valley Hospital" > > dennisb at dontspam wvhmhc.org   ------------------------------  # Date: Tue, 08 Jul 2003 00:35:54 GMTSL From: winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr")9 Subject: Re: Sybase Migrations External Website availabler6 Message-ID: <00A22836.AE98E244@SSRL.SLAC.STANFORD.EDU>  n In article <RhoOa.81004$x4o.21512@news04.bloor.is.net.cable.rogers.com>, "John Smith" <a@nonymous.com> writes: > ? >"Sue Skonetski" <susan_skonetski@hotmail.com> wrote in messagei8 >news:857e9e41.0307070723.224439cc@posting.google.com...
 >> Newsgroup,  >>4 >> I just recevied this and wanted to pass it along. >> >> sue >>4 >> _________________________________________________ >>? >> I'm happy to announce the Sybase Migrations Website.  Go to:30 >> hp OpenVMS systems solutions and applications' >(http://h71000.www7.hp.com/solutions/)  >c >u6 >http://h71000.www7.hp.com/solutions/sybase/index.html >for the full url. >n >oF >Too bad Sybase doesn't believe that there's enough business on VMS toD >justify maintaining current releases on VMS. Isn't this where carly? >(tm) steps in and pays a call on John Chen (Sybase CEO) to saydE >mano-a-mano, from one CEO to another, that HP has a HUGE advertisingtG >and marketing campaign for VMS planned and that she wants Sybase to beeA >a featured partner in that campaign, and what can HP do to help?s > 0 >Ooops. There I go again....thinking rationally.  K No arguments about your actual point here, but "mano-a-mano" actually meanstN "hand-to-hand" as in "hand-to-hand combat", not "man-to-man" so you might just0 mean "face to face", or stick with "CEO to CEO".   -- Alann -- oO ===============================================================================m0  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDUM  Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056-M  Paper mail to: SSRL -- SLAC BIN 99, 2575 Sand Hill Rd, Menlo Park CA   94025 O ===============================================================================    ------------------------------  # Date: Tue, 08 Jul 2003 00:31:45 GMT # From: "John Smith" <a@nonymous.com> 9 Subject: Re: Sybase Migrations External Website availablerH Message-ID: <RhoOa.81004$x4o.21512@news04.bloor.is.net.cable.rogers.com>  > "Sue Skonetski" <susan_skonetski@hotmail.com> wrote in message7 news:857e9e41.0307070723.224439cc@posting.google.com...m > Newsgroup, >n3 > I just recevied this and wanted to pass it along.e >v > suei >o3 > _________________________________________________n >n> > I'm happy to announce the Sybase Migrations Website.  Go to:/ > hp OpenVMS systems solutions and applicationsn& (http://h71000.www7.hp.com/solutions/)    5 http://h71000.www7.hp.com/solutions/sybase/index.htmlo for the full url.r    E Too bad Sybase doesn't believe that there's enough business on VMS tosC justify maintaining current releases on VMS. Isn't this where carly-> (tm) steps in and pays a call on John Chen (Sybase CEO) to sayD mano-a-mano, from one CEO to another, that HP has a HUGE advertisingF and marketing campaign for VMS planned and that she wants Sybase to be@ a featured partner in that campaign, and what can HP do to help?  / Ooops. There I go again....thinking rationally.3   ------------------------------  % Date: Mon, 07 Jul 2003 21:14:48 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> 9 Subject: Re: Sybase Migrations External Website availableh' Message-ID: <3F0A2918.A0E2B70B@fsi.net>   * Alan Winston - SSRL Admin Cmptg Mgr wrote: > p > In article <RhoOa.81004$x4o.21512@news04.bloor.is.net.cable.rogers.com>, "John Smith" <a@nonymous.com> writes: > >oA > >"Sue Skonetski" <susan_skonetski@hotmail.com> wrote in messageh: > >news:857e9e41.0307070723.224439cc@posting.google.com... > >> Newsgroup,h > >>6 > >> I just recevied this and wanted to pass it along. > >> > >> sue > >>6 > >> _________________________________________________ > >>A > >> I'm happy to announce the Sybase Migrations Website.  Go to:e2 > >> hp OpenVMS systems solutions and applications) > >(http://h71000.www7.hp.com/solutions/)  > >t > >h8 > >http://h71000.www7.hp.com/solutions/sybase/index.html > >for the full url. > >- > > H > >Too bad Sybase doesn't believe that there's enough business on VMS toF > >justify maintaining current releases on VMS. Isn't this where carlyA > >(tm) steps in and pays a call on John Chen (Sybase CEO) to sayoG > >mano-a-mano, from one CEO to another, that HP has a HUGE advertisingtI > >and marketing campaign for VMS planned and that she wants Sybase to be C > >a featured partner in that campaign, and what can HP do to help?l > > 2 > >Ooops. There I go again....thinking rationally. > M > No arguments about your actual point here, but "mano-a-mano" actually meanseP > "hand-to-hand" as in "hand-to-hand combat", not "man-to-man" so you might just2 > mean "face to face", or stick with "CEO to CEO".  A Well, considering they'll probably end up duking it out over nitsi9 anyway, perhaps "mano-a-mano" is appopriate anyway... ;-)M   --   David J. Dachterae dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/y   ------------------------------  # Date: Tue, 08 Jul 2003 03:51:04 GMTh# From: "John Smith" <a@nonymous.com>e9 Subject: Re: Sybase Migrations External Website availablerH Message-ID: <IcrOa.94396$2ay.68880@news01.bloor.is.net.cable.rogers.com>  ' ""Alan Winston - SSRL Admin Cmptg Mgr"" 1 <winston@SSRL.SLAC.STANFORD.EDU> wrote in message,0 news:00A22836.AE98E244@SSRL.SLAC.STANFORD.EDU... > In articleC <RhoOa.81004$x4o.21512@news04.bloor.is.net.cable.rogers.com>, "John  Smith" <a@nonymous.com> writes:J > >tA > >"Sue Skonetski" <susan_skonetski@hotmail.com> wrote in messageP: > >news:857e9e41.0307070723.224439cc@posting.google.com... > >> Newsgroup,a > >>6 > >> I just recevied this and wanted to pass it along. > >> > >> sue > >>6 > >> _________________________________________________ > >>A > >> I'm happy to announce the Sybase Migrations Website.  Go to:r2 > >> hp OpenVMS systems solutions and applications) > >(http://h71000.www7.hp.com/solutions/)e > >e > >b8 > >http://h71000.www7.hp.com/solutions/sybase/index.html > >for the full url. > >  > >hE > >Too bad Sybase doesn't believe that there's enough business on VMSy toF > >justify maintaining current releases on VMS. Isn't this where carlyA > >(tm) steps in and pays a call on John Chen (Sybase CEO) to say-; > >mano-a-mano, from one CEO to another, that HP has a HUGEo advertisingfF > >and marketing campaign for VMS planned and that she wants Sybase to beC > >a featured partner in that campaign, and what can HP do to help?e > >>2 > >Ooops. There I go again....thinking rationally. >a> > No arguments about your actual point here, but "mano-a-mano" actually meansE > "hand-to-hand" as in "hand-to-hand combat", not "man-to-man" so youh
 might just2 > mean "face to face", or stick with "CEO to CEO".  C I can see it now...The WWF presents carly (tm) The Coiffed Crusader?B vs. John "How's Our Market Share Doing" Chen in a most falls until curfew battle.......  0 Sometimes the corporate world is very Darwinian.: Certainly a lot of back-stabbing intra-corporately occurs.   ------------------------------  # Date: Mon, 07 Jul 2003 18:52:31 GMT # From: hoff@hp.nospam (Hoff Hoffman)o4 Subject: Re: SYS$SPECIFIC and SYS$COMMON not enough?2 Message-ID: <PjjOa.4042$9H7.3875@news.cpqcorp.net>  w In article <01KXZKP04MZUAM7Y4A@sysdev.deutsche-boerse.com>, Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> writes:wI :What are some real-world examples of stuff which is common to all nodes -H :which boot from a common system disk, but not common to all nodes in a 6 :cluster, even in a share-as-much-as-possible cluster?  A   You need to answer this question yourself, and specifically forf@   your local environment.  One example would be SYSUAF.DAT quota@   settings for various hosts, if running parallel SYSUAF files. B   (You need to be VERY careful here, as you must keep all UICs andC   all usernames and all identifiers involved scrupulously matched.)t  A   I am aware of nothing here, however, that can't also be handled A   "directly" with per-file logical name redirections.  SYSUAF cane%   certainly be redirected, of course.l  J :Is there any chance of extending definitions like SYS$SYSROOT to include 4 :SYS$CLUSTER while retaining backward compatibility?  C   We have something similar here in OpenVMS Engineering, and we do e6   create and use a CLU$COMMON root within SYS$SYSROOT:   $ sho log sys$sysrooto4    "SYS$SYSROOT" = "ddcu:[root.]" (LNM$SYSTEM_TABLE)         = "SYS$COMMON:" = 1  "SYS$COMMON" = "ddcu:[root.SYSCOMMON.]" (LNM$SYSTEM_TABLE)          = "CLU$COMMON:""8 2  "CLU$COMMON" = "ddcuother:[root.]" (LNM$SYSTEM_TABLE)  F   though we do know that various of the LP installation procedures canF   and regularly do become somewhat confused with this structure.  SomeH   of the engineers have informally discussed implementing and supportingF   this configuration, and (obviously) fixing and extending the variousI   OpenVMS installation procedures and tools -- but another and far larger-C   project has, um, intruded on this particular OpenVMS enhancement.n  G   We walk the current list of SYS$SYSROOT translations within some DCL eF   within SYLOGICALS.COM, and we append the CLU$COMMON translation onto   the searchlist.i  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqiN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comf   ------------------------------  * Date: Tue, 8 Jul 2003 00:44:59 +0000 (UTC), From: lewis@PROBE.mitre.org (Keith A. Lewis)4 Subject: Re: SYS$SPECIFIC and SYS$COMMON not enough?. Message-ID: <bed46b$neh$1@newslocal.mitre.org>   Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> writes in article <01KXZKP04MZUAM7Y4A@sysdev.deutsche-boerse.com> dated Mon, 07 Jul 2003 19:48:27 +0200 (MET):I >What are some real-world examples of stuff which is common to all nodes  H >which boot from a common system disk, but not common to all nodes in a 6 >cluster, even in a share-as-much-as-possible cluster?  K One use of a cluster is testing new system SW.  You can make a copy of your.I main system disk and upgrade the software there (say, a VMS patch).  ThenwK boot one system using that disk and see how it works, while the rest of thelL cluster does your production work using the old system without the upgrade. I In that case, any files affected by the upgrade would/should be differente for the test node.    8 The audit journal file is another example.  It's in eachL SYS$COMMON:[SYSMGR].  Why does it need to be on the system disk?  The systemI might need to access it at any time, and the system disk is the only diskh/ which is (or needs to be) guaranteed available.c  J >Is there any chance of extending definitions like SYS$SYSROOT to include 4 >SYS$CLUSTER while retaining backward compatibility?  J You can rig all kinds of stuff.  I'm sure there have been discussions hereI about having SYS$COMMON and SYS$SPECIFIC point to different devices.  The$J "VMSCluster Systems for OpenVMS" manual has a list of ~10 data files whichF it recommends be migrated off the system disk if you're using multiple system disks in your cluster.     + --Keith Lewis              klewis$mitre.orgr> The above may not (yet) represent the opinions of my employer.   ------------------------------  # Date: Mon, 07 Jul 2003 22:11:09 GMT 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)* Subject: Re: Upcoming release of VMS 7.3-22 Message-ID: <1emOa.9989$1F6.161357@news.chello.at>  f In article <7hJNa.8129$eF3.1139972@news20.bellglobal.com>, "Neil Rieck" <n.rieck@sympatico.ca> writes: ><PERSONAL OPINION>eM >I noticed a big jump in performance just going from 7.3 to 7.3-1 and anothertK >performance increase is expected going to 7.3-2 (mostly related to variousrO >spin locks). I believe that other companies would do the "marketing thing" and(N >release 7.3-1 as 7.4 and 7.3-2 as 7.5 so don't ignore it just because this is >a dash release. ></PERSONAL OPINION>  I Yes. From the definition of a dash release (a maintenance release - or in H other words a sum up of all the ECOs available so far - extra tested andG certified) then V7.3-1 is indeed a V7.4 (and V7.3-2 is a V7.5). And the-K binary compatibility problems of early V7.3-1 (until an ECO fixed it again) 7 and the great performance wins back up this assumption.   L But OTOH, this dash release is covered by your current license PAK (and evenL the next dash release is, too). So, don't punish HPQ for saving you money...   -- - Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialisto E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------   Date: 7 Jul 2003 12:47:42 -0700a% From: sellis@legato.com (Shaun Ellis)l- Subject: Re: Using ArcServe to backup VAX/VMSr< Message-ID: <1faa9425.0307071147.1b10074@posting.google.com>  } "Stephen Eickhoff" <operagost@example.com> wrote in message news:<npAEa.2286$qd3.1590@tornadotest1.news.pas.earthlink.net>... < > "Shiva MahaDeva" <contracer11@uol.com.br> wrote in message9 > news:ddf392ea.0304260858.6c26f157@posting.google.com... B > > Id like to know if any guy haves experience using ArcServe to+ > > backup VAX/VMS system - its possible ?r > F > I have not done it, but there is a VMS agent available as an option.  : Computer Associates have discontinued their OpenVMS agent.  D Ofcourse, you only have my word for it :-) actually, it was in their release notes for BrighStor 9.   Shaun Ellisa OpenVMS Product Managerd Legato Systems Inc   ------------------------------   Date: 7 Jul 2003 16:10 CDT' From: carl@gerg.tamu.edu (Carl Perkins)eA Subject: Re: VAX Vup Listing not available on HP - where is it ??s, Message-ID: <7JUL200316100684@gerg.tamu.edu>  8 kuhrt@nospammy.encompasserve.org (Marty Kuhrt) writes...x }In article <01KXV0FW92HUAPKEWT@sysdev.deutsche-boerse.com>, Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> writes:L }>> As a BTW, I've got a file CALCULATE_VUPS.COM which gave me very accurateL }>> answers on a variety of VAX machines that I once had.  And seems to giveL }>> a good "VUPS" for our Alpha machines where we have measured CPU times in }>> our applications.  }>> I }>> I suspect I got it from here (c.o.v or info-vax) and cut the headingsyI }>> and footings, so I have lost the attribution since the author did nots: }>> identify himself within the .COM part of the message.  }>> I }>> If the author is still around (and if it is from here that I got it),aK }>> hopefully he can post it to you and hopefully "admit" to authorship.  IS+ }>> would like to maintain an attribution.   }> lJ }> There was something like that posted here.  I was quite impressed when K }> it gave 7.6 for a VAXstation 3100 M76.  :-)  IIRC, Steve Lionel pointed j? }> out that this is NOT the actual code used to calculate VUPs.i }> 2< }> I saved the whole post, commenting out the non-code bits: }> m7 }>    http://www.astro.multivax.de:8000/phillip/vup.comq }> w } A }That's the CALCULATE_VUPS.COM that comes with Diskeeper, writteni< }by Rick Cadruvi (IIRC).   If you have DK you can find it in  G Actually, comparing the two, it looks to be a slightly modified versionnD (including stripping some write sys$output stuff that, amongst otherH things, identifies the product it came from) - unless different versionsE of Diskkeeper have used different versions of this thing. The versiondG I have is technically not from "Diskkeeper", but from "Control Master".oH I don't know if they have anything that uses that other then Diskkeeper.  A }SYS$SYSDEVICE:[ESICM]CALCULATE_VUPS.COM.  Since, at the time, we A }only had a VS2K, VS3100-20, MVII and a VS3100 M76 to test it on,/5 }it's not surprizing that the 7.6 came out as it did.e } ? }Be warned when using it on the newer Alphas, though.  Since it.> }will keep calculating until it gets a reading that is plus or> }minus five of the last reading, it may take a while for it to= }finish.  My DS10 at work took so long I thought I'd hung the = }machine (with simple DCL?), so I put in some dbg statements.e@ }Eventually it finished (with a VUPage of 1026) but it took five }minutes.  f  D Must be a DS10/600 as an XP900 comes in at 630.5 (using the originalE Diskkeeper version of the code). It "only" takes a bit over a minute.oG The various other things going on (like driving the graphics, including D my load indicator) may have eaten up a percent or so, which would beE about half a dozen VUPS (or roughly a cluster of half a dozen 11/780ssA worth of processing power - an amount of processing power that is  trivial these days).  C The most interesting part to me is that the thing drives the system C at around 27 - 28 percent kernel mode and 10 - 12 percent executives) mode (the rest going to supervisor mode).-   --- Carl   ------------------------------  $ Date: Mon, 7 Jul 2003 20:42:04 -0400) From: "Neil Rieck" <n.rieck@sympatico.ca> A Subject: Re: VAX Vup Listing not available on HP - where is it ??09 Message-ID: <wroOa.5243$ru2.349172@news20.bellglobal.com>    Try the following URL:? http://h18002.www1.hp.com/alphaserver/performance/perf_tps.htmli  
 Neil Rieck Kitchener/Waterloo/Cambridge,e Ontario, Canada.! http://www3.sympatico.ca/n.rieck/h  8 "Paul Hallam" <paul_hallam@hotmail.com> wrote in message6 news:5ed44bd3.0307030540.db77a99@posting.google.com...? > Does anyone know what HP have done with the old VAX/Alpha VUP= > comparison listings.H > I need to get the VUP ratings for Vax 7000/700A, 7000/710 and 7000/7207 > but the lists are no longer available on the HP site.h >i > Anyone help ?e >n
 > Many thankst >a
 > Paul Hallam    ------------------------------  # Date: Mon, 07 Jul 2003 22:37:56 GMT ) From: bob smith <sfmc68@bellatlantic.net>V: Subject: vms security model - does it still exist on IA64?/ Message-ID: <3F09F67F.1070002@bellatlantic.net>e  & Subject says it all, any info on this? bobB   ------------------------------  # Date: Mon, 07 Jul 2003 23:38:09 GMTr# From: hoff@hp.nospam (Hoff Hoffman) > Subject: Re: vms security model - does it still exist on IA64?1 Message-ID: <BvnOa.4064$S6.1903@news.cpqcorp.net>a  [ In article <3F09F67F.1070002@bellatlantic.net>, bob smith <sfmc68@bellatlantic.net> writes:C' :Subject says it all, any info on this?'       Yes.    *   Terse questions beget terse answers. :-)    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqkN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comV   ------------------------------  # Date: Mon, 07 Jul 2003 23:54:13 GMTe) From: bob smith <sfmc68@bellatlantic.net>n> Subject: Re: vms security model - does it still exist on IA64?/ Message-ID: <3F0A0861.2010705@bellatlantic.net>m   Hoff Hoffman wrote: ] > In article <3F09F67F.1070002@bellatlantic.net>, bob smith <sfmc68@bellatlantic.net> writes:-) > :Subject says it all, any info on this?3 >  > 
 >   Yes.   > , >   Terse questions beget terse answers. :-) >  > P >  ---------------------------- #include <rtfaq.h> -----------------------------M >     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqaP >  --------------------------- pure personal opinion ---------------------------G >         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com  >   
 Okay Hoff,I I deserved that! Thanks! now that there is a hint that such info exists, -F how about pointers to available info?  Obviously, VMS has some rather G decent capabilities (really hard for me to say but the truth is there) aH with regard to withstanding such things as buffer overflow attempts and  so on.  H The IA64 does seem to have some hardware capabilities but the area I am A interested in is what was changed with ref to the security model.  thanks bad bob    ------------------------------   Date: 7 Jul 2003 18:32:06 -0700p( From: bob@instantwhip.com (Bob Ceculski)> Subject: Re: vms security model - does it still exist on IA64?< Message-ID: <d7791aa1.0307071732.2e05cef@posting.google.com>  ` bob smith <sfmc68@bellatlantic.net> wrote in message news:<3F09F67F.1070002@bellatlantic.net>...( > Subject says it all, any info on this? > bobv  7 did it lose its security model when it went from vax tol9 alpha?  NO!  and it will not to itanium ... why would it?'7 The bliss compiler is there, as are the others ... acls-9 and uic and proxies and all the rest will be the same ...c4 What has been said by Gorham is that they are so far; ahead on the port because many things were just a recompilet9 and go ... only system specific things like the pal code, 9 debugger and such have changed, underneath that it sounds  like vms is still vms ...r   ------------------------------  # Date: Tue, 08 Jul 2003 01:35:57 GMTu# From: hoff@hp.nospam (Hoff Hoffman)*> Subject: Re: vms security model - does it still exist on IA64?1 Message-ID: <1epOa.4069$x7.1164@news.cpqcorp.net>r  [ In article <3F0A0861.2010705@bellatlantic.net>, bob smith <sfmc68@bellatlantic.net> writes:o  @   Gotta love those completely open-ended one-line questions. :-)  B   If you wish to read about the OpenVMS security model, please see@   both the IDSM and the OpenVMS Guide to System Security manual.:   These two documents cover much of what you need to know.  C   If you are programming, there are a couple of additional manuals.TA   The programming concepts manual is one, then (for instance) thew   device driver documentation.  C   If you are securing a system, please see the Class C2 appendix of-   the system security manual.   I :                                         Obviously, VMS has some rather iH :decent capabilities (really hard for me to say but the truth is there) I :with regard to withstanding such things as buffer overflow attempts and r :so on.l  D   Please see the attached posting, and also see the various existingE   discussions in the archives.  (Google for the previous discussions,a=   and you should have no problems finding related materials.)n  I :The IA64 does seem to have some hardware capabilities but the area I am MB :interested in is what was changed with ref to the security model.  E   Exceedingly little has changed from OpenVMS Alpha -- we have mappedCD   the I64 memory page protections to the Alpha page protections, forF   instance.  There are a few differences in page protections, but I amE   aware of nothing that will be of any consequence outside of kernel-iG   mode code -- and Itanium has some rather nice memory management page  D   protection enhancements available in this area, too.  For previousD   discussions, please google for URKW.  If you _have_ kernel-mode orF   all-class privileged code, then you do need to be very familiar withF   the IDSM and the driver manual, for instance -- such code is part ofD   what is known as the Trusted Computing Base (TCB); part of OpenVMS   system security.  H   I have a presentation on this topic, but -- for what should be obviousI   reasons -- the material is also effectively a guide to hacking into an UG   operating system or into an application; a very serious topic and not H   one that I am comfortable discussing in a newsgroup.  (Folks that thatG   are interested and that are attending can suggest this session :-) to I   Sue for inclusion in the next OpenVMS Advanced Technical Bootcamp (ATB).>   event -- November 11-14, 2003 -- to be held here in Nashua.)   	--i  H   I am not in a position to discuss (widely) specifics in this area, norJ   am I in a position to discuss hardware and software features and futuresF   in this area, and nor can I effectively provide lessons in attackingG   systems to folks that would misuse the knowledge -- I would encouragelH   any folks to consider carefully before discussing this area in a forumI   such as a newsgroup, as there are both folks that deserve to know these.H   details and there are unfortunately also folks that will (mis)use what<   is learned here to clobber systems and to breach security.  F   If you believe you have found a security hole, please contact an HP F   representative directly -- I will accept and will investigate and/orG   appropriately forward any such reports that are sent to me via email, E   for instance.  (I can't promise timely responses, however -- if you>G   have a support contract, please contact the support center directly.)>    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqpN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.como   	--e    2 Newsgroups: comp.os.vms,alt.sys.pdp10,comp.sys.dec Distribution: world  X-Newsreader: mxrn 6.18-32B  References: <3roT7.207043$tf5.13617499@bin5.nnrp.aus1.giganews.com> <Pine.NXT.4.50.0112210740180.6674-100000@Tomobiki-Cho.CAC.Washington.EDU> <hO42RwhQI2bm@eisner.encompasserve.org>e2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)' Reply-To: hoffman@xdelta.zko.dec.nospamtS Subject: Re: Buffer Overflows - again Was: (Re: Congratulations for the festive sea"	 Lines: 23 1 Message-ID: <tBLU7.329$sK3.5182@news.cpqcorp.net>o# Date: Fri, 21 Dec 2001 18:56:25 GMT  NNTP-Posting-Host: 16.32.80.251r! X-Complaints-To: abuse@Compaq.comoQ X-Trace: news.cpqcorp.net 1008960985 16.32.80.251 (Fri, 21 Dec 2001 10:56:25 PST)m0 NNTP-Posting-Date: Fri, 21 Dec 2001 10:56:25 PST) Organization: Compaq Computer Corporationa    a In article <hO42RwhQI2bm@eisner.encompasserve.org>, young_r@encompasserve.org (Rob Young) writes: @ :	This is a myth or legend.  Bart Z. Lederman succinctly refuted. :	such a myth recently.  Here is what he said:  H   No myth.  No legend.  OpenVMS can potentially be and has occasionally F   actually been found to be vulnerable to security problems resulting ,   from buffer overrun errors.  This is fact.  F   For what should be obvious reasons, I will not be providing details.  I   Compaq OpenVMS Engineering takes all reports of security problems quitetJ   seriously, and strives to quickly resolve any security holes identified.  H   If you believe you have encountered a security problem, please contactK   a Compaq representative directly.  In deference to the security of other mB   OpenVMS users, please do not post security problem reports here.  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 07 Jul 2003 20:55:17 -0500.1 From: "David J. Dachtera" <djesys.nospam@fsi.net>e> Subject: Re: vms security model - does it still exist on IA64?& Message-ID: <3F0A2485.A129490@fsi.net>   bob smith wrote: >  > Hoff Hoffman wrote: _ > > In article <3F09F67F.1070002@bellatlantic.net>, bob smith <sfmc68@bellatlantic.net> writes:t+ > > :Subject says it all, any info on this?k > >o > >a
 > >   Yes. > >s. > >   Terse questions beget terse answers. :-) > >" > >gR > >  ---------------------------- #include <rtfaq.h> -----------------------------O > >     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqeR > >  --------------------------- pure personal opinion ---------------------------I > >         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.come > >b >  > Okay Hoff,J > I deserved that! Thanks! now that there is a hint that such info exists,G > how about pointers to available info?  Obviously, VMS has some rather H > decent capabilities (really hard for me to say but the truth is there)I > with regard to withstanding such things as buffer overflow attempts and  > so on. > I > The IA64 does seem to have some hardware capabilities but the area I amhC > interested in is what was changed with ref to the security model.   @ If you mean does it still use the four modes: kernel, executive,G supervisor and user; and the four classes: System, Owner, Group, World; @ and the ACLs and rights identifiers; and intrusion detection andB evasion, then I would expect so, although I obviously cannot speak authoritatively.  G Just because it's running on the same CPUs as the garbage, doesn't maket VMS garbage. VMS is still VMS.   --   David J. Dachterar dba DJE Systemsn http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/i   ------------------------------  # Date: Tue, 08 Jul 2003 03:05:43 GMT # From: hoff@hp.nospam (Hoff Hoffman)t> Subject: Re: vms security model - does it still exist on IA64?1 Message-ID: <byqOa.4070$Ub.2394@news.cpqcorp.net>   Z In article <3F0A2485.A129490@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes: :bob smith wrote:tH :> ...                   now that there is a hint that such info exists,H :> how about pointers to available info?  Obviously, VMS has some ratherI :> decent capabilities (really hard for me to say but the truth is there) J :> with regard to withstanding such things as buffer overflow attempts and	 :> so on.   C   See my other post on this portion, elsewhere in the thread.  Also @   search for the URKW discussions, as mentioned in that posting.  J :> The IA64 does seem to have some hardware capabilities but the area I amD :> interested in is what was changed with ref to the security model. : A :If you mean does it still use the four modes: kernel, executive,6H :supervisor and user; and the four classes: System, Owner, Group, World;A :and the ACLs and rights identifiers; and intrusion detection andt# :evasion, then I would expect so...f  
   Correct.  J   If you dig around within the OpenVMS VAX and the OpenVMS Alpha kernels, H   you will certainly find various implementation differences -- the sameG   holds true for OpenVMS I64; there are and will be kernel differences,v   of course.  E   But as we are porting OpenVMS, the resulting implementation has the F   expected page protections, four processor-mode operations, the usualH   DCL commands and syntax, the expected security mechanisms, programmingF   APIs, and the related structures -- from user-mode code and the userH   environment, it all looks exceedingly similar to what you are familiarJ   with.  Even from within the kernel, large tracts are going to be looking/   very familiar to folks familiar with OpenVMS.P  J   Like the previous move (to Alpha), most of the porting work is expected I   to involve little more than recompilation and relinking -- and like the H   previous port from VAX to Alpha, I expect we will be providing portingI   documentation to help identify application code that makes assumptions =I   specific to Alpha.  (When I ported a very large and complex applicationUI   (to Alpha), it took me rather longer to set up the parallel application E   build environment than it did to actually port the code.  Once the TF   prerequisite products are in place, I would expect the same level ofD   effort porting this code from Alpha to I64 -- or maybe even less.)  G   Will all code port across transparently?  Probably not -- most of the,G   "fun" I am finding involves code that explicitly tests for VAX or for I   Alpha as part of selecting something -- and particularly then with the eB   path selected when the code finds neither platform matches.  :-)  F   Extra credit question: which VAX implementation had five modes. :-)     N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqaN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.como   ------------------------------   Date: 7 Jul 2003 12:34:09 -0700e% From: sellis@legato.com (Shaun Ellis)k5 Subject: Re: What Tape Library for VMS and FC clustera< Message-ID: <1faa9425.0307071134.fb99924@posting.google.com>  ` "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message news:<3EEFDDDB.773AC35E@fsi.net>... > Gunther Schadow wrote: > >  > > Hi,r > > I > > we are in the process of purchasing a tape library to back up our EMC @ > > Symmetrix SAN. Would like to poll some experiences with VMS. > > ' > > The alternatives I'm looking at areA > > / > > 1) StorageWorks MSL6060 with 4 LTO-2 drivess > ; > OpenVMS support for LTO-2 is a future. Not yet available.E  @ It is available now, or so I am informed by OpenVMS engineering.   > , > > 2) ADIC Scalar 1000 with 6x2 AIT-2 slots > , > Not sure if OpenVMS has qualified AIT yet. > ! > > 3) ADIC Scalar 100 with LTO-1s > > 4) StorageTek L180, LTO-1. > > 5) StorageTek L700, LTO-1  > ; > OpenVMS does not (and never will, I'm told) support LTO-1   E openVMs doe snot support LTO-1 due to an issue where it does not work_A with odd numbered bytes (Maximum block size for OpenVMS backup is  64K-1 byte).  K > > the options 2-5 are recertified used devices. I have the choice in tape/J > > drives for some of them, which I need, because as I undertstand, LTO-1& > > will never be supported under VMS. > > I > > However, we may need a backup server anyway, in which case the backupr+ > > server machine doesn't have to run VMS.  > I > Oh, yes it does! ...unless you never intend to save/restore your systemo > disk using a non-VMS systema  # Hmm, this is a religious argument. a  E There are many many ways to work around this issue. All of them easy, F and low cost. What you ahve to do is work out how you are going to getB a small OpenVMS system running with TCP/Ip services and teh backup? software of your choice running. In Legato, we are working withaB OpenVMS engineering on providing a more complete Disaster RecoveryF solution. However there are things you can do today, depending on your DR scenario=  3 1) Boot your VMS machine as a remote cluster membera@ 2) Have a spare disk in your storage with a minimal system on itF 3) Have a spare disk with VMS built on to it, plug it in and boot from there.  E If you are doing disaster recovery, where you are going back to a new=0 site, you can do similar things at the new site.  , This is to name but a few ways to get going.  A The important thing is time to restore. NetWorker is the only 3rdyF party solution fully endorsed by OpenVMS engineering and that supportsD a heterogeneous environment where you can backup up to disk or tape.D because we backup directly to devices connected to your VMS machine,< we can get excellent restore speeds - even across a Network.   > > My questions are:c > > A > > - any issues to report with either of the alternatives above?_ > > D > > - how can you control the robots of non-DEC/COMPAQ/HP libraries, > >    does MRU work for those?p > I > Depends. Contact HP for authoritative reference. I'm told it works witho > L700.  > I > > - given the little competition of tape library backup server software G > >    on VMS, isn't it more useful to install a non-VMS backup server?u > E > No. Non-VMS systems in general do not fully support /IMAGE backups.e  D Legato fully supports a very close equivalent to /IMAGE. That is, we@ do not backup multiple files when you have aliases. We correctly@ restore aliases, and contigious files. all you have to do, after? restoring a system disk backup with NetWorker is run writeboot.p  F I'll admit this is not as good as OpenVMs backup, but when you look atB all the other benefits you get, this is a minor inconvenience that% requires little thought to deal with.:  9 BTW, my comments are based on my experience. I worked forD> Digital/Compaq for 14.5 years before joing Legato. I worked in? Digital's own IS department, delivered consulting in DatacentrerC automation (including working with Engineering on SLS and ABS), andoF finished working in Outsourcing where I had to design, and implement a> backup solution for 200 UNIX systems, 50 VMS systems, and 8000	 desktops.   I > > - does server-less backup directly over fibre channel work for people  > >    here with VMS?_ > E > Sort of. It DEFINITELY can be made to work with all HP-badged gear.S8 > Outside of that arena, it's hit-or-miss (mostly miss). > / > See my earlier posts on this topic (FC tape).h   Shaun Ellis/ OpenVMS product manager/ Legato Systems Inc sellis@legato.come   ------------------------------  % Date: Mon, 07 Jul 2003 19:47:43 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>m5 Subject: Re: What Tape Library for VMS and FC clusterr' Message-ID: <3F0A14AF.DDBFA7B5@fsi.net>o   Shaun Ellis wrote: > b > "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message news:<3EEFDDDB.773AC35E@fsi.net>... > > Gunther Schadow wrote: > > >n	 > > > Hi,o > > > K > > > we are in the process of purchasing a tape library to back up our EMCOB > > > Symmetrix SAN. Would like to poll some experiences with VMS. > > >u) > > > The alternatives I'm looking at area > > >n1 > > > 1) StorageWorks MSL6060 with 4 LTO-2 driveso > >n= > > OpenVMS support for LTO-2 is a future. Not yet available.h > B > It is available now, or so I am informed by OpenVMS engineering. >  > >t. > > > 2) ADIC Scalar 1000 with 6x2 AIT-2 slots > >y. > > Not sure if OpenVMS has qualified AIT yet. > > # > > > 3) ADIC Scalar 100 with LTO-1l > > > 4) StorageTek L180, LTO-1t > > > 5) StorageTek L700, LTO-1  > >-= > > OpenVMS does not (and never will, I'm told) support LTO-1h > G > openVMs doe snot support LTO-1 due to an issue where it does not workaC > with odd numbered bytes (Maximum block size for OpenVMS backup is. > 64K-1 byte). > M > > > the options 2-5 are recertified used devices. I have the choice in tapeDL > > > drives for some of them, which I need, because as I undertstand, LTO-1( > > > will never be supported under VMS. > > >tK > > > However, we may need a backup server anyway, in which case the backupk- > > > server machine doesn't have to run VMS.  > >gK > > Oh, yes it does! ...unless you never intend to save/restore your systemp > > disk using a non-VMS systemi > $ > Hmm, this is a religious argument.  D ...until you get to negotiating a DR contract, then it's a matter ofH economics; or, until you get to tell your VP of IT that the alternativesG will increase the recovery time dramatically, at which point the law is.E laid down in no uncertain terms: get it back up faster than possible,b regardless of cost.r  G No offense, Shaun, but that's the bottom line in HealthCare. I'd expecteF to find similar attitudes in financial institutions, etc.; i.e., VMS's niche-market strongholds.    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/a   ------------------------------   End of INFO-VAX 2003.373 ************************