0 INFO-VAX	Sat, 24 Jan 2004	Volume 2004 : Issue 47      Contents: RE: 500.000 AMD64's shipped... Devicename for COM1 on Alpha ?" Re: Devicename for COM1 on Alpha ?* Re: Kay resigns: no WMDs since early 1990s* Re: Kay resigns: no WMDs since early 1990s* Re: Known problems with V7.3 security MUP?* Re: Known problems with V7.3 security MUP? Re: ODS5 and UNZIPG Re: OpenVMS Hardware Troubleshooting? (was: Re: walking into a war zone 4 Re: Pathworks 32 Client and Windows 2000 performance Re: SpecInt values - ES40/GS80@ Re: The Register: OpenVMS among most-secure of operating systems@ Re: The Register: OpenVMS among most-secure of operating systems$ Re: VMS authentication to Windows AD Re: walking into a war zone # Re: Where is XML generator for VMS? # Re: Where is XML generator for VMS? # Re: Where is XML generator for VMS?  Re: Your mother is so fat...  F ----------------------------------------------------------------------  % Date: Sat, 24 Jan 2004 09:37:00 -0500 ' From: "Main, Kerry" <kerry.main@hp.com> ' Subject: RE: 500.000 AMD64's shipped... R Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB2381A6@tayexc19.americas.cpqcorp.net>   > -----Original Message-----, > From: Andrew Harrison SUNUK Consultancy=203 > [mailto:Andrew_No.Harrison_No@nospamn.sun.com]=20   > Sent: January 23, 2004 6:01 AM > To: Info-VAX@Mvb.Saic.Com ) > Subject: Re: 500.000 AMD64's shipped...  >=20 > Greg Cagle wrote: > > > Andrew Harrison SUNUK Consultancy said the following on=20 > 1/22/2004 10:03 AM:  > >=20 > >> jlsue wrote:  > >> > >>> 5 > >>> So let's see, we can NEVER believe what some=20  > people/vendors tell us=20 B > >>> anymore, so let's just pack up and all go home.  Is that it? > >>>  > >> > >> You forget  > >>? > >> You work for an organisation which is a multiple offendor.  > >>E > >> On the three strikes and you are out principle you would be out.  > >=20 > >=20A > > And Sun, of course, ALWAYS delivers on their commitments. 8^)  > >=20 >=20< > There is a huge difference between being late to deliver a? > product (every IT vendor is guilty of this) to not delivering ? > the product at all because you have decided to axe it without   > consulting your customer base. >=20= > Sun is the first category along with Intel, IBM, SGI etc HP  > is in the second category. >=208 > Fab piece of spin Greg, very Rob Young esk keep it up. >=20	 > Regards  > Andrew Harrison  >=20   Andrew -  H Re: Sun not in category of axing products without consulting Customers..   ROTFL !!   :-)  :-)   What about this:  9 First, Sun pushes Cobalt servers with releases like this: F http://www.sun.com/smi/Press/sunflash/2002-06/sunflash.20020617.5.html   Then, they do this:   G http://news.com.com/2100-1010_3-5134234.html?tag=3Dnefd_top (December =  31,  2003) E "Just three years after Sun Microsystems paid $2 billion in stock for E server appliance maker Cobalt Networks, Sun has killed off the Cobalt  product line."  2 http://www.theregister.co.uk/content/61/34595.html- "Sun drives the final nail in Cobalt's coffin  By Ashlee Vance in Chicago Posted: 18/12/2003 at 19:14 GMT 6 Get The Reg wherever you are, with The Mobile Register  G $2.1 billion does not go as far these days as it used to - just ask Sun  Microsystems.=20  C Sun's massive 2001 purchase price for server appliance maker Cobalt F Networks seems a tad silly with the entire product line being sent outD to pasture. Thanks to a tip, The Reg has uncovered Sun's decision toD end-of-life every Cobalt product, including the elegant Qube and RaQF systems, with no replacements planned. And with Cobalt's demise ends aB couple of eras - one of dotcom hype-driven investments and another+ marking the death of the server appliance."     ' Oh, I know, this is different, right ..    :-)   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  Email: kerryDOTmainAThpDOTcom . (remove the DOT's and AT for email address)=20   ------------------------------  # Date: Sat, 24 Jan 2004 17:04:46 GMT 2 From: m.grafinger@tuwien.ac.at (Manfred Grafinger)' Subject: Devicename for COM1 on Alpha ? 2 Message-ID: <4012a43a.446915039@news.tuwien.ac.at>   Hello VMS-Gurus.  E I have changed the VAX-station, where our plotter was connected to an C Alpha. Now i cannot identify the devicename of the COM1. On the Vax D the plotter was connected at the serial port device tta0: but on theD alpha tta0: goes to nirwana, also ttb0: and i have not any other tt* devices in show device.   C Somebody out there knows the device name of the COM1 on Alpha-VMS ?    Much thanks, Manfred   --  # + - - - - - - - - - - - - - - - - + # ' Dr.-techn.  Manfred  GRAFINGER  ' # ' Technische  Universitaet  Wien  ' # ' Institut fr Maschinenelemente  ' # ' 1060 WIEN, Getreidemarkt 9/306  ' # ' manfred.grafinger@tuwien.ac.at  ' # ' Tel.: + 43 - 1 / 58801 / 30612  ' # + - - - - - - - - - - - - - - - - +    ------------------------------  # Date: Sat, 24 Jan 2004 17:17:54 GMT " From:   VAXman-  @SendSpamHere.ORG+ Subject: Re: Devicename for COM1 on Alpha ? 0 Message-ID: <00A2C5FC.8F54D96F@SendSpamHere.ORG>  g In article <4012a43a.446915039@news.tuwien.ac.at>, m.grafinger@tuwien.ac.at (Manfred Grafinger) writes:  >Hello VMS-Gurus.  > F >I have changed the VAX-station, where our plotter was connected to anD >Alpha. Now i cannot identify the devicename of the COM1. On the VaxE >the plotter was connected at the serial port device tta0: but on the E >alpha tta0: goes to nirwana, also ttb0: and i have not any other tt*  >devices in show device. > D >Somebody out there knows the device name of the COM1 on Alpha-VMS ?   What Alpha machine?   I On my Alpha machines, what I believe you are calling COM1 (<==> 1) is the I console port OPA0 because I have my systems configured SET CONSOLE SERIAL H This leave the COM2 (<==> 2) port to be designated TTA0:.  IIRC, settingC the console (SET CONSOLE GRAPHICS) causes the COM1 to become TTB0:.    --B http://www.legacy-2000.com  for the *best* OpenVMS system securityC                             solutions that others only claim to be.  --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM              5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------  # Date: Sat, 24 Jan 2004 11:28:38 GMT . From: "C. Pangus" <craigpangus@sprintmail.com>3 Subject: Re: Kay resigns: no WMDs since early 1990s B Message-ID: <GFsQb.22115$q4.9352@newsread3.news.atl.earthlink.net>  A "Mezei's Pearls of Wisdom" <mezeitrolls@the.net> wrote in message 1 news:FGWM9CNJ38009.9831828704@anonymous.poster... E > The Bush regime has replaced Kay with another one of their cronies.  Perhaps K > the new one will be more willing to plant evidence and produce the golden  > egg D > that Bush really needs before the election to prove he was right ? >     L     Just how far Bush & Co will go in faking it is a recurring thought.  TheJ entire war was based on falsifications of WMD's.  What else has, and will,B they fake or plant?  I mean, the number of dead from 9/11 pales inH comparison to the number they have killed under false pretenses in Iraq.K     If a cop gets caught faking the reasons for shooting someone they go to ' jail.  What will Bush get?  Re-elected?    ------------------------------    Date: 24 Jan 2004 07:49:05 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) 3 Subject: Re: Kay resigns: no WMDs since early 1990s 3 Message-ID: <BDXAfGn4urzo@eisner.encompasserve.org>   & > X-Complaints-To: abuse@earthlink.net  s In article <GFsQb.22115$q4.9352@newsread3.news.atl.earthlink.net>, "C. Pangus" <craigpangus@sprintmail.com> writes:    ------------------------------  % Date: Sat, 24 Jan 2004 14:35:34 +0100 * From: Paul Sture <nospam@sture.homeip.net>3 Subject: Re: Known problems with V7.3 security MUP? 0 Message-ID: <401282B6.7F24DC77@sture.homeip.net>   Jeff Goodwin wrote:  > B > "Charlie Hammond" <hammond@not@peek.ssr.hp.com> wrote in message/ > news:ipdQb.12915$9h6.1707@news.cpqcorp.net...  > > In articleG > <OFAA2100CF.3F3F62F5-ON85256E24.00591489-85256E24.0059BA47@metso.com, " > > norm.raphael@metso.com writes: > > > D > > >Mike Duffy <Duffy@process.com> wrote on 01/23/2004 09:55:19 AM: > > ..= > > >> The following kits were installed, in the order below:  > > >> > > >>   VMS73_PCSI-V0100  > > >>   VMS73_UPDATE-V0300  > > >>   VMS73_SYS-0700  > > >>; > > >> I did install them all without rebooting in between, ! > > >> and only booted afterward.  > > > < > > >I cannot say for certain, but whenever PCSI is patched,? > > >it is playing with fire not to do that patch by itself ...  > > = > > Yes this is a good idea.  It is not completely clear, but A > > I would read the above to indicate that three PRODUCT INSTALL D > > commands were issued.  Otherwise the order of installation would+ > > have been detemined by the PCSI utlity.  > > A > > >... and then reboot.  The failure to do that probably caused 6 > > >your problem with the second PRODUCT INSTALL. ... > > > > > Patching PCSI should not require a reboot.  If the patches< > > were installed by thre seperate PRODUCT INSTALL commands > > this should hav worked.  > K > Rebooting certainly isn't required, but it would be prudent to logout and K > back in again after installing the PCSI patch.  This will ensure that the K > install process is using the newly updated DCLTABLES for the next PRODUCT J > INSTALL.  I suspect this was the cause of the original poster's problem. >   B I encountered a similar problem when applying VMS731_PCSI V1.0 andB VMS731_UPDATE V1.0 in a single session; the second PRODUCT INSTALL; failed, and logging out and then in again was the solution.   D > > Without checking, I suspect that either the UPDATE or SYS patch,0 > > or both of them  may have required a reboot. > >  > > --N > >       Charlie Hammond -- Hewlett-Packard Company -- Ft Lauderdale  FL  USAJ > >           (hammond@not@peek.ssr.hp.com -- remove "@not" when replying)N > >       All opinions expressed are my own and not necessarily my employer's. > >    --     --  
 Paul Sture   ------------------------------  % Date: Sat, 24 Jan 2004 14:45:12 +0100 * From: Paul Sture <nospam@sture.homeip.net>3 Subject: Re: Known problems with V7.3 security MUP? 0 Message-ID: <401284F8.57E8194D@sture.homeip.net>   Jeff Goodwin wrote:  > B > "Charlie Hammond" <hammond@not@peek.ssr.hp.com> wrote in message/ > news:ipdQb.12915$9h6.1707@news.cpqcorp.net...  > > In articleG > <OFAA2100CF.3F3F62F5-ON85256E24.00591489-85256E24.0059BA47@metso.com, " > > norm.raphael@metso.com writes: > > > D > > >Mike Duffy <Duffy@process.com> wrote on 01/23/2004 09:55:19 AM: > > ..= > > >> The following kits were installed, in the order below:  > > >> > > >>   VMS73_PCSI-V0100  > > >>   VMS73_UPDATE-V0300  > > >>   VMS73_SYS-0700  > > >>; > > >> I did install them all without rebooting in between, ! > > >> and only booted afterward.  > > > < > > >I cannot say for certain, but whenever PCSI is patched,? > > >it is playing with fire not to do that patch by itself ...  > > = > > Yes this is a good idea.  It is not completely clear, but A > > I would read the above to indicate that three PRODUCT INSTALL D > > commands were issued.  Otherwise the order of installation would+ > > have been detemined by the PCSI utlity.  > > A > > >... and then reboot.  The failure to do that probably caused 6 > > >your problem with the second PRODUCT INSTALL. ... > > > > > Patching PCSI should not require a reboot.  If the patches< > > were installed by thre seperate PRODUCT INSTALL commands > > this should hav worked.  > K > Rebooting certainly isn't required, but it would be prudent to logout and K > back in again after installing the PCSI patch.  This will ensure that the K > install process is using the newly updated DCLTABLES for the next PRODUCT J > INSTALL.  I suspect this was the cause of the original poster's problem. >   B I encountered a similar problem when applying VMS731_PCSI V1.0 andB VMS731_UPDATE V1.0 in a single session; the second PRODUCT INSTALLD failed, so I rebooted and then it worked. I realised too late that IF might have simply been able to get away with logging in again, but did  kick myself that I hadn't tried.  D > > Without checking, I suspect that either the UPDATE or SYS patch,0 > > or both of them  may have required a reboot. > >  > > --N > >       Charlie Hammond -- Hewlett-Packard Company -- Ft Lauderdale  FL  USAJ > >           (hammond@not@peek.ssr.hp.com -- remove "@not" when replying)N > >       All opinions expressed are my own and not necessarily my employer's. > >    --     --  
 Paul Sture   ------------------------------  % Date: Sat, 24 Jan 2004 11:18:10 -0600 6 From: "Craig A. Berry" <craigberry@mac.com.spamfooler> Subject: Re: ODS5 and UNZIP T Message-ID: <craigberry-89D500.11181024012004@dsl081-159-101.chi1.dsl.speakeasy.net>  8 In article <burc2c$l6trb$1@ID-56200.news.uni-berlin.de>,/  "Martin Vorlaender" <mv@pdv-systeme.de> wrote:    > Craig A. Berry wrote:  > >> Gerald Marsh wrote:J > >>> After checking that I had the latest Alpha version of UNZIP (V5.5, IJ > >>> think - apologies for the uppercase commands but old habits etc!), IJ > >>> tried and tried and tried to recreate the directory structure on the > >>> ODS 5 disk to no avail.  > > : > > The problem is filename characters that are illegal onD > > ODS-2. I don't know of any way to make current versions of unzipB > > handle these without translation (short of modifying the unzip
 > > sources).  > H > I did have a look into the sources, and it shouldn't be too hard to doG > (use DVI$_ACPTYPE to determine whether it's ODS-5, add a command line F > switch to force ODS-2 names - all modeled after vmstar; add a bit ofH > code to [.vms]vms.c:mapname to change/suppress the character mapping). > B > The only thing I didn't see (it was a really quick look) is what > the output device is...   B This sounds interesting, but I'm not entirely happy with vmstar's E approach.  On an ODS-5 disk, it creates filenames in extended format  E regardless of whether extended parse is enabled.  I've lost count of  C how many times I've unpacked a package and then been unable to set  H default into its top-level directory with a name like [.foo-1^.0] until H I enable extended parse.  This is annoying to me and must be disastrous  for newbies.  E Also, one of the things I like about unzip is that it preserves case  E even when it mangles the names into ODS-2 safe form; I'd like to see  ( vmstar have an option like that as well.  G Unfortunately there are still a number of packages (Perl, for example)  I that don't handle extended syntax, and a different set of packages (MMS,  @ the librarian) that are not as case-blind as they need to be in A processing filenames, so it would be really helpful to have case  + preservation and extended syntax decoupled.    ------------------------------  # Date: Sat, 24 Jan 2004 14:49:31 GMT 2 From: "Ken Farmer" <KFarmer@NOSPAM.SpyderByte.com>P Subject: Re: OpenVMS Hardware Troubleshooting? (was: Re: walking into a war zone= Message-ID: <%BvQb.13154$5K1.629935@twister.southeast.rr.com>   0 "Hoff Hoffman" <hoff@hp.nospam> wrote in message- news:eqjQb.12978$yC6.9221@news.cpqcorp.net... > > In article <e6c6a64b.0401231240.7ebaf9a@posting.google.com>,/ emailforwes@earthlink.net (Wes Emerson) writes:  > H > :Now my question to the multitudes, are there any commands that can beF > :used to check hardware such as cpu's, memory, and discs to look for > :hardware failures.  > 8 >   Sorry.  I'm just a person, and not a multitude.  :-)  3 When it comes to VMS knowledge that's arguable.  :)    -- Kenneth Farmer <>< OpenVMS.org    ------------------------------  % Date: Thu, 22 Jan 2004 11:04:09 -0500 $ From: "PEN" <paul.nuneznosp@mhp.com>= Subject: Re: Pathworks 32 Client and Windows 2000 performance , Message-ID: <buos9t$ikk$1@hplms2.hpl.hp.com>   Hi,   L Sent Andy a message off-line with patched version of decdnp.sys that may fix this problem...    Paul   ------------------------------  % Date: Sat, 24 Jan 2004 11:50:25 -0500 2 From: "Chris Moore" <chrismichael000@sympatico.ca>' Subject: Re: SpecInt values - ES40/GS80 : Message-ID: <VlxQb.20784$cQ6.994075@news20.bellglobal.com>  J HP site gives SPECint2000 for the new boxes, SPECint95 for the older ones.I (I've never looked at the differences in the BM tests, I'll leave that to L you to judge, but if you look at the different ES40's it looks like an order of magnitude difference)   GS80/ GS160/ GS320
 Model 68/1224 "             SPECint2000        883   ES40 Model 6/667              SPECint95        40  Model 68/883             SPECint2000    565    = "Dave Baxter" <dave.baxter@bannerhealth.com> wrote in message 6 news:a3c44af1.0401221025.90e70eb@posting.google.com...E > Can anyone give me the SpecInt ratings for the 667MHz CPU's used in E > the ES40, and the 1224 MHz CPU's used in the GS80/GS160.   (or just  > the performance ratio even)  >  > Dave.    ------------------------------   Date: 24 Jan 2004 07:30:51 GMT2 From: "Dave Weatherall" <djw-nothere@nospam.nohow>I Subject: Re: The Register: OpenVMS among most-secure of operating systems 5 Message-ID: <DTiotGxQ0bj6-pn2-ugdGOYYEZQoq@localhost>   D On Thu, 22 Jan 2004 18:09:12 UTC, Andrew Harrison SUNUK Consultancy . <Andrew_No.Harrison_No@nospamn.sun.com> wrote:   > Bob Koehler wrote: > > In article <buojdg$74u$1@new-usenet.uk.sun.com>, Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> writes: > > 9 > >>Fact, HP/Compaq and the various owners of TCPWARE and < > >>Multinet have released patches for general vunerabilites< > >>in OpenSource components which apply to those components9 > >>running on OpenVMS and have admitted the vunerability ; > >>in CERT advisories. Why would they do this if they were  > >>not vunerable ?  > >  > > @ > >    Issuing a patch and admitting "affected" shows that thereC > >    must have been a bug.  It does not prove that the bug was a   > >    security issue. > > ; > Ohh more grasping at straws. Admiting that there is a bug < > with a patch for it in a forum that is only concerned with. > security issues that it is a security issue.   AndrewF                you've done this to death and it's degenerating into a  (boring) Monty Python sketch.  --   Cheers - Dave.   ------------------------------  % Date: Sat, 24 Jan 2004 02:55:30 -0500   From: John Santos <JOHN@egh.com>I Subject: Re: The Register: OpenVMS among most-secure of operating systems 6 Message-ID: <1040124023827.33368A-100000@Ives.egh.com>  = On Thu, 22 Jan 2004, Andrew Harrison SUNUK Consultancy wrote:    > John Santos wrote:A > > On Wed, 21 Jan 2004, Andrew Harrison SUNUK Consultancy wrote:  > >  > >  > >>jlsue wrote: > >>J > >>>On Fri, 16 Jan 2004 10:55:56 +0000, Andrew Harrison SUNUK Consultancy3 > >>><Andrew_No.Harrison_No@nospamn.sun.com> wrote:  > >>>  > >>>  > >>>  > >>>>jlsue wrote: > >>>> > >>>>O > >>>>>On Thu, 15 Jan 2004 02:23:45 -0500, JF Mezei <jfmezei.spamnot@istop.com> 
 > >>>>>wrote:  > >>>>>  > >>>>>  > >>>>>  > >>>>> O > >>>>>>When they discovered the flaw in the POP server that would allow one to U > >>>>>>overwrite any file on the system because the impage was installed with SYSPRV V > >>>>>>and could be called interactively with a log file specification, did that make > >>>>>>it to CERT ? > >>>>>  > >>>>> Q > >>>>>Whose POP server?  Do I run that on my systems?  If not, then now could it 9 > >>>>>affect me and why would it actually be a VMS CERT?  > >>>>>  > >>>>6 > >>>>In fact its the HP POP server but that is rather > >>>>irrelevant.  > >>>  > >>> I > >>>But my system (hypothetically) runs Multinet.  So then what do I do?  > >>>  > >>@ > >>Does it matter, CERT is not about people being selective andA > >>restricting advisories to things that will hit everyone while B > >>editing out advisories that will only impact a subset of their
 > >>users. > >  > > A > > What about things that will impact *none* of their users?  Do 9 > > you accept that no advisory is required in that case?  > >  > >  > ; > Depends, many advisories are theoretical with no recorded 9 > exploits except in a lab. You could remove all these if = > you want however it will make the number of CERT advisories , > for Linux/UNIX and Windows rather smaller.  A That's not what I'm talking about.  I'm talking about cases where > if you send a particular sequence of messages to some host (or@ if you run a particular user-mode program that calls some set of= library routines or type a particular series of commands at a @ non-privileged user prompt), you can crash the system or acquire> elevated privileges or hang the system or cause other mischief> on *SOME* system (even theoretically), but on other platforms,A the exploit *DOESN'T* *WORK* because the buffer overrun it relies @ on is detected before other memory is overwritten or because the@ XYZ utility runs in user mode without special privileges insteadA of in kernel mode or the bug in the library doesn't exist on this A platform.  So there is no exploit and no exposure to users of the ; second platform.  However, the code in question is a widely > distributed open-source application, and the maintainers of itB produce a patch and/or a new version to prevent the buffer overrun> or to drop privileges around the problem area or to check file= access correctly or to call the library routine in such a way ; that the bug doesn't occur...  In order to stay current and B portable, the supplier of this software on the 2nd platform issues@ a new version (perhaps bundled with other, non-security related A improvements, or maybe not, or as part of a patch bundle for lots D of other programs as well), incorporating the (for them unnecessary); source code changes.  Are they remiss in not issuing a CERT  advisory about this?   > : > It also doesn't remove the possibility that someone will7 > find a way of exploiting the vunerability in the wild 7 > in the future, so in reality they should be reported.   ? I'm explicitly not including exploits that are even theorically  possible on the given platform.   	 > Regards  > Andrew Harrison    --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Thu, 22 Jan 2004 11:24:03 -0500 $ From: "PEN" <paul.nuneznosp@mhp.com>- Subject: Re: VMS authentication to Windows AD , Message-ID: <buotf6$jra$1@hplms2.hpl.hp.com>   Hi Mike,  I Yes you can.  You need to install, configure, and run Advanced Server for I OpenVMS and modify user's OpenVMS accounts (in sysuaf.dat) to include the 
 flag EXTAUTH.   L Advanced Server for OpenVMS can participate in your Windows 2000 domain as a Member server.  K If the user's Windows domain username doesn't match their OpenVMS username,  use the command:  5 $ ADMIN ADD HOSTMAP <domain-username> <OVMS-username>   ? command to associate the two (Advanced Server must be running).   I Once the extauth flag is set, the user is no longer validated against the G sysuaf username/password, but instead their Windows domain username and D password (case sensitive, of course).  When they change their domainJ password, the next time they login to OpenVMS, it triggers a sync of theirJ sysuaf account password (just in case the user stops using extauth or theyK have some network (aka client/server) app that accesses sysuaf.dat directly   to verify a user's credentials).  G Best of all, no license required if you use Advanced Server for extauth K only.  The Advanced Server client access licenses are necessary only if you H wish to allow your Windows clients to map to file/print shares served by Advanced Server for OpenVMS.  F Highly recommend you obtain the latest/greatest release - v7.3A ECO2 -J available on the ITRC ftp site ftp://ftp.itrc.hp.com/.  Look for a saveset named   4 CPQ-AXPVMS-ADVANCEDSERVER-V0703-A2-1.PCSI-DCX_AXPEXE  C (I can't currently get to the site to confirm ECO2 is now there)...    HTH,     Paul  C "Michael D. Ober" <obermd-.@.-alum-mit-edu-nospam> wrote in message * news:SARPb.10$1b1.25455@news.uswest.net...J > I need to have my users periodically change their passwords, but most ofL > them are computer illiterate (they have no idea what a command line is andI > sometimes have a hard time logging into a Windows Domain without help).  IsI > there anyway to have VMS authenticate to a Windows 2000 AD Domain?  I'm J > reasonably sure I can train them to change their passwords when prompted by
 > the domain.  >  > TCPIP SHO VER returns  > @ >  Compaq TCP/IP Services for OpenVMS Alpha Version V5.3 - ECO 2: >   on a AlphaServer 1200 5/533 4MB running OpenVMS V7.3-1 > 	 > Thanks,  > Mike Ober. >  >    ------------------------------  % Date: Sat, 24 Jan 2004 11:26:27 -0500 2 From: "Chris Moore" <chrismichael000@sympatico.ca>$ Subject: Re: walking into a war zone: Message-ID: <q%wQb.20774$cQ6.991131@news20.bellglobal.com>  7 "JF Mezei" <jfmezei.spamnot@istop.com> wrote in message # news:4011F851.952CFE67@istop.com...  > "David J. Dachtera" wrote:J > > The older command is ANALYZE/ERROR (again, see the HELP), but this has@ > > been deprecated in favor of the DIAGNOSE command (DECevent). > D > DIAGNOSE does not exist on VAX, ANA/ERROR is still current on VAX.  J Sorry to be the bearer of bad tidings JF, but DIAGNOSE (aka DECevent) mostI certainly does exist on VAX (at least the 10 that I look after)  It isn't G much more functional, but it is there.  ANAL/Error can be used as well. E ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~   , NESS::CMOORE $ diagnose/since/exclude=volume  
 DECevent V3.4     L **** V3.4  ********************* ENTRY 4358 ********************************    , Logging OS                        1. OpenVMS( System Architecture               1. VAX) OS version                           V7.1 $ Event sequence number         52436.9 Timestamp of occurrence              24-JAN-2004 01:00:38 8 Time since reboot                    158 Day(s) 17:10:48) Host name                            NESS    ------------------------------  + Date: Sat, 24 Jan 2004 08:49:17 +0000 (UTC) ( From: ExGuardianReader <noway@noway.com>, Subject: Re: Where is XML generator for VMS?2 Message-ID: <butbic$qcb$1@hercules.btinternet.com>   Craig A. Berry wrote: 2 > In article <bumfm0$eg7$1@grapevine.wam.umd.edu>,. >  bleau@umtof.umd.edu (Lawrence Bleau) wrote: >  > F >>Hello.  I'm running OpenVMS AXP V7.3-2.  We have a need to create anG >>XML document containing ascii scientific data for distribution to our G >>colleagues.  A description of the XML elements to be used has already + >>been developed, though it may be refined.  >>B >>What I need is a tool that can be used to generate a file in XML >>format.    >  > E > The libxml2 package from Gnome includes a toolkit called XMLWriter  G > which sounds like it will do what you want.  There's an example in C   > here:  > * > http://xmlsoft.org/examples/testWriter.c > E > Of course if your DTD is extremely simple and not likely to change  ? > much, you could just hard-code the tags in your FORTRAN code.  > E > There are numerous Perl modules to assist with what you are doing,  > > including XML::Writer, XML::Generator, or XML::Mini.  Go to , > http://search.cpan.org and search for XML.  H Why not download Java for free and just write a simple SAX XMLReader to G read the data, and provide element start/end/content events to an XSLT   transformation? Simple as that.   9 You can easily get from any data format to XML like this.    ------------------------------  % Date: Sat, 24 Jan 2004 23:19:12 +0800 , From: Paul Repacholi <prep@prep.synonet.com>, Subject: Re: Where is XML generator for VMS?- Message-ID: <87llnx2x3j.fsf@prep.synonet.com>   , bleau@umtof.umd.edu (Lawrence Bleau) writes:  F > Hello.  I'm running OpenVMS AXP V7.3-2.  We have a need to create anC > XML document containing ascii scientific data for distribution to C > our colleagues.  A description of the XML elements to be used has 3 > already been developed, though it may be refined.   D > Btw, the XML doc we're making will have a fairly simple structure,C > just a description of a time series of data points, with the main ? > content being the data themselves.  The preferred language is B > Fortran, although I can handle C (the boss won't like it, but if- > that's all that's available, we'll use it).   > Why not use FITS or HDF or another of the existing formats for astrophysical data?    --  < 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: Sat, 24 Jan 2004 10:44:36 -0600 6 From: "Craig A. Berry" <craigberry@mac.com.spamfooler>, Subject: Re: Where is XML generator for VMS?T Message-ID: <craigberry-76382F.10443624012004@dsl081-159-101.chi1.dsl.speakeasy.net>  2 In article <butbic$qcb$1@hercules.btinternet.com>,*  ExGuardianReader <noway@noway.com> wrote:   > Craig A. Berry wrote: 4 > > In article <bumfm0$eg7$1@grapevine.wam.umd.edu>,0 > >  bleau@umtof.umd.edu (Lawrence Bleau) wrote: > >  > > H > >>Hello.  I'm running OpenVMS AXP V7.3-2.  We have a need to create anI > >>XML document containing ascii scientific data for distribution to our I > >>colleagues.  A description of the XML elements to be used has already - > >>been developed, though it may be refined.  > >>D > >>What I need is a tool that can be used to generate a file in XML
 > >>format.    > >  > > G > > The libxml2 package from Gnome includes a toolkit called XMLWriter  I > > which sounds like it will do what you want.  There's an example in C  	 > > here:  > > , > > http://xmlsoft.org/examples/testWriter.c > > G > > Of course if your DTD is extremely simple and not likely to change  A > > much, you could just hard-code the tags in your FORTRAN code.  > > G > > There are numerous Perl modules to assist with what you are doing,  @ > > including XML::Writer, XML::Generator, or XML::Mini.  Go to . > > http://search.cpan.org and search for XML. > J > Why not download Java for free and just write a simple SAX XMLReader to  > read the data,    F How is an XML reader going to help him when his data are not (yet) in F XML?  Java is a good suggestion, though; I'm sure there are XMLWriter  classes for Java available.   : > and provide element start/end/content events to an XSLT ! > transformation? Simple as that.  > ; > You can easily get from any data format to XML like this.   H XSLT can get you from one XML document type to another, and export from F an XML document type to various non-XML formats.  I've never seen any G indication it can get you from a non-XML format into XML, but would be  ( happy to hear about it if it's possible.   ------------------------------    Date: 24 Jan 2004 10:38:56 -0800( From: bob@instantwhip.com (Bob Ceculski)% Subject: Re: Your mother is so fat... = Message-ID: <d7791aa1.0401241038.47986998@posting.google.com>   - Why are you posting this on the OpenVMS site? + VMS users don't worry about viruses because  VMS is "UNHACKABLE"!  * http://www.pointsecure.com/Defconwhite.pdf   ------------------------------   End of INFO-VAX 2004.047 ************************                                                                                                                        257 "/disk$misc/decus/freewarev50/circlemud/circle30bpl17" is current directory.
 <<< CWD docnP >>> 250 Connected to /disk$misc/decus/freewarev50/circlemud/circle30bpl17/doc. <<< TYPE A >>> 200 Type A ok.
 <<< PASVA >>> 227 Entering passive mode; use PORT (198,151,12,104,11,191)
 <<< LIST >>> 150 List started.n >>> 226 Transfer completed.s	 <<< PWDsZ >>> 257 "/disk$misc/decus/freewarev50/circlemud/circle30bpl17/doc" is current directory. <<< CWD old-docsY >>> 250 Connected to /disk$misc/decus/freewarev50/circlemud/circle30bpl17/doc/old-docs.n <<< TYPE A >>> 200 Type A ok.
 <<< PASVA >>> 227 Entering passive mode; use PORT (198,151,12,104,11,192)<
 <<< LIST >>> 150 List started.  >>> 226 Transfer completed.eC <<< CWD /disk$misc/decus/freewarev50/circlemud/circle30bpl17/doc/sP >>> 250 Connected to /disk$misc/decus/freewarev50/circlemud/circle30bpl17/doc.? <<< CWD /disk$misc/decus/freewarev50/circlemud/circle30bpl17/L >>> 250 Connected to /disk$misc/decu