1 INFO-VAX	Sat, 01 Apr 2006	Volume 2006 : Issue 180       Contents: Re: CI780 specs and 8600 specs? 0 Re: Device Naming: (was OPA0 Console connection)0 Re: Device Naming: (was OPA0 Console connection)0 Re: Device Naming: (was OPA0 Console connection)$ Re: Device stuck in MntVerifyTimeout$ Re: Device stuck in MntVerifyTimeout Re: DS10 Hang on boot  DVD+RW drives on Alpha 8.x Re: DVD+RW drives on Alpha 8.x Re: DVD+RW drives on Alpha 8.x Re: DVD+RW drives on Alpha 8.x EMC Clariion CDL& Re: exe$alononpage and exe$deanopgdsiz& Re: exe$alononpage and exe$deanopgdsiz& Re: exe$alononpage and exe$deanopgdsiz Re: MOP software for Win/NT/XP?  Re: OPA0 on DS10L problem . Re: Opinion: I was just trying to sell OpenVMS. Re: Opinion: I was just trying to sell OpenVMS. Re: Opinion: I was just trying to sell OpenVMS. Re: Opinion: I was just trying to sell OpenVMS. Re: Opinion: I was just trying to sell OpenVMS. Re: Opinion: I was just trying to sell OpenVMS. Re: Opinion: I was just trying to sell OpenVMS. Re: Opinion: I was just trying to sell OpenVMS. Re: Opinion: I was just trying to sell OpenVMS4 RE: SAP small business solutions now run on OpenVMS!9 Updated VMS information - Excellent Partner information - # Re: xp1000 boot flags and vms 7.2-1   F ----------------------------------------------------------------------  # Date: Sat, 01 Apr 2006 00:25:05 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>( Subject: Re: CI780 specs and 8600 specs?2 Message-ID: <BLjXf.5697$Bb3.3701@news.cpqcorp.net>   Timothy Stark wrote:( > Does anyone have a copy of CI780 specs  G    Yes.  That doesn't really help, however, as AFAIK the CI specs have   never been made public.    ------------------------------  # Date: Sat, 01 Apr 2006 01:04:00 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>9 Subject: Re: Device Naming: (was OPA0 Console connection) 2 Message-ID: <4kkXf.5702$N03.1009@news.cpqcorp.net>   John Santos wrote:  E > My systems (work, personal, customer systems we manage) use logical I > names for all disks and tape drives, usually things like "CD0:", "CD1:" J > for the CD drives, etc., defined with /tran=concealed at system startup,E > so the users don't see the hardware names, and if a system reconfig J > changes them we just need to change one command file.  This works prettyJ > well, except in a few cases where the hardware names intrude and confuseI > people.  This is in places like ANA/ERROR, DIAGNOSE, SHOW DEVICE, etc., 7 > and in OPCOM messages (Shadowing, mount-verify, etc.)  ....  I    I've been using SYLOGICALS.COM and/or MSCPMOUNT.COM for this task for   some eons, now.   H    There might well be a case for adding tools here for managing larger H or more volatile storage configurations (eg: hundreds of disks or more, H or frequent reconfigurations, and a tool that also handle device mounts E and such), but a stack of DEFINE commands needed for the usual dozen  A disks hasn't ever really bothered me.  It's simple, and it works.   I    I also tend to prefer to use the DISK$volnam logical names, and these  B are created automatically by MOUNT.  ALternatively, data-specific F concealed rooted logical names.  This approach disconnects the device I name -- which is what the device-specific logical names -- from the disk  C volume contents.  The device name (whether a logical or a physical  F device name), after all, is far less interesting than the disk volume.   ------------------------------  % Date: Fri, 31 Mar 2006 17:28:11 -0800 # From: "Tom Linden" <tom@kednos.com> 9 Subject: Re: Device Naming: (was OPA0 Console connection) ) Message-ID: <op.s7a2c9jtzgicya@hyrrokkin>   L On Fri, 31 Mar 2006 17:19:27 -0800, Hoff Hoffman <hoff-remove-this@hp.com>   wrote:   > David J Dachtera wrote:  >> Tom Linden wrote:J >>> I understand your comments, never-the-less  it should be possible to   >>> use H >>> names for the devices which are nmemonic,  after all VMS certainly  	 >>> knows  >>> what it has, >  > K >    OpenVMS does read strings where the devices return them, but not all   J > devices have that construct.  And what you get back from those devices  , > that do return strings can look like this: > # >    Output device vendor: HL-DT-ST 1 >    Output device product name: DVD+RW GCA-4040N  > F > But I can't count on the product name containing the type of device.  K No, but you could have a table that provided the translation. As a matter    of fact J you could make this table available from a download site, as it would be   updated K  from time to time.  A sort of plug and play service.  Provide drivers as    well if  not shipped with VMS.    >  > G >>> I shouldn't have to figure out which device is the CD and which the " >>> DVD or the Floppy or whatever. >>  Well, let's explore that. K >>  Suppose we have something which probes the various SCSI and IDE devices 9 >> and examines the various identity strings they return. 5 >>  DKA500 says its and RRD45. Okay, that's a CD-ROM. ( >>  BUT WAIT!! DKB400 says its an RRD42! > G >    And there are devices that do not return this sort of information.  > K >    The device name returned is up to the device vendor, and there can't   J > be a translation from all those strings -- basically an ever-expanding  I > and free-form set -- is not possible.  And how do you translate those   6 > names into the preferred "CD" or "DVD" or otherwise. > K >    Things get more interesting when you try to figure out what a device   H > is based on smaller units of information returned from the drive, as  K > even though there are generic device type codes within MMC devices, for   K >   instance, the particular personality depends on what media is loaded.   L > (And do you call drive that's part of a robot a CD or a DVD device, or a  B > device that's a CD and a DVD and a DVD+R DL, or something else?) > G >    This problem all gets very complex, and it accordingly gets ugly   L > quickly.  (And if y'all can think of a way to code this up, I'm happy to  K > see if I can provide a field test site or two for your code, or to ship   5 > it out via the next OpenVMS Freeware distro, or...)  >  >    ------------------------------  # Date: Sat, 01 Apr 2006 01:19:27 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>9 Subject: Re: Device Naming: (was OPA0 Console connection) 2 Message-ID: <zykXf.5703$L%2.4074@news.cpqcorp.net>   David J Dachtera wrote:  > Tom Linden wrote: K >> I understand your comments, never-the-less  it should be possible to use K >> names for the devices which are nmemonic,  after all VMS certainly knows  >> what it has,     H    OpenVMS does read strings where the devices return them, but not all G devices have that construct.  And what you get back from those devices  * that do return strings can look like this:  !    Output device vendor: HL-DT-ST /    Output device product name: DVD+RW GCA-4040N   D But I can't count on the product name containing the type of device.    F >> I shouldn't have to figure out which device is the CD and which the" >> DVD or the Floppy or whatever.  >  > Well, let's explore that.  > I > Suppose we have something which probes the various SCSI and IDE devices 8 > and examines the various identity strings they return. > 3 > DKA500 says its and RRD45. Okay, that's a CD-ROM.  > & > BUT WAIT!! DKB400 says its an RRD42!  E    And there are devices that do not return this sort of information.   H    The device name returned is up to the device vendor, and there can't G be a translation from all those strings -- basically an ever-expanding  F and free-form set -- is not possible.  And how do you translate those 4 names into the preferred "CD" or "DVD" or otherwise.  H    Things get more interesting when you try to figure out what a device E is based on smaller units of information returned from the drive, as  H even though there are generic device type codes within MMC devices, for H   instance, the particular personality depends on what media is loaded. I (And do you call drive that's part of a robot a CD or a DVD device, or a  @ device that's a CD and a DVD and a DVD+R DL, or something else?)  D    This problem all gets very complex, and it accordingly gets ugly I quickly.  (And if y'all can think of a way to code this up, I'm happy to  H see if I can provide a field test site or two for your code, or to ship 3 it out via the next OpenVMS Freeware distro, or...)    ------------------------------  % Date: Fri, 31 Mar 2006 16:04:31 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> - Subject: Re: Device stuck in MntVerifyTimeout + Message-ID: <442D995F.EA7B556@teksavvy.com>    briggs@encompasserve.org wrote: K > If memory serves, the effect of $ DISMOUNT /ABORT is to abort any current  > I/O operations on the drive.    A In this particular case, it will warn you that there is already a % pending dismount and not do anything.   G You can't do a SHOW DEV/FILES on the disk because it is in mount verify G timeout with dismount pending. But if you know the exact file names you F can INSTALL DELETE them. (or INSTALL PURGE , but then the rest of yourG system is also deinstalled and you might as well rebooot). That was one N of the main reasons for my suggestion some time ago of a INSTALL PURGE/DEVICE=  B > What the OP needs to do first is to identify the installed files> > ($ INSTALL LIST) and then uninstall them ($ INSTALL REMOVE).  F LIST hangs because the drive is not accessible from the system's point. of view. (at least this is how I remember it).   ------------------------------  # Date: Sat, 01 Apr 2006 00:50:20 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>- Subject: Re: Device stuck in MntVerifyTimeout 2 Message-ID: <g7kXf.5699$0b3.3980@news.cpqcorp.net>   Jilly wrote:! > Try a DISMOUNT/ABORT against it        Or try an even bigger hammer:  !    DISMOUNT/ABORT/OVERRIDE=CHECKS   I    I've also been known to use the console IPL %xC (IPC) handler, though  E that's generally for the system disk and also only as a last resort.  G (And IPC can only be used with great care in clusters or other similar  F configurations, as it does require halting the system.  If the sanity D timers fire because it's all taken too long, the node will CLUEXIT.)   ------------------------------  # Date: Sat, 01 Apr 2006 00:02:03 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com> Subject: Re: DS10 Hang on boot2 Message-ID: <%pjXf.5694$oa3.4951@news.cpqcorp.net>   FredK wrote:J > Try setting the SRM variable BOOT_RESET to TRUE (or ON or whatever it is > supposed to be).    D    That, and also look at the setting and configuration of the SCSI H buses -- if the bus is iffy, you might get it to work by down-selecting ? the SCSI bus speed.  See the SRM console PK* settings for that.     . > <stuie_norris@yahoo.com.au> wrote in message? > news:1143797649.268876.139140@t31g2000cwb.googlegroups.com...  ... H > Upgrade the firmware on my hobbyist DS10 (thanks for the pointers) andD > successfully installed OpenVMS 8.2 and the patches from the HP web > site.  > H > I have an issue that when I reboot the system from inside the OS usingC > reboot or shutdown with auto-reboot that the machine hangs on the + > restart just after the following message.  ... L > %PKA0, Copyright (c) 1998 IntraServer Technology Inc. PKW V2.1.22 ROM V2.0@ > %PKA0, SCSI Chip is SYM53C875, Operating mode is SE Ultra SCSI > 2 > The systems hangs prior to this console message. > D > %STDRV-I-STARTUP, OpenVMS startup begun at 31-MAR-2006 03:41:57.77 > 1 > However if I repower the machine it works fine.  > " > Any ideas on what is wrong here?  I    If it's not the bus reset, my initial suspicion is that your SCSI bus  F is messed up, but this could easily be the problem that Fred mentions G around the (lack of) an I/O reset.  As for the SCSI bus itself, it can  F be too long, incorrectly terminated, bad cables, contain a failing or 1 unstable device, or could otherwise be scrozzled.   B    This particular sequence is generally also where a system disk C rebuild occurs, if that is needed, but there are a number of other  ' operations that occur within here, too.    ------------------------------  % Date: Fri, 31 Mar 2006 17:00:07 -0800 # From: "Tom Linden" <tom@kednos.com> # Subject: DVD+RW drives on Alpha 8.x ) Message-ID: <op.s7a02hd6zgicya@hyrrokkin>   K I have a Plextor 716A which seems to work in an AXP 8.2 system although I    have yet tried writing    FREJA> sho sysH OpenVMS V8.2  on node FREJA  31-MAR-2006 16:55:24.36  Uptime  8 20:42:03 FREJA> sho dev/full $7$DQA0:  K Disk $7$DQA0: (FREJA), device type PLEXTOR DVDR   PX-716A, is online, file- K      oriented device, shareable, served to cluster via MSCP Server, error    logging       is enabled.  9 Just tried installing a Plextor 740A in an AXP 8.3 system   
 ODIN> sho sys G OpenVMS F8.3  on node ODIN  31-MAR-2006 16:57:29.29  Uptime  0 00:28:30  ODIN> sho dev/full $6$DQA0:   J Disk $6$DQA0: (ODIN) is online, file-oriented device, shareable, served to7      cluster via MSCP Server, error logging is enabled.    Both systems are XP1000's   K Is there an updated list of supported devices?  Is there a driver available  to support this device?    Tom    ------------------------------  % Date: Fri, 31 Mar 2006 18:17:51 -0800 # From: "Tom Linden" <tom@kednos.com> ' Subject: Re: DVD+RW drives on Alpha 8.x ) Message-ID: <op.s7a4n106zgicya@hyrrokkin>   L On Fri, 31 Mar 2006 18:09:47 -0800, Hoff Hoffman <hoff-remove-this@hp.com>   wrote:   > Tom Linden wrote:  >  >> OpenVMS F8.3  on node...  > ... 1 >> Is there an updated list of supported devices?  > ... 6 >> Is there a driver available to support this device? > ...  > I >    There isn't a list of supported recording drives available as yet,   H > though (regardless) this Plextor drive and various other third-party  = > devices are unlikely to be considered officially supported.  > H >    There is no special device driver required.   The OpenVMS optical  J > media recording code uses ordinary SCSI commands and the existing disk  F > device drivers' IO$_DIAGNOSE interface to address the target device.  H How about EIDE drives, like these?  The 716 is clearly recognized by 8.2 as it was on 7.3 on the XP1000.    > G >    There is a PCSI installation kit containing CD and DVD recording   L > software updates and diagnostics past what was shipped in and documented  @ > in OpenVMS F8.3, and yes, the kit includes full documentation. > H >    I will ensure that an email notice around the availability of the  K > PCSI installation kit gets shipped out to the OpenVMS EFT sites -- that   H > whole process is already starting up for the latest set of recording   > bits.  > B >    It has been my experience that there is a not-insubstantial  C > difference among the commands and behaviours of various storage   L > peripherals, even those devices from the same vendor.  These devices are  J > unfortunately not as interchangeable as you or I or others might want.  E > "Compatible", of course, is another word for "different", as that   J > classic comment goes.  (If a device were truely "identical", that term   > would likely have been used.)    ------------------------------  # Date: Sat, 01 Apr 2006 02:09:47 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>' Subject: Re: DVD+RW drives on Alpha 8.x 2 Message-ID: <LhlXf.5706$Hc3.1474@news.cpqcorp.net>   Tom Linden wrote:    > OpenVMS F8.3  on node... ... 0 > Is there an updated list of supported devices? ... 5 > Is there a driver available to support this device?  ...   F    There isn't a list of supported recording drives available as yet, E though (regardless) this Plextor drive and various other third-party  ; devices are unlikely to be considered officially supported.   E    There is no special device driver required.   The OpenVMS optical  G media recording code uses ordinary SCSI commands and the existing disk  D device drivers' IO$_DIAGNOSE interface to address the target device.  D    There is a PCSI installation kit containing CD and DVD recording I software updates and diagnostics past what was shipped in and documented  > in OpenVMS F8.3, and yes, the kit includes full documentation.  E    I will ensure that an email notice around the availability of the  H PCSI installation kit gets shipped out to the OpenVMS EFT sites -- that J whole process is already starting up for the latest set of recording bits.  ?    It has been my experience that there is a not-insubstantial  @ difference among the commands and behaviours of various storage I peripherals, even those devices from the same vendor.  These devices are  G unfortunately not as interchangeable as you or I or others might want.  B "Compatible", of course, is another word for "different", as that G classic comment goes.  (If a device were truely "identical", that term   would likely have been used.)    ------------------------------  % Date: Fri, 31 Mar 2006 20:04:11 -0800 4 From: Alan Frisbie <Usenet02_REMOVE@Flying-Disk.com>' Subject: Re: DVD+RW drives on Alpha 8.x % Message-ID: <1143864127.849698@smirk>    Hoff Hoffman wrote:   E >   There is a PCSI installation kit containing CD and DVD recording  K > software updates and diagnostics past what was shipped in and documented  @ > in OpenVMS F8.3, and yes, the kit includes full documentation.  C Just out of curiosity, why does it only claim to support DVD+RW and 
 not DVD-R(W)?    Thanks,  Alan   ------------------------------  % Date: Fri, 31 Mar 2006 23:26:16 -0600 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> Subject: EMC Clariion CDL 5 Message-ID: <442E0EF8.1469A55@NeOaSrPtAhMlNiOnWk.net>    Folks,  G We have an EMC Clariion CDL (tape library emulator) at work that we are G trying to get working with VMS and Legato (don't go there - this is the G second time we've had something shoved down our throat and been told to ? make it work or else, supported or not; say, "symposium session  submission in the making").   B When these guys first got it zoned in and mapped, SYSMAN's IO LISTB command displayed all the tape devices they were presenting to me.G However, I couldn't actually configure into VMS any drive where the LUN F number was reported as a hex value greater than %X0F. I could enter itC into SYS$DEVICES.DAT, but that was ineffectual. (VMS V7.3-2 + ECOs,  before you ask.)  ) For example, IO LIST would report seeing:   	 Via FGA0:    Target 3 LUN 0 	. 	. 	. Target 3 LUN f Target 3 LUN 10  	. 	. 	. Target 3 LUN 15   E ...and showed the text form WWID (Mfr name, drive/media type and SSN, E basically the SCSI ID string) rather than the numeric WWID we usually @ get from the Quantum SDLT drives (don't have an example handy of either).  ? We should have seen $2$GGA200 for the robot LUN and $2$MGA100 - < $2$MGA120 for the emulated drives. We only got $2$GGA200 andH $2$MGA100-$2$MGA114. The last six drives ($2$MGA115 thru $2$MGA120, LUNs8 %X10 thru %X15) were missing, even though they appear in% SYS$DEVICES.DAT, even after a reboot.   F This all came as no surprise to me, because the LUN numbers %X10 on upF violate the SCSI specification. But, I was hard-pressed to explain theG FG <-> MG <-> MK driver interface in terms that made any sense to them.   D Naturally, they're all viewing VMS as the odd-ball rather than being7 compliant with the FC and SCSI specifications as it is.   D Is there someplace in the doc.'s that I might find, without actually= sifting line-by-line through the entire docset, where this is  documented?   F I've already suggested that one vendor (the VAR) refer the question to; OpenVMS Engineering through their partner support channels.    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  $ Date: Sat, 1 Apr 2006 12:57:12 +08003 From: "Richard Maher" <maher_rj@hotspamnotmail.com> / Subject: Re: exe$alononpage and exe$deanopgdsiz 1 Message-ID: <e0l164$5in$1@news-02.connect.com.au>    Hi Rob,   K > Depending on your exact need, you may be able to make use of the routines J > exe_std$alop1proc/exe_std$alop1imag and exe_std$deap1/exe_std$deap1block if' > you will always have process context.   E It's even easier than that Rob, I always have Image context let alone L process context. Here is my very simple (and I strongly contend very common) requirement: -  K [One of my Exec mode ASTs receives control along with several bytes of data L and needs to pass this on to a user specified routine. Depending on load andL the firing frequency of the Exec mode ASTs, some number of messages could beJ backed up waiting for a chance to deliver them to the User mode ASTs. So IK need some memory that I can allocate from Exec mode and (ideally) free from K User mode. (If you need privilege/inner-mode to free the memory then how to L I determine that the address that the User-mode code is presenting to me, isH mine to free? No facility codes or resource domain identifiers etc, so II think I'll settle for User-alloc/User-free.) Unlike C programmers (quick, L wet the reel!) I choose to free the memory so that I don't have to recommendH stopping/restarting these server processes on a regular basis. Qwerky, IA know :-) LIB$*_VM and LIB$*_VM_PAGE seem ideally suited to such a K requirement but, alas, are deemed too impure for the unsullied inner-modes. G Even if I were to maintain my own free memory-packet queue and keep all I memory UREW I'd still have to validate which memory went back on the free + list. And don't even mention linked-lists!]   J So that's the requirement spec; the Reader's Digest version of which is: -) "I want an inner-mode Malloc and Calloc."   I I took your suggestions and headed off to memoryalc_mon.lis and looked up J your exe$alop1proc and exe$deap1. Looks promising but are they overkill in3 that I don't need the memory to survive image exit?   G I also looked up exe$alop0imag but couldn't see a matching deallocation K routine. (Is it like lib$fis in that once it's in P0 space you can't get it  out?)   E Anyway, let's bring this game to a head - I "accuse" exe$alopaged and 6 exe$deapgdsiz in the conservatory with Kernel Mustard?  5 But I think I'm wrong for all the following reasons:-   K 1) Do these routines just round up to page boundries and offer no more than  $expreg/$deltva anyway?   G 2) It looks like thse routines can be called from Exec or Kernel but if I there is no unprivileged user-mode way to achieve what exe$deapgdsiz does G then I'm just giving some vandle a spray-can to go "free"ing up bits of  memory.   ) 3) Who'd get to re-use the memory anyway?   1 4) What is the protection on the pages allocated?   F So my conclusion is that this is all too bloody hard! If anyone in VMSI engineering gave a rat's arse about this desperately needed functionality L then we would've been able to call out to *absolutely any* sensible run-timeJ library let alone the lovely LIB$*_VM* decades ago! Don't tell me it can'tK be done! You can port VMS to Alpha and then IA64 and change scheduling from E a Process basis to a Kernel Thread basis and then change security and J privilege checking to a Persona basis, yet you can't sure up a call out to' an RTL? You're 'avin' a laugh ain't ya?   J For me, I'll just ask for a new parameter MAX_INTERRUPT_SPACE in pages. IfL the limit is exceeded then a message is logged and the interrupt is ignored.K The user can always increase the limit and stop/start the server. Ho-hum. .  .yawn. .   Regards Richard Maher   ; "Rob Brooks" <brooks@cuebid.zko.hp.nospam> wrote in message & news:zzFJSbnAoAgN@cuebid.zko.hp.com...9 > > "Richard Maher" <maher_rj@hotspamnotmail.com> writes:  > > H > > Please help with the following questions and supply any other useful advice4 > > you can when it comes to calling these services. > K > Depending on your exact need, you may be able to make use of the routines J > exe_std$alop1proc/exe_std$alop1imag and exe_std$deap1/exe_std$deap1block if' > you will always have process context.  >  > --   > 1 > Rob Brooks    VMS Engineering -- I/O Exec Group  brooks!cuebid.zko.hp.com   ------------------------------  $ Date: Sat, 1 Apr 2006 13:40:07 +08003 From: "Richard Maher" <maher_rj@hotspamnotmail.com> / Subject: Re: exe$alononpage and exe$deanopgdsiz 1 Message-ID: <e0l3mj$94q$1@news-02.connect.com.au>    Hi Rob,  > ; > You really should get a copy of the source listings . . .   H Yes I do have access to the bloody haystack thanks very much, but beforeL someone's next smug recommendation to "well look it up" may I kindly requestF that they narrow the search down to say maybe the North-East corner orL betwen 8 and 9 o'clock or perhaps even "lines x to y in [util.lis]fred.lis"?J How about going way out on a limb and saying "Module ABC will tell you allL you need to know about XYZ". But rather than placing an additional hurdle orL obstacle in the way, that would be an attempt to impart knowledge to a widerL audience and nuture a thriving development community such as one may find inK *NIX or Windows, we can't have that now can we? We'll have no trouble here! H This is a HP shop for HP people! You musn't touch Tubbs' shiny things. .H .not the precious, shiny inner-modes! We wouldn't want to . . .burn you.  H > Is this VAX-only, Alpha-only, I64-only, or for multiple architectures.  . VAX and Alpha (but let's not rule out Itanium)  H > If the VAX is not involved, I'd CALL the exe_std form of the routines, pushing K > the params on the stack, thereby not needing to shuffle registers around.   H Did anyone miss that? Rob siezed on yet another opportunity here to tellB everyone that Macro is crap and C is great! Go on - tell us again.  ( "shuffle registers around"? You kill me.   Regards Richard Maher   ; "Rob Brooks" <brooks@cuebid.zko.hp.nospam> wrote in message & news:sthfBiA5k1Za@cuebid.zko.hp.com...7 > "Richard Maher" <maher_rj@hotspamnotmail.com> writes:  > H > > Please help with the following questions and supply any other useful advice4 > > you can when it comes to calling these services. > ; > You really should get a copy of the source listings . . .  > H > Is this VAX-only, Alpha-only, I64-only, or for multiple architectures. > H > If the VAX is not involved, I'd CALL the exe_std form of the routines, pushing K > the params on the stack, thereby not needing to shuffle registers around.  >  > --   > 1 > Rob Brooks    VMS Engineering -- I/O Exec Group  brooks!cuebid.zko.hp.com   ------------------------------  $ Date: Sat, 1 Apr 2006 14:27:15 +08003 From: "Richard Maher" <maher_rj@hotspamnotmail.com> / Subject: Re: exe$alononpage and exe$deanopgdsiz 1 Message-ID: <e0l6ev$d1q$1@news-02.connect.com.au>    Hi Ian,   5 > I would stick with the exe_std$ version if you can.   
 Et tu Ian :-(   F Autodecrement mode appears to come in handy when tackling the standard' headers that you use in non-paged pool.   G > The raising of IPL to at least ASTDEL is so your process does not get : > deleted and therefore the allocated pool is never freed.  L But surely it follows from what you've just written that you can never lowerK IPL again untill the non-paged pool memory has been freed? Much of the code E I've seen lowers IPL immediately after calling exe$alononpaged so the I process could be zapped. Are you saying that, in these circumstances, the L memory is never freed? Should there be a kernel-mode rundown handler to free up all allocations?   J In my travels, I never found a exe$al* routine that said it must be calledI at higher than IPL zero. Several said that they can be called from either J Exec or Kernel mode and from IPL 0 or IPL$_ASTDEL but not above IPL$_POOL.J The mode and IPL are raised, by the allocation routine itself, as and whenJ needed. If elevated IPL is not maintained until the deallocation then what. is the point of raising it in the first place?  E > I would always have a standard header on the structure in non-paged E > pool (two longwords for pointers, size and type).  I think you need  > this to use exe$deanonpaged   G Yes you do, but I believe you don't need it for exe$deanonpgdsiz. (Just J "shuffle" the address into R0 and then somehow manifest the length into R1J before crossing one's fingers and hop-skip-jmping to G^wing_and_prayer andH you're home. I just wish VMS engineering could spend the money coming upH with some sort of C friendly shell wrapper routines that could hide this7 laberynth of spaghetti-code from our disapproving gaze)    Regards Richard Maher   + "Ian Miller" <ijm@uk2.net> wrote in message = news:1143628924.357995.252680@i40g2000cwc.googlegroups.com...  > 5 > I would stick with the exe_std$ version if you can. G > The raising of IPL to at least ASTDEL is so your process does not get : > deleted and therefore the allocated pool is never freed. > I > IIRC I think non-paged pool is only writable from Kernel mode but I may  > be wrong.  > E > I would always have a standard header on the structure in non-paged E > pool (two longwords for pointers, size and type).  I think you need  > this to use exe$deanonpaged  >    ------------------------------  % Date: Fri, 31 Mar 2006 22:52:03 -0600 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>( Subject: Re: MOP software for Win/NT/XP?6 Message-ID: <442E06F3.82A8D17D@NeOaSrPtAhMlNiOnWk.net>   "BRANDON, JOHN M" wrote: > / > I have the need for a Windows version of MOP.  >  > Anything out there?   G Not sure it will run on anything later than NT, but if you can find the H client media for Pathworks V4.1 there's a MOP daemon on there that I wasD told could be made to do the job so you didn't have to put a $14,000? MicroVAX in a wiring closet just to boot a server of some kind.    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Fri, 31 Mar 2006 22:58:57 -0600 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>" Subject: Re: OPA0 on DS10L problem6 Message-ID: <442E0891.C58ABDE9@NeOaSrPtAhMlNiOnWk.net>   Tom Linden wrote:  > 7 > On Wed, 29 Mar 2006 17:51:20 -0800, David J. Dachtera / > <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> wrote:  >  > > Tom Linden wrote:  > >>I > >> Using a DB9 null modem cable I can connect from a PC using Hyperterm K > >> to either TTA0 or OPA0 on an XP1000, but only TTA0 on a DS10L.  I have J > >> confirmed that the settings for OPA0 are identical for the two.  If I= > >> loop the cable on the DS10L from TTA0 to OPA0 I can both  > >>- > >> SET HOST/DTE OPA0  and SET HOST/DTE TTA0  > >> > >> Any ideas?  > > " > > I'm not clear on the question. > > L > > Can you get the serial console on the DS10L? Which COM port is it on? Is! > > there more than one COM port?  > > I > > If DECwindows loads at startup, try disabling that and see if the COM  > > port becomes OPA0. > > : > > Just a guess... Don't have a DS10L to experiment with. > >  > J > The problem is that I can't connect to the OPA0 port (COM2) on the DS10LM > but can to the TTA0 port (COM1) on same machine from a W2K using Hyperterm.  > D > This works with an XP1000 with identical settings, as displayed byI > SET TERM/FULL OPA0.  This has nothing to do with DECWindows.  Typically F > when you connect in this manner you will get a console login prompt.  C I think I'm being confused by the use of the word "connect" in this  context.  G It seems like you're saying that a DB9 <-> DB9 null modem cable between 0 two Alphas works but not from the Alpha to a PC.   First guess time: pinouts?  G Another possible guess would be that perhaps the PC terminal program is A expecting the modem control signals DTR, CD, CTS and/or RTS to be H asserted. They likely aren't. VT terminals had a setting for "data leadsH only". See if the terminal program has a similar setting. It may just beE as simple as selecting XON/XOF flow control rather than hardware flow  control.  3 Too bad you don't have a real VT terminal to try...    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Fri, 31 Mar 2006 14:26:00 -0700 " From: GreyCloud <mist@cumulus.com>7 Subject: Re: Opinion: I was just trying to sell OpenVMS 0 Message-ID: <d_mdnfmkFcb3A7DZRVn-rg@bresnan.com>   Michael Kraemer wrote:   > Bob Koehler schrieb: >  >>F >>    While VMS is not immune to social engineering attacks, I'm quiteA >>    sure none of my VMS users knows the administrator password.  >> > I > Well, the VMS boxes (VAX and alpha) I have "inherited" for hobbyist use  > were quite easy to "crack". B > Once you have access to the console you can apply the published F > procedure to reset the SYSTEM password and the box is at your hands.H > I didn't even need original OS media for that (as I would have needed  > e.g. for AIX). >   H Yet no one could crack VMS at the Las Vegas DEFCON trials.  How is that?     --   Where are we going?   And why am I in this handbasket?   ------------------------------  % Date: Fri, 31 Mar 2006 14:29:32 -0700 " From: GreyCloud <mist@cumulus.com>7 Subject: Re: Opinion: I was just trying to sell OpenVMS 0 Message-ID: <d_mdnfikFcaiArDZRVn-rg@bresnan.com>   Bob Koehler wrote:  \ > In article <e0ioeq$c5i$00$1@news.t-online.com>, Michael Kraemer <M.Kraemer@gsi.de> writes: > I >>Well, the VMS boxes (VAX and alpha) I have "inherited" for hobbyist use  >>were quite easy to "crack". B >>Once you have access to the console you can apply the published F >>procedure to reset the SYSTEM password and the box is at your hands.H >>I didn't even need original OS media for that (as I would have needed  >>e.g. for AIX). >  > 4 >    No OS overcomes the need for physical security. > F >    Every OS I've ever dealt with had some way of recovering from theE >    equivalent of lost administrator password.  Not a single one was D >    immune to the expedient of sticking it's system disk in another1 >    computer running the same OS as a data disk.  > F >    Your skills at getting into AIX are a little weak if you need the >    OS distribution.  > E >    At least with VMS I don't have to worry about loosing the entire E >    setup on an operational system if the admin staff quits one day.  >       C I'd say that the biggest security concerns are those accessing the  1 internet thru a web browser and the email client. < The only email client that I know of that is insecure is OE.D IE has other problems.  Having ActiveX running in IE is another big I security hole.  Also in OE, receiving email and receiving a virus at the  E same time that will execute on a machine without user interaction is  B another security hazard.  That's why I got rid of two billy boxes.     --   Where are we going?   And why am I in this handbasket?   ------------------------------  % Date: Fri, 31 Mar 2006 14:39:16 -0700 " From: GreyCloud <mist@cumulus.com>7 Subject: Re: Opinion: I was just trying to sell OpenVMS : Message-ID: <1PGdnQOgy6UaPLDZnZ2dneKdnZydnZ2d@bresnan.com>   Dave Froble wrote:   > GreyCloud wrote: >  >> Dave Froble wrote:  >> >>> GreyCloud wrote: >>>  >>>> Dr. Dweeb wrote:  >>>>L >>>>> History has shown that attempting to market/sell *anything* against anF >>>>> M$ product is incompatible with a business relationship with M$. >>>>> L >>>>> There is nothing in M$ business practices since the monpoly conviction5 >>>>> that suggests that it is any more viable today.  >>>>> I >>>>> It's not about size of the goulies, but the desire to retain them !  >>>>>  >>>>J >>>> That is the biggest obstacle today in competition with M$.  The only J >>>> leverage is the reputation of OpenVMS security and the insecurity of I >>>> M$ windows.  Constant repitition of pointing this out to the public  D >>>> could sway the pendulum.  And that will take a hefty marketing  >>>> campaign budget.  >>>> >>> E >>> As long as HP has a rather large business of selling windoz PCs,  I >>> there is no way they will allow a small part of the company publicly  . >>> trash their products.  Ain't gonna happen. >>>  >>J >> I was thinking more along the lines of repeating the point that VMS is F >> not hackable and is secure.  Sometimes the public has a very short 7 >> memory.  You see this tactic in TV ads all the time.  >>G >> If M$ can't put out Vista next year or possibly never, then HP will  H >> have a dwindling product line.  What they do then is anybodies guess. >> >> > B > Security is not an advantage unless consumers see the competing G > offerings as not having security, that security is a good thing, and  K > that they're willing to value security higher than other things, such as   > playing games. >   8 A very good point that needs to be pushed to the public.D I've seen many Seattle Times articles appear where people just Dump F their cheap Dells into the trash can for another Dell due to PCs that C just start to get slower and slower from malware from the internet.   C One fellow at Costco took back a new iMac G5 because he said there  F weren't any Anti-virus software for it.  I told him you don't need it I for these machines, just the M$ versions need it.  He was happy and left   with his iMac.  D > To push the security button, effectively, you'd have to point out E > defincincies (can't spell, and spell checker was no help) in other   > competing products.  >   G There is one big item that consumers need to know about and that is id  H theft.  Another one is the use of wireless connections where others can B just hop onto their connection and use it.  And of course another D article in the Seattle Times about this problem was printed as well.G In time people will get the idea, but it will be a painful lesson when   they do learn it.        --   Where are we going?   And why am I in this handbasket?   ------------------------------  % Date: Fri, 31 Mar 2006 14:47:25 -0700 " From: GreyCloud <mist@cumulus.com>7 Subject: Re: Opinion: I was just trying to sell OpenVMS 0 Message-ID: <8oidnZluaKjtPrDZRVn-jw@bresnan.com>   davidc@montagar.com wrote:   >>People don't buy Windows,  >  > I > Actually - they do.  Most business request Windows to be shipped on the F > box, since that's what will run their existing applications.  That'sE > what they can deal with, since often, they do not even have an "IT"  > deptartment at all.   F Mostly due to what they are most familiar with, and not realizing the C risks involved.  Those that have attended classes on computer risk  : analysis will soon realize the mistake that M$ windows is.  5 >  I seen RFP's, and they require Windows.  Not Unix, G > not OS X, not OpenVMS.  I've even tried to sell Linux sometimes, even F > though it would work exactly identical to the Windows box (actually,I > faster), and they still said no.  Few understand that the market is not B > just a "Field of Dreams", where if you build it, they will come.H > OpenVMS is not the solution by itself. People here, with their love of% > OpenVMS, seem to miss this somehow.  > G > You have to have a solution.  You have to sell the solution.  OpenVMS F > is incidental, and irrelevant, if you can't present a solution.  AndH > since OpenVMS doesn't have a WIN32 API, nor can it run ELF binaries, a1 > 8086 port of OpenVMS alone doesn't make a sale.  > D > Take a web hosting business.  They probably run Windows and Linux.F > Show then OpenVMS.  They don't care.  Show them OpenVMS with Apache,D > PHP, and MySQL, and you can at least hold their attention.  You'veE > provided them a solution that meets their needs.  Then you can show I > them clustering, security and disaster tolerance, and demonstrate value  > added.  > The clustering and disaster recovery scenarios are in need of G demonstrations.  I don't know a any clustering software that is mature  9 on M$ windows products, let alone real disaster recovery. = Gates is just now pushing into that arena, so time will tell. H If Gates does succeed in securing down Vista and provide the rest, then F all other o/ses will soon fade away into history, except for Linux...  free is hard to pass up on.    > I > What people here don't realize, is that sometimes it isn't Windows that E > sells Windows.  It's MS Office that sells Windows.  It's SQL Server F > that sells Windows.  It's Exchange that sells Windows.  And it's not > just MS apps, either.  > F > You get OpenOffice on OpenVMS, PostgreSQL on OpenVMS, Thunderbird onI > OpenVMS, and take advantage of Samba on OpenVMS, and you can compete on @ > function - security is the bonus.  But if you can't compete onF > function, you can't make the sale.  Gnome or KDE on OpenVMS would beF > cool, since it's a usable, familiar enough, and provides a good tool > set. >   A It would still be the same uphill road that Apple took with OS X. G Before M$, there was CP/M.  Back then, when the first IBM PC came out,  G some people said "Where is the software tho?"  That came later and the  H rest is history.  Funny that most people can't pick up on those lessons.  F > You want a Desktop VMS system?  Help out with the OpenOffice port toI > OpenVMS.  They could use the help.  Get Thunderbird working on OpenVMS. F >  Don't just whine about what you think HP should do - be part of theG > solution.  Pick a tool, library, application, no matter how small and  > make it work.  >   F But first you need a low cost platform to run OpenVMS on.  DEC almost H got there with the 4000vlc.  Then Compaq entered the scene and the rest 6 is history.  Again... if Apple can do it, why not HP??     --   Where are we going?   And why am I in this handbasket?   ------------------------------   Date: 31 Mar 2006 22:28:10 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)7 Subject: Re: Opinion: I was just trying to sell OpenVMS + Message-ID: <495onqFnar1jU1@individual.net>   0 In article <d_mdnfmkFcb3A7DZRVn-rg@bresnan.com>,% 	GreyCloud <mist@cumulus.com> writes:  > Michael Kraemer wrote: >  >> Bob Koehler schrieb:  >>   >>> G >>>    While VMS is not immune to social engineering attacks, I'm quite B >>>    sure none of my VMS users knows the administrator password. >>>  >>  J >> Well, the VMS boxes (VAX and alpha) I have "inherited" for hobbyist use >> were quite easy to "crack".C >> Once you have access to the console you can apply the published  G >> procedure to reset the SYSTEM password and the box is at your hands. I >> I didn't even need original OS media for that (as I would have needed   >> e.g. for AIX).  >>   > J > Yet no one could crack VMS at the Las Vegas DEFCON trials.  How is that?   G Because nobody there had any experience with VMS.  Because most of them I had probably never even heard of it.  And mostly because they really just L didn't give a damn about VMS.  Now, can we finally put this canard to rest!!   bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  % Date: Sat, 01 Apr 2006 02:26:49 +0100 ( From: Michael Kraemer <M.Kraemer@gsi.de>7 Subject: Re: Opinion: I was just trying to sell OpenVMS / Message-ID: <e0khc7$n4v$02$1@news.t-online.com>    davidc@montagar.com schrieb:H > About the only way around that is to use the BIOS passwords and encypt > your disks.     + I guess people would be reluctant to use it 1 because they'd not be able to recover their disks  once the password is lost.< IIRC VMS boxes have the possibility to use console password.1 But the docs also indicate that you're in trouble 1 if that one is lost. Call field service and such.   : > You have to enter the password at every boot, but you're2 > much more secure if someone has physical access. >   6 Or use physical keys handed out to trustworthy persons (admin and deputy) on site. ) Key position "normal": boot in user mode, D Key position "service": boot in maintenance ("conversational") mode.5 That's roughly the way the old IBM RS6K boxes worked.    ------------------------------  % Date: Sat, 01 Apr 2006 02:30:44 +0100 ( From: Michael Kraemer <M.Kraemer@gsi.de>7 Subject: Re: Opinion: I was just trying to sell OpenVMS / Message-ID: <e0khjb$n4v$02$2@news.t-online.com>    Bob Koehler schrieb: > F >    Your skills at getting into AIX are a little weak if you need the >    OS distribution.   4 Well, I followed the "official" route in both cases.   ------------------------------  % Date: Sat, 01 Apr 2006 02:43:38 +0100 ( From: Michael Kraemer <M.Kraemer@gsi.de>7 Subject: Re: Opinion: I was just trying to sell OpenVMS / Message-ID: <e0kibo$p9l$02$1@news.t-online.com>    GreyCloud schrieb: > J > Yet no one could crack VMS at the Las Vegas DEFCON trials.  How is that?  2 That's nothing, because it doesn't prove anything,; except that at that particular event people didn't succeed. , And as others (e.g. BillG) have pointed out,/ the most probable reason is, that those hackers + simply are not interested in an obscure OS. 3 Anyway, following scientific logic, you can't prove 2 that something doesn't exist, e.g. a hack for VMS.5 You can't even prove that Santa Clause doesn't exist. J (Although Santa Clause's existence is much less likely than a hacked VMS)., If you want to do your favorite OS a favour,6 don't come up with that old story over and over again.E Better find something positive, more visible to a potential end user.    ------------------------------    Date: 31 Mar 2006 20:40:10 -0800 From: davidc@montagar.com 7 Subject: Re: Opinion: I was just trying to sell OpenVMS C Message-ID: <1143866410.381116.151400@v46g2000cwv.googlegroups.com>    GreyCloud wrote:G > But first you need a low cost platform to run OpenVMS on.  DEC almost I > got there with the 4000vlc.  Then Compaq entered the scene and the rest 8 > is history.  Again... if Apple can do it, why not HP??  A That's easy.  Download SIMH from trailingedge.com, run it on your D Windows/Linux system if you have to, and get some Hobbyist Licenses.E $0.  The Hobbyist License is perfectly acceptable for contributing to E Open Source projects.  You don't need to have Alpha/IA64 binaries for G the first port, if you get the port to work on VAX, I'm sure there will : be many volunteers to crunch out some Alpha/IA64 binaries.   ------------------------------  % Date: Fri, 31 Mar 2006 15:39:23 -0500 ' From: "Main, Kerry" <Kerry.Main@hp.com> = Subject: RE: SAP small business solutions now run on OpenVMS! T Message-ID: <FA60F2C4B72A584DBFC6091F6A2B86840118E82C@tayexc19.americas.cpqcorp.net>   > -----Original Message-----8 > From: Markus D=F6hr [mailto:wantbottom@t-online.de]=20 > Sent: March 31, 2006 1:16 PM > To: Info-VAX@Mvb.Saic.Com ? > Subject: Re: SAP small business solutions now run on OpenVMS!  >=20 > bob@instantwhip.com wrote:@ > > that is what I was told by a salesman who called ... if true4 > > then excellent news ... can you verify this Sue? > >=20 >=20E > I have access to the sap service network and I haven't found ANY=20  > information about that.  >=20J > SAP has a new version of the VMS (=3D Vehicle Management System) in a=20; > RampUp for customers, maybe that was as misunderstanding.  >=20E > However, there are some libraries to develop but nowhere is told=20 . > anything about SAP beeing ported to OpenVMS. >=20 > --=20  > Markus >=20  ; No idea of what the real story is, and it may indeed be a =  misunderstanding, but -   G Just a WAG, but if this was written in 100% Java (as I have seen many = @ ISV's doing), then it may be possible to run this on OpenVMS.=20  F Like other app environments, J2EE app's usually still need to be put =J through the vendor certification process. However, this process is much, =E much less than full native port and often just requires pre-defined = : scripts to run successfully in pre-determined time frames.   Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  4 OpenVMS - the secure, multi-site OS that just works.   ------------------------------    Date: 31 Mar 2006 17:24:06 -0800) From: "Sue" <susan_skonetski@hotmail.com> B Subject: Updated VMS information - Excellent Partner information -C Message-ID: <1143854646.775532.122880@g10g2000cwb.googlegroups.com>    Dear Newsgroup,   D In this weeks update there is all kinds of information that you willE find useful and beneficial.  Let's talk about what is in this message F because there is so much.  If you are a Partner PLEASE PLEASE TAKE THE TIME TO REVIEW SECTION 8  G Have a wonderful weekend and thank you for the support and kindness you  show every day.   
 Warm Regards,  Sue     B 1=2E Time Sensitive FREE Webinar from PARSEC, Managing Transition:D Maximize your OpenVMS IT Investment with HP Integrity Servers, April 5th   H 2=2E Announcement from VMS Engineering - updates to the Performance Data	 Collector   D 3=2E Encompass Event in Montreal with a free gift to the first 50 to register  C 4=2E Sue's Fav's my favorite URL's that I have either found or been ) pointed to lately (useful or fun or both)   H 5=2E Golden Eggs -  This is the first time when HP Integrity Servers can  share a small SCSI based cluster  F 6=2E New on www.OpenVMS.org forums where to can communicate with otherG folks in the VMS community (not really new, it upgraded, but its new to  some).  I 7=2E In the Press - VMS mentions in the Press and there are a lot of them 
 this week.  H 8=2E **** For our Partners this section contains very useful informationD to Partners and can help save you big money and help you with leads. Well worth your time. **  F 9=2E From our Partners - Announcement from CA Unicenter=AE Network and> Systems Management System Monitoring Option for OpenVMS I64 r3     1=2E Time Sensitive   D PARSEC Group, HP, and CA would like to invite you to sign up for ourF FREE Webinar, Managing Transition: Maximize your OpenVMS IT InvestmentF with HP Integrity Servers, to be held on April 5, 2006, from 2:00 p.m. - 3:00 p.m. EST.= With the arrival of high performance HP Integrity servers and G availability of a host of applications, transition to Itanium has to be A in your planning horizon. Justifying and making this move without F compromising your business and ensuring that you gain maximum benefitsG from your investment require planning. Fortunately, help is on the way! G This live, interactive Web cast will help you navigate the Itanium road D map. You'll also have the opportunity to ask questions to the HP, CAF and PARSEC Group professionals who can help you meet the challenges ofF providing business justification for the transition, opportunities forD server consolidation to gain significant savings as well as managingF and effectively deploying your business-critical OpenVMS systems. Join> HP's John Egolf, CA's Prabhakara Bhat, and PARSEC Group's RussB Baldermann for a one-hour live Web cast. Our panel of experts will6 discuss: The road to Itanium,Business value of ItaniumC adoption,Seamless management, Planning considerations, Services for  optimum deployment,   @ Register today for Managing Transition: Maximize your OpenVMS IT6 Investment with HP Integrity Servers by clicking here.5 http://www.parsec.com/general/promotion.php?p=3D9T18K   ( ________________________________________  % 2=2E Announcment from VMS Engineering   F OpenVMS Engineering is pleased to announce the availability of two new> updates to the Performance Data Collector for HP OpenVMS (TDC)9 software. Both are now available from the web site at URL 2 http://h71000.www7.hp.com/openvms/products/tdc/=20  B TDC Version 2.1-84 is a maintenance-only update to the Version 2.1F product. It corrects two critical problems (possible system crash whenD invoking spinlock tracing while a TDC collector is running; creatingF huge log files when some TDC error conditions are encountered during aG collection) as well as a small number of data quality issues (disk-busy : counts, process memory use, network interface I/O, and XFC statistics-reset time).   E TDC Version 2.2-105 is a maintenance and limited-functionality update G to the product. In addition to the fixes provided by Version 2.1-84, it 5 addresses additional data quality issues as well as a B "%TDC-E-INITERR, IPC startup failed: 2544" error seen occasionallyF when starting a detached TDC collector process. Version 2.2 introducesC several new data records and extends the /LOG qualifier to accept a = file specification. Version 2.2 also provides a number of new B programming features to facilitate processing of TDC data records:B sorted views of many records; a function to match records from theG current snapshot with corresponding records from the previous snapshot; C a function to return "delta" records that reflect changes in values @ between snapshots; a function to follow record links; additionalA processor module capabilities; additional item codes for use with ( TDC_GET_INFO(); and updated sample code.  C If you are using TDC with Enterprise Capacity and Performance (ECP) A Version 5.5A, you should download the TDC Version V2.1-84 update.   E For any other use of TDC, you should download the TDC Version 2.2-105  update.   ? If you are participating in the OpenVMS Version 8.3 field test:   A =B7	The downloadable TDC Version 2.2-105 kit contains appropriate  runtime software. E =B7	TDC Version 2.1-84 runtime software can be requested via email to  VMSTDCV2    @ HP expands OpenVMS product availability with the addition of new@ capability and new software products for OpenVMS on HP Integrity servers   # ___________________________________    3=2E Encompass  D FREE OpenVMS T-SHIRT TO FIRST 20 THAT REGISTERS FOR MONTREAL SEMINARE The first 20 registrations received for the Montreal seminar on April E 25, 2006 will each receive an OpenVMS T-shirt from HP.  Registrations @ have been coming in since last week and seating for the event isE limited, so don't wait until the last minute to sign up.  Please note C that registrants must be present at the event to receive their free 	 T-shirts. + http://www.encompasscanada.com/seminars.htm   ! _________________________________    4=2E Sue's Fav's   http://tinyurl.com/jayyl Or  K http://h71028.www7.hp.com/ERC/cache/49205-0-0-0-121.aspx?bodycontentparams= < =3D313885-0-0-0-121&ERL=3Dtrue&jumpid=3Dem_CTmar06_feature04B HP set the 'gold standard' for reliability and now brings you more  L http://h71000.www7.hp.com/openvms821_announce.html?jumpid=3Dem_lightning|op= envms|in_newsletter   A http://h71000.www7.hp.com/openvms/integrity/integrity_gwm.html HP C Integrity Essentials Global WorkLoad Manager v1.1 for OpenVMS on HP ) Integrity servers and AlphaServer systems   @ http://www.migrationspecialties.com/Porting.html OpenVMS Porting Services   _______________________________   H 5=2E Golden Eggs -  This is the first time when HP Integrity Servers canD share a small SCSI based cluster storage for small business criticalE solutions. Total 4.2TB of disk storage in a small 3U rack space.There D are thousands of existing Alpha customers waiting for this IntegrityF driven Cluster. It is small in size, just total 7U rack space for full@ cluster of dual rx2620-2 Integrity servers.Even more dense entry= cluster with rx1620 hosts fit in 5U space with 4.2TB of disk.   F Direct link to: HP MSA30-MI Dual SCSI Cluster, rx1620, rx2620, rx4640,: 1page http://goldeneggs.spyderbyte.com/geggs/GTMSA30MI.pdf  ' The full Golden Eggs basket in service: ! http://goldeneggs.spyderbyte.com/   " __________________________________  C 6=2E From www.OpenVMS.Org - Ken has upgraded the forums and the new D forums are active: The forums have been upgraded to prevent spam and foul types of messages.    ______________________________   7=2E In the Press   E http://press-releases.techwhack.com/2350/arches-chip-based-solutions/ 6 Hewlett-Packard launches 'Arches' chip based solutions  K http://www.itnewsonline.com/showstory.php?storyid=3D3254&scatid=3D3&contid=  =3D3:  HP Enhances Integrity Server Line, HP-UX Operating System  A http://www.zdnetindia.com/news/hardware/stories/135544.html?s=3D1 # Integrity gets a kick in the Arches   @ http://www.serverwatch.com/news/article.php/3593136 HP Announces Integrity Enhancements  D http://techplanetasia.com/bcm/index.php/article/524 Never turn off a virtual machine   ? http://www.itjungle.com/tug/tug032306-story01.html HP Announces ) High-End 'Arches' Chipset for Integrities   G http://www.linuxelectrons.com/article.php/20060321051106955 HP Upgrades " Integrity Servers with New Chipset  G http://www.serverwatch.com/hreviews/article.php/3594606 Hardware Today: ' HPC Gets as Easy as 1-2-3  by Drew Robb   K http://news.com.com/Welcome+to+HPs+third+Superdome/2100-1006_3-6045653.html  Welcome to HP's third Superdome   D http://www.echannelline.com/usa/story.cfm?item=3D20568   HP enhances Integrity servers    8=2E For Partners   8 *********  Partner  VERY Important Information *********  E DSPP is HP's partner program and it is free to join and there are all F kinds of benefits.  If you are not a DSPP member and you are a partnerF (you provide a service or develop a software product) (large or small)? I highly recommend that you join.  HP has some really wonderful C benefits in this program, and the HP people in the group are really  helpful.  ; Itanium=AE Solutions Alliance (you can save BIG money here) L http://h21007.www2.hp.com/dspp/bus/bus_BusDetailPage_IDX/1,1252,8243,00.html  G Did you know if you are a DSPP member you get free Encompass membership L http://h21007.www2.hp.com/dspp/bus/bus_BusDetailPage_IDX/1,1252,3444,00.html  G Did you know for $255 you can build a co-branded data sheet (electronic B only) and for an additional amount order hard copy? Must be a DSPP memberL http://h21007.www2.hp.com/dspp/bus/bus_BusDetailPage_IDX/1,1252,4874,00.html    A HP Solution Demo Portal - a virtual tradeshow - First 50 are free L http://h21007.www2.hp.com/dspp/bus/bus_BusDetailPage_IDX/1,1252,8868,00.html    D 2006 series of HP-Intel Developer Forums - don't miss this chance to3 port your software and get an  HP Integrity server:     L http://h21007.www2.hp.com/dspp/bus/bus_BusDetailPage_IDX/1,1252,6045,00.html  C WIN2WIN contest - report your wins and enter to win an HP Integrity  server :    L http://h21007.www2.hp.com/dspp/OnlineForm/form_OnlineForm_IDX/1,2914,170,00= .html   C OpenVMS Bootcamp Partner Roundhouse - Tuesday, May 23, Nashua, NH - . sign up now for your free table at this event:    : http://h71000.www7.hp.com/symposium/roundhouse_signup.html    L ____________________________________________________________________________    F 9=2E From our Partners (if you need a nicer looking copy please let me know)   F CA is pleased to invite you to participate in the Unicenter=AE NetworkG and Systems Management System Monitoring Option for OpenVMS I64 r3 Beta @ program. Please visit the following site for more details and to register for beta.  K http://supportconnectw.ca.com/public/beta/nsmopenvms31/nsmopenvms31beta.asp    Regards,   Prabhakara Bhat    CA  H Unicenter=AE Network and Systems Management System Monitoring Option for OpenVMS I64 r3   Dear Beta Customer,   F CA is pleased to invite you to participate in the Unicenter=AE NetworkG and Systems Management System Monitoring Option for OpenVMS I64 r3 Beta G program. Your participation offers you the ability to validate this new D product in your own environment, allowing you to give us feedback on3 product enhancements, quality and the beta program.   A Your contribution to this critical product test cycle is directly D related to the success of the generally available (GA) release of CAE products and ensures that we deliver solutions that are ready to meet  your real-world requirements.   C As a participant in the beta program, you will communicate directly F with the Beta Research and Development team to investigate and address- any reported problems, questions or comments.   E Unicenter Network and Systems Management System Monitoring Option for A OpenVMS I64 helps Unicenter NSM discover, monitor and display the F health and availability of critical Itanium based HP Integrity servers? running OpenVMS I64 and application log files residing on those @ systems. It enables you to monitor OpenVMS I64 resources againstB user-defined thresholds and generate policy-based alerts to notify. problems before they can impact your business.   Top Three Key Features:   G =B7       Automatic discovery of OpenVMS I64 systems in your enterprise E and view them in an automatically created Business Process View (BPV)   E =B7       Monitoring the status and performance of OpenVMS I64 System ) resources, log files and log file entries A =B7       Generation of policy-based alerts based on user-defined G thresholds, allowing you to consolidate events from OpenVMS I64 systems F along with those from heterogeneous platforms, correlate them and take necessary actions    What's New:   H =B7       Ability to discover and monitor the health and availability of> Itanium based HP Integrity servers running OpenVMS I64 in your
 enterprise  = =B7       Monitor Integrity servers in homogeneous as well as $ mixed-architecture OpenVMS clusters.  G Get more information and register for the Unicenter Network and Systems C Management System Monitoring Option for OpenVMS I64 r3 beta program   
 Sincerely,  2 Unicenter Network and Systems Management Beta Team   Register Now  E Unicenter Network and Systems Management System Monitoring Option for  OpenVMS I64 r3 More Information    System Requirements  Feedback CA Beta Program Disclaimer  E For more information on CA's Enhanced Beta Programs and Participation + Requirements please visit www.ca.com/betas.   5 CA. One Computer Associates Plaza, Islandia, NY 11749 F This message is a solicitation from CA. To stop receiving such emails, click here.   3 Contact    Legal Notice    Privacy Policy    ca.com + Copyright =A9 2006 CA. All rights reserved.    ------------------------------  # Date: Sat, 01 Apr 2006 00:19:57 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>, Subject: Re: xp1000 boot flags and vms 7.2-12 Message-ID: <NGjXf.5696$Bb3.2231@news.cpqcorp.net>   gobo20@lycos.com wrote:   F > will 7.2-1 work ok unpatched on the xp1000?  i have 7.2-1 on severalI > machines at work.  yeah i know, need to move to 7.3, but getting the ok  > from mgmt...  1    V7.1-2 and ECOs, or V7.2-1 or later, and ECOs.   A    Do ECO it, or do upgrade to V7.3-2 or V8.2, and then ECO that.   F    Yes, you do want and need these mandatory ECO kits.  V7.2-1 may or C may not work for your configuration and your application(s) -- the  E mandatory ECO kits were and are created for various serious problems  & encountered in the release, after all.  H    If this AlphaStation XP1000 series box is a hobbyist system, you can H and likely should acquire the (free) hobbyist licenses and the hobbyist I distribution.  <http://www.openvmshobbyist.org/> is the URL.  If this is  E a commercial (non-hobbyist) system, you will need to transfer and/or  " purchase licenses for this system.  H    Information on the minimum OpenVMS version required for a particular F VAX, Alpha or Integrity server are available at the HP web site.  The @ URL is <http://h71000.www7.hp.com/openvms/hw_supportchart.html>.  >    The URL <ftp://ftp.itrc.hp.com> has the available ECO kits.  '    These and other URLs are in the FAQ.    ------------------------------   End of INFO-VAX 2006.180 ************************                                                            7jO/}WKڞɴ=&$wb)Eh+%S~׵792^tV>(LL+MIH@7Qjw6Fr ƕ ՁޮD'=[kNǴl_-	VEp{#Ez4}>r.@=90l=I$`{q8Yp;
pS/[ Y0ڃ~Ϥ&7-`,}^rXWֱ1bEpQl6Dɯ_:,ҹ5=}ٞMԿ}&_Xl :r#
"t$9(Xy[EvJEb\]a/ܤT<NA@Y[{
hb;U#/,FYCy)
,b[&g0i̔"|b6'vC1fy/C#X> =oT$AxFZtQv(ъKI;:msқ}q3:΀4Ź u9#)3|xdk"5)Ȗ<ZE	]dQ7M;csxۘ"	4ɧ~?L0w d\R$3"6 cCvcQ3+䃱XD]J'W^ԥK2K:"[x.	2J6;Fr#"/97nu'϶?hkT߸҄;<}mHo
:iqyE;&+BM;KJ"1B&>Te{.$GL\KHDbh$QbMs
A޿L@#qll3Gg"~K*u!S",z72ڎ18n
B.8		"_gNy
 &셔V
cY`,_{\[%`޾Sip~qlJkb2(s_9_&va%m_f{(#hۮ1o:5YD'ᷘݸΗaٚ֩~D}d}>4nɍ
g1 x'2W>ebTІ)c]bE 9ĵWɌRFįyLj:wpRAX1f_Tx*J&Ci3ؼ"1?融DC6!V5!ZP#@W[pF~E-O0{5"~>t	}>d1=i{h=˰87ϠŵнG۶TNn=V;Td,N=D#M6ߴ)44xV)WLtL@CH3h;W8z.2!l+D}I