1 INFO-VAX	Mon, 24 Mar 2003	Volume 2003 : Issue 164       Contents:$ Re: 9gig 7200rpm drives in PWS500au?3 Re: An opportunity for HP? (wes: Micromedex on VMS) * Re: Cluster, half in the DMZ, half outside* Re: Cluster, half in the DMZ, half outside* Re: Cluster, half in the DMZ, half outside compatibility problem  Re: compatibility problem   DECNET Object Connection Problem* Re: Determining Serial Port parity via QIO= Re: EFI Specifications (was: I Have Seen The IA64 Future !!!) = Re: EFI Specifications (was: I Have Seen The IA64 Future !!!) = Re: EFI Specifications (was: I Have Seen The IA64 Future !!!) = Re: EFI Specifications (was: I Have Seen The IA64 Future !!!) = Re: EFI Specifications (was: I Have Seen The IA64 Future !!!) @ RE: How to search for last login, but not on disusered accounts.@ Re: How to search for last login, but not on disusered accounts.# Re: I Have Seen The IA64 Future !!! # RE: I Have Seen The IA64 Future !!! # Re: I Have Seen The IA64 Future !!! # RE: I Have Seen The IA64 Future !!! # Re: I Have Seen The IA64 Future !!! # RE: I Have Seen The IA64 Future !!! # Re: I Have Seen The IA64 Future !!! # Re: I Have Seen The IA64 Future !!! # RE: I Have Seen The IA64 Future !!!   Installation faq for VMS on simh% Re: Mark Gorham was Re: Rich Marcello  Re: Micromedex on VMS  Re: One version of a file ONLY. : Re: OpenVMS as a growth platform; and low-cost development+ OpenVMS Pearl Monday March 24 - Announcment P Re: OpenVMS.org: Marvel article and HP's press release for Marveland Alpha Retai/ Re: Remotely opening a window on my workstation  Re: Some Windows ammunition & Re: Sun unix/linux new nasty bug cert!& Re: Sun unix/linux new nasty bug cert!& Re: Sun unix/linux new nasty bug cert!& Re: Sun unix/linux new nasty bug cert!& Re: Sun unix/linux new nasty bug cert!$ Re: System Special for VMS NewsGroup- Terminal driver for VAX synchronous interface 1 Re: Terminal driver for VAX synchronous interface H Re: [Q] Files not found during image backup, w/ and w/o directory-specs.H Re: [Q] Files not found during image backup, w/ and w/o directory-specs.  F ----------------------------------------------------------------------    Date: 24 Mar 2003 10:20:27 -0800, From: mcbill20@hotmail.com (Bill McLaughlin)- Subject: Re: 9gig 7200rpm drives in PWS500au? < Message-ID: <e9cbc4f2.0303241020.9057346@posting.google.com>   David Spencer <spencer@spaamfree.pageweavers.com> wrote in message news:<200320032006200230%spencer@spaamfree.pageweavers.com>... ^ > In article <CIEJLCMNHNNDLLOOGNJIAEDMGNAA.tom@kednos.com>, Tom Linden <tom@kednos.com> wrote: > N > > have 3 IBM 10k dives in a PWS500, which probably run hotter and works fine > >  > > >-----Original Message----- 8 > > >From: Bill McLaughlin [mailto:mcbill20@hotmail.com]) > > >Sent: Monday, March 17, 2003 4:07 PM  > > >To: Info-VAX@Mvb.Saic.Com. > > >Subject: 9gig 7200rpm drives in PWS500au? > > >  > > > K > > >I have a PWS500au with three 7200rom 9 gig drives (Seagate ST39175LW). I > > >The cover has been off so far as I just got the box a week or so ago J > > >and I had to install a second SCSI card, etc. Now that it all works IJ > > >was going to put the cover on and put it in the rack. The side of theH > > >case where the drives are feels pretty warm and I got to thinking--G > > >are these drives supported internally in this box? Anyone else out 7 > > >there with a PWS using these drives? Any problems?  > > >  > > >Thanks in advance.  > > >  > > >Bill McLaughlin > P > I have a similar configuration that runs without problems. Yes, the drives get > hot but that's not unusual.  >  >  > -- Dave Spencer   E Thanks for all the input. I moved one drive from the 3-1/2" slot to a @ 5-1/4" slot to make more room for airflow and I then attached anE exhaust fan to the back behind the 3-1/2" slots and put the cover on. F Everything inside stays pretty cool now. In the future I'll try to get? any drives I add in StorageWorks containers and put them in the < external box instead. I just wish they weren't so expensive.   Bill   ------------------------------    Date: 22 Mar 2003 23:00:59 +0800, From: Paul Repacholi <prep@prep.synonet.com>< Subject: Re: An opportunity for HP? (wes: Micromedex on VMS)- Message-ID: <87smtfh2dw.fsf@prep.synonet.com>   3 "Lonnie Blevins" <lblevins@regenstrief.org> writes:   E > Both IDX and CERNER use (where I have seent them) workstations that D > are WINDOWS machines.  Only the servers are AIX or OpenVMS.  UsersF > still see the WINDOWS interface and think of that as "their system".  F How do they used M$ licencing conditions and conform to HIP<whatever>?   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------    Date: 22 Mar 2003 22:51:15 +0800, From: Paul Repacholi <prep@prep.synonet.com>3 Subject: Re: Cluster, half in the DMZ, half outside - Message-ID: <87wuirh2u4.fsf@prep.synonet.com>   + Bart Zorn <B.Zorn@xs4all.nospam.nl> writes:   F > DMZ is purely a TCP/IP concept. OpenVMS clusters do not use (TCP/)IPE > for cluster communications. If you can configure your router and/or E > firewall to just bridge non-IP packets, a cluster should be able to " > use the network as interconnect.  B DMZ is not just a IP concept, though that is where it is generallyB found. The `DMZ' machines are inside your network, but outside the? fire wall. The idea is that a relayed attach from a compromised F machine will still have to get though your firewall, as will any other external attack.  B For the ultimate in security you could boot from a CD and send all> the log files to  FOO::file.log on the other side of a bridge.  A Having SYS$LOGDEVICE as a standard logical is an even better idea  for this :)    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  + Date: Mon, 24 Mar 2003 16:18:00 +0100 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> 3 Subject: Re: Cluster, half in the DMZ, half outside ; Message-ID: <01KTWQ5XIB42A9LL1B@sysdev.deutsche-boerse.com>   L > > What do you mean here?  The "host" to which one forwards things could be > > the cluster alias!   > 2 > Cluster alias is a DNS "trick" from what I read. > C > Routers, at least the consumer grade ones, route to a specific IP B > address, not a host name. So your inbound call going through the2 > consumer grade router will go to a specific IP.   I Right, but the cluster alias IS an IP address!  SYS$MANAGER:TCPIP$CONFIG  I asks you if you want to define it.  TCPIP SHOW INTERFACE will list it as  G a "cluster impersonator".  It is sort of like a pseudointerface (which  F also has its own IP address) but a) more than one machine can have it H and b) it is only for INCOMING connections; outgoing connections appear I to come from the real address.  (I mean outgoing connections originating  7 on the VMS box, not return traffic from incoming ones.)   G > Now, if you have a real internet connection with your own DNS server, J > then when "foreign" folks want to connect to www.chocolate.com , then itF > is your DNS which will decide to which host in the cluster this will
 > translate.   > A > But when you are in a consumer grade internet connection (read: J > crippled) with a consumer grade router (NAT), then  the cluster alias is > of not much use.    A What you are discussing is a cluster alias implemented in the DNS E server.  This is something completely different.  Here, one can just  F have more than 1 IP address and have round robin.  More sophisticated I schemes due load balancing etc.  On VMS, this is the load broker, metric  < server etc which one can enable in SYS$MANAGER:TCPIP$CONFIG.  2 What I mean is the "cluster alias" as mentioned inH SYS$MANAGER:TCPIP$CONFIG.  This is basically a failover mechanism.  See   the TCPIP docs for more details.   ------------------------------   Date: 24 MAR 2003 17:01:49 GMT4 From: karcher@thuria.waisman.wisc.edu (Carl Karcher)3 Subject: Re: Cluster, half in the DMZ, half outside 6 Message-ID: <24MAR03.17014994@thuria.waisman.wisc.edu>  Q In a previous article, Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> wrote:  ..C ->What you are discussing is a cluster alias implemented in the DNS G ->server.  This is something completely different.  Here, one can just  H ->have more than 1 IP address and have round robin.  More sophisticated K ->schemes due load balancing etc.  On VMS, this is the load broker, metric  > ->server etc which one can enable in SYS$MANAGER:TCPIP$CONFIG.  H As of TCPIP V5.3 (bind 9) it's no longer round robin but random. See the release notes.   --G -- Carl Karcher, Waisman Computing Services, Waisman Center, UW-Madison 5 --              karcher.nomorespam@waisman.wisc.edu      ------------------------------  % Date: Mon, 24 Mar 2003 13:10:23 +0000  From: Atanas <atanas@iec.co.il>  Subject: compatibility problem) Message-ID: <3e7ee797@news.hai.iec.co.il>   M I have AplaServer DS-10 and VMS 7.3 installed. I need to implement interface  L for data acquisition from control system  (PROCONTROL) to Plant Information J System (P.I.) based on ABB's CPS package. CPS require UCX V4.0 and do not J work with new TCP/IP that replaces UCX  starting with VMS 7.2 I installed L UCX 4.0 and CPS and wrote my interface. All works file, but  after 1-3 days L system freezes. I tried to solve the problem upgrading VMS to version 7.3-1 I - now system do  not freeze , just crashes every 30 minutes. Do somebody  H know how is possible to solve the problem without replacing  hardware ?  Thanks.    ------------------------------  % Date: Mon, 24 Mar 2003 12:02:31 +0000 ( From: Nic Clews <sendspamhere@127.0.0.1>" Subject: Re: compatibility problem) Message-ID: <3E7EF3D7.13BB0846@127.0.0.1>   
 Atanas wrote:  > N > I have AplaServer DS-10 and VMS 7.3 installed. I need to implement interfaceM > for data acquisition from control system  (PROCONTROL) to Plant Information K > System (P.I.) based on ABB's CPS package. CPS require UCX V4.0 and do not K > work with new TCP/IP that replaces UCX  starting with VMS 7.2 I installed M > UCX 4.0 and CPS and wrote my interface. All works file, but  after 1-3 days M > system freezes. I tried to solve the problem upgrading VMS to version 7.3-1 J > - now system do  not freeze , just crashes every 30 minutes. Do somebodyI > know how is possible to solve the problem without replacing  hardware ?   G There simply isn't enough information here, and you've effectively told G us what you think your fix will be without permitting a deeper analysis  of your problems.   2 What is the bugcheck your system is crashing with?  D I'm sorry to say this, but I think the problem is most likely in theB interface you've written. If you fully adopted all the programmingB standards and requirements laid down for UCX 4 and VMS at 7.2, youC really should not have a problem. Upward compatibility is generally - maintained when you follow what is laid down.   D Have you tried contacting ABB (whoever they are) about CPS (whateverG that is). Perhaps they have updated versions. Why didn't you upgrade to H TCPIP v 5 when at 7.2? Why didn't you upgrade to 7.3 on the old hardware. if you were migrating a sensitive application?  E I presume you are paying for support, this is the value of paying for D support when upgrading, "big bang" approaches are often fraught withG issues and potential problems. Upgrading the operating system, hardware C and the communications package, you have one of three or a possible ) combination of where the real problem is.   G I know this doesn't really help, and it's all well said with hindsight, ? but the only way you'll fix this is with a 'phased' or 'tasked' A approach. It is almost like buying a brand new car in a different H country, then finding you keep getting lost driving around, is it really the new car's fault? --  ? Regards, Nic Clews a.k.a. Mr. CP Charges, CSC Computer Sciences  nclews at csc dot com    ------------------------------    Date: 24 Mar 2003 04:32:55 -0800+ From: n8pvl@yahoo.com (Christopher Francis) ) Subject: DECNET Object Connection Problem = Message-ID: <7ea798ef.0303240432.2882cd04@posting.google.com>   A We are having a problem with launching a process through a DECNET D network object connection. The connection is made to an object usingA the cluster alias, therefore we could be connecting to any one of F three cluster nodes. On occasion we notice that our process is gettingF started on 2 nodes simultaneously or in close succession. Any ideas on what is going on here?  C  The cluster consists of three DEC 3000 computers running VMS 7.3-1 B and using DECNET Phase IV. No ECO's have been applied. The cluster$ interconnect being used is Ethernet.   Thanks
 Chris Francis    ------------------------------  % Date: Mon, 24 Mar 2003 02:12:59 -0400 0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>3 Subject: Re: Determining Serial Port parity via QIO / Message-ID: <3E7EA1E9.21667D82@vl.videotron.ca>    Stuart Norris wrote: >  > Hello Readers, > A > I am trying to determine the partiy setting on a serial port.     , the parity_flags should give you the parity.  ( Here is some code on setting the parity:   sysparity=0x00000000;    switch (parity) 	         { G         case PARITY_EVEN  :     sysparity = 0x00000000 | TT$M_ALTRPAR ; :                                 sysparity |= TT$M_PARITY ;=                                 sysparity |= TT$M_ALTDISPAR ; =                                 sysparity |= TT$M_DISPARERR ; &                                 break;  G         case PARITY_ODD  :      sysparity = 0x00000000 | TT$M_ALTRPAR ; :                                 sysparity |= TT$M_ODD    ;:                                 sysparity |= TT$M_PARITY ;=                                 sysparity |= TT$M_ALTDISPAR ; =                                 sysparity |= TT$M_DISPARERR ; &                                 break;  G         case PARITY_NONE  :     sysparity = 0x00000000 | TT$M_ALTRPAR ; =                                 sysparity |= TT$M_ALTDISPAR ; =                                 sysparity |= TT$M_DISPARERR ; &                                 break;  &         default           :     break;	         }      /* Set character length */  
 switch (byte) 	         { <                 case 5  :       sysparity |= TT$M_ALTFRAME ;3                                 sysparity |= 0x05 ; @                                 charac->b_char |= TT$M_EIGHTBIT;@                                 charac->b_char ^= TT$M_EIGHTBIT;&                                 break;  <                 case 6  :       sysparity |= TT$M_ALTFRAME ;3                                 sysparity |= 0x06 ; @                                 charac->b_char |= TT$M_EIGHTBIT;@                                 charac->b_char ^= TT$M_EIGHTBIT;&                                 break;  <                 case 7  :       sysparity |= TT$M_ALTFRAME ;3                                 sysparity |= 0x07 ; @                                 charac->b_char |= TT$M_EIGHTBIT;@                                 charac->b_char ^= TT$M_EIGHTBIT;&                                 break;  <                 case 8  :       sysparity |= TT$M_ALTFRAME ;3                                 sysparity |= 0x08 ; @                                 charac->b_char |= TT$M_EIGHTBIT;&                                 break;  &                 default :       break;  	         }      status= SYS$CANCEL(channel);  > status= SYS$QIOW(0,channel,IO$_SETMODE,&statblk,0,0,charac,12,'                 syspeed,0,sysparity,0);     I where the charac is the  characteristics, 12 bytes long. syspeed is a bit  coded speed definition, M and sysparity is a long integer (4 bytes) containing the parity and number of  bits per byte.  J The TT$M_ALT* codes are set to tell the drive to update the relevant stuff= (parity, treatment of parity error, number of bits per frame)     I Sorry, I haven't found anything obvious on getting the number of bits per G bytes, however the seem to be embedded in the parity byte. There are 20 5 possivble values for speed 1 to 20, requiring 5 bits.     J PARITY is x40 and ODD is x80.  This leaves the first 5 bits , in which the speed could fit.   eg: bits  7 6 5 4 3 2 1 0 K           O P S S S S S S   where O is ODD parity, P is PARITY, S is speed.   3 (I assume that P set without O means even parity.    	O = 1 and P =1 = odd parity 	O = 0 and P = 1 = even parity       O = 0 and P = 0 = no parity   ------------------------------  % Date: Mon, 24 Mar 2003 09:48:51 -0500 A From: "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com> F Subject: Re: EFI Specifications (was: I Have Seen The IA64 Future !!!), Message-ID: <3e7f1ad5_1@hpb10302.boi.hp.com>  = "JF Mezei" <jfmezei.spamnot@vl.videotron.ca> wrote in message ) news:3E7B385E.2ADBBA17@vl.videotron.ca...  > Fred Kleinsorge wrote:I > > There is no "boot command", think of it like a NT boot menu.  You can  get toJ > > something (the shell) that you can boot from if you want.  The devices haveD > > the (horrible) but familiar pathname format.  VMS is considering providing a L > > VMS-friendly "boot manager" which will give you a command line interfaceL > > that will convert the pathnames (for example) to VMS-friendly names like	 > > DKA0.  > J > If you use DOS disk names, does this mean that VMS will be limited to 24K > drives when running on IA64 ? What happens when you want to boot from the  25thG > disk drive ?  Will A: and D: be assigned to diskette and cdrom drives L > respectively ? How will the hardware determine which drive is the C: drive ?  >   L You can create a DOS-like alias in the shell, but devices are represented by paths, not DOS aliases.   I > Once booted, will VMS have to continue to translate (at very low level)  the I > VMS device names into the intel device names ? Or does VMS get to fully  map L > the names to the real device, at which point there would no longer be a 24 > disk drive limit ?  > Devices when running in VMS will look just like they do today.   ------------------------------  % Date: Mon, 24 Mar 2003 09:53:52 -0500 A From: "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com> F Subject: Re: EFI Specifications (was: I Have Seen The IA64 Future !!!). Message-ID: <3e7f1c7a$2_2@hpb10302.boi.hp.com>  8 "David Webb" <david20@alpha2.mdx.ac.uk> wrote in message% news:b5fja3$dt7$1@aquila.mdx.ac.uk...  > F > And even more importantly if a disk fails or is removed will all the	 disknames J > change (and thereby stop VMS mounting them because of a label mismatch). >   K No more so than today.  VMS names controllers in bus order, if you remove a G controller - then the names will change for example.  A path name is no I different than what the SRM console passes us today, it is a geographical E reference to the device based on the hose/bus/controller/unit type of  information.  F IDE, SCSI, and Fiber unit numbers don't change unless you do somethingD phyisical to change them.  The controller letters change only if you0 reconfigure the HW.  The same with hose and bus.   ------------------------------  % Date: Mon, 24 Mar 2003 09:55:52 -0500 A From: "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com> F Subject: Re: EFI Specifications (was: I Have Seen The IA64 Future !!!), Message-ID: <3e7f1c7b_2@hpb10302.boi.hp.com>  1 "Michael Unger" <unger@decus.de> wrote in message % news:00A1D363.26CA9A1F.19@decus.de... D > "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com> wrote: > A > > "JF Mezei" <jfmezei.spamnot@vl.videotron.ca> wrote in message - > > news:3E79EEF3.88DCB053@vl.videotron.ca...  > > 	 > > [...]  > > L > > The OS primary bootstrap lives in the FAT partition.  It is a file basedJ > > boot, not a boot-block based boot.  This, and the partitioning record,K > > allows multiple-OS disks.  While *we* won't support that (for a while),  it > > is useful. > J > To whom? I don't want VMS and Winwoes to co-reside on the very same disk	 > device.  >   J Nobody will ever force that, and at least for the next few years VMS isn't* capable of supporting it if you wanted to.  	 > > [...]  > > H > > > Will you specify a FAT file name in the boot command, or just some numberD > > > (similar to specifying 0 or 1 to boot from SYS0 or SYS1 in VMS > > terminology).  > > >  > > I > > There is no "boot command", think of it like a NT boot menu.  You can  get toJ > > something (the shell) that you can boot from if you want.  The devices haveD > > the (horrible) but familiar pathname format.  VMS is considering providing a L > > VMS-friendly "boot manager" which will give you a command line interfaceL > > that will convert the pathnames (for example) to VMS-friendly names like	 > > DKA0.  > > 	 > > [...]  > J > Considering all the possible combinations of boot flags and devices thisH > "menu" has to be displayed on a "multi-headed" graphics screen ... :-) > B > And only "considering providing a VMS-friendly boot manager" ??? >   H It's listed as a desireable item, but not as show-stopper functionality.   ------------------------------  % Date: Mon, 24 Mar 2003 09:48:51 -0500 A From: "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com> F Subject: Re: EFI Specifications (was: I Have Seen The IA64 Future !!!), Message-ID: <3e7f1c7a_2@hpb10302.boi.hp.com>  = "JF Mezei" <jfmezei.spamnot@vl.videotron.ca> wrote in message ) news:3E7B385E.2ADBBA17@vl.videotron.ca...  > Fred Kleinsorge wrote:I > > There is no "boot command", think of it like a NT boot menu.  You can  get toJ > > something (the shell) that you can boot from if you want.  The devices haveD > > the (horrible) but familiar pathname format.  VMS is considering providing a L > > VMS-friendly "boot manager" which will give you a command line interfaceL > > that will convert the pathnames (for example) to VMS-friendly names like	 > > DKA0.  > J > If you use DOS disk names, does this mean that VMS will be limited to 24K > drives when running on IA64 ? What happens when you want to boot from the  25thG > disk drive ?  Will A: and D: be assigned to diskette and cdrom drives L > respectively ? How will the hardware determine which drive is the C: drive ?  >   L You can create a DOS-like alias in the shell, but devices are represented by paths, not DOS aliases.   I > Once booted, will VMS have to continue to translate (at very low level)  the I > VMS device names into the intel device names ? Or does VMS get to fully  map L > the names to the real device, at which point there would no longer be a 24 > disk drive limit ?  > Devices when running in VMS will look just like they do today.   ------------------------------  % Date: Mon, 24 Mar 2003 09:56:17 -0500 A From: "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com> F Subject: Re: EFI Specifications (was: I Have Seen The IA64 Future !!!). Message-ID: <3e7f1c93$1_2@hpb10302.boi.hp.com>  H "Bob Koehler" <koehler@eisner.nospam.encompasserve.org> wrote in message- news:Omm4$5k$Kgyb@eisner.encompasserve.org... : > In article <3E7B385E.2ADBBA17@vl.videotron.ca>, JF Mezei) <jfmezei.spamnot@vl.videotron.ca> writes:  > > Fred Kleinsorge wrote:J > >> There is no "boot command", think of it like a NT boot menu.  You can get toK > >> something (the shell) that you can boot from if you want.  The devices  haveE > >> the (horrible) but familiar pathname format.  VMS is considering  providing a C > >> VMS-friendly "boot manager" which will give you a command line 	 interface H > >> that will convert the pathnames (for example) to VMS-friendly names like
 > >> DKA0. > > L > > If you use DOS disk names, does this mean that VMS will be limited to 24I > > drives when running on IA64 ? What happens when you want to boot from  the 25thI > > disk drive ?  Will A: and D: be assigned to diskette and cdrom drives H > > respectively ? How will the hardware determine which drive is the C: drive ?  > >  > I >    You're confusing Intel device names with DOS device names.  Intel != F >    DOS.  I suspect "(horrible) but familiar pathname" is much closerH >    to the adapter/bus/path/node/unit naes that one typically sees when/ >    booting Tru64, Solaris, and other eunichs.  >    Correct.   ------------------------------  % Date: Mon, 24 Mar 2003 06:53:27 -0500 ' From: "Main, Kerry" <Kerry.Main@hp.com> I Subject: RE: How to search for last login, but not on disusered accounts. T Message-ID: <BE56C50EA024184DAF48F0B9A47F5CF403FB5B1E@kaoexc01.americas.cpqcorp.net>  1 Re: last login, but not on disusered accounts ...    Real rock simple way -  G If you have access to PC - use the OpenVMS Management Station tool that  comes free with OpenVMS.  G Point-click on which field you want the entire UAF sorted on (including G "enabled-disabled" or "last login time"), then click "export list" icon F to export that sorted list to a csv file. Import to excel or any other report tool.  @ I just did it on my lab systems and it took me about 30 seconds.  G Sometimes the gui can be very handy and this is likely a case where the  gui is an advantage.   :-)    Regards   
 Kerry Main Senior Consultant  Hewlett-Packard (Canada) Co.! Consulting & Integration Services  Voice: 613-592-4660  Fax   : 613-591-4477 Email: kerryDOTmain@hpDOTcom-     (remove the DOT's and replace with "."'s)  OpenVMS DCL - the original .COM      -----Original Message-----D From: Craig A. Berry [mailto:craig.berry@SignalTreeSolutions.com]=20 Sent: March 24, 2003 12:17 AM  To: Info-VAX@Mvb.Saic.Com ? Subject: Re: How to search for last login, but not on disusered 	 accounts.     / Hein <hein_cov@eps.zk.dec.com> wrote in message * news:<3E7C9AAD.D0F6671E@eps.zk.dec.com>...  J > Anyway... here is a much similar example to the above, this time done=20
 > in PERL.  F And here's another example in Perl, which doesn't really save much butG illustrates the fact that the decision to use Perl does not necessarily 7 mean just parsing through the output of other commands.    use VMS::User;" @users =3D VMS::User::user_list();   for my $user (@users) { *   $uairef =3D VMS::User::user_info($user);2   next if $uairef->{FLAGS} & 0x10; # UAI$M_DISACNT1   print "$user last login (interactive)    : "=20 $     . $uairef->{LASTLOGIN_I} . "\n";1   print "$user last login (non-interactive): "=20 $     . $uairef->{LASTLOGIN_N} . "\n"; }   ? The VMS::User extension (like just about any Perl extension) is E available from http://search.cpan.org.  It's still officially in beta C but seems to work ok for simple lookups like this.  Eventually it's 5 supposed to be able to do $setuai as well as $getuai.   I > The 'date' manipulation is tricky again, this time because the ascii=20 D > date in the listing can not directly be used for comparisons. I=20I > decided to use a quick subroutine to convert to an encoded intege in=20 B > the form <YYYY><MM><DD>. I'm sure there are neat date package=20$ > available for other manipulations.  C The package is VMS::Misc and includes routines for dealing with VMS D quadword dates and assorted conversions.  Using that you could add aC check for disusered in the last 30 days (or whatever) to my example  above.  G Yet another Perl option would be to use VMS::IndexedFile, which creates C a tied hash to any indexed file, and of course SYSUAF.DAT is one of H those.  Conveniently, it's the one used in the example that comes in the extension's documentation.   ------------------------------  % Date: Mon, 24 Mar 2003 12:14:42 -0500 < From: "Peter Weaver" <WeaverConsultingServices@sympatico.ca>I Subject: Re: How to search for last login, but not on disusered accounts. 6 Message-ID: <b5nee5$2a5597$1@ID-141708.news.dfncis.de>   Vic Mendham wrote:> > I have a script which searches for last logins older than x, anyone9 > have any idea how to modify it so that it disregards an  account  > flagged as disuser?  >...  6 A simple way would be to get Joe Meadows' UAF program.; Download the .ZIP file (I forget where I got it from, but a ; Google search should find it, if you want a copy via e-mail ; then let me know), unzip the files into a directory and set = default there, then these three commands will get you exactly : what you need (modify the first line if you are on a VAX);8 $ assign 'f$environment("default")'uaf.alpha_exe uaf/job $ set command uafcld $ = uaf/select=(flag=nodisuser,interactive=(17-apr-1963,-30-:)) - 0   /match=and/display=(username,flag,interactive)   -- Peter Weaver Weaver Consulting Services Inc. ) Serving Southern Ontario/Western New York    ------------------------------  % Date: Mon, 24 Mar 2003 10:01:37 -0500 A From: "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com> , Subject: Re: I Have Seen The IA64 Future !!!. Message-ID: <3e7f1dd3$1_3@hpb10302.boi.hp.com>  = "JF Mezei" <jfmezei.spamnot@vl.videotron.ca> wrote in message ) news:3E7C11A9.BF345AA4@vl.videotron.ca...  > question:  > H > With the return of NT running on the same platform as VMS if that IA64 thing L > succeeds, will EFI provide protection to prevent a rogue microsoft NT fromC > fucking up a VMS drive if one system has dual-boot capabilities ?  >   J Because we will support the same partition record as our "boot block", the/ issue of NT mucking with this "should" go away.   J > Would an NT system be able to access the FAT container ona VMS drive and mess/ > with it ? (and vice-versa, for that matter ?)  >    No.   J > Will EFI (the vanilla version stored in ROM) be able to hide drives from NT,  > or will NT see all devices ?  C It will see any drive that has a valid partition record, and an EFI L partition with OS Loaders.  So it will see all the drives, including NT ones that might be attached.    ------------------------------  % Date: Mon, 24 Mar 2003 07:07:11 -0800 # From: "Tom Linden" <tom@kednos.com> , Subject: RE: I Have Seen The IA64 Future !!!9 Message-ID: <CIEJLCMNHNNDLLOOGNJIOENNGNAA.tom@kednos.com>   ; I doubt many users would ever use a dual-boot capability, I  certainly wouldn't.    >-----Original Message----- G >From: Fred Kleinsorge [mailto:kleinsorge@star-dot-zko-dot-dec-dot-com] % >Sent: Monday, March 24, 2003 7:02 AM  >To: Info-VAX@Mvb.Saic.Com- >Subject: Re: I Have Seen The IA64 Future !!!  >  >  > > >"JF Mezei" <jfmezei.spamnot@vl.videotron.ca> wrote in message* >news:3E7C11A9.BF345AA4@vl.videotron.ca... >> question: >>I >> With the return of NT running on the same platform as VMS if that IA64  >thing< >> succeeds, will EFI provide protection to prevent a rogue  >microsoft NT fromD >> fucking up a VMS drive if one system has dual-boot capabilities ? >> > K >Because we will support the same partition record as our "boot block", the 0 >issue of NT mucking with this "should" go away. > K >> Would an NT system be able to access the FAT container ona VMS drive and  >mess 0 >> with it ? (and vice-versa, for that matter ?) >> >  >No. > K >> Will EFI (the vanilla version stored in ROM) be able to hide drives from  >NT, >> or will NT see all devices ?  > D >It will see any drive that has a valid partition record, and an EFI< >partition with OS Loaders.  So it will see all the drives,  >including NT ones >that might be attached. >  >  >  >---' >Incoming mail is certified Virus Free. ; >Checked by AVG anti-virus system (http://www.grisoft.com). A >Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003  >  --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003   ------------------------------  % Date: Mon, 24 Mar 2003 15:28:44 -0000 * From: "Richard Brodie" <R.Brodie@rl.ac.uk>, Subject: Re: I Have Seen The IA64 Future !!!+ Message-ID: <b5n87d$q6c@newton.cc.rl.ac.uk>   = > I doubt many users would ever use a dual-boot capability, I  > certainly wouldn't.   A A cleaner multibooting system would have a lot of advantages over A the rather finicky systems of today. Although (say) Linux/Unix or A five different flavours of windows would likely be a more typical  combination.   ------------------------------  % Date: Mon, 24 Mar 2003 07:46:06 -0800o# From: "Tom Linden" <tom@kednos.com>:, Subject: RE: I Have Seen The IA64 Future !!!9 Message-ID: <CIEJLCMNHNNDLLOOGNJIMENOGNAA.tom@kednos.com>,  : I guess I didn't make the point,  HW is cheap.  Only way I< would run multiple OSes on a given box is simultaneously and in contained partitions.   >-----Original Message-----j0 >From: Richard Brodie [mailto:R.Brodie@rl.ac.uk]% >Sent: Monday, March 24, 2003 7:29 AMs >To: Info-VAX@Mvb.Saic.Com- >Subject: Re: I Have Seen The IA64 Future !!!v >e >T >I> >> I doubt many users would ever use a dual-boot capability, I >> certainly wouldn't. >pB >A cleaner multibooting system would have a lot of advantages overB >the rather finicky systems of today. Although (say) Linux/Unix orB >five different flavours of windows would likely be a more typical
 >combination.u >o >n >---' >Incoming mail is certified Virus Free.F; >Checked by AVG anti-virus system (http://www.grisoft.com).SA >Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003  >a ---e& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003   ------------------------------  % Date: Mon, 24 Mar 2003 18:04:53 +0100r$ From: Michael Unger <unger@decus.de>, Subject: Re: I Have Seen The IA64 Future !!!* Message-ID: <00A1D5B8.55A7AF43.4@decus.de>  B "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com> wrote:  ? > "JF Mezei" <jfmezei.spamnot@vl.videotron.ca> wrote in messagey+ > news:3E7C11A9.BF345AA4@vl.videotron.ca...e
 > > question:t >  > [...]  > L > > Will EFI (the vanilla version stored in ROM) be able to hide drives from > NT,x  > > or will NT see all devices ? > E > It will see any drive that has a valid partition record, and an EFItN > partition with OS Loaders.  So it will see all the drives, including NT ones > that might be attached.y  E So there is definitely a requirement for an (additional) EFI console  @ (ROM!) command to make a drive unavailable for access by any OS:   	SET <drive> OFFLINE  = and of course the inverse command to make it available again.-   Michael-   ------------------------------  % Date: Mon, 24 Mar 2003 12:59:08 -0500u' From: "Main, Kerry" <Kerry.Main@hp.com>i, Subject: RE: I Have Seen The IA64 Future !!!T Message-ID: <BE56C50EA024184DAF48F0B9A47F5CF403FB5B24@kaoexc01.americas.cpqcorp.net>   Tom,  5 Re: multiple partitions ..as you stated, HW is cheap.r  F For med to large ISV's, I suspect the more preferred approach would beD to use small, relatively cheap SAN's like MSA1000. Simply change the9 console boot designator to boot off different devices.=20-  6 Same HW system could support multiple OS environments.   Regards2  
 Kerry Main Senior Consultant, Hewlett-Packard (Canada) Co.! Consulting & Integration Servicesb Voice: 613-592-4660i Fax   : 613-591-4477 Email: kerryDOTmain@hpDOTcom-     (remove the DOT's and replace with "."'s)T OpenVMS DCL - the original .COMe     -----Original Message-----+ From: Tom Linden [mailto:tom@kednos.com]=20l Sent: March 24, 2003 10:46 AMt To: Info-VAX@Mvb.Saic.Coms, Subject: RE: I Have Seen The IA64 Future !!!    D I guess I didn't make the point,  HW is cheap.  Only way I would run? multiple OSes on a given box is simultaneously and in containedi partitions.n   >-----Original Message----- 0 >From: Richard Brodie [mailto:R.Brodie@rl.ac.uk]% >Sent: Monday, March 24, 2003 7:29 AMB >To: Info-VAX@Mvb.Saic.Com- >Subject: Re: I Have Seen The IA64 Future !!!l >. >s >hH >> I doubt many users would ever use a dual-boot capability, I certainly   >> wouldn't. >eI >A cleaner multibooting system would have a lot of advantages over the=20oF >rather finicky systems of today. Although (say) Linux/Unix or five=20@ >different flavours of windows would likely be a more typical=20
 >combination.o >I >h >---' >Incoming mail is certified Virus Free.t; >Checked by AVG anti-virus system (http://www.grisoft.com).eA >Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003- >- ----& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003   ------------------------------  % Date: Mon, 24 Mar 2003 13:01:26 -0500oA From: "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com> , Subject: Re: I Have Seen The IA64 Future !!!, Message-ID: <3e7f47f7_1@hpb10302.boi.hp.com>  1 "Michael Unger" <unger@decus.de> wrote in message"$ news:00A1D5B8.55A7AF43.4@decus.de...D > "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com> wrote: >iA > > "JF Mezei" <jfmezei.spamnot@vl.videotron.ca> wrote in message - > > news:3E7C11A9.BF345AA4@vl.videotron.ca...  > > > question:  > > 	 > > [...]W > >uI > > > Will EFI (the vanilla version stored in ROM) be able to hide drivesl from > > NT,l" > > > or will NT see all devices ? > >hG > > It will see any drive that has a valid partition record, and an EFI-K > > partition with OS Loaders.  So it will see all the drives, including NTe ones > > that might be attached.i >hF > So there is definitely a requirement for an (additional) EFI consoleB > (ROM!) command to make a drive unavailable for access by any OS: >P > SET <drive> OFFLINEe >d? > and of course the inverse command to make it available again.i >e   Why?   ------------------------------  % Date: Mon, 24 Mar 2003 13:03:49 -0500 A From: "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com>P, Subject: Re: I Have Seen The IA64 Future !!!, Message-ID: <3e7f4886_2@hpb10302.boi.hp.com>  J While using the ability to have multiple OS's co-resident on the same diskJ device may not be a high use item, we have a number of large customers whoL are very interested in the concept of buying a single standard platform, andJ being able to boot VMS, Linux, HP-UX, or Windows64 at will on any of them.      . "Tom Linden" <tom@kednos.com> wrote in message3 news:CIEJLCMNHNNDLLOOGNJIOENNGNAA.tom@kednos.com...c= > I doubt many users would ever use a dual-boot capability, I5 > certainly wouldn't.  >  > >-----Original Message----- I > >From: Fred Kleinsorge [mailto:kleinsorge@star-dot-zko-dot-dec-dot-com],' > >Sent: Monday, March 24, 2003 7:02 AMo > >To: Info-VAX@Mvb.Saic.Com/ > >Subject: Re: I Have Seen The IA64 Future !!!, > >y > >l > > @ > >"JF Mezei" <jfmezei.spamnot@vl.videotron.ca> wrote in message, > >news:3E7C11A9.BF345AA4@vl.videotron.ca... > >> question: > >>K > >> With the return of NT running on the same platform as VMS if that IA64K > >thing= > >> succeeds, will EFI provide protection to prevent a rogue? > >microsoft NT fromF > >> fucking up a VMS drive if one system has dual-boot capabilities ? > >> > >SI > >Because we will support the same partition record as our "boot block",, thee2 > >issue of NT mucking with this "should" go away. > >nI > >> Would an NT system be able to access the FAT container ona VMS drive  and  > >messb2 > >> with it ? (and vice-versa, for that matter ?) > >> > >G > >No. > >iH > >> Will EFI (the vanilla version stored in ROM) be able to hide drives from > >NT,! > >> or will NT see all devices ?e > > F > >It will see any drive that has a valid partition record, and an EFI= > >partition with OS Loaders.  So it will see all the drives,c > >including NT ones > >that might be attached. > >m > >u > >g > >---) > >Incoming mail is certified Virus Free.u= > >Checked by AVG anti-virus system (http://www.grisoft.com).nC > >Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003o > >a > ---o( > Outgoing mail is certified Virus Free.< > Checked by AVG anti-virus system (http://www.grisoft.com).B > Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003 >e   ------------------------------  % Date: Mon, 24 Mar 2003 10:51:20 -0800 # From: "Tom Linden" <tom@kednos.com>s, Subject: RE: I Have Seen The IA64 Future !!!9 Message-ID: <CIEJLCMNHNNDLLOOGNJIOEOCGNAA.tom@kednos.com>m  ? Well that is a different proposition altogether and it benefitssC both HP and that customer.  What I was responding to was the notioniC a given customer could usefully boot different OSes on the same boxo at different times.M   >-----Original Message-----mG >From: Fred Kleinsorge [mailto:kleinsorge@star-dot-zko-dot-dec-dot-com]i& >Sent: Monday, March 24, 2003 10:04 AM >To: Info-VAX@Mvb.Saic.Com- >Subject: Re: I Have Seen The IA64 Future !!!a >  >MK >While using the ability to have multiple OS's co-resident on the same diskuK >device may not be a high use item, we have a number of large customers who4? >are very interested in the concept of buying a single standardl >platform, andK >being able to boot VMS, Linux, HP-UX, or Windows64 at will on any of them.a >s >p >e/ >"Tom Linden" <tom@kednos.com> wrote in messagem4 >news:CIEJLCMNHNNDLLOOGNJIOENNGNAA.tom@kednos.com...> >> I doubt many users would ever use a dual-boot capability, I >> certainly wouldn't. >> >> >-----Original Message-----J >> >From: Fred Kleinsorge [mailto:kleinsorge@star-dot-zko-dot-dec-dot-com]( >> >Sent: Monday, March 24, 2003 7:02 AM >> >To: Info-VAX@Mvb.Saic.Come0 >> >Subject: Re: I Have Seen The IA64 Future !!! >> > >> > >> >A >> >"JF Mezei" <jfmezei.spamnot@vl.videotron.ca> wrote in messagem- >> >news:3E7C11A9.BF345AA4@vl.videotron.ca...- >> >> question:o >> >>aL >> >> With the return of NT running on the same platform as VMS if that IA64	 >> >thing > >> >> succeeds, will EFI provide protection to prevent a rogue >> >microsoft NT fromlG >> >> fucking up a VMS drive if one system has dual-boot capabilities ?y >> >>P >> >J >> >Because we will support the same partition record as our "boot block", >the3 >> >issue of NT mucking with this "should" go away.c >> >J >> >> Would an NT system be able to access the FAT container ona VMS drive >and >> >mess3 >> >> with it ? (and vice-versa, for that matter ?)l >> >>p >> > >> >No.g >> >I >> >> Will EFI (the vanilla version stored in ROM) be able to hide drivese >fromo >> >NT, " >> >> or will NT see all devices ? >> >G >> >It will see any drive that has a valid partition record, and an EFI-> >> >partition with OS Loaders.  So it will see all the drives, >> >including NT onesu >> >that might be attached.l >> > >> > >> > >> >---3* >> >Incoming mail is certified Virus Free.> >> >Checked by AVG anti-virus system (http://www.grisoft.com).D >> >Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003 >> > >> ---) >> Outgoing mail is certified Virus Free.S= >> Checked by AVG anti-virus system (http://www.grisoft.com)./C >> Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003n >> >n >r >---' >Incoming mail is certified Virus Free.3; >Checked by AVG anti-virus system (http://www.grisoft.com).iA >Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003h >e ---3& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/2003   ------------------------------    Date: 24 Mar 2003 09:20:14 -0800+ From: hsnewman@austin.rr.com (HarrisNewman)h) Subject: Installation faq for VMS on simh = Message-ID: <73dff34c.0303240920.6b78ad27@posting.google.com>n  C Could someone post a faq on how to install everything that's on thegB hobbiest cdrom please?  I've been able to do the base install, butF can't seem to get past that.  I've added my license, but can't seem toD mount the hobbiest cd in order to accomplish the rest of the install (such as tcpip).  E I think there must be a trick here.  I am (trying) to mount the cd aso follows:  . In simh my config file to start the simulator: load -r ka655.bino set cpu 64ml set rq0 ra82 attach rq0 OpenVMS.dsk
 set rq1 cdromt% attach -r rq1 openvmsrelease.dskimagep set dz lines=8 att -a dz 12000  boot cpu   I then boot dua0  F but the OS comes up without the cd mounted.  I can't seem to mount the
 cd either. Thanks in advance. -Harrisr   ------------------------------    Date: 24 Mar 2003 05:26:17 -08001 From: susan_skonetski@hotmail.com (Sue Skonetski) . Subject: Re: Mark Gorham was Re: Rich Marcello= Message-ID: <857e9e41.0303240526.25cbf897@posting.google.com>h   Nope JF not even you ;')  O just because you have a match it does not mean you have to start a forest fire.d   sue   g JF Mezei <jfmezei.spamnot@vl.videotron.ca> wrote in message news:<3E7DF830.25297DF9@vl.videotron.ca>...P > Sue Skonetski wrote:8 > > Mark Gorham is the best VP I have ever worked with.  >  ...I > > thing a VP can tell his people.  He also NEVER EVER says anything bada > > about anybody. E >  >  > Not even about me ???? g > + > :-) :-) :-) Talk about self restraint :-)e   ------------------------------    Date: 22 Mar 2003 23:18:58 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: Micromedex on VMS- Message-ID: <87of43h1jx.fsf@prep.synonet.com>t  & Lee Y T Mah <lytmah@cha.ab.ca> writes:  B > Micromedex on VMS (VAX/Alpha) is a text-based database providingB > toxicology, drug, disease... information to practitioners in the6 > healthcare industry.  The vendor wants to move theirC > VMS/AIX/Sun... customers to their internet, intranet, and Windows  > platforms.  < Ask them how they are going to enable US customers to comply@ with HIP<thing I still can't remember> and the billyware licence> conditions that allows the beast of redmond to browse or alter patient data at will.i  3 Watch the spinning start at 10K rpm and counting :).   -- 2< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.a@                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Mon, 24 Mar 2003 00:10:19 -0800 # From: "Thanatos" <nobody@noway.net> ( Subject: Re: One version of a file ONLY./ Message-ID: <v7tf8sbogpq90a@corp.supernews.com>     Try using the following command:  (     $ SET FILE filename /VERSION_LIMIT=1    9 "Robert Palmer" <news.robert@greetin.gs> wrote in messagey# news:3E7BBB66.8020801@greetin.gs... " > Set the version number to 32767. >A > Shane Smith wrote:L > > Depending on how you're set up, and what version of VMS, you may be ableH > > to do this by removing everyone's delete access to the files. If youF > > can't delete it you can't replace it, since somewhere around 6.1 I
 > > think. > > 	 > > Shane  > >  > > -----Original Message-----: > > From: Barry in Indy [mailto:barrymeindy@ameritech.net]) > > Sent: Tuesday, March 11, 2003 9:41 AM; > > To: Info-VAX@Mvb.Saic.Com ( > > Subject: One version of a file ONLY. > >n > >/D > > Is there a way in VMS to specify that there is to be one versionC > > of a file ONLY, meaning that the creation of a second file with0B > > the same name would fail? We have an online system which is up< > > most of the day. But even when it is running, if someoneD > > inadvertently copies, say, a set of test files to the productionD > > system, new versions of the files are created. What I am lookingE > > for is a simple way to avoid this problem. Of course, there wouldhA > > also have to be a way to override this protection in order tor  > > restore files intentionally. > >  > > Thank you, > > 	 > > Barry  > >a >7   ------------------------------    Date: 24 Mar 2003 07:35:47 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)cC Subject: Re: OpenVMS as a growth platform; and low-cost development_3 Message-ID: <ianEid3WjtH$@eisner.encompasserve.org>   q In article <cf15391e.0303201707.609dc699@posting.google.com>, keithparris_NOSPAM@yahoo.com (Keith Parris) writes:= > C > HP OpenVMS will be making OpenVMS Software Development Kits (SDK);F > available for partners at a very low cost ($75) in 2003. InformationA > will be posted on the OpenVMS Web site when they are available.s  G    Nice price.  But so far I haven't even got planning info on the costy    of the box it will run on.r   ------------------------------    Date: 24 Mar 2003 08:53:37 -08001 From: susan_skonetski@hotmail.com (Sue Skonetski) 4 Subject: OpenVMS Pearl Monday March 24 - Announcment= Message-ID: <857e9e41.0303240853.3bbbe8d9@posting.google.com>v  > hp Reliable Transaction Router (RTR) Version 4.2 Announcement   uC HP Reliable Transaction Router (RTR) Version 4.2 is available now!  B RTR is software fault tolerant  transactional messaging middleware@ used to implement large, distributed applications using a uniqueE three-tier, highly interoperable HA/DT client/server technology. This @ maintenance release of RTR V4.2 has been designed to provide the) highest level of quality and reliability.    D This release includes the capability of transmitting broadcast eventA and transaction reply data in a compressed format, addressing the F needs of users who wish to reduce their network bandwidth requirements> for the transfer of such data. User data passed to RTR via theF rtr_reply_to_client() and rtr_broadcast_event() APIs may optionally be; compressed prior to being passed to the RTR ACP process forFD transmission to the RTR router. The data will be decompressed to itsF original state prior to being presented to the receiving applications.  7D Since 1990 major financial exchanges and banks across the globe haveA relied on RTR as the best and simplest method of providing 24 x 7o: availability for their transaction-intensive applications.  v RTR V4.2 Product Availabilityb  fF RTR is now available for customers on the following platforms: OpenVMSF (Alpha(tm) and VAX(tm)),Tru64 UNIX, Sun Solaris, Windows 2000, WindowsC XP, Windows NT, Windows 98 and Windows ME. Individual RTR V4.2 kitse? can be ordered today. It will also ship on the Software Productt. Libraries in the April - June 2003 time frame.   3 Please visit the RTR web site for more information:  http://www.hp.com/go/rtr.A   ------------------------------  # Date: Mon, 24 Mar 2003 16:02:29 GMTw& From: jlsue <jefflsxxxz@sbcglobal.net>Y Subject: Re: OpenVMS.org: Marvel article and HP's press release for Marveland Alpha Retair8 Message-ID: <eu6u7v0550ebphtt4ah5sonfb8h9ikaqpo@4ax.com>  F NOTE:  I know the attribution below may not be exactly correct....  inE switching ISPs I missed some notes and had to look them up on Google.   E On Tue, 13 Mar 2003 09:12:05 +0000, Andrew Harrison SUNUK Consultancy . <Andrew_No.Harrison_No@nospamn.sun.com> wrote:  F >> I don't divulge any details about my customer.  However, there is aI >> web page for HP wins, and one that's kinda neat is at Bank of Austria.n= >> They have 16-P GS160 systems.  check out the report below:a >>  < > >http://h71000.www7.hp.com/openvms/brochures/Bank-Austria/ >> p  3 >Great another example that proves my point thanks.a >k6 >The Turbo Laser was the codename for the 8400 so your7 >customer got a 28% performance improvement moving from ) >an 8400 to a GS160 with 16 CPUs and 7.3.( > blah, blah, blah...u  ? You still completely ignore the point in order to continue youra worthless rants.  A I never made claims about the performance in specific numbers, soi. you're wasting your time with that argument.      But you're lieing in any event:   C The article DOES NOT say that the GS160 gave them a 28% performanceeA increase.  Try reading for comprehension next time.  It says thatFE "moving to VMS 7.3 gave them a 28% performance increase.  The articleaD actually does not give any info as to the performance gains from theA GS160.  This is yet another attempt on your part to mis-represent ? things to try to back up your unsupportable logical conclusion.   C Now, it's possible to surmise that the reason for not telling GS160iC performance gains was because they weren't stellar.  But that wouldp# only be a guess, and amount to fud.   E You still can't prove that the GS160/320 does not perform well, ever. F You can't even say how often it performs well.  In one of the examplesA given, and which you conveniently ignore as a data point, anothergE typical tactic of yours, Oracle Financials applications on GS160 were ? the PREFERRED solution.  Yep, those same transaction-processingiA applications that you swear never perform well on the GS160.  Whyh don't you address that one?l  @ Oh, but it's so much easier to pick-and-choose your data points,D including repeating (for the umpteen millionth time) the TP-whateverF benchmarks.  If your customers make money by running these benchmarks,C good for them.  Ours typically run other apps, some of which mirrorp= the results of the benchmarks, but certainly not all of them.u  E The FACT is that I have shown TWO examples where customers were happy = with their "wildfire" systems.  This flies in the face of the A contention that you keep repeating (ad nauseum) in here that theyh can't peform well.   ------------------------------  % Date: Mon, 24 Mar 2003 10:05:18 -0500rA From: "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com> 8 Subject: Re: Remotely opening a window on my workstation. Message-ID: <3e7f1eb0$1_2@hpb10302.boi.hp.com>  6 "Paul Sture" <p_sture@elias.decus.ch> wrote in message# news:W7JV9o3v8jkf@elias.decus.ch... E > In article <3iLea.653$A75.554@news.cpqcorp.net>, "John E. Malmberg"c+ <Malmberg@dskwld.zko.dec.compaq.hp> writes:  > > JF Mezei wrote:lK > >> Is there some service or website somehwere that would allow me to open  an XE > >> display on my workstation from the remote system ? (to test that 
 capability) ?s > >-L > >> For instance, a web site where I would enter my IP address and it would openG > >> an X-clock or others imple app onto my workstation ?  (or a telnetd site)  > >jH > > You do realize that any one else on that system would be able to useF > > your X-11 server to read your keystrokes and mouse clicks, or take > > snapshots of your display? > >sK > > I really would not do X-11 on the Internet unless I trusted everyone ons7 > > the remote host not to take advantage of my system.  > > L > > DECNET transport allows authenticating the user.  TCP/IP only allows you  > > to specify the I.P. address. > >l > L > True at the moment, _but_ the Motif 1.3 documentation now up on the HP VMSH > site includes a comprehensive looking set of new qualifiers supporting > authentication and security. >f> > See http://h71000.www7.hp.com/doc/731final/6663/6663PRO.HTML >eD > Does anyone know when Motif 1.3 is likely to appear on the CONDIST > CDs? >h  K I would assume in the next quarterly release.  You can get it as a seperate J product right now, and it will be the standard release in the next OpenVMS Alpha release.   ------------------------------   Date: 24 Mar 2003 07:16:25 GMT/ From: "Dave Weatherall" <djweath@attglobal.net>h$ Subject: Re: Some Windows ammunition5 Message-ID: <DTiotGxQ0bj6-pn2-qnDdUo8pdo7z@localhost>v  F On Sat, 22 Mar 2003 01:15:31 UTC, peter@langstoeger.at (Peter 'EPLAN'  LANGSTOEGER) wrote:   V > In article <3E797A7F.AC9913E6@127.0.0.1>, Nic Clews <sendspamhere@127.0.0.1> writes: > >JF Mezei wrote:S > >> How can one continue to develop on Windows when you are spending all your time- > >> installing patches ?0 > >> VMS all the way ;-) > >iI > >I've not checked the validity, but I've no reason to doubt the reportsiI > >that these other worm infestations that folks think are under control,pG > >have meanwhile planted little time bombs, so far undetected ready too6 > >unleash another wave of regret among windoze users. > M > I've found such a "time bomb". Since installation of the latest fix for XP,sD > MSIE (and Outlook when reading a HTML mail) die now immediately...  D As they used to say in Liverpool "are you bragging or complaining?"  :-)    -- t Cheers - Dave.   ------------------------------  % Date: Mon, 24 Mar 2003 11:46:18 +0100e( From: "Rudolf Wingert" <win@fom.fgan.de>/ Subject: Re: Sun unix/linux new nasty bug cert! : Message-ID: <MDEJJFGEEOPAFONJONBKEEMACOAA.win@fom.fgan.de>   Hello,   Andrew Harrison wrotes:o   >>>l Well to be more clear.* Solaris, HP-UX, Tru64, OpenVMS, AIX, Linux  IRIX are all probably vunerable. <<<l  I Where did you get the info about OpenVMS. Years ago we did use the XDR toaI exchange data from Sun platform to OpenVMS. The Sun user did report a bug F within OpenVMS (ACCVIO). What was the problem? H e did not specify anyF memory address (0 for get automatic memory). So the memory address wasL outsite of his space. On Sun this is not an error. In case of this, there isJ no possibility to get root priviledges under OpenVMS. All what you do (XDRH or other tools with the buffer overflow problem), can you do only withinH your context, or yue will be stopped via the OS. Look also the intrutionL report of DECUS Muenchen. XDR under OpenVMS may be buggy, but you do not get* any right over the normal user's right!!!!   Best regards Rudolf Wingerts   ------------------------------  % Date: Mon, 24 Mar 2003 11:58:09 +0000.' From: Andrew Harrison SUNUK Consultancyn/ Subject: Re: Sun unix/linux new nasty bug cert!-. Message-ID: <3E7EF2D1.8060209@nospamn.sun.com>   Rudolf Wingert wrote:a > Hello, >  > Andrew Harrison wrotes:c >  >  > Well to be more clear., > Solaris, HP-UX, Tru64, OpenVMS, AIX, Linux" > IRIX are all probably vunerable. > <<<t > K > Where did you get the info about OpenVMS. Years ago we did use the XDR tohK > exchange data from Sun platform to OpenVMS. The Sun user did report a bugeH > within OpenVMS (ACCVIO). What was the problem? H e did not specify anyH > memory address (0 for get automatic memory). So the memory address wasN > outsite of his space. On Sun this is not an error. In case of this, there isL > no possibility to get root priviledges under OpenVMS. All what you do (XDRJ > or other tools with the buffer overflow problem), can you do only withinJ > your context, or yue will be stopped via the OS. Look also the intrutionN > report of DECUS Muenchen. XDR under OpenVMS may be buggy, but you do not get, > any right over the normal user's right!!!! >  > Best regards Rudolf Wingert  >   3 I didn't there is currently no response for OpenVMSs0 on the CERT web page along with HP-UX and Tru64.  1 However it is a generic XDR issue so Bob's claims 6 for OpenVMS being invunerable are as always premature.   Regardsc Andrew Harrisons   ------------------------------  % Date: Mon, 24 Mar 2003 12:06:31 +0000e' From: Andrew Harrison SUNUK Consultancy / Subject: Re: Sun unix/linux new nasty bug cert!e, Message-ID: <3E7EF4C7.10102@nospamn.sun.com>   David Webb wrote:ej > In article <d7791aa1.0303211729.730c8be3@posting.google.com>, bob@instantwhip.com (Bob Ceculski) writes: >  >>Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote in message news:<3E7B2646.70809@nospamn.sun.com>...A >> >>>Bob Ceculski wrote: >>>:/ >>>>the inquirer has the details, and Andrew, Io. >>>>guess certs aren't important, esp. if they >>>>point to your os ... >>>>, >>>>http://www.theinquirer.net/?article=8436 >>>  >>>Well to be more clear.t >>>a- >>>Solaris, HP-UX, Tru64, OpenVMS, AIX, Linux # >>>IRIX are all probably vunerable.t >>>i
 >>>Regards >>>Andrew Harrison >>- >>what's vms got to do with a unix/linux bug?i >  >  > P > Probably referring to the fact that the DEC TCPIP services stack uses the sameP > codebase as the TRU64 TCPIP stack and the fact that the HP VMS Kerberos server > is based on MIT's code.kL > However the substantial differences between VMS and Unix doesn't mean thatL > these facts automatically make VMS vulnerable even if TRU64 is vulnerable. >   = No but then it also doesn't mean that OpenVMS isn't vunerablee= so Bob in his great wisdom has chosen to publicise what couldi" easily be an OpenVMS vunerability.   Way to go Bob.   Regards  Andrew Harrisont   ------------------------------    Date: 22 Mar 2003 23:30:55 +0800, From: Paul Repacholi <prep@prep.synonet.com>/ Subject: Re: Sun unix/linux new nasty bug cert! - Message-ID: <87k7erh100.fsf@prep.synonet.com>i  " Cthulhu <spambox@rlyeh.it> writes:  R > Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote:  .. > > Solaris, HP-UX, Tru64, OpenVMS, AIX, Linux$ > > IRIX are all probably vunerable.  t; > So, finally Sun managed to get something that is _really_i > multi-platform! ;)  A Oh please, RPC have been around and multi platform for `forever'.a7 If you want to diss Andrew find something new or funny.e   -- i< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------    Date: 24 Mar 2003 08:37:22 -0800( From: bob@instantwhip.com (Bob Ceculski)/ Subject: Re: Sun unix/linux new nasty bug cert!c< Message-ID: <d7791aa1.0303240837.bca11ce@posting.google.com>   Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote in message news:<3E7EF2D1.8060209@nospamn.sun.com>...: > Rudolf Wingert wrote: 
 > > Hello, > >  > > Andrew Harrison wrotes:b > >  > >  > > Well to be more clear.. > > Solaris, HP-UX, Tru64, OpenVMS, AIX, Linux$ > > IRIX are all probably vunerable. > > <<<  > > M > > Where did you get the info about OpenVMS. Years ago we did use the XDR to M > > exchange data from Sun platform to OpenVMS. The Sun user did report a bug J > > within OpenVMS (ACCVIO). What was the problem? H e did not specify anyJ > > memory address (0 for get automatic memory). So the memory address wasP > > outsite of his space. On Sun this is not an error. In case of this, there isN > > no possibility to get root priviledges under OpenVMS. All what you do (XDRL > > or other tools with the buffer overflow problem), can you do only withinL > > your context, or yue will be stopped via the OS. Look also the intrutionP > > report of DECUS Muenchen. XDR under OpenVMS may be buggy, but you do not get. > > any right over the normal user's right!!!! > >  > > Best regards Rudolf Wingert  > >  > 5 > I didn't there is currently no response for OpenVMS 2 > on the CERT web page along with HP-UX and Tru64. > 3 > However it is a generic XDR issue so Bob's claimsL8 > for OpenVMS being invunerable are as always premature. > 	 > Regards  > Andrew Harrisona  @ wrong, as always they are right on the money ... VMS can squelchA the nastiest unix kernel bugs ... just admit that VMS is superiorm= to slowaris, unix, linux, windoze or any other garbage os outa	 there ...b   ------------------------------  % Date: Mon, 24 Mar 2003 18:36:52 +0100i From: Dirk Munk <munk@home.nl>- Subject: Re: System Special for VMS NewsGroupn2 Message-ID: <b5nfo1$brv$1@news1.tilbu1.nb.home.nl>   Larry Kilgallen wrote:a > In article <CIEJLCMNHNNDLLOOGNJIGEMOGNAA.tom@kednos.com>, "Tom Linden" <tom@kednos.com> writes:o >  > 6 >>Is the open PCI slot consumed by the Graphics board/ >  > I > The DS10L has only one PCI slot.  If you add a graphics card, that willuG > take up the slot.  I though there was one card that could be added to G > provide a combination of functions in a single slot, but someone else / > would have to state what those functions are.h >   P There is a combo card with graphics, LVD SCSI and ethernet. It should be in the * quickspecs on the HP Alphaserver web site.   ------------------------------  % Date: Mon, 24 Mar 2003 10:41:55 +0000o( From: Nic Clews <sendspamhere@127.0.0.1>6 Subject: Terminal driver for VAX synchronous interface) Message-ID: <3E7EE0F3.A590DA98@127.0.0.1>   > Has anyone written one of these, including full modem control?  E This is the situation. I want to connects to a TT port which supports = synchronous signalling. This is for an ISDN terminal adapter.i  H My ideal situation would be a QBUS card for a VAX, presenting a TX or TTH port so that the communications software would not distinguish it from a regular TX or TT port.   I'm using 6.2 of VMS FWIW.  C This is for the hobby system. I am using AUTODIAL UUCP (ported from:F UNIX) to manage the dial-up, wrapped in a DCL procedure to perform theG dial out and establish the link, then switch up a dynamic PPP link from C the IP software. The complication is that the ISDN terminal adapterlF talks synchronous, and no serial ports I know of are capable under VAXG and VMS which present themselves as terminal class (unless anyone knowsm3 better). Only looking for single port connectivity.-   Thanks in anticipation.  -- 0? Regards, Nic Clews a.k.a. Mr. CP Charges, CSC Computer Sciences: nclews at csc dot comu   ------------------------------  % Date: Mon, 24 Mar 2003 18:03:28 +0100u$ From: Michael Unger <unger@decus.de>: Subject: Re: Terminal driver for VAX synchronous interface* Message-ID: <00A1D5B8.22F11DAA.2@decus.de>  + "Nic Clews" <sendspamhere@127.0.0.1> wrote:d   > [...]i > E > This is for the hobby system. I am using AUTODIAL UUCP (ported fromAH > UNIX) to manage the dial-up, wrapped in a DCL procedure to perform theI > dial out and establish the link, then switch up a dynamic PPP link fromnE > the IP software. The complication is that the ISDN terminal adaptervH > talks synchronous, and no serial ports I know of are capable under VAXI > and VMS which present themselves as terminal class (unless anyone knows 5 > better). Only looking for single port connectivity.e >  > Thanks in anticipation.   I Strange -- I haven't seen any ISDN adapter with a synchronous interface, aE just native RS/EIA-232 ones and asynchronous communication. To avoid dI problems the baud rate from/to the computer has to be set above the ISDN eC basic channel rate of 64kbit and _hardware_ flow control has to be -
 activated.  4 No, I don't have a solution to your special problem.   Michaelh   ------------------------------  # Date: Mon, 24 Mar 2003 14:33:48 GMT 3 From: hammond@not@peek.ssr.hp.com (Charlie Hammond)lQ Subject: Re: [Q] Files not found during image backup, w/ and w/o directory-specs... Message-ID: <gHEfa.704$Js.35@news.cpqcorp.net>  n In article <b096a4ee.0303211500.3ab58fcf@posting.google.com>, spamsink2001@yahoo.com (Alan E. Feldman) writes: >Hello,) > D >Question about BACKUP/IMAGE files not found: Below you can see someF >files called XXMONREM.LOG which were not found. The job XXMONREM runs@ >every 35 minutes and it purges its logfile, XXMONREM.LOG, to 20G >versions each run. So I assume this has something to do with the filesqE >being purged during the backup. Now, can anyone explain why one fileiE >appears twice with and without a real dir-spec and why the other hasc	 >just []?n  E Remember that *NOTHING* is guaranteed when you use /IGNORE=INTERLOCK.-C There is NO coordination between what BACKUP is doing and the file ,D deletes your XXMONREM job is doing.  It is practically impossible toB reconstruct the relative timing of these two operations, but it isG pretty clear that BACKUP has out-of-date and/or incomplete information.,  F That said, my guess is that the file that appears twice may be in both4 SYS$COMMON and one or more SYS$SPECIFIC directories.     -- 0J       Charlie Hammond -- Hewlett-Packard Company -- Ft Lauderdale  FL  USAF           (hammond@not@peek.ssr.hp.com -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------    Date: 24 Mar 2003 10:07:43 -0800. From: spamsink2001@yahoo.com (Alan E. Feldman)Q Subject: Re: [Q] Files not found during image backup, w/ and w/o directory-specs. = Message-ID: <b096a4ee.0303241007.4ab2772d@posting.google.com>t  i hammond@not@peek.ssr.hp.com (Charlie Hammond) wrote in message news:<gHEfa.704$Js.35@news.cpqcorp.net>...up > In article <b096a4ee.0303211500.3ab58fcf@posting.google.com>, spamsink2001@yahoo.com (Alan E. Feldman) writes:	 > >Hello,i > > F > >Question about BACKUP/IMAGE files not found: Below you can see someH > >files called XXMONREM.LOG which were not found. The job XXMONREM runsB > >every 35 minutes and it purges its logfile, XXMONREM.LOG, to 20I > >versions each run. So I assume this has something to do with the filesrG > >being purged during the backup. Now, can anyone explain why one fileoG > >appears twice with and without a real dir-spec and why the other has( > >just []?i > G > Remember that *NOTHING* is guaranteed when you use /IGNORE=INTERLOCK.0E > There is NO coordination between what BACKUP is doing and the file tF > deletes your XXMONREM job is doing.  It is practically impossible toD > reconstruct the relative timing of these two operations, but it isI > pretty clear that BACKUP has out-of-date and/or incomplete information.t    C But wouldn't this have happened even without /IGNORE=INTERLOCK? TheDA files that were not found were created and closed well before theaF backup started. The only thing that happened to those files during theD backup was the PURGE command. Remember, 20 versions are kept. So theD files that were purged were last open more than 20*35 minutes beforeE the end of the save pass of the backup operation. It looks to me that A they were being deleted just as the backup operation was reaching D those files during its directory tree pass. But why with and withoutF directory-specs, and why one of them twice? (It is incredibly unlikelyD that any user was actually looking at these files during the backup.E The only person likely to look at them was I and I know I didn't look B at them during this backup. I would really be totally astounded ifB anyone except me here has ever looked at any of the log files with this name.)i  D I am currently under the impression that during BACKUP/IMAGE, one ofE the first things that happens is a scan of INDEXF.SYS to build a listeD of all files on the disk. Then BACKUP walks the directory structure,E marking off files in the index list it made as it copies files to the A save set. Then, when BACKUP has finished traversing the directory0B structure, the index list is checked for uncopied files, and theseF files are copied last and recorded with directory "[]". Now, if a fileF is deleted after the index scan, but before the directory pass reachesD that file, I would expect the "file not found" message. That's fine.> But I don't see what this has to do with /IGNORE=INTERLOCK. If> /IGNORE=INTERLOCK were not specified, how would that make this situation different?  D It appears to me that file deletion is somewhat complicated and thatD has something to do with the strange error messages I received. What? is the best place to look for how file deletion works in VMS onb Files-11 ODS-2 structure disks?o  E Summary: These files were *not* open during the backup operation. TheaA only thing that happened to them is that they were victims of therF PURGE command. So I would think that would mean that /IGNORE=INTERLOCK% has nothing to do with it. OCICBW,YK.l    H > That said, my guess is that the file that appears twice may be in both6 > SYS$COMMON and one or more SYS$SPECIFIC directories.    , Nope. The files lived in the directory [XX].   Thanks for your response.I   Disclaimer: JMHO Alan E. FeldmanF   ------------------------------   End of INFO-VAX 2003.164 ************************