1 INFO-VAX	Thu, 18 May 2000	Volume 2000 : Issue 277       Contents: "Modern" OpenVMS?  Backup image problem Re: Backup image problem Re: Backup solution/server Re: Backup solution/server, Re: Compaq Bets Big on New Web Servers (WSJ), Re: Compaq Bets Big on New Web Servers (WSJ), Re: Compaq Bets Big on New Web Servers (WSJ) Re: CPU Temperature from DCL Re: CPU Temperature from DCL- Re: crystal clear vms filesystem from nt side - re: crystal clear vms filesystem from nt side  Re: DFOR$ALLOC_ALLOCATABLE64, Re: Duplicated messages: are only I see it ?
 Error on SMTP ( Re: External authentication in a cluster F$GETQUI() and job info help  Re: F$GETQUI() and job info help  Re: F$GETQUI() and job info helpA Re: Geting Temperature from CA (was Re: CPU Temperature from DCL) A Re: Geting Temperature from CA (was Re: CPU Temperature from DCL)  How do you search for files?  Re: How do you search for files?  Re: How do you search for files?  Re: How do you search for files?) RE: Inserting a DATE (was Re: EDT macros) ) RE: Inserting a DATE (was Re: EDT macros) % Re: Is "The GNU on VMS Project" dead? ) IS THERE LIMITS TO THE LOCAL SYMBOL TABLE - Re: IS THERE LIMITS TO THE LOCAL SYMBOL TABLE  Re: Linux ==> Free VMS Re: Linux ==> Free VMS Re: Linux ==> Free VMS- re: Linux port question. $QIOW() to sendto(). - re: Linux port question. $QIOW() to sendto(). - Re: Linux port question. $QIOW() to sendto(). ' Re: Looking for COBOL GETQUI example(s)  MicroVAX, MS and RD53 disks  Re: MicroVAX, MS and RD53 disks  multia communication port . OpenVMS and Windows NT Integration for Dummies2 Re: OpenVMS and Windows NT Integration for Dummies2 Re: OpenVMS and Windows NT Integration for Dummies2 Re: OpenVMS and Windows NT Integration for Dummies2 Re: OpenVMS and Windows NT Integration for Dummies Re: the latest billybox virus  Re: UCX Printing Problems  UCX Printing Problems  Re: UCX Printing Problems  Re: UCX Printing Problems  Re: UCX Printing Problems , Re: UCX Printing to external printer servers, Re: UCX Printing to external printer servers, Re: UCX Printing to external printer servers Ultrix for mVax3100 ?  Re: VAX servers for sale( Re: Vaxstation graphics to SVGA monitor?( Re: Vaxstation graphics to SVGA monitor?( Re: Vaxstation graphics to SVGA monitor?' VMS 5.2 DCL treats &symbol unexpectedly + Re: VMS 5.2 DCL treats &symbol unexpectedly  Re: VMS File Modes Re: VMS File Modes Re: VMS File Modes Re: VMS on the desktop?  Re: VMS on the desktop?  Re: VMS on the desktop?  Re: VMS on the desktop?  re: VMS on the desktop?  Re: VMS on the desktop?  re: VMS on the desktop?  Re: VMS on the desktop?  Re: VMS on the desktop?  Re: VMS on the desktop?  Re: VMS on the desktop?  Re: VMS on the desktop?  Re: VMS on the desktop?  Re: VMS on the desktop?  Re: VMS on the desktop?  Re: VMS on the desktop?  Re: VMS on the desktop?  re: VMS on the desktop?  Re: VMS on the desktop?  VMS-NT "affinity" solution Re: VMS-NT "affinity" solution Re: VMS-NT "affinity" solution Re: VMS-NT "affinity" solution Re: VMS-NT "affinity" solution( What cobol statements affect bytlm quota Re: Wildfire Announcement  Re: Wildfire Announcement  Re: Wildfire Announcement  Re: Wildfire Announcement  Re: Wildfire Announcement = re: Wildfire Announcement: Michael Capellas, can you say VMS? = re: Wildfire Announcement: Michael Capellas, can you say VMS? = Re: Wildfire Announcement: Michael Capellas, can you say VMS? = Re: Wildfire Announcement: Michael Capellas, can you say VMS? = Re: Wildfire Announcement: Michael Capellas, can you say VMS? = Re: Wildfire Announcement: Michael Capellas, can you say VMS? = Re: Wildfire Announcement: Michael Capellas, can you say VMS? = re: Wildfire Announcement: Michael Capellas, can you say VMS? ! Re: Windows 98 Vs. Windows NT 4.0 ! Re: Windows 98 Vs. Windows NT 4.0   F ----------------------------------------------------------------------   Date: 18 May 2000 16:39:59 GMT2 From: mathog@seqaxp.bio.caltech.edu (David Mathog) Subject: "Modern" OpenVMS?, Message-ID: <8g16cv$4h9@gap.cco.caltech.edu>  K Having just been bitten on the butt AGAIN by a 16 bit limit ( DEC C write() G won't move >64K worth of data over TCP/IP due to some funky interaction F with a QIO) I'm beginning to wonder if we're ever going to see OpenVMSF dragged into the 21st century.  I know we're going to hear the refrainJ about resources being limited, but near as I can tell that's still becauseK most of the money taken in on OpenVMS products is being diverted to support H development elsewhere in the company.   We'll also hear that "not enoughG people asked for this", which more than anything else suggests that the D "suggestion box" funneling requests into OpenVMS engineering is well hidden.   K Be all of that as it may, can any of the folks at Compaq answer officially, B or at least speculate wildly, on the chances that we'll ever see:   G 1.  RMSng  (64 or at least 32 bit records).  RMSng is long overdue - it F should have been phased in circa 1990, and its absence in 2000 is justF ridiculous.  This would be a backwards compatible change - new systemsI could read older RMS16 files, but older systems would not need to be able G to read RMSng files.  I would accept having to relink or even recompile C everything on my system to obtain this functionality, so long as it 4 requires no additional compiler switches.  That is:    $ cc program $ link program  F and PROGRAM is now rid of QIOs (unless they were called explicitly, of	 course.)    G Among the obvious benefits this would (finally!) result in a completely J Unix compatible streamlf file.  It would offer an opportunity to introduce# the missing "streamcrlf" file type.   J RMSng would also be a good place to phase in file caching in memory, whichF would greatly improve the performance of OpenVMS systems in the common processing modes like:    J   $! require that all data be written to disk within 3 minutes of enteringK   $!   the cache, but wait at least 2 minutes, if possible, before writing     $!   anything @   $ set rms/cache=(maxholdtime=00:03:00.00,waittime=00:02:00.00)   $ cc module.c #   $ lib/object mylib.olb module.obj    $ delete module.obj.	   $! etc.   G In this instance file caching would eliminate entirely the write of the I small temporary file "module.obj" file to disk.  This would speed up this I particular process and would not slow down others which really do need to K get their data out onto disk.   That is, this type of optional file caching L is a win/win option for performance on OpenVMS systems as the process using I it goes faster, and processes contending with it for disk access also go  I faster. (Setting maxholdtime to 0 would disable the cache, leaving things J exactly as they are in current versions of OpenVMS, for applications which0 really need to get their data onto disk "now".)   K Oh yes, and since it never seems to get done otherwise, PLEASE finally make J DEC C set the RMS bits correctly when it writes a streamlf file one recordJ at a time, LRL=32767 is just unacceptable when the real value is 20.  It'sI bad enough now when SORT tries to act on one of these files and allocates I 32k for each record, just imagine what it could do when LRL is 2147483647  or 9.223372037e+18!   3 2.  Transition from $QIO to $IO_PERFORM everywhere.   @ If this leaves the VAXes out in the cold, so be it.  It's simplyC unacceptable that a 64 bit OS has so many 16 bit bottlenecks in it. E However, since even $IO_PERFORM has a buffer limit (on my system it's H currently set to 819200 bytes) it's still essential that Compaq suppliedJ functions like write() in DEC C be smart enough to know when to break up aJ large buffer transfer and not bomb out just because the pipe is too narrow1 to handle the entire transfer in one fell swoop.    $ 3.  Finish plugging ICC into the OS.  H ICC appears to be a well thought out, modern, replacement for mailboxes.I So how about finishing integrating ICC into the OS?  The system calls are K nice, but there are no programming examples provided and there is no way to C access ICC via DCL, especially to use it instead of a mailbox.  For H instnace, there's no RUN/DETACHED/ICC=termicc::, only /mailbox=mba123::   9 While ICC looks reasonably complete it seem to be missing K $ICC_BROADCAST[W], which would allow a sender to broadcast a message to all I clients in one fell swoop and save the bandwidth and trouble of having to G do $ICC_TRANSMIT[W] to each client.   When the same message needs to be J sent to N nodes, where N is large, this would be more efficient than doingJ a bunch of separate transmits.  (But maybe it's there and I just don't seeG how to do it?)  In any case, this fits in with the lack of a SUBMIT/ALL < function for the queues and the lack of a RUN/DETACHED/ON=*   I Here is an example where all of this would come together in a useful way:   J   $! start http servers on all nodes and monitor for a termination messageI   $! should any of them crash for some reason.  Then restart the crashed     $! one   $!%   $! make a termination icc "mailbox"    $!   $ create/icc termicc:    $!   $! set up a log file   $!4   $ open/write logfile: sys$manager:http_servers.log   $!#   $! start the servers on all nodes    $!   $ fornode="*" 	   $ loop: U   $ run/detached/on='fornode'/process_name=localhttp/icc=termicc:  restart_local_http    $ read termicc: string   $!   $! code goes here to  F   $! figure out which node's process died from the termination message5   $! sent through ICC.   store that string in fornode    $!   $ time = f$time() A   $ write logfile: "Node ''fornode' crash and restart at ''time'" 
   $ goto loop     4. Increase the size of SCSNODE.  I This isn't of huge importance, but we've got a lot of memory these days,  G so can't we get beyond the 6 letter SCSNODE limit?   No more situations I where the SCSNODE isn't long enough to match the TCP/IP name, and you end 	 up with:    0   $ copy/ftp file.txt sanfrancisco.company.com::0   $ copy     file.txt                  sanfran::   Regards,   David Mathog mathog@seqaxp.bio.caltech.edu ? Manager, sequence analysis facility, biology division, Caltech     ------------------------------  % Date: Thu, 18 May 2000 08:52:49 +0000 - From: ezzaoudi med <m.ezzaoudi@digitem.co.ma>  Subject: Backup image problem - Message-ID: <3923AF61.2BC64030@digitem.co.ma>    Hello  My probleme is :D I have an Alpha server 800 with OpenVMS 7.1H1 , the system disk is a# mirror Raid controlled with a Mylex  ( DAC 960). H I boot with the VMS CDROM , and I do a backup image from the system disk (DRA0: ) to a non raid disk @ controlled with normal SCSI controler ( DKA0:). I have no error.  > When I try to boot with the target disk , I have the message :* "... block 0 is not a valid boot block..".> I have the same message when I put the disk in  another Alpha.  . 1- Why the block 0 is not a valid boot block ?@ 2- I resolved my probleme by doing an upgrade on the target disk (DKA0:).G 3- Is there a procedure to make the bloque 0 as " a valid boot block" ? G 4- Is there special procedure to do a backup image from a Raid 0 system  disk ?B 5- If I restore the backup from tape or disk , the block 0 will be
 affected ?   Thank you for your  answers.   EZZAOUDI Mohamed m.ezzaoudi@digitem.co.ma   ------------------------------  # Date: Thu, 18 May 2000 13:57:07 GMT  From: briggs@eisner.decus.org ! Subject: Re: Backup image problem + Message-ID: <PrDsJLJ2HH4X@eisner.decus.org>   ] In article <3923AF61.2BC64030@digitem.co.ma>, ezzaoudi med <m.ezzaoudi@digitem.co.ma> writes:  > Hello  > My probleme is :F > I have an Alpha server 800 with OpenVMS 7.1H1 , the system disk is a% > mirror Raid controlled with a Mylex 
 > ( DAC 960). J > I boot with the VMS CDROM , and I do a backup image from the system disk > (DRA0: ) to a non raid disk B > controlled with normal SCSI controler ( DKA0:). I have no error. > @ > When I try to boot with the target disk , I have the message :, > "... block 0 is not a valid boot block..".@ > I have the same message when I put the disk in  another Alpha.  E When you say that you do a "backup image", what do you mean?  What is G the command (or sequence of commands) that you used to copy your system  disk from DRA0: to DKA0:  F In my experience, $ BACKUP /IMAGE always produces a bootable disk when the source disk is bootable.  & 	John Briggs			briggs@eisner.decus.org   ------------------------------  % Date: Thu, 18 May 2000 08:41:32 +0200 ! From: "Luc BEDU" <bedu@promod.fr> # Subject: Re: Backup solution/server 6 Message-ID: <8g03dd$ok7$1@news.entreprises.cegetel.fr>  : > I must admin that I have not studied VMS backup in full, but K > from what I've seen it takes a lot more to produce a complete backup of a I > live system using VMS backup than most backup utils on other platforms.  >   L I'm sorry but for Y2K tests we use VMS backups to restore our configurationsL on a separate network. It was very easy. We tried to do the same with NT and# it was very very very... difficult.   K take a look at "$ help backup" and try backup/ignore=interlock for rms open = files. If you have databases like Rdb try rmu/backup/online !    ------------------------------  % Date: Thu, 18 May 2000 12:00:22 -0400 " From: Dan Sugalski <dan@sidhe.org># Subject: Re: Backup solution/server 8 Message-ID: <4.3.1.0.20000518115805.0222b730@24.8.96.48>  * At 08:41 AM 5/18/00 +0200, Luc BEDU wrote:< > > I must admin that I have not studied VMS backup in full, >butM > > from what I've seen it takes a lot more to produce a complete backup of a K > > live system using VMS backup than most backup utils on other platforms.  > >  > M >I'm sorry but for Y2K tests we use VMS backups to restore our configurations M >on a separate network. It was very easy. We tried to do the same with NT and $ >it was very very very... difficult.  K Ah, that's too hard. HSx controllers and the CLONE command are your friend  F for things like this. Even works for NT if the hardware on the backup  machine's identical. :)   F Regardless, making a good, restorable backup of a VMS system's pretty H simple. Not being able to manage it is a good sign you really ought not 8 have "System Administrator" as part of your job title...   					Dan  I --------------------------------------"it's like this"------------------- 2 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and even ;                                       teddy bears get drunk    ------------------------------  # Date: Thu, 18 May 2000 08:02:40 GMT - From: young_r@eisner.decus.org (Robert Young) 5 Subject: Re: Compaq Bets Big on New Web Servers (WSJ) + Message-ID: <DjY6+IzMCcJY@eisner.decus.org>   \ In article <392362DD.904F7574@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes: > Robert Young wrote: 6 >> http://www.digital.com/hpc/news/news_pr160500a.html >>  O >> "Josh Levine, Chief Information Officer at E*Trade, said: "When we pioneered P >> online investing years ago, we didn't know E*Trade today would be the world'sP >> most visited online investing site. Our partnership with Compaq has helped usQ >> to accommodate this business and infrastructure growth. From the beginning, we F >> have leveraged enterprise solutions from Compaq  particularly theirQ >> AlphaServers and OpenVMS clusters, along with ProLiant NT servers, storage and  >> mission-critical services   >  > J > Why didn't Compaq invite that guy to the wordwide conference, instead ofK > inviting the Oracle guy who had absolutely no vested interest in Compaq's  > success ?  >   ? 	I had one response and totally deleted it.  I wasn't answering > 	your question.  Oracle is a very important ISV and folks needD 	faster boxes to run their very large databases (among other things)< 	and to have Larry via video endorse the box and another rep' 	on site was important to both parties.    				Rob    ------------------------------  # Date: Thu, 18 May 2000 13:46:55 GMT 9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) 5 Subject: Re: Compaq Bets Big on New Web Servers (WSJ) + Message-ID: <HUv5nn6BemRN@eisner.decus.org>   \ In article <392362DD.904F7574@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes: > Robert Young wrote: 6 >> http://www.digital.com/hpc/news/news_pr160500a.html >> sO >> "Josh Levine, Chief Information Officer at E*Trade, said: "When we pioneeredaP >> online investing years ago, we didn't know E*Trade today would be the world'sP >> most visited online investing site. Our partnership with Compaq has helped usQ >> to accommodate this business and infrastructure growth. From the beginning, wepF >> have leveraged enterprise solutions from Compaq  particularly theirQ >> AlphaServers and OpenVMS clusters, along with ProLiant NT servers, storage andt >> mission-critical services ? >  > J > Why didn't Compaq invite that guy to the wordwide conference, instead ofK > inviting the Oracle guy who had absolutely no vested interest in Compaq's  > success ?a  K Because it is more impressive to have someone without a vested interest !!!A   ------------------------------  # Date: Thu, 18 May 2000 13:19:47 GMTo0 From: "Terry C. Shannon" <shannon@world.std.com>5 Subject: Re: Compaq Bets Big on New Web Servers (WSJ)t& Message-ID: <FurBuC.32p@world.std.com>  F "Larry Kilgallen" <Kilgallen@eisner.decus.org.nospam> wrote in message% news:HUv5nn6BemRN@eisner.decus.org... 7 > In article <392362DD.904F7574@videotron.ca>, JF Mezeie& <jfmezei.spamnot@videotron.ca> writes: > > Robert Young wrote:V8 > >> http://www.digital.com/hpc/news/news_pr160500a.html > >>G > >> "Josh Levine, Chief Information Officer at E*Trade, said: "When wee	 pioneeredeJ > >> online investing years ago, we didn't know E*Trade today would be the world'sSH > >> most visited online investing site. Our partnership with Compaq has	 helped usDE > >> to accommodate this business and infrastructure growth. From the 
 beginning, weIH > >> have leveraged enterprise solutions from Compaq  particularly theirG > >> AlphaServers and OpenVMS clusters, along with ProLiant NT servers,y storage ande > >> mission-critical services > >g > >lL > > Why didn't Compaq invite that guy to the wordwide conference, instead ofD > > inviting the Oracle guy who had absolutely no vested interest in Compaq's
 > > success ?s >eI > Because it is more impressive to have someone without a vested intereste !!!   @ C'est vrai! E-Trade and Northern Light did get mentioned (ratherE extensively) in the customer presentations. I don't think OpenVMS waso' short-shrifted during the announcement.l  H What's more, Michael Capellas and Rich Marcello left the NYC event a bit7 early (they weren't around for the customer reception).   L Seems they had to get back to Nashua to get ready for a meeting with OpenVMS7 employees and Ambassadors that took place on Wednesday.M   ------------------------------  # Date: Thu, 18 May 2000 12:50:42 GMTe% From: Alan Greig <agreig@my-deja.com>d% Subject: Re: CPU Temperature from DCL ) Message-ID: <8g0our$v3j$1@nnrp1.deja.com>p  . In article <8fupj3$5v7$3@info.service.rug.nl>,   helbig@astro.rug.nl wrote:- > In article <hnBuwjU7c3c1@eisner.decus.org>,t8 > kaplow_r@eisner.decus.org.spamnot (Bob Kaplow) writes: >i! > >MARS, a AlphaServer 8400 5/440  >         ^fB > This missing "n" (which is also missing from tcpip sh vers) will forevert= > remind us of the many VAXen which have populated the world.m  F But at least they fixed the problem by selling themselves to Compaq :)  
 $ SHOW CPU    xxxA1, a Compaq Alphaserver ES40   $ tcpip sho vers  7  DIGITAL TCP/IP Services for OpenVMS Alpha Version 5.0Ay3  on a Compaq Alphaserver ES40 running OpenVMS 7.2-1l     --
 Alan Greig    & Sent via Deja.com http://www.deja.com/ Before you buy.V   ------------------------------   Date: 18 May 2000 14:24:17 GMT* From: helbig@astro.rug.nl (Phillip Helbig)% Subject: Re: CPU Temperature from DCLu. Message-ID: <8g0ueh$qdp$1@info.service.rug.nl>  4 In article <8g0our$v3j$1@nnrp1.deja.com>, Alan Greig <agreig@my-deja.com> writes: s  / >In article <8fupj3$5v7$3@info.service.rug.nl>,- >  helbig@astro.rug.nl wrote:-. >> In article <hnBuwjU7c3c1@eisner.decus.org>,9 >> kaplow_r@eisner.decus.org.spamnot (Bob Kaplow) writes:D >>" >> >MARS, a AlphaServer 8400 5/440 >>         ^C >> This missing "n" (which is also missing from tcpip sh vers) willt >forever> >> remind us of the many VAXen which have populated the world. >rG >But at least they fixed the problem by selling themselves to Compaq :)e >f >$ SHOW CPUo > ! >xxxA1, a Compaq Alphaserver ES40s >e >$ tcpip sho ver >g8 > DIGITAL TCP/IP Services for OpenVMS Alpha Version 5.0A4 > on a Compaq Alphaserver ES40 running OpenVMS 7.2-1  H The string seems to be f$getsyi("hw_name"); some hardware has "Digital" = before the name, some "Compaq"---even with the exact same OS.h   ------------------------------  % Date: Thu, 18 May 2000 09:50:48 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> 6 Subject: Re: crystal clear vms filesystem from nt side' Message-ID: <3923A0D8.8E9C09@gtech.com>r   danny_erres@my-deja.com wrote:1 > hello everybody , i will start by saying that i + > speak the "ls -la" language and not "showd0 > mount /all" (i think it goes like that) . i am2 > looking for a tool that will gain me the ability3 > to "see" a vms filesystem from NT and mount it (io. > am going to backup it) . what should i use ?0 > nfs , pathworks , samba or other tools i don't3 > really familiar with . one major thing is that asr1 > i know vms file attributes are very detailed soo1 > is there any tool out there that will keep/haveh0 > all the atrributes and protection although its
 > NTFS ??? > 3 > i am open for suggestion but keep in mind that myf1 > major need is to backup the vms filesystem withl- > NT tools without damaging the vms data (anda) > metadata) so i can restore it perfectlyo  , If you want to be sure that the files are in3 perfect shape, then use VMS BACKUP to put them intos a BACKUP saveset on disk.,  4 Next problem is to get the VMS BACKUP saveset to NT.7 Many solutions exist for that: PathWorks/Samba/NFS/FTP.r  6 Forget about using PathWorks/Samba/NFS/FTP directly to backup with.  > And BTW the cheapest and best solution is undoubtetly to buy a tape-drive for the VMS box !   Arne   ------------------------------  % Date: Thu, 18 May 2000 13:14:48 +0000 / From: Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk>d6 Subject: re: crystal clear vms filesystem from nt side7 Message-ID: <009EA453.818B7C58.15@maxwell.ph.kcl.ac.uk>    > 1 > hello everybody , i will start by saying that i + > speak the "ls -la" language and not "showo0 > mount /all" (i think it goes like that) . i am2 > looking for a tool that will gain me the ability3 > to "see" a vms filesystem from NT and mount it (iS. > am going to backup it) . what should i use ?0 > nfs , pathworks , samba or other tools i don't3 > really familiar with . one major thing is that asa1 > i know vms file attributes are very detailed so 1 > is there any tool out there that will keep/havei0 > all the atrributes and protection although its
 > NTFS ???  # If you're a troll, you just failed.o  7 If not, you've been seriously brainwashed by Microsoft.e% Think hard about what you just wrote.   6 It's fundamentally impossible to mount a VMS filestore2 on an NT system, or on a Unix one, and back it up.8 This is because the VMS filesystem does many things that4 the filesystems on other systems don't, and any such3 crossmount will inevitably not preserve filesystem f4 meta-data that is necessary for a successful restore of a full VMS filesystem.   9 Get a tape drive for your VMS system, and use VMS Backup.m: Or for smallish backups, use VMS BACKUP to pack files into4 a save-set, the VMS port of ZIP with "-V" option to 6 network-proof and compress the save-set, and then copy8 it to a storage medium on some other system. (Some might2 say ZIP "-V" can replace BACKUP ... I still prefer BACKUP for backup).a  < If your question is how to access a subset of VMS filesystem< functionality from another system, say for data-exchange or : interoperability, there are many solutions. To name a few:  9 Compaq sell Pathworks Advanced Server, which will let you 6 share VMS directories much as NT shares NT directories  ; There is a VMS port of Samba that does much the same thing.L3 It's less efficient and has less functionality, butn
 it's free.  6 UCX allows you to NFS-export a VMS tree, and there are/ products that give NT the ability to mount NFS.o  8 But these are inter-operability solutions, and cannot be4 used in conjunction with a backup tool on NT to make; a guaranteed restorable copy of an arbitrary VMS filestore._7 Only VMS backup, or code with equivalent functionality  ) executing on the VMS system, can do that.t   > 3 > i am open for suggestion but keep in mind that my 1 > major need is to backup the vms filesystem withs- > NT tools without damaging the vms data (andi) > metadata) so i can restore it perfectlyt  4 Why not get a tape device and use VMS Backup on VMS?   	Yours,e
 		Nigel Arnoth- 		NRA@MAXWELL.PH.KCL.AC.UK                   !  7 		"In the beginning there was nothing, which exploded."i   ------------------------------  / Date: Thu, 18 May 2000 09:35:56 +0200 (MET DST) & From: Rudolf Wingert <win@FOM.FGAN.DE>% Subject: Re: DFOR$ALLOC_ALLOCATABLE64t/ Message-ID: <200005180636.IAA07934@fom.fgan.de>    Hello,  E you wrote: both machines running VMS 7.1. Are both Alphas? Is on bothl@ machines the same FORTRAN version? Are the same RTL? Did you use" text library and be they are same?F You see a lot of difference could be between to machines with the same OpenVMS version    Regards Rudolf Wingert   ------------------------------  , Date: Thu, 18 May 2000 16:15:27 +0200 (CEST): From: "Gotfryd Smolik, VMS lists" <gotfryd@stanpol.com.pl>5 Subject: Re: Duplicated messages: are only I see it ? K Message-ID: <Pine.LNX.4.10.10005181613500.14238-100000@irys.stanpol.com.pl>r  % On 17 May 2000, Phillip Helbig wrote:e [...] D +I read this in the newsgroup, not the mailing list.  However, when H +someone from the mailing list emails me a personal reply, I always get  +that twice.  A  Ok. But I have get two copy of ALL messages. Probably my address - was somewhere duplicated in the listserver :],    Regards - Gotfryd   --E =====================================================================sF $ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") - 		THEN EXCUSE/OBJECT=ME . $!                        GS@stanpol.zabrze.plE =====================================================================    ------------------------------  # Date: Thu, 18 May 2000 14:48:25 GMTH' From: Roose Chua <roose_chua@yahoo.com>t Subject: Error on SMTP) Message-ID: <8g0vrj$7fb$1@nnrp1.deja.com>    Hi!b  B I have been trying to resolve a problem on SMTP and had no luck inC looking under DSNlink. Basically, the problem is that when I try totC send an email through SMTP from one of the node in a 2-node clusteriE (VAX, OpenVMS 7.1, UCX 4.2 ECO 2), the mail is not sent and I get thes following error:  ' ---- Transcript of session follows ----t: 501  %UCX-E-SMTP_COMMANDERR,  Smtp command error intel.com  C Anybody who had experience this and/or had any solution? Any advisea would be highly appreciated!   Thanks,p Rooser    & Sent via Deja.com http://www.deja.com/ Before you buy.-   ------------------------------  % Date: Thu, 18 May 2000 09:17:10 -0600?1 From: Glen Martin <GLENMARK@utxvms.cc.utexas.edu>d1 Subject: Re: External authentication in a cluster-4 Message-ID: <3923B516.4760B802@utxvms.cc.utexas.edu>   Stuart, Ed wrote:. >  > [...snip, snip, snip...] > 5 > Is OpenVMS able to use Kerberos for authentication?n  . Multinet includes a Kerberos implementation...   Glen   ------------------------------  % Date: Thu, 18 May 2000 02:01:32 -0500a% From: Paul Lentz <plentz@airmail.net> % Subject: F$GETQUI() and job info helptO Message-ID: <90118BEE8A3F7418.242C4BB5B5AB97F8.C9309A6740B52019@lp.airnews.net>c  G I'm trying to write a DCL .com file to delete/bounce return and requeuedB smtp mail that has sat and retried for X amount of hours/days on aE multinet box. I'm having alot of trouble eeking out the information I0% need from the job *without* using... eG SH ENT/FULL/OUT=SHOW_ENT.LIS SMTP-REQUEUE and parsing out the .lis filetG for the ENTRY, FILE_SPEC, DATE/TIME SUBMITTED and PARAM (presumably for I the "connection refused", etc. to use as info in a log/mail message).    o  E The documentation for the multi-multi-purpose lexical like F$GETQUI()sE are real confusing about which item can go with which function... :-)c" I'd like to use something like... H F$GETQUI("DISPLAY_ENTRY", ... and get the filespec, etc. associated with; the entry, but I can't come up with the right combination. 8    Anybody got any help for me? :-)   TIA      -- a *Paul*   plentz@airmail.net   ------------------------------  % Date: Thu, 18 May 2000 10:27:00 +0900u2 From: Mike Rechtman <michael.rechtman@digital.com>) Subject: Re: F$GETQUI() and job info helpf+ Message-ID: <3923C574.686D71E7@digital.com>u  , This is a multi-part message in MIME format.  % --------------EF811942172C43D79D65432 * Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bite   See below. Will that do?   Mike   Paul Lentz wrote:k > I > I'm trying to write a DCL .com file to delete/bounce return and requeue D > smtp mail that has sat and retried for X amount of hours/days on aG > multinet box. I'm having alot of trouble eeking out the information Ir& > need from the job *without* using...I > SH ENT/FULL/OUT=SHOW_ENT.LIS SMTP-REQUEUE and parsing out the .lis file I > for the ENTRY, FILE_SPEC, DATE/TIME SUBMITTED and PARAM (presumably for G > the "connection refused", etc. to use as info in a log/mail message).e > G > The documentation for the multi-multi-purpose lexical like F$GETQUI() G > are real confusing about which item can go with which function... :-)a# > I'd like to use something like...sJ > F$GETQUI("DISPLAY_ENTRY", ... and get the filespec, etc. associated with< > the entry, but I can't come up with the right combination. > " > Anybody got any help for me? :-) >  > TIA  >  > -- > *Paul* >  > plentz@airmail.net   -- hE --------------------------------------------------------------------- E Usual disclaimer: All opinions are mine alone, perhaps not even that.i? Mike Rechtman                            *rechtman@tzora.co.il*yF Kibbutz Tzor'a.                          Voice (home): 972-2-9908337  B   "20% of a job takes 80% of the time, the rest takes another 80%"E ---------------------------------------------------------------------a  % --------------EF811942172C43D79D65432 @ Content-Type: text/plain; charset=us-ascii; name="Q_STAT.COM.28" Content-Transfer-Encoding: 7bit45 Content-Disposition: inline; filename="Q_STAT.COM.28"    $! Q _ S T A T . C O M $!8 $!  Procedure example using F$GETQUI lexical function to $!  extract information on 9 $!   Queues7	 $!   Jobs.
 $!   Files $!= $!                                              Mike Rechtman>= $!                                              ~~~~~~~~~~~~~"& $  TEMP = F$GETQUI("CANCEL_OPERATION")N $  STAT_LIST = "Aligning,Idle,Lowercase,OperatorRequest,Paused,Pausing,Remote"P $  STAT_LIST = STAT_LIST + ",Resetting,Resuming,Server,Stalled,Starting,Stopped"R $  STAT_LIST = STAT_LIST + ",Stopping,Unavailable,Closed,Busy,Undefined,Available"F $  STAT_LIST = STAT_LIST + ",Disabled,AutoStart Inactive,Stop Pending"     $QLOOP:o5 $  QNAME = F$GETQUI("DISPLAY_QUEUE","QUEUE_NAME","*")l% $  IF QNAME .EQS. "" THEN GOTO QLOOP2  $  WRITE SYS$OUTPUT ""
 $  QTYPE = ""cH $  QBATC = F$GETQUI("DISPLAY_QUEUE","QUEUE_BATCH","*","FREEZE_CONTEXT" )) $  IF QBATC THEN QTYPE = QTYPE + "Batch "hI $  QSERV = F$GETQUI("DISPLAY_QUEUE","QUEUE_SERVER","*","FREEZE_CONTEXT" )d* $  IF QSERV THEN QTYPE = QTYPE + "Server "J $  QPRIN = F$GETQUI("DISPLAY_QUEUE","QUEUE_PRINTER","*","FREEZE_CONTEXT" )+ $  IF QPRIN THEN QTYPE = QTYPE + "Printer "a, $  WRITE SYS$OUTPUT "''QTYPE'Queue: ", QNAMEQ $  P_COUNT = F$GETQUI("DISPLAY_QUEUE", "PENDING_JOB_COUNT", "*","FREEZE_CONTEXT") W $  IF P_COUNT .NE. 0 THEN WRITE SYS$OUTPUT "Queue ''QNAME' has ''P_COUNT' pending jobs"rK $  QSTATUS = F$GETQUI("DISPLAY_QUEUE","QUEUE_STATUS","*","FREEZE_CONTEXT" )  $  IF ( QSTATUS .NE. 0 ) $  THEN  $	GOSUB GET_QUE_STATUS? $	WRITE SYS$OUTPUT "Queue Status is ''QUESTAT'    (''QSTATUS')"a $  ENDIF $! $JLOOP:aD $  NOACCESS = F$GETQUI("DISPLAY_JOB","JOB_INACCESSIBLE",,"ALL_JOBS")+ $  IF NOACCESS .EQS. "TRUE" THEN GOTO JLOOP>( $  IF NOACCESS .EQS. "" THEN GOTO QLOOP13 $  JENTR = F$GETQUI("DISPLAY_JOB","ENTRY_NUMBER",,-t(               "FREEZE_CONTEXT,ALL_JOBS")/ $  JNAME = F$GETQUI("DISPLAY_JOB","JOB_NAME",,-v(               "FREEZE_CONTEXT,ALL_JOBS")7 $  JCOND = F$GETQUI("DISPLAY_JOB","CONDITION_VECTOR",,-r(               "FREEZE_CONTEXT,ALL_JOBS")O $  WRITE SYS$OUTPUT "    Entry:''JENTR'    Jobname: ''JNAME'   Status:''JCOND'"v $FLOOP:p; $  FSPEC = F$GETQUI("DISPLAY_FILE","FILE_SPECIFICATION",, ) % $  IF FSPEC .EQS. "" THEN GOTO JLOOP1 , $  WRITE SYS$OUTPUT "        File: ''FSPEC'"
 $  GOTO FLOOPe $JLOOP1: $  IF QBATCg $  THENl; $     LSPEC = F$GETQUI("DISPLAY_JOB","LOG_SPECIFICATION",,-u(               "FREEZE_CONTEXT,ALL_JOBS")3 $     WRITE SYS$OUTPUT "        Logfile: ''LSPEC' "- $  ENDIF
 $  GOTO JLOOP- $QLOOP1:P $  GEN1 = F$GETQUI("DISPLAY_QUEUE","QUEUE_GENERIC","''QNAME'","FREEZE_CONTEXT" )
 $  IF GEN1 $  THENeS $    GEN2 = F$GETQUI("DISPLAY_QUEUE","GENERIC_TARGET","''QNAME'","FREEZE_CONTEXT" )l8 $    WRITE SYS$OUTPUT "  Generic queues target: ''GEN2'" $  ENDIF
 $  GOTO QLOOPn $! $QLOOP2:& $  TEMP = F$GETQUI("CANCEL_OPERATION") $  EXIT, $! $GET_QUE_STATUS: $   QUESTAT = "" $   COUNT   = 0o $   TEMP = QSTATUS $   BIT = 1w $STAT_LOOP:/) $ IF TEMP .EQ. 0 THEN GOTO DONE_STAT_LOOPo $   IF TEMP .AND. 1 THEN -: 	QUESTAT = QUESTAT + ", " + F$ELEMENT(COUNT,",",STAT_LIST) $   COUNT = COUNT + 1w $   TEMP = TEMP/2d $   GOTO STAT_LOOP $! $DONE_STAT_LOOP: $   QUESTAT = QUESTAT - ", "
 $   RETURN  ' --------------EF811942172C43D79D65432--c   ------------------------------   Date: 18 May 2000 11:33 CSTi' From: carl@gerg.tamu.edu (Carl Perkins)e) Subject: Re: F$GETQUI() and job info help - Message-ID: <18MAY200011331418@gerg.tamu.edu>i   plentz@airmail.net writes...H }I'm trying to write a DCL .com file to delete/bounce return and requeueC }smtp mail that has sat and retried for X amount of hours/days on at }multinet box.   }  }--  }*Paul*e  = Not that this answeres your question, but why do you want to?o  F Multinet will bounce it for you after the time period specified by theG MULTINET_SMTP_RETURN_INTERVAL logical name. As I recall the default was I to retry for 4 days, then return to sender (or sent to the postmaster, ifnI it was the return that was not getting through). You can set this logicalt< name to whatever you want it to be (I changed it to 3 days).   --- Carl   ------------------------------  # Date: Thu, 18 May 2000 14:45:25 GMTi1 From: "Mark D. Jilson" <jilly@clarityconnect.com>cJ Subject: Re: Geting Temperature from CA (was Re: CPU Temperature from DCL)2 Message-ID: <392401F7.25A9520F@clarityconnect.com>  / My understanding is that you'll need to use CA.-   Peter Weaver wrote:. > D > Paul A. Jacobi wrote in message <8fshed$c7v$1@lead.zk3.dec.com>... > >...H > >Platform specific knowledge about the various sensors are included in > the.	 > >Compaq G > >Analyze tool which can make a determination if the sensor values aref > beyond > >an" > >acceptable range. > >... > D > How do you get this information from Compaq Analyze? I have playedG > with CA as much as possible and I do not recall seeing anything aboute2 > temperature in any output that I managed to get. > G > We have two GS160's on order, will DIAGNOSE be supported on the GS160S > or will we have to use CA?   -- pD Jilly	- Working from Home in the Chemung River Valley - Lockwood, NY0 	- jilly@clarityconnect.com			- Brett Bodine fan. 	- Mark.Jilson@Compaq.com			- since 1975 or so, 	- http://www.jilly.baka.com               -   ------------------------------  % Date: Thu, 18 May 2000 11:42:32 -0400e- From: "Peter Weaver" <peter.weaver@stelco.ca>oJ Subject: Re: Geting Temperature from CA (was Re: CPU Temperature from DCL)/ Message-ID: <si83rra4ifb126@corp.supernews.com>h   Mark D. Jilson wrote in messager) <392401F7.25A9520F@clarityconnect.com>...k0 >My understanding is that you'll need to use CA.     RATS!!!!!!!!!!!!!!!!!!   ------------------------------   Date: 18 May 2000 12:48:54 GMT% From: andrew3748@aol.com (Andrew3748)v% Subject: How do you search for files?h: Message-ID: <20000518084854.06824.00000016@ng-fo1.aol.com>  I How do you search for files AND include the subdirectories in the search.   2 i.e. I would issue '$find . -name *.sql'  in unix.    A   ------------------------------  # Date: Thu, 18 May 2000 13:23:53 GMTe0 From: carlini@true.lkg.dec.com (Antonio Carlini)) Subject: Re: How do you search for files? * Message-ID: <8g0qa6$pe8@usenet.pa.dec.com>  a In article <20000518084854.06824.00000016@ng-fo1.aol.com>, andrew3748@aol.com (Andrew3748) wrote:0J >How do you search for files AND include the subdirectories in the search. >R3 >i.e. I would issue '$find . -name *.sql'  in unix.-     $ DIR [...]*.SQL   Antonio   I Antonio Carlini                            Mail: carlini@true.lkg.dec.comt# DECnet-Plus for OpenVMS Engineering 6 COMPAQ                                     Reading, UK   ------------------------------  % Date: Thu, 18 May 2000 15:25:48 +0200v= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>)) Subject: Re: How do you search for files? ) Message-ID: <3923EF5B.41E845A2@gtech.com>l   Andrew3748 wrote:tK > How do you search for files AND include the subdirectories in the search.e > 4 > i.e. I would issue '$find . -name *.sql'  in unix.   $ DIR [...]*.SQL   Arne   ------------------------------  # Date: Thu, 18 May 2000 15:54:11 GMTm From: briggs@eisner.decus.orgh) Subject: Re: How do you search for files?d+ Message-ID: <R+Kt0WebOPbw@eisner.decus.org>c  b In article <20000518084854.06824.00000016@ng-fo1.aol.com>, andrew3748@aol.com (Andrew3748) writes:K > How do you search for files AND include the subdirectories in the search.t > 4 > i.e. I would issue '$find . -name *.sql'  in unix.   $ dir [...]*.sql   ------------------------------  % Date: Thu, 18 May 2000 11:33:29 -0400p. From: "Weaver, Peter" <Peter.Weaver@stelco.ca>2 Subject: RE: Inserting a DATE (was Re: EDT macros)G Message-ID: <2F068F8A3066D311A7550000E8961C6401503C66@tootle.stelco.ca>:  0 Try this out. First you create a file like this;  F ;*<<<DATE>>>  Terry          Original                             <<>>  L Define a logical called PRW$EDP_HEAD_LINE that points to the file, then editJ a new file with the following as your .INI. CTRL-D will then prompt you ifJ you are working in Admins, Powerhouse or VMS (DCL). Enter in A, P or V andK then press <ENTER>. After that use CTRL-D to go to each field that needs toSI be filled in. I wrote this section in 1986, tried it today on V7.1 and it 
 still works. i    B DEFINE KEY CONTROL D AS "EXT HEADING_INSERT_?*'Enter A (ADMINS), P< (Powerhouse) or V (VMS). ' ; CHANGE ; BR'<<>>'CUTSR=DELETE." !+ !     Heading Insert Macros,; !     to use PRW$EDP_HEAD_LINE must be defined as a logical . !     pointing to a file that looks like this;L !     ;*<<<DATE>>>  P.R. Weaver    Original                             <<>> !- !e DEFINE MACRO HEADING_INSERT_Ai FIND =HEADING_INSERT_A !e INSERTL ;INSERT;********************************************************************
 ********** INSERT ;INSERT;**i( INSERT ;INSERT;**               ID: <<>>( INSERT ;INSERT;**            Title: <<>> INSERT ;INSERT;**e( INSERT ;INSERT;**         Language: <<>>( INSERT ;INSERT;**  Program Name(s): <<>> INSERT ;INSERT;**y8 INSERT ;INSERT;**        Called By: <<>>  (Option: <<>>)( INSERT ;INSERT;**            Calls: <<>>( INSERT ;INSERT;**      Files (I/O): <<>> INSERT ;INSERT;**r( INSERT ;INSERT;**      Description: <<>> INSERT ;INSERT;** ( INSERT ;INSERT;**  Special Remarks: <<>> INSERT ;INSERT;**p INSERTL ;INSERT;********************************************************************
 ********** INSERT ;INSERT;** ! INSERT ;INSERT;**  Modifications:s INSERT ;INSERT;**e7 INSERT ;INSERT;**    Date      Author       Description 	 Request #o* INSERT ;INSERT;** *********  *************. ***********************************  *********" INSERT ;INCLUDE PRW$EDP_HEAD_LINE: INSERT ;CHANGEE ;-LD+CI*^Z("<<<DATE>>>"CUTSR=DELETE)DATE14(-C)2(D+C)2(+C)10(D+C)+L EXt INSERT ;INSERT;**s INSERTL ;INSERT;********************************************************************
 ********** INSERT ;INSERT;**  INSERT ;INSERT;<<>>p5 INSERT ;DEFINE KEY CONTROL D AS "'<<>>'CUTSR=DELETE."  !h DEFINE MACRO HEADING_INSERT_P  FIND =HEADING_INSERT_P !o INSERTL ;INSERT;;*******************************************************************
 ********** INSERT ;INSERT;;*,( INSERT ;INSERT;;*               ID: <<>>( INSERT ;INSERT;;*            Title: <<>> INSERT ;INSERT;;*h( INSERT ;INSERT;;*         Language: <<>>( INSERT ;INSERT;;*  Program Name(s): <<>> INSERT ;INSERT;;* 8 INSERT ;INSERT;;*        Called By: <<>>  (Option: <<>>)( INSERT ;INSERT;;*            Calls: <<>>( INSERT ;INSERT;;*      Files (I/O): <<>> INSERT ;INSERT;;*n( INSERT ;INSERT;;*      Description: <<>> INSERT ;INSERT;;*-( INSERT ;INSERT;;*  Special Remarks: <<>> INSERT ;INSERT;;*T INSERTL ;INSERT;;*******************************************************************
 ********** INSERT ;INSERT;;*4! INSERT ;INSERT;;*  Modifications:t INSERT ;INSERT;;*n7 INSERT ;INSERT;;*    Date      Author       Descriptions	 Request # * INSERT ;INSERT;;* *********  *************. ***********************************  *********" INSERT ;INCLUDE PRW$EDP_HEAD_LINE:J INSERT ;CHANGE ;-L("<<<DATE>>>"CUTSR=DELETE)DATE14(-C)2(D+C)2(+C)10(D+C)+L EX INSERT ;INSERT;;*  INSERTL ;INSERT;;*******************************************************************
 ********** INSERT ;INSERT;;*: INSERT ;INSERT;<<>> 5 INSERT ;DEFINE KEY CONTROL D AS "'<<>>'CUTSR=DELETE."8 !3 DEFINE MACRO HEADING_INSERT_Vo FIND =HEADING_INSERT_V !h INSERTL ;INSERT;$!******************************************************************
 ********** INSERT ;INSERT;$! ( INSERT ;INSERT;$!               ID: <<>>( INSERT ;INSERT;$!            Title: <<>> INSERT ;INSERT;$! ( INSERT ;INSERT;$!         Language: <<>>( INSERT ;INSERT;$!  Program Name(s): <<>> INSERT ;INSERT;$!d8 INSERT ;INSERT;$!        Called By: <<>>  (Option: <<>>)( INSERT ;INSERT;$!            Calls: <<>>( INSERT ;INSERT;$!      Files (I/O): <<>> INSERT ;INSERT;$!C( INSERT ;INSERT;$!      Description: <<>> INSERT ;INSERT;$!l( INSERT ;INSERT;$!  Special Remarks: <<>> INSERT ;INSERT;$!= INSERTL ;INSERT;$!******************************************************************
 ********** INSERT ;INSERT;$!h! INSERT ;INSERT;$!  Modifications:e INSERT ;INSERT;$!f7 INSERT ;INSERT;$!    Date      Author       Descriptiono	 Request #e* INSERT ;INSERT;$! *********  *************. ***********************************  *********" INSERT ;INCLUDE PRW$EDP_HEAD_LINE:L !               Notice the difference between this line and the others (-C). INSERT ;CHANGEK ;-L(D+CD+CI$!^Z-C"<<<DATE>>>"CUTSR=DELETE)DATE14(-C)2(D+C)2(+C)10(D+C)+L EX- INSERT ;INSERT;$!P INSERTL ;INSERT;$!******************************************************************
 ********** INSERT ;INSERT;$!o INSERT ;INSERT;<<>>a5 INSERT ;DEFINE KEY CONTROL D AS "'<<>>'CUTSR=DELETE."w !d       > -----Original Message-----8 > From: Terry Marosites [mailto:TMarosites@unitedad.com]' > Sent: Thursday, May 18, 2000 11:20 AMv+ > To: 'Peter Weaver'; Info-VAX@Mvb.Saic.Comh4 > Subject: RE: Inserting a DATE (was Re: EDT macros) >  >  > Thanks Peter,  > 8 >            But just for fun lets say I have in syloginD > $UNAME == f$edit(f$getjpi("","username"),"COLLAPSE,TRIM,COMPRESS") > ; > How do I get the user name inserted in place of Terry in - > 8 > define key gold c as "(i$! Changed by Terry on^ZDate). > = > Also would there be a way to changed the above line if the   > file type is .cob8 > to . > > > define key gold c as "(I       * Changed by Terry on^ZDate). >  > Just having  fun > Terry    ------------------------------  % Date: Thu, 18 May 2000 08:20:27 -0700f/ From: Terry Marosites <TMarosites@unitedad.com>f2 Subject: RE: Inserting a DATE (was Re: EDT macros)M Message-ID: <1137A4A23A51D311B2D600105A1D5213019AEE23@seantexch.unitedad.com>n  
 Thanks Peter,l  6            But just for fun lets say I have in syloginB $UNAME == f$edit(f$getjpi("","username"),"COLLAPSE,TRIM,COMPRESS")  9 How do I get the user name inserted in place of Terry in -  6 define key gold c as "(i$! Changed by Terry on^ZDate).  L Also would there be a way to changed the above line if the file type is .cob to .  < define key gold c as "(I       * Changed by Terry on^ZDate).   Just having  fun Terry  -----Original Message-----2 From: Peter Weaver [mailto:peter.weaver@stelco.ca]% Sent: Wednesday, May 17, 2000 3:05 PMa To: Info-VAX@Mvb.Saic.Com-. Subject: Inserting a DATE (was Re: EDT macros)    Terry Marosites wrote in messageD <1137A4A23A51D311B2D600105A1D5213019AEE1A@seantexch.unitedad.com>...  B >Does anyone know how to define a gold key  C as  that will insert some aB >line line of text and the date and time  ( example: $! Changed by Terry on, >16-MAY-2000 14:40:08) .This has me stumped.    E Here is an EDT line that will define GOLD D to insert the date with a   two digit year (i.e. 17-MAY-00);  F define key gold d as "(i..^zdate-'..'CUTSR+'-'''+C2(D+C)2(+C)9(D+C))."  % Here is the GOLD C key you asked for;u  7 define key gold c as "(i$! Changed by Terry on^ZDate)."m  E I know I wrote the first line at a site running V4.7, I do not recallED if the DATE command was available in prior versions of EDT. It works fine on AXP V7.2.    -- Peter Weaver      5 *****************************************************i    5 *****************************************************h4 Any views or opinions are solely those of the author) and do not necessarily represent those of  United News& Media.a5 *****************************************************P4 The information transmitted is intended only for the1 person or entity to which it is addressed and mayh3 contain confidential and/or privileged material. If)3 you are not the intended recipient of this message,l. please do not read, copy, use or disclose this3 communication and notify the sender immediately. Itr0 should be noted that any review, retransmission,2 dissemination or other use of, or taking action in- reliance upon, this information by persons or - entities other than the intended recipient is2 prohibited.a5 *****************************************************- **   ------------------------------  # Date: Thu, 18 May 2000 10:26:42 GMT-' From: Colin Blake <colin@theblakes.com>e. Subject: Re: Is "The GNU on VMS Project" dead?, Message-ID: <3923C5AC.8E192A8@theblakes.com>  & john babiarz at babiarz dot org wrote:  E > Where might I get GTK/GDK? I need to compile a program from a linuxI > box.  F The shareables (for 1.2.0) are included in the Mozilla kit. Work is inK progress to get the source code changes back into the official source tree.!   ------------------------------  % Date: Thu, 18 May 2000 12:05:54 +0100E+ From: Helmut Rondthaler <coremit@indigo.ie>g2 Subject: IS THERE LIMITS TO THE LOCAL SYMBOL TABLE< Message-ID: <000c01bfc0c0$f46b9bd0$4f01a8c0@hr1.core2000.ie>  8 VMS 7.2-1 ALPHA (4100) RUNNING 200+ USERS 2G.B OF MEMORY  C 3 SYMBOLS DEFINED IN THE BATCH LOGIN PROCESS HAVE NO VALUE WHEN THE_	 FOLLOWINGsG COMMANDS ARE PROCESSED AT THE BEGINNING OF A COBOL PROGRAMMING WHICH IS(% EXECUTED AS PART OF THE BATCH PROCESSI  9         CALL "LIB$GET_SYMBOL" USING BY DESCRIPTOR LOC_SYM >                                     BY DESCRIPTOR WS_USER_LOC.  9         CALL "LIB$GET_SYMBOL" USING BY DESCRIPTOR USR_SYMc=                                     BY DESCRIPTOR WS_USER_ID.R  :         CALL "LIB$GET_SYMBOL" USING BY DESCRIPTOR LEDG_SYM>                                     BY DESCRIPTOR WS_SYS_LEDG.  K However when we run the exact same software and command procedures on other'G alphas running vms7.2-1 with 10-30 users on average there is no problemO  K We are wondering is there some system limit that has been surpassed becauseu of the number of$ users running on our problem alpha .  I Note we built a standard VMS 7.2-1 kit which we have used to install manyAL alphas thus the alphas are setup similarly . Autogen does run once a week on the alphas !   Any help will be appreciated !   helmut@core2000.ie   ------------------------------  # Date: Thu, 18 May 2000 14:15:16 GMTS= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)T6 Subject: Re: IS THERE LIMITS TO THE LOCAL SYMBOL TABLE0 Message-ID: <009EA43A.6D595C2A@SendSpamHere.ORG>  j In article <000c01bfc0c0$f46b9bd0$4f01a8c0@hr1.core2000.ie>, Helmut Rondthaler <coremit@indigo.ie> writes:9 >VMS 7.2-1 ALPHA (4100) RUNNING 200+ USERS 2G.B OF MEMORYZ >OD >3 SYMBOLS DEFINED IN THE BATCH LOGIN PROCESS HAVE NO VALUE WHEN THE
 >FOLLOWINGH >COMMANDS ARE PROCESSED AT THE BEGINNING OF A COBOL PROGRAMMING WHICH IS& >EXECUTED AS PART OF THE BATCH PROCESS >O: >        CALL "LIB$GET_SYMBOL" USING BY DESCRIPTOR LOC_SYM? >                                    BY DESCRIPTOR WS_USER_LOC.E >I: >        CALL "LIB$GET_SYMBOL" USING BY DESCRIPTOR USR_SYM> >                                    BY DESCRIPTOR WS_USER_ID. >P; >        CALL "LIB$GET_SYMBOL" USING BY DESCRIPTOR LEDG_SYMI? >                                    BY DESCRIPTOR WS_SYS_LEDG.  > L >However when we run the exact same software and command procedures on otherH >alphas running vms7.2-1 with 10-30 users on average there is no problem    A Ever consider checking the return error codes from these calls???C  H The DCL symbol table pool is governed by the SYSGEN parameter CLISYMTBL.I On Alphas, the default is set at 512 pages.  Your other machines may haveE this value increased.   G I suspect that if you look at the return errors from the LIB$SET_SYMBOL,) call, you will likely see LIB$_INSCLIMEM.P       >dL >We are wondering is there some system limit that has been surpassed because >of the number of-% >users running on our problem alpha .- >-J >Note we built a standard VMS 7.2-1 kit which we have used to install manyM >alphas thus the alphas are setup similarly . Autogen does run once a week onM
 >the alphas !g >. >Any help will be appreciated !w >e >helmut@core2000.iew >e >D      H BTW, I recently augmented SYMBOL to display the pool/usage statistics ofF the DCL symbol table and its pool region defined by CLISYMTBL.  It's a- real nice way to quickly debug such problems.u     --N VAXman- OpenVMS APE certification number: AAA-0001           VAXman@TMESIS.COM  L GNU Freeware -- What does the GNU *really* stand for?  Garbage!  Not Usable!   ------------------------------  % Date: Thu, 18 May 2000 11:23:07 +0200i= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>t Subject: Re: Linux ==> Free VMSy) Message-ID: <3923B67B.2C0EDE42@gtech.com>    Mark Tarka wrote:-. > There was some guy at Cal Tech ranting about/ > a free VMS project, IIRC (not Vance...someoner > saner :-)m >  > Is this an option (free VMS)?r > ' > I ask, because I'm taking a hard looks# > at Red Hat Linux right now (gottan" > find a big enough hard drive :-) > $ > The box is an old DECstation 425c,$ > a 486DX at a blistering 25 MHz.... > # > Doesn't seem reasonable that it'd. > run VMS...anyone?    There is a "free VMS" project.  2 See http://www.free-vms.org/ for more information.  6 AFAIK very little is happening in that forum and there6 is no free VMS for x86 yet (and my guess is that there never will be).u   Arne   ------------------------------  + Date: Thu, 18 May 2000 10:53:18 -0400 (EDT)n* From: John MOore <john_d_moore@reyrey.com> Subject: Re: Linux ==> Free VMSmJ Message-ID: <Pine.GSO.4.05.10005181047560.7460-100000@poohbear.reyrey.com>   > -----Original Message-----5 > From:=09Arne Vajh=F8j [SMTP:arne.vajhoej@gtech.com]e( > Sent:=09Thursday, May 18, 2000 5:23 AM > To:=09Info-VAX@Mvb.Saic.Comt' > Subject:=09Re: Linux =3D=3D> Free VMS	 >=20 > Mark Tarka wrote::0 > > There was some guy at Cal Tech ranting about1 > > a free VMS project, IIRC (not Vance...someone2
 > > saner :-)m > >=20! > > Is this an option (free VMS)?  > >=20) > > I ask, because I'm taking a hard lookU% > > at Red Hat Linux right now (gotta8$ > > find a big enough hard drive :-) > >=20& > > The box is an old DECstation 425c,& > > a 486DX at a blistering 25 MHz.... > >=20% > > Doesn't seem reasonable that it'd! > > run VMS...anyone?- >=20  > There is a "free VMS" project. >=204 > See http://www.free-vms.org/ for more information. >=208 > AFAIK very little is happening in that forum and there8 > is no free VMS for x86 yet (and my guess is that there > never will be).d >=20 > Arne   Also have a peek at this URL:w  &   http://www.forest-edge.net/evax.html  8 'eVAX is a software implementation of a vax computer...'   -JM1 -----------------  QUOTE OF THE DAY:cE "I'm really enjoying not talking to you ... Let's not talk again REALs	 soon ..."0   --A            .--.                -----BEGIN GEEK CODE BLOCK-----=20g.      .-.    \ \                Version: 3.1=20G      `-'     \ \   \__.   .__. GCS/IT/MU/C/L/P d-(?) s: a36(18) C+(---)eH      ._.  ---'  \  |   \_/   | ULS++++$ P+ L++>+++ E-@() W+ N+ o-- K?=20D      | |.' .--.  \ | .-. .-. | w+@(--) O? M- V(-) PS+ PE Y+ PGP++=20G      | ||  `--'   ;| | | | | | t(--) 5 X+ !R+(-) tv+ b+++ DI- D+(--)=20 ?      | | `____,-__||_; `-' `_; G(-) e+@>++@ h---- r+++ y+++ =20-< ,^   ; | John D. Moore         -----END GEEK CODE BLOCK-----@ \ `-'  ; john_d_moore@reyrey.com   http://2000run.virtualave.netL  `._,-'It's another promise d.o.a. and despite my every hope there is no tr= uthcL        behind my best intentioned oath. -- "Come Down", Toad the Wet Sprock= et  $ -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2  @ mQCNAzHa3p4AAAEEAK3OwgZHti9HntYO/el8P19uIYNnGTJt2x7vwEdb52iLqPzL@ dzmsPxDvavz0JMFsZ4XPuOWuXRmSJZqAuPCu3d/t7cvX8K/g0d2eXsCrsDELreEA@ Q9lfdN2K5UPgn4Fx5l6CGOgnO5s2ztmkl5LfM+A/A3YypECAwZ9zaiFsI+ORAAUR: tCdKb2huIEQuIE1vb3JlIDxqb2huX2RfbW9vcmVAcmV5cmV5LmNvbT4=3D =3DnSqd5" -----END PGP PUBLIC KEY BLOCK-----   ------------------------------  + Date: Thu, 18 May 2000 15:54:06 +0000 (   )n3 From: Christopher Smith <chriss@Mufasa.pubserv.com>I Subject: Re: Linux ==> Free VMS'J Message-ID: <Pine.LNX.4.05.10005181547480.18134-100000@Mufasa.pubserv.com>  & On Wed, 17 May 2000, Mark Tarka wrote:   > Is this an option (free VMS)?>  J It's not even half complete yet.  Right now, I'd say (no disrespect to the@ project intended, and I wish them the best of luck) it's only an interesting side-note.  $ > The box is an old DECstation 425c,$ > a 486DX at a blistering 25 MHz....  # > Doesn't seem reasonable that it'dD > run VMS...anyone?t  C No, VMS only runs on alpha and vax cpus.  Freevms, if and when it'sT? finished should be based on mach, and runnable on lots of othersJ architectures, but, as I said earlier, there's not enough done to use yet.  C This is a more or less common mistake, and DEC didn't help by usingcH DECStation to identify not only some alphas, but some mips machines, and some peesee type computers.I  E If you're looking for something functional to run on that machine I'd>G suggest linux or netbsd (netbsd might be a better choice, since linux'sHJ system requirements have been steadilly increasing to the point where it's: not feasible to run it on such modest hardware these days.  G If you're looking for something that's just kind of cool, and more of a=9 curiousity, download the demonstration version of plan-9.*F (plan9.bell-labs.com, I think)... That's a pretty interesting project.   Regards,   ChrisT  O ===============================================================================T@ "My two cents"			(http://rootworks.com/twocentsworth.cgi?128562)= Christopher Smith(chriss@pubserv.com)			Prgramer^W Programmer  Prime Synergy of Champaign, IL.>% ------------------------------------- I "Where a calculator on the ENIAC is equipped with 18,000 vacuum tubes and;H weighs 30 tons, computers in the future may have only 1,000 vacuum tubes; and weigh only 1.5 tons." -- Popular Mechanics, March 1949 *O -------------------------------------------------------------------------------E   ------------------------------  % Date: Thu, 18 May 2000 13:36:12 +0000E/ From: Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk>o6 Subject: re: Linux port question. $QIOW() to sendto().7 Message-ID: <009EA456.7F39B999.28@maxwell.ph.kcl.ac.uk>T   >  > Hi,$H >     I've been working on porting an network traffic generator app fromG > an Alpha to Linux. The fundamental difference is that the Alpha (Open*G > VMS 7.1-1H1) uses a $QIO() to sned the ethernet packet to the driver. 7 > Where as the Linux system uses the sendto() function.K [snip]B > My question is: When I use the Alpha implementation there are noE > collosion problems. It only occurs using Linux. Both boxes have DEC*G > tulip PCI cards. Does anyone have any suggestions as to what might be H > causing this? Does $QIO do anything different. I can't see why because > it's really up to the card.N  / I wasn't too clear exactly what you are doing. E  > However, 50% collisions is way, WAY too high and implies that E some hardware somewhere is not working right, or that the software isC* interpreting some hardware status wrongly.  I On a test network of small extent with just two systems on it, I'd expectTJ the collision rate to be very small. A collision is what happens when bothJ systems start to transmit before they realise that the other one has also G started, because of the propagation delay between the two systems. TheysC then back off for a random time and try again. Propagation delay iseG related to the speed of a signal in the cable (a decent fraction of the*A speed of light) plus a small delay at any hubs it goes through.  E  E Sounds to me like the VMS version is working fine, and there's a bug CC somewhere in the Linux one! And as you say, it IS a function of the*: Ethernet card rather than $QIO or any other host software.   	Yours,;
 		Nigel ArnotE- 		NRA@MAXWELL.PH.KCL.AC.UK                   A  7 		"In the beginning there was nothing, which exploded."o   ------------------------------   Date: 18 May 2000 13:52:10 GMT1 From: JONESD@er6.eng.ohio-state.edu (David Jones)*6 Subject: re: Linux port question. $QIOW() to sendto().: Message-ID: <8g0sia$5l2$1@charm.magnus.acs.ohio-state.edu>  C >> My question is: When I use the Alpha implementation there are noTF >> collosion problems. It only occurs using Linux. Both boxes have DECH >> tulip PCI cards. Does anyone have any suggestions as to what might beI >> causing this? Does $QIO do anything different. I can't see why becauseE >> it's really up to the card. >T   >E> >However, 50% collisions is way, WAY too high and implies thatF >some hardware somewhere is not working right, or that the software is+ >interpreting some hardware status wrongly.T  I You can get lots of collisions if a the NIC is set to full duplex and the$5 swtich port it is connected to isn't (or vice versa).N    < David L. Jones               |      Phone:    (614) 292-6929- Ohio State University        |      Internet:_L 140 W. 19th St. Rm. 231a     |               jonesd@er6s1.eng.ohio-state.edu: Columbus, OH 43210           |               vman+@osu.edu  + Disclaimer: Dogs can't tell it's not bacon.N   ------------------------------  % Date: Thu, 18 May 2000 11:53:48 -0400*" From: Dan Sugalski <dan@sidhe.org>6 Subject: Re: Linux port question. $QIOW() to sendto().8 Message-ID: <4.3.1.0.20000518115010.02189dc0@24.8.96.48>  & At 08:16 PM 5/17/00 +0100, Mark wrote:H >Each frame is 146 bytes long. Which works out at about 22% (1000 framesG >per sec) band width used by the test gen and 22% from the system underI7 >test. Total 44% total bandwidth usaed on a 10Mbps LAN.t > A >My question is: When I use the Alpha implementation there are noUD >collosion problems. It only occurs using Linux. Both boxes have DECF >tulip PCI cards. Does anyone have any suggestions as to what might beG >causing this? Does $QIO do anything different. I can't see why becausee >it's really up to the card.  I This means that either the Alpha code is waiting for the response before  L sending the next packet, or you're just getting lucky with the timing. It's I possible that the two OSes are using different wait times to see whether e' there's traffic on the network segment.   K It's also possible that the linux system is sending more traffic over that 1O segment than just your test packets. Does it have something broadcasty running?    					Dan  I --------------------------------------"it's like this"-------------------O2 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and evena;                                       teddy bears get drunkg   ------------------------------  % Date: Thu, 18 May 2000 04:11:53 -0700I5 From: Richard  <maher_rjNOmaSPAM@hotmail.com.invalid>n0 Subject: Re: Looking for COBOL GETQUI example(s)9 Message-ID: <1821ebda.24832fea@usw-ex0108-062.remarq.com>y   Hi,0  6 Among other things the following code contains $getqui9 stuff which IMHO should be a good starting point. I don'ts; see how a language other than COBOL could be anymore usefult0 or appropriate for the job, but each to his own.   Regards Richard Maher.  ; PS. I've used the persona system services just to show how,m3 because these are incredibly useful for other TIER3.6 applications. If you want to just $getqui on behalf of< another user you can use jbc$_search_as_username (spelling?)  < ************************************************************ ************************ *e                        *7 *         COPYRIGHT (c) 1994 BY TIER3 SOFTWARE LTD. ALLn RIGHTS RESERVED.           * *f                        *: *    THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED ONLY    *t9 *    IN ACCORDANCE  WITH THE TERMS AND CONDITIONS OF SUCH* LICENSE AND  WITH THE    *8 *    THE INCLUSION  OF THE ABOVE COPYRIGHT NOTICE.  THIS SOFTWARE  OR ANY OTHER    *i7 *    COPIES  THEREOF MAY NOT  BE PROVIDED  OR OTHERWISEt MADE AVAILABLE  TO  ANY    *9 *    OTHER  PERSON.  NO  TITLE TO  AND OWNERSHIP  OF  THE* SOFTWARE  IS  HEREBY    *n *m TRANSFERRED.                   *f *t                        *5 *    THE INFORMATION  IN THIS SOFTWARE  IS SUBJECT TOo CHANGE WITHOUT NOTICE AND    *5 *    SHOULD NOT BE CONSTRUED AS A COMMITMENT BY TIER3e SOFTWARE LTD.                * *                         *< ************************************************************ ************************ *+ * Routine Name: USER_INITa *g: * This routine is called by Tier3 as part of the execution server's initializationn
 * procedures.t *2: * In this routine you would normally open files or connect to any database(s): * required by your application. In the DEMO application no files or databases are7 * accessed directly, but an exit handler is declared toM listen for an abnormal * termination. *9< * As a CLI has been loaded you are also free to spawn a sub- process via LIB$SPAWNT6 * if that is a requirement of your application, and it should be noted that there7 * is no restriction on this execution server becoming at client of different Tier3e" * application(s) on other node(s). *- identification division. program-id.    user_init.  data division. working-storage section.8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal.08 01  sys_status                      pic s9(9)       comp# value   external        ss$_normal.  01  exit_desblk.9     03                              pic s9(9)       comp._8     03                              pic s9(9)       comp% value   external        exit_handler.A8     03                              pic s9(9)       comp
 value   1.;     03                                              pointerD$ value   reference       exit_status.9 01  exit_status                     pic s9(9)       comp.  *  01  demo_context. -     03  system_name                 pic x(8).$9     03  buffer_size                 pic 9(9)        comp. .     03  session_user                pic x(12).9     03  timer_context               pic 9(9)        comp.c9     03  session_count               pic 9(9)        comp.o9     03  message_count               pic 9(9)        comp. 9     03  lostlnk_count               pic 9(9)        comp.n9     03  persona_context             pic 9(9)        comp.u *+3 * DEBUG area. TIER3 sets the "language" to COBOL byl default, so the followingh2 * debugger commands are included just to show how. *-8 \d01  ss$_debug                     pic s9(9)       comp" value   external        ss$_debug. \d01  debug_commands.,, \d    03  cmd_len                   pic x(1) value   x"25".- \d    03                            pic x(37)H0 value   "set language cobol; show process/full". *9 linkage section.- 01  t3_system_name                  pic x(8).99 01  t3_buffer_size                  pic 9(9)        comp.n7 procedure division using t3_system_name, t3_buffer_sizeE giving sys_status. 00.3 *+8 * In this example, for the VMS debugger to be invoked at
 run-time thenG6 * the /conditionals=d qualifier needs to be applied at
 compile-time.  * 7 * To assist a run-time decision as to whether or not to  invoke debug5 * TIER3 has defined a local DCL symbol T3$DEBUG. This 
 symbol is set ; * to the value specified by the system manager in the Tier3U
 ConfigurationT * file ie: "Y" or "N". *- \d      call "lib$signal"C4 \d              using   by value        ss$_debug, 17 \d                      by reference    debug_commands.  *+; * Record some startup information in the execution server'st	 log file.m *-7     display "Initializing application " t3_system_name.m;     display "Buffer size is           " t3_buffer_size withv conversion.h *+5 * These example routines are designed specifically toC handle requests fors8 * the DEMO application only and require a buffer size of 510 bytes, but a9 * single shareable image, or set of user action routines,c could be designedc8 * to service the requests of multiple applications. Such routines could use: * the t3_system_name argument to determine the appropriate code path to8 * execute at run-time. Similarly, by designing your user action routines to8 * be able to cope with a variable buffer size you afford the system manager1 * greater flexibility in tuning your application.a *r9 * We'll remember the Tier3 application parameters as theya may come in handy. *-'     move t3_system_name to system_name.0'     move t3_buffer_size to buffer_size.m *+; * By passing the address of the data structure DEMO_CONTEXTb as the context5 * argument to the routine T3$SETCTX, the data is madea available to all9 * subsequent user routines by becoming the first argument 
 in each call.1 *-:     call "t3$setctx" using demo_context giving sys_status..     if sys_status not = ss$_normal go to fini. *+9 * DEMO does not need any application specific cleanup but0 we'll check the exit * status anyway. *-:     call "sys$dclexh" using exit_desblk giving sys_status. *  fini.-     exit program.E *g end program user_init. *+ * Routine Name: USER_LOGON *a; * This routine is called by Tier3 when a client request has. been allocated to-9 * the execution server for processing. From this point onu an association is said7 * to exist between the client and execution server. Theo association is terminatedh/ * by specifying either the t3$m_close or the t3b# $m_disconnect modifier in a call toe8 * the T3$SEND routine. The communication server may also cancel an association at2 * any time if the link to the client task is lost. *F; * Note: The output channel to the client will not be openedr until the USER_LOGON8 *       routine has returned control to Tier3. Therefore any attempt to call-; *       T3$SEND from this routine would result in the erroro T3$_CHANCLOSE beinge *       returned.c *- identification division. program-id.    user_logon. data division. working-storage section.8 01  t3$k_decnet                     pic s9(9)       comp$ value   external        t3$k_decnet.8 01  t3$k_tcp_ip                     pic s9(9)       comp$ value   external        t3$k_tcp_ip.8 01  lib$_strtru                     pic s9(9)       comp$ value   external        lib$_strtru.8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal. 8 01  sys_status                      pic s9(9)       comp# value   external        ss$_normal.w *o8 01  persona_create_flags            pic s9(9)       comp- value   external        persona_create_flags.t8 01  persona_assume_flags            pic s9(9)       comp- value   external        persona_assume_flags.  *r. 01  remote_node_name                pic x(31).. 01  remote_user_name                pic x(12).- 01  remote_user_socket              redefinesd remote_user_name.e     03  remote_host_addr.e*         05  rha_1                   pic x.*         05  rha_2                   pic x.*         05  rha_3                   pic x.*         05  rha_4                   pic x.9     03  remote_port_num             pic 9(9)        comp.  *m9 01  tcpip_rem_user_len              pic 9(4)        comp.n. 01  tcpip_rem_user                  pic x(21). *  linkage section. 01  demo_context.2-     03  system_name                 pic x(8).=9     03  buffer_size                 pic 9(9)        comp. .     03  session_user                pic x(12).9     03  timer_context               pic 9(9)        comp. 9     03  session_count               pic 9(9)        comp.|9     03  message_count               pic 9(9)        comp.-9     03  lostlnk_count               pic 9(9)        comp.+9     03  persona_context             pic 9(9)        comp.C * 9 01  transport_type                  pic 9(4)        comp.u *i- 01  remote_node_desc                pic x(8).. *d- 01  remote_user_desc                pic x(8).  *  01  local_user_desc.     03  lud_class_len.9         05  lud_len                 pic 9(4)        comp.L9         05  lud_class               pic 9(4)        comp.O9     03  lud_addr                    pic 9(9)        comp.R *Z& procedure division using demo_context,(                          transport_type,*                          remote_node_desc,*                          remote_user_desc,1                          local_user_desc   giving- sys_status.- 00.  *+: * Initialize the timers and counts for session statistics. *-4     call "lib$init_timer" using timer_context giving sys_status. .     if sys_status not = ss$_normal go to fini.       add 1 to session_count.n *+; * COBOL cannot receive arguments by descriptor transparenty  so8 * the Run-Time Library routine LIB$SCOPY_DXDX is used to copy: * the remote_node, remote_user and local_user arguments to fixedk* * length strings in local working-storage. *-     call "lib$scopy_dxdx"54             using   by reference    remote_node_desc4                     by descriptor   remote_node_name             giving sys_status.8     if sys_status not = ss$_normal and lib$_strtru go to fini.a       call "lib$scopy_dxdx"t4             using   by reference    remote_user_desc4                     by descriptor   remote_user_name             giving sys_status.8     if sys_status not = ss$_normal and lib$_strtru go to fini.m *+7 * The return status lib$_strtru is treated as a seriousr	 error foro; * the local username. ie 12 bytes is the maximum length fori a VMSn * username.  *-     call "lib$scopy_dxdx" 3             using   by reference    local_user_descr0                     by descriptor   session_user             giving sys_status..     if sys_status not = ss$_normal go to fini. *+9 * Report the client association in the execution server'sd	 log file.n *-;     display "Association with ", session_user(1:lud_len), "p
 established".n:     display "Transport = " transport_type with conversion.,     display "Rem node  = " remote_node_name.(     display "Rem user  = " no advancing.       evaluate    transport_type8         when    t3$k_decnet     display remote_user_name.         when    t3$k_tcp_ip     call "sys$fao"2                                         using   by& descriptor   "!@UB.!@UB.!@UB.!@UB:!ZL"2                                                 by reference    tcpip_rem_user_lent2                                                 by descriptor   tcpip_rem_user-2                                                 by' reference    rha_1, rha_2, rha_3, rha_4-2                                                 by value        remote_port_num:                                         giving  sys_status3                                 if sys_status not =l ss$_normal go to fini end-if6                                 display tcpip_rem_user (1:tcpip_rem_user_len)     end-evaluate.e *+6 * By assuming the persona of the VMS username that the remote client hasd: * been authorized to use on local node we have removed the need to performo9 * additional security checking such as $check_access. IE:  This server will9 * be running with only those privileges and access rights  that the clientr5 * is entitled to assume. (Let VMS do all the work :-)g *s0 * NB: Again, this is only a suggestion and not a requirement of Tier3. If: *     you choose to use this extremely usefull VMS feature then the usernamel8 *     that the demo application will run under will need DETACH privilege1 *     and read access to SYSUAF (Usually SYSPRV).$ *-     call "sys$persona_create"t/         using   by reference    persona_contexti7                 by descriptor   session_user(1:lud_len) 4                 by value        persona_create_flags         giving  sys_status. .     if sys_status not = ss$_normal go to fini.       call "sys$persona_assume"t/         using   by reference    persona_context 4                 by value        persona_assume_flags         giving  sys_status.  *  fini.      exit program.v *o end program user_logon.x *+ * Routine: USER_RECV *p3 * The USER_RECV routine is called by Tier3 for eachi message, orn7 * fragment of a message, that is received from a clienta
 with which% * the execution server is associated.l *e6 * In the DEMO example we are receiving one message per association  * with no fragmentation. *s; * If the status value T3$_CHANCLOSE is returned from the T3o $SENDc7 * routine it is assumed that the link to the client hasn	 been losto: * so we simply return control to Tier3 after resetting our existt- * status to SS$_NORMAL to avoid server crash.r *p; * NB:   If you application incorporates User Written Systemt Services: *       do NOT use any executive mode dispatching codes in	 the range < *       -3000 to -2900 as these codes are reserved to Tier3. *- identification division. program-id.    user_recv.t data division. working-storage section.8 01  t3$_chanclose                   pic s9(9)       comp& value   external        t3$_chanclose.8 01  jbc$_nosuchent                  pic s9(9)       comp' value   external        jbc$_nosuchent. 8 01  jbc$_nomoreent                  pic s9(9)       comp' value   external        jbc$_nomoreent. 8 01  jbc$_normal                     pic s9(9)       comp$ value   external        jbc$_normal.8 01  ss$_abort                       pic s9(9)       comp" value   external        ss$_abort.8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal. 9 01  sys_status                      pic s9(9)       comp.i *a8 01  t3$m_close                      pic 9(9)        comp# value   external        t3$m_close.s8 01  t3$m_now                        pic 9(9)        comp! value   external        t3$m_now.N8 01  t3$m_more                       pic 9(9)        comp" value   external        t3$m_more.8 01  t3$m_oob                        pic 9(9)        comp! value   external        t3$m_oob.r8 01  qui$_display_entry              pic s9(9)       comp+ value   external        qui$_display_entry. 8 01  qui$_cancel_operation           pic s9(9)       comp. value   external        qui$_cancel_operation.8 01  qui$m_search_wildcard           pic s9(9)       comp. value   external        qui$m_search_wildcard. *c9 01  sts_index                       pic s9(9)       comp.n9 01  on_or_off                       pic s9(9)       comp. 9 01  entry_count                     pic 9(9)        comp. 
 01  qui_iosb. 9     03  qui_cond                    pic s9(9)       comp. 9     03                              pic s9(9)       comp.  01  que_status_table. 8     03                              pic s9(9)       comp. value   external        qui$m_queue_available.-     03                              pic x(10)a value   "AVAILABLE".8     03                              pic s9(9)       comp) value   external        qui$m_queue_busy. -     03                              pic x(10)n value   "BUSY". 8     03                              pic s9(9)       comp- value   external        qui$m_queue_disabled.e-     03                              pic x(10)e value   "DISABLED". 8     03                              pic s9(9)       comp) value   external        qui$m_queue_idle.i-     03                              pic x(10). value   "IDLE"._8     03                              pic s9(9)       comp+ value   external        qui$m_queue_paused.e-     03                              pic x(10)  value   "PAUSED". 8     03                              pic s9(9)       comp, value   external        qui$m_queue_pausing.-     03                              pic x(10)  value   "PAUSING".8     03                              pic s9(9)       comp- value   external        qui$m_queue_resuming. -     03                              pic x(10)  value   "RESUMING". 8     03                              pic s9(9)       comp, value   external        qui$m_queue_stalled.-     03                              pic x(10)  value   "STALLED".8     03                              pic s9(9)       comp- value   external        qui$m_queue_starting. -     03                              pic x(10)  value   "STARTING". 8     03                              pic s9(9)       comp, value   external        qui$m_queue_stopped.-     03                              pic x(10)) value   "STOPPED".8     03                              pic s9(9)       comp- value   external        qui$m_queue_stopping. -     03                              pic x(10)  value   "STOPPING".o- 01  que_status_array                redefinesd que_status_table. .     03  que_status_item             occurs 11.9         05  que_value               pic s9(9)       comp.n.         05  que_text                pic x(10). 01  que_flags_table.8     03                              pic s9(9)       comp, value   external        qui$m_queue_printer.-     03                              pic x(10)s value   "PRINTER".8     03                              pic s9(9)       comp* value   external        qui$m_queue_batch.-     03                              pic x(10)a value   "BATCH".8     03                              pic s9(9)       comp, value   external        qui$m_queue_generic.-     03                              pic x(10)  value   "GENERIC".8     03                              pic s9(9)       comp- value   external        qui$m_queue_terminal. -     03                              pic x(10)  value   "TERMINAL".d- 01  que_flags_array                 redefinesg que_flags_table.-     03  que_flags_item              occurs 4.g9         05  flags_value             pic s9(9)       comp.d.         05  flags_text              pic x(10). 01  job_status_table.x8     03                              pic s9(9)       comp+ value   external        qui$m_job_aborting.e-     03                              pic x(15)s value   "ABORTING".r8     03                              pic s9(9)       comp, value   external        qui$m_job_executing.-     03                              pic x(15)i value   "EXECUTING".8     03                              pic s9(9)       comp* value   external        qui$m_job_holding.-     03                              pic x(15)= value   "HOLDING".8     03                              pic s9(9)       comp/ value   external        qui$m_job_inaccessible. -     03                              pic x(15)k value   "INACCESSIBLE"."8     03                              pic s9(9)       comp* value   external        qui$m_job_pending.-     03                              pic x(15)e value   "PENDING".8     03                              pic s9(9)       comp* value   external        qui$m_job_refused.-     03                              pic x(15)e value   "REFUSED".8     03                              pic s9(9)       comp+ value   external        qui$m_job_retained. -     03                              pic x(15)t value   "RETAINED". 8     03                              pic s9(9)       comp* value   external        qui$m_job_stalled.-     03                              pic x(15)  value   "STALLED".8     03                              pic s9(9)       comp+ value   external        qui$m_job_starting.t-     03                              pic x(15)s value   "STARTING".n8     03                              pic s9(9)       comp, value   external        qui$m_job_suspended.-     03                              pic x(15)  value   "SUSPENDED".8     03                              pic s9(9)       comp0 value   external        qui$m_job_timed_release.-     03                              pic x(15)N value   "TIMED RELEASE".- 01  job_status_array                redefinesi job_status_table.o.     03  job_status_item             occurs 11.9         05  job_value               pic s9(9)       comp.i.         05  job_text                pic x(15). *r< 01  item_list_addr                                  pointer. *o 01  entry_item_list.     03  item_search_entry.#         05  pic s9(4) comp value 4.t)         05  pic s9(4) comp value externalo qui$_search_number.,2         05  pointer value reference search_number.         05  pic s9(9) comp.o     03  item_queue_flags.i#         05  pic s9(4) comp value 4.t;         05  pic s9(4) comp value external qui$_queue_flags. .         05  pointer value reference que_flags.         05  pic s9(9) comp.t     03  item_que_status.#         05  pic s9(4) comp value 4. <         05  pic s9(4) comp value external qui$_queue_status./         05  pointer value reference que_status.e         05  pic s9(9) comp.      03  item_job_status.#         05  pic s9(4) comp value 4. :         05  pic s9(4) comp value external qui$_job_status./         05  pointer value reference job_status.2         05  pic s9(9) comp.D     03  item_que_name.$         05  pic s9(4) comp value 31.:         05  pic s9(4) comp value external qui$_queue_name.-         05  pointer value reference que_name.i1         05  pointer value reference que_name_len.e     03  item_job_name.$         05  pic s9(4) comp value 39.8         05  pic s9(4) comp value external qui$_job_name.-         05  pointer value reference job_name.?1         05  pointer value reference job_name_len.e     03  pic s9(9) comp.  *t 01  wild_item_list.H     03  item_search_flags.#         05  pic s9(4) comp value 4.m<         05  pic s9(4) comp value external qui$_search_flags.:         05  pointer value reference qui$m_search_wildcard.         05  pic s9(9) comp.      03  item_queue_flags.e#         05  pic s9(4) comp value 4.e;         05  pic s9(4) comp value external qui$_queue_flags. .         05  pointer value reference que_flags.         05  pic s9(9) comp.t     03  item_job_entry.3#         05  pic s9(4) comp value 4.n<         05  pic s9(4) comp value external qui$_entry_number..         05  pointer value reference job_entry.         05  pic s9(9) comp.-     03  item_que_status.#         05  pic s9(4) comp value 4.r<         05  pic s9(4) comp value external qui$_queue_status./         05  pointer value reference que_status.2         05  pic s9(9) comp.6     03  item_job_status.#         05  pic s9(4) comp value 4.1:         05  pic s9(4) comp value external qui$_job_status./         05  pointer value reference job_status.r         05  pic s9(9) comp.T     03  item_que_name.$         05  pic s9(4) comp value 31.:         05  pic s9(4) comp value external qui$_queue_name.-         05  pointer value reference que_name..1         05  pointer value reference que_name_len.      03  item_job_name.$         05  pic s9(4) comp value 39.8         05  pic s9(4) comp value external qui$_job_name.-         05  pointer value reference job_name.h1         05  pointer value reference job_name_len.e     03  pic s9(9) comp.e *o9 01  search_number                   pic s9(9)       comp.e. 01  que_name                        pic x(31).9 01  que_name_len                    pic 9(4)        comp. 9 01  que_status                      pic s9(9)       comp.e9 01  que_flags                       pic s9(9)       comp.D. 01  job_name                        pic x(39).9 01  job_name_len                    pic 9(4)        comp.t9 01  job_status                      pic s9(9)       comp. 9 01  job_entry                       pic s9(9)       comp.e *d9 01  local_flags                     pic 9(9)        comp.e 01  show_entry_reply. *     03                              pic xx
 value   "11".:-     03  se_entry_number             pic 9(4).h.     03  se_job_name                 pic x(39)..     03  se_job_status               pic x(15)..     03  se_que_name                 pic x(31)..     03  se_que_type                 pic x(10)..     03  se_que_status               pic x(10).8 01  show_entry_len                  pic 9(9)        comp value   111. 01  error_msg.*     03                              pic xx
 value   "00". ,     03  error_len                   pic 999./     03  error_text                  pic x(505).d *y linkage section. 01  demo_context.s-     03  system_name                 pic x(8).t9     03  buffer_size                 pic 9(9)        comp. .     03  session_user                pic x(12).9     03  timer_context               pic 9(9)        comp. 9     03  session_count               pic 9(9)        comp.D9     03  message_count               pic 9(9)        comp. 9     03  lostlnk_count               pic 9(9)        comp. 9     03  persona_context             pic 9(9)        comp.H *E
 01  msg_buff.I+     03  msg_type                    pic xx.          88  show_entry
 value   "10".T/     03                              pic x(508).  01  show_entry_msg redefines       msg_buff.W+     03                              pic xx.R-     03  show_entry_number           pic 9(4).*-     03  show_entry_max              pic 9(4).  * 9 01  msg_size                        pic s9(9)       comp.F *A9 01  msg_flags                       pic s9(9)       comp.C *N procedure division         using   demo_context,T                 msg_buff,                  msg_size,                  msg_flags*"                 giving sys_status. kick_off section.* 00.*     add 1 to message_count.  *+; * If the client has sent a message that is greater than thef buffer sizen6 * for this application, then Tier3 will set the bit T3 $V_MORE in the4 * msg_flags argument. The remaining fragments of the message are not lost,p: * and will be delivered to user_recv routine in subsequent invocations.9 * This example does not contain all of the code necessary  to properlye: * handle fragmented messages. The following "IF" statement is includedu9 * merely to illustrate how your routine would be notifiedo of fragmentation.  *-6     call "mth$jiand" using msg_flags, t3$m_more giving local_flags.:     if local_flags not = zeros display "Fragmented message - More to come". *+8 * NOTE: All Tier3 parameters passed to your routines are
 maintained ino: * user mode read-only storage. Any attempt to modify their
 contents will 9 * result in an access violation. Take a copy of any input  parameter that0 * needs to be modified to local working-storage. *-"     move low-values to error_text.       evaluate        true:             when    show_entry      if show_entry_number = zeros93                                             perform  get_entry_wild3                                     else    perform  get_entry_info*                                     end-if5             when    other           move ss$_abort to 
 sys_status     end-evaluate.        exit program.e *c get_entry_wild section.n 00. 3     set item_list_addr to reference wild_item_list.        perform get_que_info.   "     if sys_status = jbc$_nosuchent             perform send_error'     else    if sys_status = jbc$_normal -                     move zeros to entry_count 2                     perform until sys_status not =+ jbc$_normal or entry_count = show_entry_max 0                             add 1 to entry_count.                             perform send_entry6                             if sys_status = ss$_normal8                                     perform get_que_info"                             end-if                     end-perform 2                     if sys_status = jbc$_normal or jbc$_nomoreent*                             call "t3$send"8                                     using   by reference "99EOF"a4                                             by value
 5, t3$m_close 7                                     giving  sys_status.t *+5 * The maximum number of entries may have been reachedr before all $GETQUI information4 * had been retrieved for the wildcard search, or the association with the client maym7 * have been terminated prematurely by the communicationu server, therefore we muste4 * be sure to tell the job controller that we wish to terminate the wildcard search. *-/     if sys_status = ss$_normal or t3$_chanclose              call "sys$getquiw"'                     using   by value 0,n qui$_cancel_operation, 0, 0y1                             by reference qui_iosb )                             by value 0, 0 &                     giving  sys_status9             if sys_status = ss$_normal and qui_cond not =_ jbc$_normal 0                     move qui_cond to sys_status. *  get_entry_info section.e 00._7     move show_entry_number to search_number, job_entry. 4     set item_list_addr to reference entry_item_list.       perform get_que_info.   "     if sys_status = jbc$_nosuchent             perform send_error'     else    if sys_status = jbc$_normalc&                     perform send_entry.                     if sys_status = ss$_normal*                             call "t3$send"8                                     using   by reference "99EOF" 4                                             by value
 5, t3$m_closen7                                     giving  sys_status.o *o fini.e4     if sys_status = t3$_chanclose move ss$_normal to sys_status.v *c send_error section.f 00.a     move 13 to error_len.r5     move "No such entry" to error_text (1:error_len).u     call "t3$send"-             using   by reference    error_msga;                     by value        buffer_size, t3$m_closes             giving  sys_status.  *a send_entry section.t 00. &     move job_entry to se_entry_number.1     move job_name(1:job_name_len) to se_job_name. 1     move que_name(1:que_name_len) to se_que_name.   '     move zeros to sts_index, on_or_off. 9     perform until sts_index = 11 or on_or_off not = zeros              add 1 to sts_index.             call "mth$jiand" using job_status,8                                    job_value (sts_index),                             giving on_or_off     end-perform.     if on_or_off = zeros+             move "UNKNOWN" to se_job_status 6     else    move job_text (sts_index) to se_job_status$             move zeros to on_or_off.       move zeros to sts_index.9     perform until sts_index = 11 or on_or_off not = zeros              add 1 to sts_index/             call "mth$jiand" using  que_status, 9                                     que_value (sts_index)1-                             giving  on_or_off      end-perform.     if on_or_off = zeros+             move "UNKNOWN" to se_que_status 6     else    move que_text (sts_index) to se_que_status$             move zeros to on_or_off.       move zeros to sts_index.8     perform until sts_index = 4 or on_or_off not = zeros             add 1 to sts_index.             call "mth$jiand" using  que_flags,;                                     flags_value (sts_index)x-                             giving  on_or_offt     end-perform.     if on_or_off = zeros)             move "UNKNOWN" to se_que_type 7     else    move flags_text (sts_index) to se_que_type.        call "t3$send"4             using   by reference    show_entry_reply<                     by value        show_entry_len, t3$m_now             giving  sys_status._ *t get_que_info section.  00. (     call "sys$getquiw" using by value 0,$ qui$_display_entry, 0 item_list_addr2                              by reference qui_iosb*                              by value 0, 0(                     giving   sys_status.;     if sys_status = ss$_normal move qui_cond to sys_status.  *  end program user_recv. *+ * Routine: USER_LOGOFF * 6 * This routine is called when the association with the client has been_4 * terminated, either by the USER_RECV routine or the communication server,S: * and the USER_RECV routine has returned control to Tier3. *o; * For the DEMO example we are logging resource usage by the  client.  *- identification division. program-id.    user_logoff.  data division. working-storage section.8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal.u9 01  sys_status                      pic s9(9)       comp.9 * 8 01  persona_assume_flags            pic s9(9)       comp- value   external        persona_assume_flags.a8 01  restore_persona                 pic 9(9)        comp
 value   1. *p linkage section. 01  demo_context._-     03  system_name                 pic x(8). 9     03  buffer_size                 pic 9(9)        comp. .     03  session_user                pic x(12).9     03  timer_context               pic 9(9)        comp. 9     03  session_count               pic 9(9)        comp. 9     03  message_count               pic 9(9)        comp. 9     03  lostlnk_count               pic 9(9)        comp. 9     03  persona_context             pic 9(9)        comp.  * 8 procedure division using demo_context giving sys_status. 00._9     display "Session completed with user ", session_user.a      move spaces to session_user.       call "sys$persona_assume" /         using   by reference    restore_personai4                 by value        persona_assume_flags         giving  sys_status._.     if sys_status not = ss$_normal go to fini.  :     call "sys$persona_delete" using persona_context giving sys_status._.     if sys_status not = ss$_normal go to fini. *+( * Display the user's session statistics. *u: * The Run-Time Library performance reporting routines have	 been usedp6 * as a very simple example of obtaining information on server resource 5 * usage by a client. If this is a requirement of your  application then9 * you should consider obtaining more detailed informationu via the VMS 6 * system services $GETTIM and $GETJPI and accumulating totals for each ; * user in a disk file. This disk file could be processed atl a lateru4 * date as part of charge-back accounting procedures. *-4     call "lib$show_timer" using timer_context giving sys_status.i *9 fini.      exit program.e *l end program user_logoff. *+ * Routine: USER_FINI * : * This routine is called by Tier3 when the server has been culled from 6 * the execution server pool due to inactivity timeout. *m7 * In the DEMO aplication there are no files to close or  databases to4 * disconnect from so the only image rundown activity performed here& * is the logging of server statistics. *- identification division. program-id.    user_fini.  data division. working-storage section.8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal.  *  linkage section. 01  demo_context._-     03  system_name                 pic x(8). 9     03  buffer_size                 pic 9(9)        comp. .     03  session_user                pic x(12).9     03  timer_context               pic 9(9)        comp. 9     03  session_count               pic 9(9)        comp. 9     03  message_count               pic 9(9)        comp. 9     03  lostlnk_count               pic 9(9)        comp. 9     03  persona_context             pic 9(9)        comp.  * 8 procedure division using demo_context giving ss$_normal. 00.$-     display "Execution server shutting down". ;     display "Number of associations formed: " session_count  with conversion.;     display "Number of messages received  : " message_count  with conversion.;     display "Number of client links broken: " lostlnk_count  with conversion.     exit program.o *  end program user_fini. *+ * Routine: USER_INT  * 8 * The user interrupt routine differs from the five other user action : * routines invoked by Tier3, in that it is called from AST level. * ; * In this example we merely increment a count of the number( associations5 * that were terminated abnormally. This count will be9 reported at image  * exit.l *- identification division. program-id.    user_int. data division. working-storage section.8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal.u, 01  link_lost                       pic x(1) value   x"01". *  linkage section. 01  demo_context. -     03  system_name                 pic x(8).n9     03  buffer_size                 pic 9(9)        comp. .     03  session_user                pic x(12).9     03  timer_context               pic 9(9)        comp.s9     03  session_count               pic 9(9)        comp. 9     03  message_count               pic 9(9)        comp. 9     03  lostlnk_count               pic 9(9)        comp.l9     03  persona_context             pic 9(9)        comp.  *r. 01  interrupt_msg                   pic x(16). *59 01  interrupt_type                  pic 9(9)        comp.e     88  system_msg$ value   external        t3$k_system.     88  user_msg" value   external        t3$k_user. * ) procedure division using    demo_context, *                             interrupt_msg,*                             interrupt_type'                   giving    ss$_normal.. 00.  *+6 * The client program in the DEMO example does not send interrupts, 9 * therefore the only interrupt that this routine needs tou	 cater fora8 * is that of link disconnection notification sent by the
 communication9	 * server.  * 3 * The Interrupt_Type field with contain T3$K_SYSTEMe indicating that 6 * the message is from the communication server and the
 first byte ofu; * the interrupt message will contain the value 1 indicating3
 that it is9 * a link disconnection message. Currently bytes 2 thru 16 
 are unused; * for Tier3 interrupts, and link disconnection notificatione is the onlye" * interrupt that is sent by Tier3. * 5 * Note: The maximum message size for TCP/IP interrupt  messages is 1 byte. 9 *       This is a network transport restriction and not a  TIER3 restriction. *-6     if (system_msg and interrupt_msg(1:1) = link_lost)"             add 1 to lostlnk_count3             display "Link to client has been lost"._       exit program.i *9 end program user_int.  *+ * Routine: exit_handler. *r: * This routine is application specific and not required by Tier3. *h3 * For the DEMO example there are no special cleanupm
 procedures9 * required but we'll interogate the exit status for error9 loggingv * purposes.  *$9 * VMS won't let a new persona to survive after image exitg so no $ * special cleanup check is required. *- identification division. program-id.    exit_handler. data division. working-storage section.8 01  t3$_nocomsrv                    pic s9(9)       comp% value   external        t3$_nocomsrv. 8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal.a linkage section.9 01  exit_status                     pic s9(9)       comp. % procedure division using exit_status.b 00.u.     display "In exit handler - " no advancing.     evaluate        exit_statusa3             when    ss$_normal      display "Normalc rundown. Everything is OK"7             when    t3$_nocomsrv    display "Can't find  Tier3 communication server" 5             when    other           if exit_status is  failureo9                                             display "This ) will bring down the communication server"n3                                     else    display50 "Problem, but another server will take my place"*                                     end-if     end-evaluate.e       exit program._ *e end program exit_handler.o     Build Routine:-n   ! < ************************************************************ ************************ !1 *u                        *8 !*         COPYRIGHT (c) 1994 BY TIER3 SOFTWARE LTD. ALL RIGHTS RESERVED.           * !  *_                        *; !*    THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE  USED AND COPIED ONLY    *n: !*    IN ACCORDANCE  WITH THE TERMS AND CONDITIONS OF SUCH LICENSE AND  WITH THE    *9 !*    THE INCLUSION  OF THE ABOVE COPYRIGHT NOTICE.  THIS9 SOFTWARE  OR ANY OTHER    *_8 !*    COPIES  THEREOF MAY NOT  BE PROVIDED  OR OTHERWISE MADE AVAILABLE  TO  ANY    *: !*    OTHER  PERSON.  NO  TITLE TO  AND OWNERSHIP  OF  THE SOFTWARE  IS  HEREBY    *( !* TRANSFERRED.                   *  !i *(                        *6 !*    THE INFORMATION  IN THIS SOFTWARE  IS SUBJECT TO CHANGE WITHOUT NOTICE AND    *6 !*    SHOULD NOT BE CONSTRUED AS A COMMITMENT BY TIER3 SOFTWARE LTD.                * !w *t                        * !(< ************************************************************ ************************ $! $! Procedure: BUILD_DEMO $!; $! This command procedure builds and installs the DEMO_UARS  shareable image 7 $! for the Tier3 DEMO example. After this procedure hasn been run successfully 6 $! the DEMO application can be registered in the Tier3 configuration file.e $! $   SAY := WRITE SYS$OUTPUT2  $   REQD_PRIVS = "CMKRNL,SYSNAM"% $   PREV_PRIVS = F$SETPRV(REQD_PRIVS)e $   ON ERROR THEN GOTO FINI  $   ON CONTROL_Y THEN GOTO FINIg1 $   IF F$PRIVILEGE(REQD_PRIVS) THEN GOTO BUILD_IT37 $   SAY "You need (CMKRNL,SYSNAM) privilege to run this 
 command file"t
 $   GOTO FINI  $!
 $BUILD_IT: $!8 $! Compile the source files. P1 is checked to see wheter debug is required.% $   IF P1 .EQS. "Y" .OR. P1 .EQS. "y"  $   THEN5 $       COBOL/LIST/DEBUG/CONDITIONALS=D DEMO_UARS.COBe $       LINK_QUAL = "/DEBUG" $   ELSE  $       COBOL/LIST DEMO_UARS.COB $       LINK_QUAL = ""	 $   ENDIF  $! $   CREATE QUIDEF.MARm ;+: ; Some of the external references in DEMO_UARS.COB will be
 unresolved8 ; at link-time because the linker won't find them in the default system7 ; libraries. This macro file is needed to resolve thoset references.  ; 5 ; Note: This is not a Tier3 requirement. This file is  needed only because 9 ;       the DEMO User Access Routines need to talk to thed job controller, ;       and use the persona system services. ;-;                 .TITLE          GETQUI External symbols and  condition codese  &                 $QUIDEF         GLOBAL&                 $JBCMSGDEF      GLOBAL&                 $IMPDEF         GLOBAL    / PERSONA_CREATE_FLAGS==<IMP$M_ASSUME_DEFPRIV!  -i   IMP$M_ASSUME_DEFCLASS>  / PERSONA_ASSUME_FLAGS==<IMP$M_ASSUME_SECURITY! -e   IMP$M_ASSUME_JOB_WIDE! -<                                        IMP$M_ASSUME_ACCOUNT>                   .END ;o $   MACRO QUIDEF.MAR $!; $! We'll define the logical name LNK$LIBRARY to point to T3r
 $USER so that_4 $! the Tier3 system service library will be searched automatically. $!# $   DEFINE/USER LNK$LIBRARY T3$USERa $! $   LINK/SHARE'LINK_QUAL'a) DEMO_UARS.OBJ,QUIDEF.OBJ,SYS$INPUT/OPTIONt !g: ! Transfer Vectors were not used in the DEMO example so we
 need to forcet8 ! the linker to define the procedure entry masks for our User Actiont7 ! Routines as universal symbols. If not, Tier3 won't ber able to find them. ! 9 ! There are no EXTERNAL file connectors, database handlesr or working-e6 ! storage variables defined in the DEMO example, so no PSECT attributed9 ! modification is required to build this shareable image._ !r         UNIVERSAL=USER_INIT          UNIVERSAL=USER_LOGON         UNIVERSAL=USER_RECVo         UNIVERSAL=USER_LOGOFF          UNIVERSAL=USER_FINIp         UNIVERSAL=USER_INT $!9 $! Unless the resulting shareable image will be placed in_
 the SYS$SHAREe; $! directory, a trusted logical name needs to be defined so 
 that Tier37 $! can locate the shareable image at run-time. NB: this  requirement is# $! *not* enforced for DEBUG images.  $!; $! SYSNAM privilege is required to define a trusted logicalt name and8 $! CMKRNL privilege is required to install the shareable image. $!- $   UAR_SPEC = F$PARSE("DEMO_UARS.EXE") - ";" 0 $   DEFINE/SYSTEM/EXEC/NOLOG DEMO_UARS 'UAR_SPEC $! $   INSTALL := $INSTALL/COMMAND  $!3 $! In the following command the /SHARE qualifier isf required. The /OPEN ' $! and /HEADER qualifiers are optional.s $!1 $   IF F$FILE_ATTRIBUTES("DEMO_UARS.EXE","KNOWN") ; $   THEN        INSTALL REPLACE DEMO_UARS/OPEN/HEADER/SHARE ; $   ELSE        INSTALL ADD     DEMO_UARS/OPEN/HEADER/SHARE 	 $   ENDIF  $! $FINI:% $   PREV_PRIVS = F$SETPRV(PREV_PRIVS)  $   EXIT $!       * Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautifulr   ------------------------------   Date: 18 May 2000 14:36:05 GMT, From: bill@cs.scranton.edu (Bill Gunshannon)$ Subject: MicroVAX, MS and RD53 disks, Message-ID: <8g0v4l$18dt$1@info.cs.uofs.edu>  E Is there a utility in VMS that can format RD53/RD54 disks??  I have a F MicroVAXII which does not have the format command in the Monitor and IE have two disks I could use on the MicroVAX if I could only find a wayiF to format them.  I have an older version of VMS on TK50's that I could. install on this machine if this was an option.   bill   -- iJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   e   ------------------------------  % Date: Thu, 18 May 2000 12:00:29 -0500d% From: Chris Scheers <asi@airmail.net>$( Subject: Re: MicroVAX, MS and RD53 disksO Message-ID: <CC577F4442BA9DBA.B9DA315446B91F1A.CF3F1FA10EA3FDA6@lp.airnews.net>    Bill Gunshannon wrote: > G > Is there a utility in VMS that can format RD53/RD54 disks??  I have a H > MicroVAXII which does not have the format command in the Monitor and IG > have two disks I could use on the MicroVAX if I could only find a wayhH > to format them.  I have an older version of VMS on TK50's that I could0 > install on this machine if this was an option.  A You mention RD54s, so I assume that you have an RQDX3 controller.n  C To format on a MVII, you need a diagnostic tape that has the formatf" capability.  (Not all of them do.)  F If you can get access to a VAXstation 2000 (or MicroVAX 2000), you canH use that to format your RD53/RD54 disks.  The formatter code is built in to that machine.  C If you have an RQDX3 controller, you should then be able to use the A disks in the MVII.  (This does not work with a RQDX2 controller.)   
 Good luck!  ? PS: This all assumes that the disks really need to be low level B formatted.  If they have already been low level formatted for your? controller, the VMS command to put a file system on the disk isz INITIALIZE.   G ----------------------------------------------------------------------- $ Chris Scheers, Applied Synergy, Inc.  G 817-237-3360 (Voice)    817-237-3074 (Fax)    Internet: asi@airmail.nete   ------------------------------  % Date: Thu, 18 May 2000 11:43:04 -0400 1 From: "dgg@robbinsauto.com" <dgg@robbinsauto.com> " Subject: multia communication port3 Message-ID: <01BFC0BE.3B51D080.dgg@robbinsauto.com>_  D Hello out there. I hope that I may be guided in the right direction.  J I have OpenVMS 7.2 installed on a Multia and it boots up listing opa0: as  an unknow device.zE That is ok with me. I can use the VGA terminal to run commnands with t needing decwindows.oI Decwindows is another story. I cannot get a login window to come up. The "? issue I have is that I'm trying to get a VT320 to work off the uK communication port which is listed as tta0: It appears to work when I boot rH from it (that is until VMS forces ouput to opa0:). I've tried using the  following commands:s. SET TERMINAL TTA0:/DEVICE_TYPE=VT300/PERMANENTI (gives write error but set paramenters correctly, causes screen to blank   but no other functionality)e  0 SET TERMINAL TTA0:/SPEED=9600/ANSI_CRT/PERMANENT? (produces no errors, but gives no sign of life on the terminal)b  - Is there some special setup the Multia needs?    Dave   ------------------------------   Date: 18 May 2000 09:46:56 GMT* From: helbig@astro.rug.nl (Phillip Helbig)7 Subject: OpenVMS and Windows NT Integration for Dummies_. Message-ID: <8g0e6g$lil$1@info.service.rug.nl>  E I was somewhat surprised to find this, an AlphaServer bookmark and a iC signed (with a stamp) letter from Rich Marcello in my mailbox this C morning!   Who else got these?e   ------------------------------    Date: 18 May 2000 12:26:28 +0200* From: eplan@kapsch.net (Peter LANGSTOEGER); Subject: Re: OpenVMS and Windows NT Integration for Dummiesr* Message-ID: <3923c554$1@news.kapsch.co.at>  [ In article <8g0e6g$lil$1@info.service.rug.nl>, helbig@astro.rug.nl (Phillip Helbig) writes:eF >I was somewhat surprised to find this, an AlphaServer bookmark and a D >signed (with a stamp) letter from Rich Marcello in my mailbox this 	 >morning!  >x >Who else got these?  I Me. A week or two ago. But I still haven't found time to read the book...u -- .< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888 < FBFV/Information Services           E-mail  eplan@kapsch.netF <<< KAPSCH AG  Wagenseilgasse 1     PSImail PSI%(0232)281001141::EPLANH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"N "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998   ------------------------------  % Date: Thu, 18 May 2000 13:13:15 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>s; Subject: Re: OpenVMS and Windows NT Integration for Dummiese) Message-ID: <3923D04B.F20E550D@gtech.com>e   Peter LANGSTOEGER wrote:] > In article <8g0e6g$lil$1@info.service.rug.nl>, helbig@astro.rug.nl (Phillip Helbig) writes:sG > >I was somewhat surprised to find this, an AlphaServer bookmark and asE > >signed (with a stamp) letter from Rich Marcello in my mailbox thist > >morning!y > >t > >Who else got these? > K > Me. A week or two ago. But I still haven't found time to read the book...   7 I think several participants here has received a copy !e   But not me !  :-(    Arne   ------------------------------    Date: 18 May 2000 13:44:49 +0200* From: eplan@kapsch.net (Peter LANGSTOEGER); Subject: Re: OpenVMS and Windows NT Integration for Dummiesn* Message-ID: <3923d7b1$1@news.kapsch.co.at>  i In article <3923D04B.F20E550D@gtech.com>, Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> writes:s >Peter LANGSTOEGER wrote: ^ >> In article <8g0e6g$lil$1@info.service.rug.nl>, helbig@astro.rug.nl (Phillip Helbig) writes:H >> >I was somewhat surprised to find this, an AlphaServer bookmark and aF >> >signed (with a stamp) letter from Rich Marcello in my mailbox this >> >morning! >> > >> >Who else got these?  >> tL >> Me. A week or two ago. But I still haven't found time to read the book... >e8 >I think several participants here has received a copy ! >e >But not me !  :-(  < Call/Mail Susan Skonetski (sp?) or your local VMS Ambassador   -- d< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888 < FBFV/Information Services           E-mail  eplan@kapsch.netF <<< KAPSCH AG  Wagenseilgasse 1     PSImail PSI%(0232)281001141::EPLANH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"N "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998   ------------------------------  % Date: Thu, 18 May 2000 12:28:36 -0600 1 From: Glen Martin <GLENMARK@utxvms.cc.utexas.edu> ; Subject: Re: OpenVMS and Windows NT Integration for Dummies 4 Message-ID: <3923E1F4.19808CD3@utxvms.cc.utexas.edu>   Peter LANGSTOEGER wrote:K > Me. A week or two ago. But I still haven't found time to read the book...i  F It appears to be primarily marketing material. Very short on technical content.  $ Marketing? VMS? Who would've though?   Glen   ------------------------------  # Date: Thu, 18 May 2000 14:03:21 GMT % From: jlsue <jlsuexxxz@dialupnet.com> & Subject: Re: the latest billybox virus8 Message-ID: <6rt7is86g6b0fj944jkq0gi6j0391ruup3@4ax.com>  / On Wed, 17 May 2000 15:18:03 +0200, Arne Vajhjs <arne.vajhoej@gtech.com> wrote:   
 >jlsue wrote:kG >> Well, now remember, to get on the system you'd need a valid account. F >> After that, just doing SHOW USERS would get you all the information >> you need. >l >????  >n: >Not all users are logged in. In theese client/server days> >it is often only the system manager that logs in. Other users >useJ >browser/PathWorks/Windoes-email-client/windows-special-client-application >etc. to access the VMS system.  >k >Arne   D Possibly, but most of the ways that users/applications would use VMSE authentication (which would require entries in SYSUAF and RIGHTSLIST) > would result in some process on the system running under their6 username.  If not SHOW USERS, then SHOW SYSTEM/FULL.    F On the other hand, if it was a client-server (non-interactive) system,A then who would have access to the system services to scan through( RIGHTSLIST?p  A If you're logged-on as an interactive user, over time (probably a3A relatively short period of time) you could have many of the validrD users, without writing code to find them in the RIGHTSLIST.DAT file.@ My point being that this isn't *that* much of a security breach.  1 Not speaking for anyone, certainly not DEC/Compaqe- (get rid of the xxxx in my address to e-mail)u   ------------------------------  % Date: Thu, 18 May 2000 15:32:08 +0200 2 From: Bernard Schluep <Bernard.Schluep@azisoft.ch>" Subject: Re: UCX Printing Problems* Message-ID: <3923F0D8.CC7514AD@azisoft.ch>  0 Please send the result of the    show queue/full   z wrote:  A > We have traditionaly printed using LAT but have recently set upi? > printing using UCX (LPR).  I used the ucx$lprsetup program tor@ > set up the devices and all seems to be working well.  The only? > problem I have is that after every print job submitted to the A > queue I get an extra page showing the user name and host serveri? > name.  I would like to stop this last page from printing.  We ? > are using HP Jet Direct cards and I think they are configuredcA > correctly.  I think there is a setting on the queue that I neede) > to change but I do not know what it is.r >   > Any help would be appreciated. >iN > * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *I > The fastest and easiest way to search and participate in Usenet - Free!c   ------------------------------  % Date: Thu, 18 May 2000 06:18:58 -0700r+ From: z <jasakNOjaSPAM@hotmail.com.invalid>n Subject: UCX Printing Problems9 Message-ID: <0dd24fe8.ab6d10ad@usw-ex0105-037.remarq.com>h  ? We have traditionaly printed using LAT but have recently set up = printing using UCX (LPR).  I used the ucx$lprsetup program tog> set up the devices and all seems to be working well.  The only= problem I have is that after every print job submitted to the.? queue I get an extra page showing the user name and host servera= name.  I would like to stop this last page from printing.  We = are using HP Jet Direct cards and I think they are configuredo? correctly.  I think there is a setting on the queue that I need ' to change but I do not know what it is.k   Any help would be appreciated.    L * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *G The fastest and easiest way to search and participate in Usenet - Free!x   ------------------------------  % Date: Thu, 18 May 2000 06:39:08 -0700E+ From: z <jasakNOjaSPAM@hotmail.com.invalid>o" Subject: Re: UCX Printing Problems9 Message-ID: <1022653b.b0b013e6@usw-ex0105-037.remarq.com>   " Here is the information requested.    $sh queue icsd1q /fu < Server queue ICSD1Q, idle, on STGAX1::, mounted form DEFAULT?   /BASE_PRIORITY=8 /DEFAULT=(FEED,FORM=DEFAULT) /OWNER=[SYSTEM]o6   /PROCESSOR=UCX$LPD_SMB /PROTECTION=(S:M,O:D,G:R,W:S) $   L * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *G The fastest and easiest way to search and participate in Usenet - Free!*   ------------------------------  % Date: Thu, 18 May 2000 10:37:36 -0400 & From: Ken Robinson <ksrobin@erenj.com>" Subject: Re: UCX Printing Problems4 Message-ID: <200005181440.KAA07624@clmail.erenj.com>  H When you set up the LPD queues, you were asked the question "Do you wantI the queue to default to print flag pages [y] :" and you probably took theTK default. Answering "yes" to this question, gives the result you see. To fixOD your problem, the "/flag" qualifier has to be removed from the queue3 definition, both on the live system and in the fileB" "sys$startup:ucx$lpd_startup.com".   Ken Robinson ksrobin@erenj.com   
 ----------4 > From: Bernard Schluep <Bernard.Schluep@azisoft.ch> > To: Info-VAX@MVB.SAIC.COM $ > Subject: Re: UCX Printing Problems& > Date: Thursday, May 18, 2000 9:32 AM > 2 > Please send the result of the    show queue/full > 
 > z wrote: > C > > We have traditionaly printed using LAT but have recently set up A > > printing using UCX (LPR).  I used the ucx$lprsetup program to*B > > set up the devices and all seems to be working well.  The onlyA > > problem I have is that after every print job submitted to the!C > > queue I get an extra page showing the user name and host servereA > > name.  I would like to stop this last page from printing.  WeoA > > are using HP Jet Direct cards and I think they are configuredSC > > correctly.  I think there is a setting on the queue that I needR+ > > to change but I do not know what it is.O > >g" > > Any help would be appreciated. > >OF > > * Sent from RemarQ http://www.remarq.com The Internet's Discussion	 Network *tK > > The fastest and easiest way to search and participate in Usenet - Free!k   ------------------------------  % Date: Thu, 18 May 2000 08:45:30 -0700 0 From: "William S. LaCounte" <vmsmanager@ups.edu>" Subject: Re: UCX Printing Problems# Message-ID: <39241019.2620@ups.edu>I  D You may also have to telnet to the printer's JetDirect card, get theG current configuration and see if banner is enabled. If this is the case C you will get the 2 line printout after every job. To disable banner ? simple enter "banner:0", save the configuration, and then exit.    Bill   ------------------------------  % Date: Thu, 18 May 2000 08:59:38 +0300e% From: Gabriel Sterk <gabi@aipm.co.il>e5 Subject: Re: UCX Printing to external printer servers 2 Message-ID: <000601bfc08e$408f85e0$2c46bf10@manai>  < What does the 34 stand for in the DEFINE command? (We use 1)  
 Gabriel Sterk      -----Original Message-----0 From: Jerry Leslie [mailto:leslie@clio.rice.edu]  @ We have been able to use H-P JetDirect print servers, which comeA in one-port (9100) or three-port (9100, 9101, 9102) models; e.g.:A  6    $ DEFINE/SYSTEM UCX$TELNETSYM_SUPRESS_FORMFEEDS  34@    $ INIT/QUE/START/ON="138.53.135.5:9100"/PROC=UCX$TELNETSYM/ -/      DEFAULT=(NOBURST,NOFLAG,NOTRAIL,NOFEED)/ -!/      DEVICE=PRINTER /RECORD_BLOCKING  SYS$PRINT   4 --Jerry Leslie     (my opinions are strictly my own)   ------------------------------  % Date: Thu, 18 May 2000 13:36:03 +0100 , From: "pete.walker" <pete.walker@virgin.net>5 Subject: Re: UCX Printing to external printer serversV@ Message-ID: <hwRU4.4281$J06.54143@news6-win.server.ntlworld.com>  L Thanks for the help - I'm pleased to say that it was not an error on my partI (for once) but a firmware issue in the D-Link DP301 printer servers.  Nowh sorted.o   Regardsi   Pete Walkerd   ------------------------------   Date: 18 May 2000 16:57:28 GMT) From: leslie@clio.rice.edu (Jerry Leslie)i5 Subject: Re: UCX Printing to external printer serversr' Message-ID: <8g17do$d7b$1@joe.rice.edu>N  & Gabriel Sterk (gabi@aipm.co.il) wrote:> : What does the 34 stand for in the DEFINE command? (We use 1)   : Gabriel SterkR     : -----Original Message-----2 : From: Jerry Leslie [mailto:leslie@clio.rice.edu]  B : We have been able to use H-P JetDirect print servers, which comeC : in one-port (9100) or three-port (9100, 9101, 9102) models; e.g.:   8 :    $ DEFINE/SYSTEM UCX$TELNETSYM_SUPRESS_FORMFEEDS  34B :    $ INIT/QUE/START/ON="138.53.135.5:9100"/PROC=UCX$TELNETSYM/ -1 :      DEFAULT=(NOBURST,NOFLAG,NOTRAIL,NOFEED)/ -a1 :      DEVICE=PRINTER /RECORD_BLOCKING  SYS$PRINTR  6 : --Jerry Leslie     (my opinions are strictly my own)    E I think it suppresses an initial form-feed in the file to be printed,nD but I'm not sure where I got this information.  There is one articleG available from DejaNews that mentions it, saying it should be 35 or 34,"! to suppress an initial form-feed.   4 --Jerry Leslie     (my opinions are strictly my own)   ------------------------------  # Date: Thu, 18 May 2000 15:25:41 GMTS& From: winfried.bergmann@frankendata.de Subject: Ultrix for mVax3100 ?/ Message-ID: <VXTU4.74$s07.24452157@news.odn.de>t   Hello,J I have an old mVax 3100 currently running OpenVMS 7.x. I'd like to replaceH this with Ultrix (I'm not interrested in NetBSD or Linux) for nostalgic I reasons. Where can I get Ultrix for this machine (version not important, s maybe 4.5) ?   	thanx	 	Winfried.   --  J ==========================================================================<                                          | Winfried BergmannD email: winfried.bergmann@frankendata.de  | FrankenData GmbH & Co. KGC Tel  : +49 9131 7704-26                  | Am Weichselgarten 11-13 t; Fax  : +49 9131 7704-44                  | D-91058 Erlangeni   ------------------------------  % Date: Thu, 18 May 2000 11:01:42 -0400h From: Keith <kmannist@ford.com> ! Subject: Re: VAX servers for salef( Message-ID: <392405D6.FDB22626@ford.com>  ! Where are these system located?  l     Nate Johnson wrote:e > F > I have three VAX servers for sale right now.  If you are interested, > please let me know.a > 	 > thanks,$ > nate > 
 > 1)DEC R400X  > ( > Bus details: Q-bus - 12 slots all Q/CD) > Drive bays: four full height 5.25 bays.s > One with front access. > Used in: VAX 4000 M300  > image (VAX 4000/300 in a BA440L > enclosure):http://www.netbsd.org/images/machines/vax/vax4000-300-ba440.jpg > selling for $50.00 > - > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o >  > 2)DEC VAX 4000-500 > % > 3 bays, DAT drive. lots of cabling.M* > manual:EK-KA670-TM Nickname: Omega/N (?)  > CPU: KA681 '69D' (NVAX) @83MHz > Bus: Q-bus, DSSI# > Interfaces: ethernet on CPU boardt
 > Memory: (?)f > Introduced: 1991 or lateri > Enclosure: BA440 > selling for $50.00 > - > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-s >  > 3)DEC ChannelServer II >  > Chassis is mostly emptyt > selling for $20.00 > - > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-a >  > 4)DEC ChannelServer II >  > Chassis is mostly empty  > selling for $20.00 > -- > <>      nate johnson      <> > <>  mailto:nate@kiva.net  <>   ------------------------------  # Date: Thu, 18 May 2000 07:25:23 GMT 0 From: carlini@true.lkg.dec.com (Antonio Carlini)1 Subject: Re: Vaxstation graphics to SVGA monitor?p* Message-ID: <8g059s$8mf@usenet.pa.dec.com>  ^ In article <3922B9CD.24FF1D8C@trailing-edge.com>, Tim Shoppa <shoppa@trailing-edge.com> wrote:  E >even provide the full sync range specs.  So I'm specifically lookingnC >for an answer like "a Yoyodyne GX-16 monitor works and you can buy11 >new ones today from John Bigboote on Planet 10".c   More data points for you:u  O The Iiyama Vision Master Pro 17" monitor has both BNC and VGA inputs and takes m< sync-on-green. Works happily with a VAXstation 3100 M76/SPX.  N The PCXAV-WZ monitor currently on my desk is happily accepting input from the  VAXstation 4000-90 with SPXgt.   Antoniot  I Antonio Carlini                            Mail: carlini@true.lkg.dec.como# DECnet-Plus for OpenVMS Engineeringo6 COMPAQ                                     Reading, UK   ------------------------------  / Date: Thu, 18 May 2000 10:00:31 +0200 (MET DST)a& From: Rudolf Wingert <win@fom.fgan.de>1 Subject: Re: Vaxstation graphics to SVGA monitor?./ Message-ID: <200005180701.JAA10385@fom.fgan.de>    Hello,  C we do have a lot of new one multisync monitors. All seems to be ok.sB We have tested the PCXAV-WZ, VRC21-WZ, P110 and P1100. All do workD good. We do use them also to share a VAXStation or AlphaStation with# a PC (all of them have two inputs).e   Regards Rudolf Wingert   ------------------------------   Date: 18 May 2000 14:33:32 GMT+ From: Jeff Shirley <slinkerx@xprimenet.com>m1 Subject: Re: Vaxstation graphics to SVGA monitor?e. Message-ID: <8g0uvs$241$1@nnrp02.primenet.com>  , Tim Shoppa <shoppa@trailing-edge.com> wrote:B : A question that's a bit different than the typical "How do I use : my old VR299 on a PC clone":  D : Does anyone here have any experience hooking VAXstations (anythingC : from VS2000's to 3100's with SPX or GPX graphics to 4000VLC's and2 : 4000/60's)J : to a modern multisync SVGA monitor?  It'd be nice if the monitor accepts? : sync-on-green, but if not I'd be willing to build my own sync J : separator.  And obviously the multisync SVGA monitor will have to handleH : the scan rates from the Vaxstation(s) - but unfortunately I'm having a : hardI : time getting scan rate details on many modern commercial SVGA monitors. F : The specs usually list the supported resolutions, but not the actual
 : scan rates.u  B : Any leads?  Words from the wise?  I have too many customers withD : dying VR160's, VR190's, VR290's, VR299's, etc., who really need toB : keep their screens running reliably, and it'd be a big win if weD : could just plug in a nice modern (maybe even generic) SVGA monitorE : when their current monitor dies.  (Notice I said "when", not "if"!)t   Hi Tim.l  M I was faced with the same problem when my cat Bucky camped on the VR290 I got9; from you.  He blocked the air vents and it overheated.  :^(0  K I bought a 19" Iiyama Visionmaster 450.  It has separate BNCs (as well as asM VGA connector), and does sync-on-green, composite, and separate H/V sync.  It2N works great as a replacement for VR290/299s on VS3100 or uVII/GPX machines, asJ well as for VRT19-HAs on DECstations or DEC 3000s.  It also works with SunL SPARC or IBM RS/6000 systems.  I have not found anything it will not sync up
 to, actually.)  L Of course a VR290 is closer to a 21" monitor in PC-speak, so I lost a littleK screen real estate, but after seeing the amazing sharpness of the Iiyama, Ia did not mind a bit.h  J They run anywhere from $450 to $500 on the net these days.  It is the onlyL monitor on my desk these days; I just switch inputs when I move from the VAX to the Alpha or the Linux box.  M The other monitor that looked attractive at the time was the Viewsonic PS790,D7 but I think recent models have lost the BNC connectors.F   Jeff.t -- oK NOTICE TO BULK EMAILERS:  I am really getting tired of your junk email.  ItLM costs me both time and money.  Send spam to me, and I WILL GET YOUR OPERATIONt6 SHUT DOWN.  So far, 47 web sites deleted.  Who's next?  7                     Jeff Shirley slinkerx@xprimenet.comiG           Remove the "x" characters from my email address when replyingnG          ** UNSOLICITED COMMERCIAL/PROMOTIONAL EMAIL IS NOT ACCEPTED **    ------------------------------   Date: 18 May 2000 16:57:11 GMT3 From: du651@FreeNet.Carleton.CA (Joseph Ballantyne)t0 Subject: VMS 5.2 DCL treats &symbol unexpectedly/ Message-ID: <8g17d7$76j$1@freenet9.carleton.ca>A  C I originally had a need to SEARCH for the DEL (%X7F) character in amC    file, and that worked as expected.  Then the application changed C    slightly, and I needed to SEARCH for two consecutive DELs.  Thati%    turned up an apparent DCL anomaly.EF I have no easy way to test-run this file on a more modern VMS version.9    There is no SPR or other Compaq support on the system.2D Because DCL expands apostrophes before logging the command line, andH    because DEL has no graphic, I have lightly edited the following batchG    log.  Commands that included apostrophes have trailing comments with2A    the apostrophes shown as plus signs.  DELs are shown as stars. >    (There is no apparent significance to the %X7F value of theG    symbol--that just happens to be the value I needed when I discoveredn    the anomaly.)G The test data file JUNK.0 contains four lines, with 0 to 3 DELs between-    the parens.( $ show syst ! many output lines omitted.G VAX/VMS V5.2  on node V7  18-MAY-2000 14:56:14.49   Uptime  25 00:19:03 7 $ anal/imag sys$system:dcl ! many output lines omitted. M Analyze Image                                18-MAY-2000 14:56:15.66   Page 1o SYS$COMMON:[SYSEXE]DCL.EXE;1(         Image Identification Information!                 image name: "DCL"t1                 image file identification: "X-20"f7                 link date/time: 10-MAY-1989 18:00:50.77e.                 linker identification: "05-05"         Patch Informationg2                 There are no patches at this time.! The analysis uncovered NO errors.c $ x7f[0,8]=%x7fa $ sear junk.0 &x7f has 1: (<DEL>) has 2: (<DEL><DEL>)s has 3: (<DEL><DEL><DEL>) $ sear junk.0 &x7f&x7fN %DCL-W-VALREQ, missing qualifier or keyword value - supply all required values1 $ sear junk.0 "**" ! $ sear junk.0 "++x7f+++x7f+"r has 2: (<DEL><DEL>)s has 3: (<DEL><DEL><DEL>)+ $ sear junk.0 ** ! $ sear junk.0 +x7f++x7f+n has 2: (<DEL><DEL>)- has 3: (<DEL><DEL><DEL>)- $ sear junk.0 &x7f* ! $ sear junk.0 &x7f+x7f+mN %DCL-W-VALREQ, missing qualifier or keyword value - supply all required values- $ sear junk.0 *&x7f ! $ sear junk.0 +x7f+&x7ft' %SEARCH-I-NOMATCHES, no strings matchedh $ defi &x7f junk $ show tran &x7f!   * = "JUNK"  (LNM$PROCESS_TABLE)T $ defi &x7f&x7f junkN %DCL-W-VALREQ, missing qualifier or keyword value - supply all required values- $ defi "**" junk ! $ defi "++x7f+++x7f+" junki $ assi junk &x7f9 %DCL-I-SUPERSEDE, previous value of * has been supersededa- $ assi junk "**" ! $ assi junk "++x7f+++x7f+"B: %DCL-I-SUPERSEDE, previous value of ** has been superseded $ deas &x7fD $ deas &x7f&x7f4N %DCL-W-VALREQ, missing qualifier or keyword value - supply all required values# $ deas "**" ! $ deas "++x7f+++x7f+"g $ defi junk &x7f $ defi junk &x7f&x7f@ %DCL-W-NULFIL, missing or invalid file specification - respecify $ requ &x7f&x7faN %DCL-W-VALREQ, missing qualifier or keyword value - supply all required valuesF So--how have I misunderstood the effect of ampersand-controlled symbolF    expansion?  If adjoining a &symbol with a non-blank string preventsB    recognition of the symbol, I would expect the &symbol to eitherE    remain literally in the command (which apparently happens when thetD    non-blank string precedes the &symbol), or to be replaced with anB    empty string, and the command to be diagnosed accordingly.  Or,:    alternatively, UNDSYM.  I don't understand the VALREQs.   ------------------------------   Date: 18 May 2000 17:40:52 GMT8 From: hammond@not@peek.ppb.cpqcorp.net (Charlie Hammond)4 Subject: Re: VMS 5.2 DCL treats &symbol unexpectedly6 Message-ID: <8g19v4$ls0$1@mailint03.im.hou.compaq.com>  0 In article <8g17d7$76j$1@freenet9.carleton.ca>, 5 du651@FreeNet.Carleton.CA (Joseph Ballantyne) writes:g  D >I originally had a need to SEARCH for the DEL (%X7F) character in aD >   file, and that worked as expected.  Then the application changedD >   slightly, and I needed to SEARCH for two consecutive DELs.  That& >   turned up an apparent DCL anomaly. ..  < It appears that the & symbol substitution is not terminated.> i.e. the string "&x7f&x7f" is being parsed as if the first "&"< was forcin symbol substitution for the symbole "x7f&x7f" --  which is not defined.o  C Unfortunately, I do not know of any way to terminate & substitutionQ6 except with a space, which will not work in this case.  G Unless there is a reason to use ampersand (&) instead of apostrophy (')xA for sybmol substitution -- and there probably is not -- try this:0       $ sear junk.0 'x7f''x7f'     C Alternatively, build a symbol that contains the value "<del><del>".2          $ x7f[0,8]=%x7f3     $ x7f_2 := x7f + x7f     ! Then either of these should work:i          $ sear junk.0 'x7f_2'i     $ sear junk.0 &x7f_2  E Hint: Unless you have a real reason and know that you need to use theT5 & form of symbol substitution, always use the ' form.,       --  K     Charlie Hammond -- Compaq Computer Corporation -- Pompano Beach  FL USA F          (hammond@peek.ppb.cpqcorp.net -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------  + Date: Thu, 18 May 2000 05:38:57 -0500 (EST)s1 From: "Robert J. Slover" <slover@Rose-Hulman.Edu>  Subject: Re: VMS File ModessW Message-ID: <Pine.LNX.3.96.1000518013520.11836A-100000@rocinante.admin.rose-hulman.edu>:   Clayton,  7 I'm familiar with your products, in about a week one of,5 them will print my next payroll check. (Assuming the /4 'E-Visions' in your address in the first post is the same E-Visions I know).s  : I wanted to address your remark regarding the 'cumbersome': VMS file attributes.  While unix is not 'plagued' by this,9 it can't take advantage of it either.  VMS files provide B; for many different tuning parameters, support indexes, etc,r9 and in general enjoy many of the benefits of databases in 8 their own right.  This might not matter much when you're7 just wanting to write a spoolable binary file, but I'd  : submit that this is a degenerate case of creating a binary: file anyway.  The only time it has been an issue for me in: writing something to run on VMS and on Unix (not something; I get to do much) is in Perl, where the extra functionalityh9 of fopen() isn't there (AFAIK).  In this case, I create ao9 dummy template file with the attributes I want, then callD7 system() to do a DCL copy of the template to the targetl6 filename, then I open it.  This preserves the RMS file6 attributes I want.  Be glad DEC C at least lets you do this cleanly...b   --Robert      . On Thu, 18 May 2000 confusu@my-deja.com wrote:  
 > Dirk and JFi > E > Thank you both for your replies.  I must say again that VMS is verypH > foreign to me.  The idea that there are so many different file formatsE > at the OS level is an idea that is a tad cumbersome.  This does notdF > plague a UNIX or Windows-based environment.  I am quite used to (andC > happy with) creating a file with "w" access and having it work nog > matter what the circumstance.  > I > I figured the Queue was having problems with the file format.  The besttH > solution however would be to not have the user modify their queue.  WeG > would rather correct the file-format than have each user create a new 4 > queue just to handle our "incorrect" binary files. > E > All examples I've ever seen on the newsgroups, regarding fopen() invE > VMS, have always used a simple "w" access to create files.  AnotherhE > person on my team was able to track down the following solution.  I 9 > would like to know if you have any further suggestions.i > 2 >    fopen("filename", "w", "rat=none", "rfm=fix",( >       "mrs=512", "ctx=stm", "mbc=20"); > @ > Our files now print correctly.  The above code is bracketed in? > #ifdef ... #endif for a VMS OS and will not be used for otherN > environments (of course).$ > " > Thanks again for your responses, > - ClaytonF >  > ( > Sent via Deja.com http://www.deja.com/ > Before you buy.  >    ------------------------------  % Date: Thu, 18 May 2000 11:06:51 -0400 " From: Dan Sugalski <dan@sidhe.org> Subject: Re: VMS File Modest8 Message-ID: <4.3.1.0.20000518110543.02222e50@24.8.96.48>  2 At 05:38 AM 5/18/00 -0500, Robert J. Slover wrote:- >The only time it has been an issue for me ine; >writing something to run on VMS and on Unix (not somethingt< >I get to do much) is in Perl, where the extra functionality  >of fopen() isn't there (AFAIK).  L Turns out not to be the case--check out the docs for the VMS::Stdio module, J packaged with all versions of perl since 5.003 (I think) and installed by & default with all versions since 5.005.  H You get pretty much full access to all the twiddly bits you can pass to 
 fopen() in C.      					Dan  L ----------------------------------------------------------------------------L Dan Sugalski                          General and VMS-specific perl training
 dan@sidhe.orgJ>                                       Mail me for more details   ------------------------------  % Date: Thu, 18 May 2000 11:09:27 -0400S" From: Dan Sugalski <dan@sidhe.org> Subject: Re: VMS File Modes98 Message-ID: <4.3.1.0.20000518110431.02222840@24.8.96.48>  6 At 09:37 PM 5/17/00 +0000, carends@evisions.com wrote:8 >The program is written in C and creates the file using: >    fopen("filename", "w");  >This file is a binary PCL file.  L The problem is that when the C RTL creates a new file this way, it's marked J as a type Stream_LF. VMS knows that this is a record-oriented file, and a J record in a VMS file can't be larger than 32K. You likely have a chunk of J data larger than that without a linefeed in it, so anything that uses the K VMS I/O system will throw an error because the file is, strictly speaking, :L bad. (Whether you should be allowed to write a file like this is a separate 1 issue, and we Just Won't Go There right now... :)n  J Change the attributes to make it either unformatted or a plain block file J and you'll be fine. (I read the other postings and I think you've already H done that--if not I'll dig up the magic incantation you need to pass to  fopen() to do this)=   					Dan  L ----------------------------------------------------------------------------L Dan Sugalski                          General and VMS-specific perl training
 dan@sidhe.org >                                       Mail me for more details   ------------------------------  % Date: Thu, 18 May 2000 01:52:46 -0400- From: "dls2" <dls2@Lehigh.EDU>  Subject: Re: VMS on the desktop?- Message-ID: <8g00h1$gfo@fidoii.CC.Lehigh.EDU>X  8 "David J. Dachtera" <djesys.nospam@earthlink.net> wrote:
 > dls2 wrote:h6 > > Aren't HSC (CI), HSJ (CI), HSD (DSSI), HSZ (SCSI),8 > > & HSG (FC) just designations for device controllers? >r? > As applied to these devices, the term "cluster controller" isEA > inappropriate. They "control" disk arrays, and can be used in as) > clustered or non-clustered environment.f  6 "Device controllers," as in "SCSI device controllers."  - > > Do the names have any particular meaning?g >aJ > Originally, "H.S.C." stood for "Hierarchical Storage Controller". As forI > the others, the third character now designates the transport (physical)sD > medium: HSJ is CI, HSD is DSSI, HSZ is SCSI, HSG is "glass" (read:	 > fibre).:  5 How does the J in HSJ come to represent CI?  The D inc5 HSD obviously represents the start of DSSI.  The Z ind7 HSZ sounds similar to the second syllable of SCSI.  And0; the G from HSG is also the first letter of glass, as you've) been kind enough to point out.  + > > What are CI and DSSI?  Do they see much * > > use relative to SCSI and FibreChannel? > G > Well, DSSI is officially "deprecated", to use a UN*Xly term. It was aoE > sort of DEC-proprietary, SCSI-like interface. Throughput is roughlynA > equivalent to SCSI-1, according to Hoff. CI is a co-axial loop,0F > dual-path arrangement with automatic failover should one path (TX/RXF > pair of coax. cables) become unusable. In practice, it actually usesD > both paths, if I'm not too badly mistaken. I'll assume that you'reC > familiar with SCSI and FC/fabric (note that OpenVMS supports onlysG > fabric, not FCAL, again if my info. is correct - and it may very welly
 > not be).  2 I am familiar enough with SCSI and FC to know what1 they represent.  I use SCSI, myself, actually. :)r  / > > Would the workstations likely be clustered?h >bF > With each other? You do sometimes see this, though the usefulness isI > debatable since the cluster communications medium for both SCS and MSCPp. > traffic would be the ethernet (10/100Mbits).   What are SCS and MSCP?  7 Are ethernet and fast ethernet really so inadequate fori1 relaying (SCS & MSCP?) messages between machines?r  & How, then, are server clusters linked?  * > > Would the servers likely be clustered?3 > > Would the workstations and servers be clusteredD& > > together, or clustered seperately? >>E > The servers with each other, probably. With the workstations, you'd0 > likely see it both ways.  8 What is meant by "both ways."  That the workstations and; servers may be clustered together, but workstations are notW6 clustered among themselves?  If workstations are being= clustered with servers, then aren't they also being clustered  with other workstations?  8 > > The UAF for a cluster would have to be accessible to > > all cluster nodes. > >r6 > > But what do you mean that "*sometimes*, nodes have9 > > local UAFs?"  Do you mean that cluster nodes may have$ > > node specific UAFs?> > J > Yes. This is sometimes necessary, for certain reasons. Normally, cluster  > nodes will share a common UAF.  # Where is this common UAF preserved?   8 > > Yes, I am talking about disk images; having a single8 > > disk, or boot, image propagated to multiple machines> > > of a single configuration, with, or without, local drives. >t > Again, possible. >e6 > > Does VMS support boot serving for machines without > > local disks? >sG > Yes. There is also a discontinued device known as an InfoServer which  > serves a similar purpose.   , Supposedly it also allowed for CD-R burning?  ( > > Does VMS support serving disk images, > > at bootup for machines with local disks? > I > Well, I suppose you could. However, with system disks reaching the 4 totG > 8 GB range, I can't imagine a workstation having enough memory for anhH > 8GB ramdisk AND a running OpenVMS system - unless you're talking aboutJ > some "magic" outside of my experience (very possible and highly likely).  , Why would such a large ramdisk be necessary?/ I was thinking that the served disk image wouldN. be written to disk, in fragments, as received.   <snip>H > So, IMNSHO, it's fairly safe to say that while total death for OVMS isD > not on the visible horizon, within five years OVMS will become the > "PICK" of the 21st century.I  3 What is PICK?  A lost & forgotten operating system?   ? > > Are the OpenVMS file and print services similar to those ofr > > Un*x, or different, still? >  > See http://www.samba.org/s  1 Samba is what MS Windows uses.  Is there anything06 other than that, though, which might be unique to VMS?  ! > > What about database services?n >sE > There exists a product called CONNX, and others, which provide ODBCiH > access to RMS files. I believe similar facilities may exist for OracleB > and/or RDB, but these are not within my sphere of daily contact.  6 Nothing unique to VMS (or Un*x), though, I take it...?     appreciatively,m Derrick Shearer; dls2@Lehigh.EDUp   ------------------------------  % Date: Thu, 18 May 2000 03:46:19 -0400o- From: JF Mezei <jfmezei.spamnot@videotron.ca>e  Subject: Re: VMS on the desktop?, Message-ID: <39239FC3.AFC905EA@videotron.ca>   dls2 wrote:OH > > With each other? You do sometimes see this, though the usefulness isK > > debatable since the cluster communications medium for both SCS and MSCPO0 > > traffic would be the ethernet (10/100Mbits). >  > What are SCS and MSCP? > 9 > Are ethernet and fast ethernet really so inadequate for"3 > relaying (SCS & MSCP?) messages between machines?   H SCS is the cluster communicatiosn protocol, and MSCP is the disk servingC protocol (which, I assume uses SCS packets between nodes, right ?).u  G Ethernet is more than adequate for small lightly loaded systems. In thesI heydays of VMS, folks had  many workstations wit just 50meg drive for therN page/swap file, and they booted off the cluster server though ethernet and got> all their files/applications/authorisation from the "cluster".  L Unfortunatly, DEC's pricing releagted VMS to only sites that could afford toG pay the big bucks, and Windows took over. VMS still has that capabilitymN (workstations booting from the net), but the pricing makes this uncompetitive.  J At the time of q-bus systems, ethernet at 10mbps was faster than the 3mbps Q-bus inside the machine.v  L In 1992, I setup a disaster tolerant cluster with 2 nodes linked by ethernetN bridged by fibre across 2 buildings. The ethernet handled the volume shadowingM of 2 drives as well as terminal IO traffic and it was pretty decent. This wastK more CPU than IO intensive, so the relatively slower writes weren't slowing 6 the system down that bad (besides, reads were faster).   ------------------------------   Date: 18 May 2000 09:29:22 GMT' From: Osmo Kujala <kujala@tukki.jyu.fi>n  Subject: Re: VMS on the desktop?, Message-ID: <8g0d5i$h76$1@mordred.cc.jyu.fi>  + Phillip Helbig <helbig@astro.rug.nl> wrote:g  > <kujala@tukki.jyu.fi> writes: H >>Yes. And I don't know of any other os that so well suites every place.1 >>Windows and/or Linux will be there soon though.g  J > I doubt it.  I have to use Microsoft stuff from time to time (OK, I'm a J > prostitute, but the money is good!), after having worked with computers H > for 10 years (but never PCs).  It is incredible how low quality it is.  . Quality doesn't seem to be very relevant here.G I think stability of NT is good enough that big systems CAN be build to(C use it and then they WILL, no matter that VMS would be much better.WE Then there are unix'es. Especially Linux has good potential to spreadsF everywhere. For example Crusoe-Linux may be success at low end. I hopeD Linux will do it (not much hope for VMS with current Compaq policy).  J >>It's sad, but we need Microsoft stuff. For example some documents is www% >>are only in Microsoft file formats.m  ! > Complain, don't be assimilated!u  @ Yes. I'm trying, but sometimes I feel that resistance is futile.? I haven't yet used Microsoft products though, and will not but  D there seems to be common belief that everyone has word and excel and* can download and use windows programs. :-(   /OKa   ------------------------------   Date: 18 May 2000 09:55:06 GMT' From: Osmo Kujala <kujala@tukki.jyu.fi>P  Subject: Re: VMS on the desktop?, Message-ID: <8g0elq$h76$2@mordred.cc.jyu.fi>  4 Christopher Smith <chriss@mufasa.pubserv.com> wrote:$ > On 17 May 2000, Osmo Kujala wrote:  K >> It's sad, but we need Microsoft stuff. For example some documents is wwwr& >> are only in Microsoft file formats.  L > That's not nessecarilly true.  I've found some pretty creative ways around > microsoft stuff, myself. r  H Yes, but those "emulating" programs don't give exact picture of documentE and microsoft may change the "standard" whenever it will. This way we A still support microsoft "standards" by accepting to use them evenoG partially. Right approach would be to give honour back to standards and $ deny to accept proprietary formats.   < > but I offer that as proof that you don't "need" microsoft.  E Agreed.                                                           /OKe   ------------------------------  % Date: Thu, 18 May 2000 12:42:12 +0000i/ From: Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk>   Subject: re: VMS on the desktop?7 Message-ID: <009EA44E.F405F53D.31@maxwell.ph.kcl.ac.uk>b  K > >It's sad, but we need Microsoft stuff. For example some documents is wwwt& > >are only in Microsoft file formats. > ! > Complain, don't be assimilated!7 >   J Indeed. I'll accept .pdf files (reluctantly), but if I find a website withF a .doc file and an identifiable web-manager, I make a point of sendingD a mail explaining why the .doc file will not be viewed by anyone whoH knows and cares about security, and that therefore using .doc is harming
 his business.u  A Some companies do respond! I've seen .doc pages disappear and gettG replaced by .htm or .pdf. (Usually the horrid .htm that Word emits, butfE mostly it's viewable with Netscape and the rest of the time I dig out"M another standard letter for the Webmin about the evils of MS supposedly-html.i  A I take similar action if anyone sends me an unsolicited .doc mails' attachment with no textual alternative.   G Get the word out: reading any .doc file is like unsafe sex, it could beeB lethal (to your PC, your business, your continued employment ...)    	Yours,t
 		Nigel Arnots- 		NRA@MAXWELL.PH.KCL.AC.UK                      7 		"In the beginning there was nothing, which exploded."h   ------------------------------  % Date: Thu, 18 May 2000 07:23:36 -0500e) From: "John E. Malmberg" <wb8tyw@qsl.net>   Subject: Re: VMS on the desktop?7 Message-ID: <0fb301bfc0c3$e594c070$020a0a0a@xile.realm>h  . JF Mezei <jfmezei.spamnot@videotron.ca> wrote: > L > At the time of q-bus systems, ethernet at 10mbps was faster than the 3mbps > Q-bus inside the machine.n   ?????)  K Ethernet at 10mbs is 10 Megabits/second or 1 Megabyte per second.  And that  is a theoretical maximum.-  0 Q-bus is approximately 3.8 Megabytes per second.  G RQDX3 controllers delivered at best 0.6 Megabytes per second.  Based onoI posts about the VAX/VAXstation 2000 MFM disk controller circuitry, it wasn also restricted on disk speed.  L For these systems it was possible to get a little better performance from anI Ethernet link than the local disks, but it was the disk hardware that wast the limitation, not the Q-bus.  L Local observations show that it seems to take 30 Pentium Mhz to equal 1 VUP. Your mileage may vary.   -Johna   ------------------------------  % Date: Thu, 18 May 2000 14:41:03 +0000 / From: Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk>e  Subject: re: VMS on the desktop?7 Message-ID: <009EA45F.8E1BA36F.21@maxwell.ph.kcl.ac.uk>h  4 > "Nigel Arnot" <sysmgr@maxwell.ph.kcl.ac.uk> wrote:J > > From a sysop's perspective its an absolute dream ... PROVIDED that all; > > the VMS workstations are clustered. If that's the case:e > >iF > > Adding another desktop is a one-off process taking an hour or two.: > > Per-user administration scales as the number of users.> > > Per-system administration scales as the number of systems.: > > Per-disk administration scales as the number of disks.= > > Any user can log into any system with no problems at all.eF > > Everything works as per the documentation, which is comprehensive. > D > Is there a central cluster server, or is everything decentralized?   Your choice. You can do either.o  ? > For storage?  Where do files get saved?  Is there redundancy?   = On disks. You can have redundancy (RAID or mirroring, with ora3 without redundant system boxes)  if you pay for it.O  B > For control?  Where are user profiles, and cloning images, kept?  D Dunno what a "cloning image" is. If by "User Profile" you mean MotifA preferences, in the user's login directory for the ones chosen bytG the user, and in a system directory for ones set by the administration.   ) > Does VMS even support cloning, or such?h  E What is cloning? If you mean, can you copy a system disk from one VMShG system to another and boot it as a new system by making minimal changest thereto, yes it does.  > H > > The fly in the ointment is the cost of VMScluster licenses. And thatK > > most users want applications on their desks that you can't get for VMS.  > E > What is the cost of a clustering license?  Is the cost per cluster,. > or per node? e  H Per node. Thousands of dollars, though it was reduced somewhat recently.  0 > Is there more than one cluster license type?    B Yes, there is a "client" license that's crippled so the only thingP that the node can do is share disks being served by a full-license cluster node.  
 > Is thereC > variance in the cost of a cluster license?  By machine types?  ByF > other criteria?a  G By machine type, in three classes: workgroup, departmental, enterprise.-I Most folks who are unhappy with the price are looking at the entry-level.<   > 8 > Is VMS still as worth having, even when not clustered?  M Depends what you want it for. I'd choose to write and run my number-crunchingo1 programs on VMS any day, if cost wasn't an issue.    	Yours,i
 		Nigel Arnott- 		NRA@MAXWELL.PH.KCL.AC.UK                   t  7 		"In the beginning there was nothing, which exploded."    ------------------------------  # Date: Thu, 18 May 2000 14:46:41 GMTh" From: Art Rice <arice@ue.itug.org>  Subject: Re: VMS on the desktop?8 Message-ID: <2b08isc6ks7i9c3bd4nre2hrrp98blvhgj@4ax.com>  C On Wed, 17 May 2000 16:31:37 -0400, "dls2" <dls2@Lehigh.EDU> wrote:i  # >"SysAdmin" <djesys@fsi.net> wrote:C >> dls2 wrote:= >> > A well designed GUI does not require one to use a mouse.-3 >> > Microsoft Windows is a very well designed GUI,  >>; >> No, it isn't. Remember those words: "well designed GUI".  >> >> > in that it C >> > allows for complete navigation of its interface, by keyclicks, A >> > alone.  Motif also has such functionality.  This is known ash >> > "explicit keyboard focus."e >>F >> ...but depends upon the program author to provide support for them. >7< >Yes, but remember my wording of "allows for."  "Allows for" >does not mean "implements."  > IIRC MS Windows (3.1) and NT 3.5 did allow and implement totalF functionality via keyclick.  Windows95,98, and NT4.0 and up absolutely6 require the use of a mouse or other pointing device.   >e; >> > Maybe if you learned to use the keyboard shortcuts, itg0 >> > might have been somewhat easier for you.... >>K >> I known of many places - even in MS Orifice where you are "trapped", andm% >> cannot navigate except by mousing.s >>? >> So far, Linux + KDE + Navigator poses such challenges, also.a >l& >Is VMS any better off in this regard? >u >W >Derrick Shearer >dls2@Lehigh.EDU >e   -- t
 Art Rice   *# # Special Data Processing Corporationk& --------------------------------------' All opinions expressed are mine and do  % not reflect the views of my employer.i   ------------------------------  # Date: Thu, 18 May 2000 14:54:56 GMT-" From: Art Rice <arice@ue.itug.org>  Subject: Re: VMS on the desktop?8 Message-ID: <dg08is43ol70dk1n0fbn0apkvf1d37annf@4ax.com>  ; On Wed, 17 May 2000 20:32:08 +0000 (   ), Christopher Smith " <chriss@Mufasa.pubserv.com> wrote:  & >On 17 May 2000, Phillip Helbig wrote: >eL >> This lets me read text files people send as base64 encoded .DOC files (I I >> decode them with the C code below).  However, there is the more basic DH >> problem that people think it's OK to send this stuff, and even worse + >> that they expect to receive it from you.( >IH >True enough.  Allthough, if they really want to recieve .doc files, why* >not send them a plain ascii .doc file? :) >lB >I imagine that word would open it.... well, on the other hand...? >iJ >If it were up to me, people who need (and only people who _need_) to sendF >formatted text to somebody else would do it using HTML or postscript.1 >Plain ascii works just fine for everything else.r >hG >I consider it common (maybe it's not common) curtesy to work out whicheG >formats your intended recipient can read before sending anything aside   >from human-readable ascii text. >r	 >Regards,  >s >Chris  E For the most part,  even when working in Windows, I prefer to receivetC ASCII text files.  I might open it with Wordpad rather than NotepadS but only if it is really big.o  B Release notes, on the other hand,  I prefer to receive via Word orD .PDF formats.  Since Acrobat Reader is free and I don't have to giveD Billy any of my cash for it, a PDF is more preferable.  Unfortunaly,' PDFs are not readable on ALL platforms.    -- p
 Art Rice   *#i# Special Data Processing Corporation & --------------------------------------' All opinions expressed are mine and do r% not reflect the views of my employer.d   ------------------------------  % Date: Thu, 18 May 2000 11:01:16 -0400a" From: Dan Sugalski <dan@sidhe.org>  Subject: Re: VMS on the desktop?8 Message-ID: <4.3.1.0.20000518105409.00e99840@24.8.96.48>  & At 01:52 AM 5/18/00 -0400, dls2 wrote:9 >"David J. Dachtera" <djesys.nospam@earthlink.net> wrote: H > > With each other? You do sometimes see this, though the usefulness isK > > debatable since the cluster communications medium for both SCS and MSCP 0 > > traffic would be the ethernet (10/100Mbits). >e8 >Are ethernet and fast ethernet really so inadequate for2 >relaying (SCS & MSCP?) messages between machines?  B Under any sort of load, yes. It's not so much that their speed is K inadequate (though the alternative to ethernet is either CI running a pair (K of 70Mb/sec channels, fibre running lots more than that, or Memory Channel nK which just cruises) though it is the slowest medium. The bigger problem is s latency.  F The distributed lock manager does all its communication via SCS. When F you're exchanging locks around you want the response to be as fast as J possible. A 100 Mb/sec channel with five times the latency of a 70 Mb/sec  channel is suboptimal.  K You will (and people have) see significant performance boosts in clustered o2 apps just by switching to a lower-latency channel.  ' >How, then, are server clusters linked?a  J In the "old" days it was CI for the bigger machines. Nowadays it seems to I be switching over to glass, fast ethernet, or memory channel. I think it  K might be worthwhile, in clusters using SCSI to get to storage and ethernet  I for cluster communications, to throw in some used CI controllers just to l0 get a lower-latency channel between the systems.   					Dan  I --------------------------------------"it's like this"-------------------i2 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and evenl;                                       teddy bears get drunko   ------------------------------  % Date: Thu, 18 May 2000 10:50:05 -0400a" From: Dan Sugalski <dan@sidhe.org>  Subject: Re: VMS on the desktop?8 Message-ID: <4.3.1.0.20000518104541.00e91890@24.8.96.48>  0 At 09:46 PM 5/17/00 +0000, Phillip Helbig wrote:& >If you're in an academic environment,I >the cost is nominal (and probably paid for out or a budget which doesn'tt >impact you directly).  L I think you really mean "Minimal" here, as nominal is a synonym for normal.  (Sorry, pet peeve of mine)  K The CSLG covers the cluster licenses, and it is pretty cheap. Whether it's hG cheap enough is another question entirely, as it is still pricier than nF things like the WinNT license. (I think I was paying $5k for up to 10 K machines. That was dirt cheap for me, since I had 3 8400s and a 2100 using t1 it, but for folks with workstations it's less so)   K The cluster stuff saves great gobs of sysadmin time, but for most academic iJ sites it's slave labor (aka workstudy or student labor) time saved, which E is usually cheaper than the license and coming out of someone else's  K budget. Plus there's also the argument that having things go wrong is good aL education, and how can you train a student sysadmin on a system that rarely 
 breaks? :)   					Dan  L ----------------------------------------------------------------------------L Dan Sugalski                          General and VMS-specific perl training
 dan@sidhe.orgs>                                       Mail me for more details   ------------------------------  # Date: Thu, 18 May 2000 15:04:12 GMTa" From: Art Rice <arice@ue.itug.org>  Subject: Re: VMS on the desktop?8 Message-ID: <q418isoiqf0i6av1dhd4uconhkpluek2mq@4ax.com>  C On Wed, 17 May 2000 23:33:53 -0400, "dls2" <dls2@Lehigh.EDU> wrote:9  ' >"sol gongola" <sol@adldata.com> wrote:  >> dls2 wrote:8 >> > "Richard B. Gilbert" <DRAGON@compuserve.com> wrote:% >> > > Message text written by "dls2"cD >> > > >On the desktop, is it likely to be perceived any differently@ >> > > >than a Un*x workstation?  Other than stability, does VMS= >> > > >have any benefits when used as a desktop workstation?  >> > >K >> > >         Fewer applications are "windowed".  Most people open a bunch  >ofiH >> > > DECterm windows and use the command line interface.   Many of theI >> > > applications that are windowed have both a windows interface and ay  >> > > character cell interface. >> >< >> > Then for the desktop, doesn't it make more sense to use; >> > terminals, rather than actual VMS machines?  Graphicala# >> > terminals, or character-based.a >> >) >> > For standalone desktop VMS machines? ( >> > For clustered desktop VMS machines? >> >> not really. >a >Why "not really?" >nI >> A single workstation display functioning as a x terminal (or x server)tH >> allows me to have many terminal sessions at the same time. I can haveH >> sessions open from any accessible VMS system as well as sessions openI >> from other unix systems on my network. To get the same capability withdI >> terminals, i'd have to surround myself with up to 10 terminal displays 8 >> and keyboards, each with a cable running to a system. >a7 >Terminals can have the same graphical and multisessionn8 >capabilities as Un*x or VMS workstations; individually,; >rather than the 10 or so equivalent terminals you suggest.- >-3 >By example, NCD HMXpro24s provide such capability.T >r6 >I now think that standalone VMS machines are not very7 >good as desktop machines.  They lack the graphical andu< >audial capability of other offerings, such as Irix, or even	 >Windows..  E Lots of people, and some corporations, are getting really fed up wtih F Microsoft.  Even though I use an NT workstation and currently have sixD terminal emulator sessions up on my screen, plus Agent, Lotus Notes,< and Internet Exploder,  MS products are not a viable option.  = I like my data intact, on my disk when I need it, and quickly C displayed.  MS can't provided that.   UNIX, IRIX and their variantsrE can provide this but at today's prices, it is cost effective to put adE workstation on a desk rather than a terminal.  Unless,  the person atrF the desk is doing something like data entry into a specific system and that's all they do.x   > 2 >Is VMS any better for the desktop when clustered? >i >d >Derrick Shearer >dls2@Lehigh.EDU >t   --  
 Art Rice   *#t# Special Data Processing CorporationF& --------------------------------------' All opinions expressed are mine and do p% not reflect the views of my employer.m   ------------------------------   Date: 18 May 2000 09:38 CST'' From: carl@gerg.tamu.edu (Carl Perkins)   Subject: Re: VMS on the desktop?- Message-ID: <18MAY200009385299@gerg.tamu.edu>a  ! tim.llewellyn@bbc.co.uk writes...r }"Ebinger . Eric" wrote:I }> Yes, I spent a summer doing keypunching to put myself through college.lE }> Somehow, the idea of spending eight hours a day entering names and K }> address using a Windows applications makes me break out in a cold sweat.c }> } M }Doing anything repetitive with windows is a pain. When I scan I counted overs } G }10 mouse moves required just to scan another sheet, as the scan windowt }closeshM }and has to be reactivated and setup for each page. This is progress? Oh, andr } J }an "apply" button used by many X and Mac applications seems like an alien }concept to M$ }  }> }> Eric Ebingern }--e7 }Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project   @ "Apply" buttons show up all over the place. The quickest example@ is to right click on the desktop. Notice that there is one rightB there in the properties dialog. Of course, being MS software thereD are plenty of cases where it makes you reboot before it can actually; apply any changes, which makes an "apply" button pointless.-  F As for the scanning, I would have to guess that you were not using theA scanning software directly, but rather calling it from some other G application. I have scanned things and never had this problem, but thenMG I directly use the scanning application instead of calling it from someoE other graphics application or image cataloging application. Those are E good when you only want to scan one image and them manipulate it, butd; get in the way when you just want to scan a bunch of stuff.n   --- Carl   ------------------------------  % Date: Thu, 18 May 2000 12:28:35 -0400a' From: "Bill Todd" <billtodd@foo.mv.com>i  Subject: Re: VMS on the desktop?( Message-ID: <8g15ih$erm$1@pyrite.mv.net>  : Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk> wrote in message1 news:009EA44E.F405F53D.31@maxwell.ph.kcl.ac.uk...'   ...b  I > Get the word out: reading any .doc file is like unsafe sex, it could be C > lethal (to your PC, your business, your continued employment ...)l  L While not in a position to refute the above assertion, I do question it:  itA looks a great deal like others that I *do* know to be significant  exaggerations.  H A while ago, my impression was that the only threat in reading a .doc MSI file was macro viruses, which could only affect other Word documents that H you created or edited.  If so, using Word only to read such things wouldL seem relatively safe.  Has this changed (e.g., are there now embedded-script6 facilities that execute without warning and without an# appropriately-restrictive sandbox)?4  L And there are other ways to read Word documents.  MS provided a free 'Word 7L viewer' read-only application after inadvisably changing Word 7 such that itH created documents unreadable by previous versions of Word that one wouldB expect would not transmit macro viruses, and the Wordpad half-WordJ application that comes with their OSs may also be sufficiently limited (it* sure is in other ways) to avoid the issue.  K As I said, I'm not knowledgeable one way or the other in these matters, butrI I do think people should be as careful to be accurate in their statementsiJ about other environments as they would like others to be about VMS, and myH experience is that, especially w.r.t. MS products, this is often not the case.    - bill   >o > Yours,
 > Nigel Arnott > NRA@MAXWELL.PH.KCL.AC.UK >U7 > "In the beginning there was nothing, which exploded."- >-   ------------------------------  + Date: Thu, 18 May 2000 15:59:15 +0000 (   )w3 From: Christopher Smith <chriss@Mufasa.pubserv.com>   Subject: Re: VMS on the desktop?J Message-ID: <Pine.LNX.4.05.10005181558090.18134-100000@Mufasa.pubserv.com>  " On 18 May 2000, Osmo Kujala wrote:  J > Yes, but those "emulating" programs don't give exact picture of documentG > and microsoft may change the "standard" whenever it will. This way werC > still support microsoft "standards" by accepting to use them evenhI > partially. Right approach would be to give honour back to standards andy& > deny to accept proprietary formats.   J I agree completely.  As I said in a previous post, it is common curtesy toB work out the formats that your recipient can accept before sending$ anything that's not just plain text.   Regards,   Chriso  O ===============================================================================?@ "My two cents"			(http://rootworks.com/twocentsworth.cgi?128562)= Christopher Smith(chriss@pubserv.com)			Prgramer^W Programmeru Prime Synergy of Champaign, IL.o% -------------------------------------rI "Where a calculator on the ENIAC is equipped with 18,000 vacuum tubes and H weighs 30 tons, computers in the future may have only 1,000 vacuum tubes; and weigh only 1.5 tons." -- Popular Mechanics, March 1949 rO -------------------------------------------------------------------------------h   ------------------------------  % Date: Thu, 18 May 2000 12:56:49 -0400h" From: Dan Sugalski <dan@sidhe.org>  Subject: Re: VMS on the desktop?8 Message-ID: <4.3.1.0.20000518125229.02192ba0@24.8.96.48>  + At 12:28 PM 5/18/00 -0400, Bill Todd wrote:tI >A while ago, my impression was that the only threat in reading a .doc MSSJ >file was macro viruses, which could only affect other Word documents thatI >you created or edited.  If so, using Word only to read such things wouldeM >seem relatively safe.  Has this changed (e.g., are there now embedded-script,7 >facilities that execute without warning and without ant$ >appropriately-restrictive sandbox)?  H I think at this point Word has full VB scripting capabilities built in, K just like Outlook does. And they just announced some evil vulnerability in  G that stupid paperclip thingie that gives someone with too much time on -1 their hands the capability to toast your machine.k   					Dan  I ------------------------------------------------------------------------- @ Dan Sugalski                          Microsoft *is* the answer.I dan@sidhe.org                         "Where's my Elder Seal" is the nexts9                                       logical question...    ------------------------------   Date: 18 May 2000 17:21:16 GMT* From: helbig@astro.rug.nl (Phillip Helbig)  Subject: Re: VMS on the desktop?- Message-ID: <8g18qc$6t$1@info.service.rug.nl>S  A In article <dg08is43ol70dk1n0fbn0apkvf1d37annf@4ax.com>, Art Rice. <arice@ue.itug.org> writes:   H >>I consider it common (maybe it's not common) curtesy to work out whichH >>formats your intended recipient can read before sending anything aside! >>from human-readable ascii text.n  G Well-meaning employee:  Boss, I consider it common courtesy to work outdG                         which formats your intended recipient can read nJ                         before sending anything aside from human-readable #                         ascii text.>  C Boss:                   Who cares about common courtesy?  The only aB                         question is whether or not it is industry !                         standard.d   ------------------------------   Date: 18 May 2000 12:12 CSTd' From: carl@gerg.tamu.edu (Carl Perkins)   Subject: re: VMS on the desktop?- Message-ID: <18MAY200012121118@gerg.tamu.edu>u  3 Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk> writes...e5 }> "Nigel Arnot" <sysmgr@maxwell.ph.kcl.ac.uk> wrote:vK }> > From a sysop's perspective its an absolute dream ... PROVIDED that allS< }> > the VMS workstations are clustered. If that's the case: }> >G }> > Adding another desktop is a one-off process taking an hour or two. ; }> > Per-user administration scales as the number of users.D? }> > Per-system administration scales as the number of systems.c; }> > Per-disk administration scales as the number of disks.-> }> > Any user can log into any system with no problems at all.G }> > Everything works as per the documentation, which is comprehensive.h }>  E }> Is there a central cluster server, or is everything decentralized?: }   }Your choice. You can do either. } @ }> For storage?  Where do files get saved?  Is there redundancy? } > }On disks. You can have redundancy (RAID or mirroring, with or4 }without redundant system boxes)  if you pay for it.  D Not only can they be in redundant boxes, but those boxes can also beA placed many miles apart to allow for disaster recovery. (Say youreB building burns down, what do you do? With a distributed VMSclusterC that is mirroring everything across two sites the cluster might notuE even go down if the surviving site had sufficient nodes/votes to havenI quorum - at worst you should be able to just reboot the surviving systemseI after they hung due to loosing quorum; there is also the middle ground ofnG the system manager ebing able to adjust quorum on the fly, but that hase0 a very limited window during which it can work.)  1 }> Is there more than one cluster license type?  i } C }Yes, there is a "client" license that's crippled so the only thingsC }that the node can do is share disks being served by a full-licenseo }cluster node. }		Nigel Arnot  F That isn't quite all it can do - it can't serve disks, but it can be aG client to all served things, not just disks but also tapes, queues, and F anything else. I'm not sure, but it can probably "serve" queues to theE other nodes, i.e. print and batch (and any other kind) of queues thate8 run on that node may be accessable to the whole cluster.  B In many cases, the client license should be sufficient for some ofA the nodes in a cluster. Diskless, or nearly diskless (i.e. it hasa@ a disk but the only thing on it are page, swap, and dump files),D workstations this would be ideal - they don't have anything to serve: to the cluster anyway, so you may as well save the $4,500.   --- Carl   ------------------------------  + Date: Thu, 18 May 2000 17:57:43 +0000 (   )k3 From: Christopher Smith <chriss@Mufasa.pubserv.com>.  Subject: Re: VMS on the desktop?J Message-ID: <Pine.LNX.4.05.10005181748410.18134-100000@Mufasa.pubserv.com>  % On 18 May 2000, Phillip Helbig wrote:e  I > Well-meaning employee:  Boss, I consider it common courtesy to work outoI >                         which formats your intended recipient can read ML >                         before sending anything aside from human-readable % >                         ascii text.eE > Boss:                   Who cares about common courtesy?  The only  D >                         question is whether or not it is industry # >                         standard.   7 Well, *ouch* -- but I see where you're going there.. :)t  H Unfortunately, nobody with any great deal of power in most companies has, realised that "industry standard" is a myth.  J Yes, there are good standards available, but not enough people use them to, make them the "normal" way of doing things.   G Of course, I'd consider ASCII pretty "industry standard."  That doesn't.F mean that before sending some data over to an IBM shop I may not check0 that their computers want it in ASCII or EBCDIC.  * So let's name some "industry standards..."   ASCII.   SCSI? (which version? :)    HTML? (Who decides what's HTML?)  J PDF? (Yeah, maybe if they gave every platform at least a chance to support it...)  I Java? (Certainly seems to be the "industry standard" way of making littlet' programs that emulate animated gifs...)i   IDE? (tee hee)  A PCI bus? (ok.. possibly... but what's a bus without peripherals?)   ; Compact Disc? (the media... but what about the formatting?)t  I Microshaft word files? (Yeah, if you strip all the special formatting out 6 they turn into ascii... I guess that's close enough ;)   Regards,   Chris   O =============================================================================== @ "My two cents"			(http://rootworks.com/twocentsworth.cgi?128562)= Christopher Smith(chriss@pubserv.com)			Prgramer^W Programmer1 Prime Synergy of Champaign, IL.6% -------------------------------------lI "Where a calculator on the ENIAC is equipped with 18,000 vacuum tubes andnH weighs 30 tons, computers in the future may have only 1,000 vacuum tubes; and weigh only 1.5 tons." -- Popular Mechanics, March 1949 iO -------------------------------------------------------------------------------e   ------------------------------  % Date: Thu, 18 May 2000 07:50:08 -0400 2 From: "William Hymen" <t18_pilot@hotmail.spam.com># Subject: VMS-NT "affinity" solution 7 Message-ID: <hJQU4.96726$VR.1851345@news5.giganews.com>h   Hi all,   , I just spoke with Compaq pre-sales techincal4 support, and they told me that the affinity solution, allows me to see a vms "container" and store windows files there from NT.  , What do I do if *both* vms and NT developers, need the files.  I (we) have vms programmers) doing c.. etc, and need to keep the filess/ in a configuration managment database.  Howevera* the client piece of the system (Clearcase)) only runs on NT, UNIX, and IBM mainframe.a  * My hope was to have the VMS people develop' from their side, and manage the code by-- doing a standard "map network drive" from NT,s2 (to see the files on vms).   Compaq says the files* in a "container" are *not* visible to vms.   Whats a fellow to do?    Bill   ------------------------------  # Date: Thu, 18 May 2000 15:41:58 GMT0* From: young_r@eisner.decus.org (Rob Young)' Subject: Re: VMS-NT "affinity" solution?+ Message-ID: <y4CHl3QnSyoz@eisner.decus.org>k  l In article <hJQU4.96726$VR.1851345@news5.giganews.com>, "William Hymen" <t18_pilot@hotmail.spam.com> writes:	 > Hi all,o > . > I just spoke with Compaq pre-sales techincal6 > support, and they told me that the affinity solution. > allows me to see a vms "container" and store > windows files there from NT. > . > What do I do if *both* vms and NT developers. > need the files.  I (we) have vms programmers+ > doing c.. etc, and need to keep the files>1 > in a configuration managment database.  Howevere, > the client piece of the system (Clearcase)+ > only runs on NT, UNIX, and IBM mainframe.  > , > My hope was to have the VMS people develop) > from their side, and manage the code bya/ > doing a standard "map network drive" from NT,e4 > (to see the files on vms).   Compaq says the files, > in a "container" are *not* visible to vms. >  > Whats a fellow to do?t >    	Bill,  A 	What I did in a previous existence was to NFS mount a filesystems? 	from AIX (product is SourceSafe, runs on Micro$ and Unix also)nB 	visible on VMS.. run a nice big COM file on VMS that did VMS typeB 	setup things, reexec the sourcesafe commands to pull the if'defedB 	source out of sourcesafe into the NFS mount, ran KMAKE I believe 8 	(can't say for sure, of course I blew away all the old ? 	builds... copyright issues , etc.) and in the makefile the cc  G 	commands and other VMS'isms were ifdefed... KMAKE was a pretty decent w< 	make knockoff , there were glitches but easy to get around.  > 	Long story short it worked quite well.. in fact the build ran= 	faster on a MicroVax than it did on Alpha 2000/300 because ItB 	loaded up all the .h files in Gerald Newman's RAMDISK (not enough: 	memory to do the entire build in memory) on the VAX side.  : 	I would have a separate tree to do development/support inA 	NFS mounted back to VMS so I could use TPU to hack at the commonv8 	source, checking the files out of sourcesafe from a PC.   				Robr   ------------------------------  % Date: Thu, 18 May 2000 15:24:09 +0200r= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>s' Subject: Re: VMS-NT "affinity" solutione) Message-ID: <3923EEF8.2F469CBF@gtech.com>    William Hymen wrote:. > I just spoke with Compaq pre-sales techincal6 > support, and they told me that the affinity solution. > allows me to see a vms "container" and store > windows files there from NT. > . > What do I do if *both* vms and NT developers. > need the files.  I (we) have vms programmers+ > doing c.. etc, and need to keep the filest1 > in a configuration managment database.  Howeverd, > the client piece of the system (Clearcase)+ > only runs on NT, UNIX, and IBM mainframe.* > , > My hope was to have the VMS people develop) > from their side, and manage the code bys/ > doing a standard "map network drive" from NT,w4 > (to see the files on vms).   Compaq says the files, > in a "container" are *not* visible to vms. >  > Whats a fellow to do?u   Install PathWorks or Samba !   Arne   ------------------------------  # Date: Thu, 18 May 2000 15:13:34 GMT.1 From: "Mark D. Jilson" <jilly@clarityconnect.com>m' Subject: Re: VMS-NT "affinity" solutionh2 Message-ID: <39240890.B75FEEFB@clarityconnect.com>  H OpenVMS Disk Services for Windows NT allows you to create a container onA the VMS system and then serve that container to WNT systems.  Seee> http://www.openvms.digital.com/openvms/products/ntds/ for more information.   William Hymen wrote: > 	 > Hi all,  > . > I just spoke with Compaq pre-sales techincal6 > support, and they told me that the affinity solution. > allows me to see a vms "container" and store > windows files there from NT. > . > What do I do if *both* vms and NT developers. > need the files.  I (we) have vms programmers+ > doing c.. etc, and need to keep the filese1 > in a configuration managment database.  Howevers, > the client piece of the system (Clearcase)+ > only runs on NT, UNIX, and IBM mainframe.o > , > My hope was to have the VMS people develop) > from their side, and manage the code by / > doing a standard "map network drive" from NT,-4 > (to see the files on vms).   Compaq says the files, > in a "container" are *not* visible to vms. >  > Whats a fellow to do?m >  > Bill   -- cD Jilly	- Working from Home in the Chemung River Valley - Lockwood, NY0 	- jilly@clarityconnect.com			- Brett Bodine fan. 	- Mark.Jilson@Compaq.com			- since 1975 or so, 	- http://www.jilly.baka.com               -   ------------------------------  % Date: Thu, 18 May 2000 18:40:24 +0200 + From: Michal Kowalczyk <MKK@npd.fuw.edu.pl> ' Subject: Re: VMS-NT "affinity" solution-- Message-ID: <39243918.3084440@npd.fuw.edu.pl>3   William Hymen wrote: > 	 > Hi all,o > . > I just spoke with Compaq pre-sales techincal6 > support, and they told me that the affinity solution. > allows me to see a vms "container" and store > windows files there from NT.  .     Containers are used to create filesystems @ that are exported by NFS server to NFS clients (UNIX machines). = Files stored in containers are not directly visible from VMS o: machines unless you mount NFS filesystem using NFS client ; software - UCX and TCPIP services for OpenVMS include both b  NFS server and client software.    On UNIX machine:   ls /mnt/axp/etc/XF*y   /mnt/npdaxp/etc/XF86Config i on VMS:c $ dir dnfs230:[etc]$xf*n   Directory DNFS230:[ETC]n   $XF86C$ONFIG.;1e   Total of 1 file.   > . > What do I do if *both* vms and NT developers. > need the files.  I (we) have vms programmers+ > doing c.. etc, and need to keep the filesi  = 	I know nothing about NFS client running under Windows NT OS.4; You can export VMS filesystems to Windows NT clients using i> Advanced Server V7.2A for OpenVMS software. This will emulate > WindowsNT 3.51 Backup Server on OpenVMS Alpha. You can export A ODS-2 and ODS-5 filesystem; the second one supports Extended FileiD Specifications  (up to 243 characters including the version number).@ You can export any VMS directory structure as Windows NT public  or private share.   	 			MichalI   ------------------------------  % Date: Thu, 18 May 2000 17:40:39 +0200 > From: "Jean-Franois Marchal" <jean-francois.marchal@x9000.fr>1 Subject: What cobol statements affect bytlm quotak3 Message-ID: <8g12r0$1o4t$1@s2.feed.news.oleane.net>   " Considering a program using cobol,+ and no direct call to vms library routines,r+ where should I dig to see where the programK, is burning large quantities of BYTLM quota ?   Jean-Franois Marchal- X9000 - LYON   ------------------------------  # Date: Thu, 18 May 2000 14:26:47 GMTi, From: koehler@eisner.decus.org (Bob Koehler)" Subject: Re: Wildfire Announcement+ Message-ID: <2oGfhgpe$$RR@eisner.decus.org>0  ] In article <3bb5isgnjj5mq1ag7oj4se7ob4of9jmrvh@4ax.com>, Art Rice <arice@ue.itug.org> writes:o< > It stands to reason that they would misdefine "mainframe."H > Recently I have heard many lay people decribe HP9000 and SUN E10000 asH > mainframes.  They are not but under the really old definition of beingE > the "main" computer within the corporation you can see where peoplep > make that mistake.  E "mainframe" is in the eye of the beholder.  My sister worked with SAS B data sets which her PC couldn't handle.  Those data sets had to be& processed on the VAX 3300 "mainframe".  E We had a development done on some VAX 3300.  When we went to ship the=F system to the customer the programmers stopped in the computer room to? see the system they had been using all along.  They thought the	0 pedestal cabinet was just the tape drive (TK70).  F ----------------------------------------------------------------------? Bob Koehler                     | Computer Sciences Corporations= Hubble Space Telescope Payload  | Federal Sector, Civil Group E  Flight Software Team           | please remove ".aspm" when replying-   ------------------------------  # Date: Thu, 18 May 2000 13:15:36 GMT-" From: Art Rice <arice@ue.itug.org>" Subject: Re: Wildfire Announcement8 Message-ID: <5sp7is0lr0ea09vt6c743hpr6s5qfjp1l5@4ax.com>  , On Wed, 17 May 2000 15:29:57 -0400, JF Mezei% <jfmezei.spamnot@videotron.ca> wrote:0   >Art Rice wrote:I >> Recently I have heard many lay people decribe HP9000 and SUN E10000 asdI >> mainframes.  They are not but under the really old definition of beingtF >> the "main" computer within the corporation you can see where people >> make that mistake.i >yP >Was the VAX9000 a mainframe ? If so, wouldn't the GS series be mainframes too ? >uH >> The article does state that Linux would run natively on the S/390 andI >> then goes on to describe them as "virtual" servers (presumably running  >> on MVS?)l > J >I doubt very much that LINUX could run as a task in MVS. It would also beM >quite interesting to see how IBM would have implemented a terminal interfaceiN >to LINUX since the 390 is so "3270" oriented (block mode instead of character >cell mode). >-N >My guess is that they are using the 390's partitioning abilities which also aK >CPU to be shared amongst multiple OS instances. (think of it as a hardwaren >implementation of VM).  > G >> On point number two I agree totally.  The Linux instances should fita7 >> right in with the UNIX average of 35 hours downtime.P >lJ >Not so sure. It all depends on how much effort IBM will put on the device >drivers etc etc.   E Agreed.  Although I doubt that they have dedicated the same amount ofeE time fine tuning Linux as they have MVS, I do believe that they would)E have invested heavily in development of Linux for MVS.  Maybe it willb? have a better uptime than UNIX but many of the Panics and other F crashes I have seen on UNIX systems are caused by applications.  (Yes,E there are a lot caused by drivers, misperforming hardware, memory ande? so on.)  It seems in the Tandem world, as in the IBM world, andh? hopefully in the OpenVMS world we just don't see those kinds of & problems because of several factors.    E 1.)  The proprietary OS has been developed over a long period of time D and the developers have "learned" from their mistakes.  (MS tends toC repeat them time after time and so do some versions of UNIX.)  ThisuA proprietary OS only runs on specific hardware (no BillyBoxes) andM" probably will for quite some time.  F 2.)  System Managers/Administrators on these systems tend to be peopleE who grew up on these platforms and most know them intimatly.  Lots ofn> people grew up on UNIX but many go directly from graduation to? administrator.  On our platforms, one tends to spend time as aneF operator and/or programmer for quite some time before even consideringB administering a corporate or large educational system.  (there are8 always some exceptions)   I have met some very good UNIX administrators.   D 3.)  The programmers allowed to touch these systems are usually of aE higher quality  (Don't flame me.  I said "usually")  The compilers on E these systems also seem to be a much better quality than those on thev
 UNIX systems.r  C 4.)  The level of service from the vendor (preventative maintenanceeF included) is far better that that of lesser hardware vendors.  Notices  of fixes and patches is better.      Just my opinion. a >sI >Considering that the press only knows about LINUX (and has no idea about,L >True64), I have a feeling that the IBM announcement will make a much biggerH >splash because it will feture the word "LINUX" which gives the media an >instant orgasm. > F >Here is a question: Could Compaq  legally and ethically port its unixK >clustering to Linux but only on ALPHA linux ? If so, perhaps Compaq shouldsM >have really announced it was going to port TRue64 to Linux and from then on, O >only has VMS as a proprietary for the robustness, and sell Linux for midrange,aM >and Microsoft softwrae for those who like to practice their <atl><ctrl><del>i >typing skills.  >> > M >I think that Compaq's wildfire announcement could have had more media weighteO >if they had featured Linux more prominently in it. Just as "open systems" weregL >the "soupe du jour" in Palmer's days, "LINUX" is the current soupe du jour.   --  
 Art Rice   *#'# Special Data Processing Corporationt& --------------------------------------' All opinions expressed are mine and do .% not reflect the views of my employer.v   ------------------------------   Date: 18 May 2000 13:31:31 GMT8 From: hammond@not@peek.ppb.cpqcorp.net (Charlie Hammond)" Subject: Re: Wildfire Announcement6 Message-ID: <8g0rbj$h6b$1@mailint03.im.hou.compaq.com>  , In article <2oGfhgpe$$RR@eisner.decus.org>, . koehler@eisner.decus.org (Bob Koehler) writes:  F >"mainframe" is in the eye of the beholder.  My sister worked with SASC >data sets which her PC couldn't handle.  Those data sets had to bes' >processed on the VAX 3300 "mainframe".-  G On the ALPHAstation 255 that is my primary workstation I have a printer H which is used mostly on Windows systems.  I had to call customer supportI for some information when I first installed it.  My inquiry got *nowhere*.I until the woman realized, "Oh, you're using it on a mainframe!"  Then thepI call was trasferred and the information I needed was faxed minutes later.   " Yes, "in the eye of the beholder".   --  K     Charlie Hammond -- Compaq Computer Corporation -- Pompano Beach  FL USAnF          (hammond@peek.ppb.cpqcorp.net -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------  % Date: Thu, 18 May 2000 10:57:56 -0400n  From: norm.raphael@jamesbury.com" Subject: Re: Wildfire Announcement4 Message-ID: <C22568E3.00516016.00@jklh21.valmet.com>   /To:  Info-VAX@mvb.saic.coma /cc:# /Subject: Re: Wildfire Announcemente /a /g" /norm.raphael@jamesbury.com wrote:E /> swithcing backplane (with a bigger cabinet, IIRC) is required. The H /> existing quad modules can be moved, however.  Another nice feature isG /> that in different quads different versions of the CPU can run so thehJ /> processors in any existing quads do not have to be swapped, but can be. /sN /Another aspect of Capellas missing an opportunity. While he did allude to theO /20-fold increase in power and how existing wildfire customers would be able tooN /benefit from that, he did not give it in ELIQUENT WORDING SUCH AS YOURS which1 /makes it obvious to the press what it all means.  /D" Thank you for the compliment.  ;-)  ( I also agree completely with you points.   -Normp  K /Also, when asked if this would result in lwoer sales, Capellas should haveeN /been quote direct: "Wildfire computers are not disposable machines. By makingE /these machines fully upgradable for quite some time, our customers's=E /investments will last a long time, and we will be building long termw# /relationships with our customers."e /wM /(or include some other wording to let the media know that Compaq's customers1L /are less likely to switch vendors because Compaq protects their investmentsN /instead of making the machises obsolete as fast as possible. Remember that asM /an enterprise computing company, our revenus do not come solely from sellingnK /as many boxes as possible, but servicing and maintaining our customers' IT-N /infrastructure is a major part of our business, so looking only at the numberE /of units shipped doesn't provide an indication of our profitability.  /8   ------------------------------  # Date: Thu, 18 May 2000 14:40:32 GMTD" From: Art Rice <arice@ue.itug.org>" Subject: Re: Wildfire Announcement8 Message-ID: <emv7is4lh1gvj2e4638iupdfmvi0h1huhh@4ax.com>  F On 18 May 2000 13:31:31 GMT, hammond@not@peek.ppb.cpqcorp.net (Charlie Hammond) wrote:    > - >In article <2oGfhgpe$$RR@eisner.decus.org>, e/ >koehler@eisner.decus.org (Bob Koehler) writes:m >sG >>"mainframe" is in the eye of the beholder.  My sister worked with SAStD >>data sets which her PC couldn't handle.  Those data sets had to be( >>processed on the VAX 3300 "mainframe". >hH >On the ALPHAstation 255 that is my primary workstation I have a printerI >which is used mostly on Windows systems.  I had to call customer supportnJ >for some information when I first installed it.  My inquiry got *nowhere*J >until the woman realized, "Oh, you're using it on a mainframe!"  Then theJ >call was trasferred and the information I needed was faxed minutes later. >j# >Yes, "in the eye of the beholder".    Wow!  F According to an old reference I have, not necessarily accurate but the0 only thing handy, "Newton's Telecom Dictionary":  F "Mainframe:   A powerful computer, almost always linked to a large setF of peripheral devices (disk storage, printers, and so forth), and usedB in a multipurpose environment at the corporate or major divisionalB level.  A mainframe is a large-scale computer typically containingF hundreds of megabytes of main memory and hundreds of gigabytes of diskF storage.  It is capable of "serving" thousands of "on-line" terminals.B The term -main frame- derives from the racks that typically hold a  large computer and it's memory."  C So, as technology advances, the mainframe keeps getting smaller and F smaller until, in some cases, it really is a desktop computer (in some instances.)s -- C
 Art Rice   *#f# Special Data Processing Corporations& --------------------------------------' All opinions expressed are mine and do i% not reflect the views of my employer.s   ------------------------------  % Date: Thu, 18 May 2000 12:16:36 +0000s/ From: Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk> F Subject: re: Wildfire Announcement: Michael Capellas, can you say VMS?7 Message-ID: <009EA44B.609268C0.30@maxwell.ph.kcl.ac.uk>a   > J > But from what I've seen of the "technical press" in the UK (the likes ofK > Computing, Computer Weekly, TheRegister and so on), they are generally astQ > clueless as any other interviewer unless you're talking of billyboxes and Intelr > based systems. >   L The technical press needs handling. As far as I can tell they are reasonablyE clued up about the nontechnical asects of IBM's product range as well J as Billyboxes. IBM marketing is good, Compaq's is poor, and its marketing  of VMS is worse than poor.  A As far as VMS is concerned, I suspect that the average journalistp@   - remembers Digital always referring to VMS as a legacy systemD   - and more recently, Digital+Compaq never referring to VMS at all K   - certainly doesn't get sent press releases trumpeting the virtues of VMS E   - and hasn't seen a VMS advert in years (let alone be informed that H         VMS advertising pays a significant part of his salary so be nice         to it!)lD   - and either can't find VMS in Compaq's web site, or does and sees<         all the things that we see and keep criticising hereK   - and if he phones Compaq, gets told that someone will call him back, whohE         doesn't, or not in the next four hours before the press date,a&          (This last pure speculation).  F In short, if he ignores VMS or insults it, it's pretty understandable.  L This is the tune that Compaq can change if it wants to. Start paying for VMSH adverts, start briefing the journalists, send them VMS freebies, fix theL web site, make sure that a VMS evangelist has a full-time PR job keeping theE journalists informed and sweet, and keep it up year after year so it o, doesn't get dismissed as a flash in the pan.  6 BTW "The Register" has at least half a clue. Check outF http://www.theregister.co.uk/000510-000012.html (utterly dismissive ofK Microsoft and Linux efforts at clustering to date. Friendly nod to Digital.aK Now, if they'd just been briefed about what's happened since the VAXclustern3 was state-of-the-art ... read between the lines of  4 http://www.theregister.co.uk/000202-000017.html ...)   	Yours,N
 		Nigel Arnote- 		NRA@MAXWELL.PH.KCL.AC.UK                   t  7 		"In the beginning there was nothing, which exploded."    ------------------------------  % Date: Thu, 18 May 2000 13:08:56 +0100a  From: steven.reece@quintiles.comF Subject: re: Wildfire Announcement: Michael Capellas, can you say VMS?> Message-ID: <802568E3.0042C8BC.01@qedilc01.qedi.quintiles.com>  O Although it doesn't trumpet the virtues of any particular operating system overkL another (which is reasonable since it is an AlphaServer announcement, not anO operating system one), I was very pleasantly surprised to see that the headline P on "Computing" here in the UK this week is "Compaq bets its Unix push on Alpha".  P Now ok, Unix gets a mention in the headline, but the article goes on to describeL "the AlphaServer GS Series, a server range running Unix, Linux and OpenVMS."  N Then, later in the article, this point is re-iterated with "The GS 80, 160 andJ 320 come with up to 8, 16 and 32 processors and can run OpenVMS, Linux and Compaq's Tru64 Unix."s  I My complements, congratulations and most of all thanks to those involved.    Steve. Steve Reece, Perot Systems.   ------------------------------  # Date: Thu, 18 May 2000 11:58:03 GMTu% From: Alan Greig <agreig@my-deja.com>tF Subject: Re: Wildfire Announcement: Michael Capellas, can you say VMS?) Message-ID: <8g0ls3$ro3$1@nnrp1.deja.com>s  & In article <FuqAA4.BBH@world.std.com>,3   "Terry C. Shannon" <shannon@world.std.com> wrote: ? > August 23. Microsoft dearly wanted to showcase NT on a 32-wayr
 enterprise  < Is the NT console code (which you mentioned exists) actuallyF shipping with end user systems (ie can we switch between ARC and SRM)?A If so then Microsoft could presumably just buy a machine and bootnC NT on it as they apparently still do daily build of Windows 2000 on B Alpha but just don't ship it. (Seen reported a few times including" in an interview with Dave Cutler).  ? Looks like Microsoft are still keeping their Alpha options justn slightly open.   --
 Alan Greig    & Sent via Deja.com http://www.deja.com/ Before you buy.b   ------------------------------  % Date: Thu, 18 May 2000 13:54:50 +0000 / From: Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk>IF Subject: Re: Wildfire Announcement: Michael Capellas, can you say VMS?7 Message-ID: <009EA459.192D6C92.20@maxwell.ph.kcl.ac.uk>c   >  > Nigel Arnot wrote:J > > I think we should wait and see how the story develops in the technicalN > > press, where Compaq briefings might be read, where Compaq can legitimatelyL > > smooch the journalists, and where Compaq can reasonably influence thingsK > > with its advertizing. that's where we'll first notice a change of tune,a > > should there be one. > P > I disagree. Those in the know, are, and have been, fully aware of wildfire for [snip] hN > Capellas missed a HUGE opportunity to push the alpha architecture when askedM > the question about itanium/ia64.  "While others may be struggling to remove M > the bugs from their first 64 bit chip, the Alpha chip has been around for 8dG > years, spans from the desktop to the datacentre providing scalabilityoL > unmatched by any other vendor. Compaq may not have marketed its leadershipP > very well but it will keep it, and the introduction of Wildfire raises the bar> > quite high at a time when others are just learning to jump." >   I Great stuff, but where this thread started was specifically about why VMS,M wasn't pushed to the forefront during a ten-minute live interview (presumablyi unscripted).  I Several reports of this launch suggest that VMS enjoyed a reasonably high H profile, but the press still report it as the launch of a Unix platform.K It'll take a planned and extended advertising and press-relations campaign  M to get VMS back into the news, not merely a few words during a live interviewkF about a new hardware platform. A few words now and again was Digital'sG mis-strategy, and therefore exactly what the technical press corps are d expecting to hear and ignore.w   	Yours, 
 		Nigel Arnot - 		NRA@MAXWELL.PH.KCL.AC.UK                   p  7 		"In the beginning there was nothing, which exploded."    ------------------------------  # Date: Thu, 18 May 2000 13:38:44 GMT-0 From: "Terry C. Shannon" <shannon@world.std.com>F Subject: Re: Wildfire Announcement: Michael Capellas, can you say VMS?& Message-ID: <FurCqL.6B1@world.std.com>  J "Brian Schenkenberger, VAXman-" <system@SendSpamHere.ORG> wrote in message* news:009EA3C9.2DEEC529@SendSpamHere.ORG...; > In article <FuqAA4.BBH@world.std.com>, "Terry C. Shannon"  <shannon@world.std.com> writes:> > >{...snip...}lL > >Apparently you were not in NYC yesterday. Rich Marcello spent a half hourH > >talking to customers (nope, not the press/analyst folks, who probably can'to= > >even spell VMS) about OpenVMS. Did a pretty good job, too.p >dE > Reality check.  Torquemada didn't invade the Vatican to convert ther	 faithful!  > B > Compaq needs to have an Alpha and VMS inquisition to convert the billyheathen
 > sinners.   Sounds like a plan!    ------------------------------  % Date: Thu, 18 May 2000 08:22:52 -0700m7 From: "Arthur E. Ragosta" <ragosta@merlin.arc.nasa.gov>rF Subject: Re: Wildfire Announcement: Michael Capellas, can you say VMS?3 Message-ID: <39240ACC.674D32FE@merlin.arc.nasa.gov>I   "Terry C. Shannon" wrote:o   >uH > Oh, by the way, WildFire is NT-capable (the microcode is there, a betaM > release booted, etc), but it ain't gonna happen. That was decided back last"J > August 23. Microsoft dearly wanted to showcase NT on a 32-way enterpriseM > server, but Compaq sorta kinda got sick and tired of paying $150M per annuma > in fealty to MisterBill.  B The proper use for $150M per year would be to fund lost-sole DecusI alumni to develop high-quality free software for VMS and distribute it ing* the face of some other, unnamed companies.   ------------------------------  % Date: Thu, 18 May 2000 11:36:03 -0400 + From: Tim Shoppa <shoppa@trailing-edge.com>tF Subject: Re: Wildfire Announcement: Michael Capellas, can you say VMS?1 Message-ID: <3923D5A3.64F02E1D@trailing-edge.com>   $ Brian Schenkenberger, VAXman- wrote: > [ > In article <FuqAA4.BBH@world.std.com>, "Terry C. Shannon" <shannon@world.std.com> writes:  > >{...snip...} L > >Apparently you were not in NYC yesterday. Rich Marcello spent a half hourN > >talking to customers (nope, not the press/analyst folks, who probably can't= > >even spell VMS) about OpenVMS. Did a pretty good job, too.V > O > Reality check.  Torquemada didn't invade the Vatican to convert the faithful!  > O > Compaq needs to have an Alpha and VMS inquisition to convert the billyheatheno
 > sinners.  E          NOBODY expects the Spanish Inquisition!  Our chief weapon isnE          suprise...surprise and fear...fear and surprise....  Our twocE          weapons are fear and surprise...and ruthless efficiency....  =          Our *three* weapons are fear, surprise, and ruthlessbF          efficiency...and an almost fanatical devotion to the Pope....C          Our *four*...no...  *Amongst* our weapons....  Amongst our =          weaponry...are such elements as fear, surprise....  s          I'll come in again. r   Tim.   ------------------------------  % Date: Thu, 18 May 2000 12:03:59 -0400u" From: Dan Sugalski <dan@sidhe.org>F Subject: re: Wildfire Announcement: Michael Capellas, can you say VMS?8 Message-ID: <4.3.1.0.20000518120127.021a1e70@24.8.96.48>  - At 12:16 PM 5/18/00 +0000, Nigel Arnot wrote:a > >sL > > But from what I've seen of the "technical press" in the UK (the likes ofM > > Computing, Computer Weekly, TheRegister and so on), they are generally asoJ > > clueless as any other interviewer unless you're talking of billyboxes  > and Intels > > based systems. > >p >h$ >The technical press needs handling.  K This is so true in general that it's pathetic. One of the biggest mistakes ,G I see people make is assuming they're talking to someone technical who iI writes for one of the rags. What's really happening is you're talking to  : someone who writes for a rag that happens to be technical.  J Assuming a reporter needs good handling will get you much, *much* further I than assuming a reporter knows something about what you're talking about.o   					Dan  I --------------------------------------"it's like this"-------------------s2 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and evenp;                                       teddy bears get drunke   ------------------------------  % Date: Thu, 18 May 2000 11:19:52 +0200o= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>u* Subject: Re: Windows 98 Vs. Windows NT 4.0( Message-ID: <3923B5B8.BC10B60@gtech.com>   Joe Thomas wrote: M > What is the key differences in the Windows 98 system and the Windows NT? IteI > would just be for home use not for a business. I know it costs more but-M > still. Is there any hardware you need, and is there any specifications thato > need to be made?   ????  . Why do you post this question to comp.os.vms ?   Arne   ------------------------------  # Date: Thu, 18 May 2000 15:11:59 GMTr" From: Art Rice <arice@ue.itug.org>* Subject: Re: Windows 98 Vs. Windows NT 4.08 Message-ID: <pq18iskhvg2lnseog6n92om6l3o0744bid@4ax.com>  / On Thu, 18 May 2000 11:19:52 +0200, Arne Vajhj  <arne.vajhoej@gtech.com> wrote:0   >Joe Thomas wrote:N >> What is the key differences in the Windows 98 system and the Windows NT? ItJ >> would just be for home use not for a business. I know it costs more butN >> still. Is there any hardware you need, and is there any specifications that >> need to be made?  >n >????  >a/ >Why do you post this question to comp.os.vms ?  >o >Arne ? Maybe he's hoping someone will recommend a DS10 and TRU64 Unix.oF Although that would still be the wrong news-group, it would be closer.* And, there would be another Alpha convert.   -- q
 Art Rice   *#o# Special Data Processing Corporationp& --------------------------------------' All opinions expressed are mine and do -% not reflect the views of my employer.0   ------------------------------   End of INFO-VAX 2000.277 ************************