1 INFO-VAX	Fri, 12 May 2000	Volume 2000 : Issue 265       Contents: Re: alpha problem  Re: big Fortran data file  Re: big Fortran data file  Re: big Fortran data file  Re: big Fortran data file  Re: big Fortran data file ) Re: Booting a Vax 4090 from Infoserver CD ) Re: Booting a Vax 4090 from Infoserver CD  Re: comparative TCP/IP tests Re: DECserver 90M boot file  DEFINE ? Re: DEFINE ? RE: DEFINE ? HSG/Fibre training???  Re: HSG/Fibre training???  Re: HSG/Fibre training???  Re: HSG/Fibre training??? % Re: Is "The GNU on VMS Project" dead? % Re: Is "The GNU on VMS Project" dead? % Re: Is "The GNU on VMS Project" dead? % Re: Is "The GNU on VMS Project" dead? 3 Looking for recording of VT200-series terminal beep  Re: Marketing opportunity  New FORTRAN documentation? Re: New FORTRAN documentation? Re: New FORTRAN documentation?4 Open VMS connectivity problem- Urgent please respond4 Re: Problem with Seagate disk on VAXstation 4000 VLC4 Re: Problem with Seagate disk on VAXstation 4000 VLC Re: S80 competitor of E10000?!3 Re: sharing large amounts of data between processes 3 Re: Suggest a better file serving solution than NT? 3 RE: Suggest a better file serving solution than NT? 3 Re: Suggest a better file serving solution than NT? 3 re: Suggest a better file serving solution than NT? 3 Re: Suggest a better file serving solution than NT? 9 System halts after %EWA0, Twisted-Pair mod set by console  Re: the latest billybox virus  Re: the latest billybox virus  re: the latest billybox virus  Re: the latest billybox virus  Re: Unsolicited OpenVMS/NT book  VMS backup on PC" Re: Wildfire and the future of VMS  F ----------------------------------------------------------------------  % Date: Fri, 12 May 2000 06:58:47 -0500 ) From: "John E. Malmberg" <wb8tyw@qsl.net>  Subject: Re: alpha problem7 Message-ID: <015801bfbc09$70d75130$020a0a0a@xile.realm>   1 Joseph Antony <tonijoe@rediffmail.company> wrote:  > " > Please find attached the problem >    Problem appears to be:  C 1. Newsgroups / Mailing lists are plain text only.  No attachments.   I 2. Unsolicited Microsoft Word Documents are NEVER safe to open with WORD. H They can launch all sorts of nasty Macros.  Even ones that the sender is clueless are present.   K 3. Quickview shows that the attachment is empty.  Quickview and Notepad are E the only Microsoft Windows tools I will use to examine an attachment.  Recommended practice.   J 4. Many of the more knowledgeable people on this mailing list / news group< can not or will not open a Microsoft Word document.  See #2.  J 5 A brief description of the problem and usually relevant product versions should be in the title.    -John  wb8tyw@qsl.network   ------------------------------    Date: 12 May 2000 09:26:01 +0100& From: Clive Page <cgp@nospam.le.ac.uk>" Subject: Re: big Fortran data file+ Message-ID: <8fgf6p$5fpcf@harrier.le.ac.uk>   . In article <8fe81u$svq$1@info.service.rug.nl>,+ Phillip Helbig <helbig@astro.rug.nl> wrote:   H >The application uses the values in a certain order and I can precomputeF >them in this order.  Should I make one large file and let the virtualG >memory system take care of the fact that it won't all fit into memory, I >keeping in mind that the values are accessed in the order they are used, - >or should I split it up into smaller files?    H >We're talking about 1.5 GB or so of data, i.e. 360 million values to be
 >computed.  J I think you are getting into a problem where the hardware starts to matterD - I'd strongly recommend getting a workstation or whatever which hasI at least 1.5 GB of memory so, whichever way you store it on disc, you can 5 read it all into memory at the start of your program.   F I, and I suspect most people reading this group, don't have any recentH experience of Alpha/VMS.  You may have to experiment with different file formats.   --   --   Clive Page, + Dept of Physics & Astronomy,                + University of Leicester.                       ------------------------------  % Date: Fri, 12 May 2000 09:46:52 -0400 $ From: Herman D. Knoble <hdk@psu.edu>" Subject: Re: big Fortran data file8 Message-ID: <co2ohskbagt1qfrb33vee5hhjn4ccr0vvq@4ax.com>  D An example of some virtual memory file "handling" times on a 100 MB+ file is at: 6 http://ftp.cac.psu.edu/pub/ger/documents/handstat.html  H On 11 May 2000 19:52:37 GMT, helbig@astro.rug.nl (Phillip Helbig) wrote:  J -|In article <y4n1lwdgyz.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>,C -|Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> 
 -|writes:  -|F -|Most followups have commented on various Fortran solutions, with or @ -|without VMS-specific extensions, or using global sections etc. -|H -|One thing I hadn't thought through was the fact that the array is onlyJ -|half full, since the range of the last index depends on the value of theH -|previous one.  Thus, I could halve the space by using the indices as a5 -|record number or whatever and using direct access.   -|F -|What about just doing it straightforwardly and let the fact that theC -|whole file won't fit into memory be handled by the Virtual Memory K -|System?  Would folks expect this to be more or less efficient than doing  K -|things by hand?  I guess a disadvantage is that more disk space would be  : -|needed since the page file would have to be quite large.    .    Herman D. (Skip) Knoble, Research Associate    Mailto:hdk@psu.edu '    Web: http://www.personal.psu.edu/hdk      Center for Academic Computing    Penn State University      214C Computer Building #      University Park, PA 16802-2101 .    Phone:+1 814 865-0818   Fax:+1 814 863-7049   ------------------------------  % Date: Fri, 12 May 2000 10:07:33 -0400 # From: Jim Agnew <agnew@hsc.vcu.edu> " Subject: Re: big Fortran data file+ Message-ID: <391C1025.535AE998@hsc.vcu.edu>   E if you can comput and issue a QIO call to perform the next read while 9 you're doing the cpu, you could speed up quite a lot!!!..    jim    Phillip Helbig wrote:  > H > In article <11MAY200008520469@gerg.tamu.edu>, carl@gerg.tamu.edu (Carl > Perkins) writes: > I > >Additional speed improvements could be gotten by storing more than one D > >value per record and using a subroutine to get the value you want > J > Actually, the first four variables are stepped through sequentially, andF > the fifth variable is used in a more-or-less random order.  Thus, itH > would make sense to put all of these values (between 1 and 599) in oneJ > record.  Once this record is in memory, the computation time is probablyG > comparable to the time to read the next record so I/O won't be a real 
 > bottleneck.  > I > >This could result in less I/O overhead, although it may be possible to I > >get much the same effect simply by specifying a good set of options in : > >your OPEN statment, particularly a large "buffercount". >  > Non-standard?  > 
 > > You might C > >also get some benefit from making it a fixed record length file.  >  > Why?   ------------------------------  # Date: Fri, 12 May 2000 16:32:33 GMT  From: briggs@eisner.decus.org " Subject: Re: big Fortran data file+ Message-ID: <2t0HBaJfTxXU@eisner.decus.org>   T In article <8fgf6p$5fpcf@harrier.le.ac.uk>, Clive Page <cgp@nospam.le.ac.uk> writes:0 > In article <8fe81u$svq$1@info.service.rug.nl>,- > Phillip Helbig <helbig@astro.rug.nl> wrote:  > I >>The application uses the values in a certain order and I can precompute G >>them in this order.  Should I make one large file and let the virtual H >>memory system take care of the fact that it won't all fit into memory,J >>keeping in mind that the values are accessed in the order they are used,. >>or should I split it up into smaller files?  > I >>We're talking about 1.5 GB or so of data, i.e. 360 million values to be  >>computed.  > L > I think you are getting into a problem where the hardware starts to matterF > - I'd strongly recommend getting a workstation or whatever which hasK > at least 1.5 GB of memory so, whichever way you store it on disc, you can 7 > read it all into memory at the start of your program.   D I'm puzzled.  We've got 1.5GB of data that is accessed sequentially.  F Why on God's green Earth would you want to put it in main memory?  PutB it in a disk file and read it.  Save space in your working set for7 stuff you're actually going to be using more than once.   B Since performance matters, use unformatted I/O with large buffers. For example:  D 	OPEN ( UNIT=1, FILE='myfile.dat', STATUS='OLD', FORM='UNFORMATTED',. 	1      ORGANIZATION='SEQUENTIAL', BKS=65024 )  E Since VMS Fortran doesn't memory map opened files and since you don't < _want_ Fortran to memory map this file, the size of the file> and the size of main memory are irrelevant.  Use one big file.  , 	John Briggs			briggs@alpha.tst.tracor.com     ------------------------------   Date: 12 May 2000 15:03:43 GMT0 From: "Dale A. Dellutri" <ddellutr@enteract.com>" Subject: Re: big Fortran data file- Message-ID: <8fh6gf$1565$1@news.enteract.com>   X On 11 May 2000 21:48:00 GMT, in comp.os.vms, Phillip Helbig <helbig@astro.rug.nl> wrote:E > A final comment.  For the time being, it is true that the stuff is  J > essentiallyb being read sequentially.  In the longer term, I might want 0 > it all, at least virtually, in memory at once.  F Then I'd say for now, read it sequentially.  Later, use a disk-file orF page-file global section to put the whole thing in virtual memory, and$ let the system page it as necessary.   --  & Dale Dellutri -- ddellutr@enteract.com   ------------------------------  # Date: Fri, 12 May 2000 07:22:50 GMT 0 From: carlini@true.lkg.dec.com (Antonio Carlini)2 Subject: Re: Booting a Vax 4090 from Infoserver CD* Message-ID: <8fgatj$7gt@usenet.pa.dec.com>  g In article <391B0E32.E75C58E4@ikp.tu-darmstadt.de>, "Dr. Otto Titze" <titze@ikp.tu-darmstadt.de> wrote:   C >how can I boot an OS VMS CD on an InfoServer for a complete system  >generation G >from a VAX WS 4060? I know how to do this for every Alpha but I looked  >throughH >all my older documentation and found nothing. In the VMS_Install manual= >on the OS CD e.g. 6.2 there is only an example for a VAX6000  >(B/r5:100/x:../d:...)  N This is from memory - I haven't done this in a few years and I don't have the L right stuff running to check. I'm fairly sure this is correct in priciple - - just the essential details might be wrong :-)   O From the console prompt (>>>) SHOW DEVICE should show you what the name of the  L ethernet device is; I'm guessing that it is EZA0 but it might be ESA0. Once  you know what it is you can do:            >>> B/100 EZA0  M and when it asks for Bootfile: you enter ISL_SVAX_xxx where xxx is likely to  N be 062 or 071 or 072 depending on which version of OpenVMS CD your infoserver  is serving.   N You should end up with a menu that lets you pick a particular service to boot N from. If you pick the right one you will end up in Standalone Backup then you O can procede as you would for a fresh install of OpenVMS (which is what I think   you are trying to do).  O "Modern" OpenVMS distribution CDs have a bootable version of OpenVMS available  M as the [SYS1] root (I think ...). You should be able to boot this instead by   starting with:           >>> B/10000100 EZA0   M but if all you want to do is get OpenVMS up and running, then you don't need   to do this.   K This should work on all "small" VAXes that support netbooting - except the  M network device name changes (EZA0, ESA0, XQA0 etc.). For the VAX 6000 series  L (and some others too I guess) you boot ISL_LVAX_xxx instead (LVAX for Large J VAX vs SVAX for Small VAX, I suppose) and the way you specify the netwrok 0 device is also different (and more complicated).   Antonio       I Antonio Carlini                            Mail: carlini@true.lkg.dec.com # DECnet-Plus for OpenVMS Engineering 6 COMPAQ                                     Reading, UK   ------------------------------  % Date: Fri, 12 May 2000 11:38:50 +0200 2 From: "Dr. Otto Titze" <titze@ikp.tu-darmstadt.de>2 Subject: Re: Booting a Vax 4090 from Infoserver CD3 Message-ID: <391BD12A.53B4D563@ikp.tu-darmstadt.de>   D Thanks Antonio, for the detailed explanation. In the meantime I justF found it out too. It works just as you told. (Now my system generation is already running.    Regards    Otto --  ,  -------------------------------------------, | Dr. Otto Titze, Kernphysik TUD           |, | Schlossgartenstr. 9, D-64289 Darmstadt   |, | titze@ikp.tu-darmstadt.de                |, | Tel: +49(6151)16-2916,FAX:16-4321        |,  -------------------------------------------   ------------------------------   Date: 12 May 2000 14:55:38 GMT2 From: mathog@seqaxp.bio.caltech.edu (David Mathog)% Subject: Re: comparative TCP/IP tests , Message-ID: <8fh61a$4s2@gap.cco.caltech.edu>  r In article <391B558C.F48B78C7@ssrl.slac.stanford.edu>, Clemens Wermelskirchen <wermelsk@SLAC.Stanford.EDU> writes:I >Keep in mind that TCP does not handle packets. It handles a byte stream. B >The network packet size is much smaller anyways and, assuming theI >network packets arrive fast enough, they might get assembled into larger L >I/O blocks returned to the application. The 64k QIO limit is irrelavant for >TCP/IP.  E Perhaps Netpipe crashes on OpenVMS when the data size exceeds 64k for K some other reason.  However, I can't recall the last time I hit a 64k limit G on OpenVMS that wasn't due to the use of a QIO, and both OpenVMS TCP/IP L stacks had this limit - even when the packets only went through localhost.     Regards,   David Mathog mathog@seqaxp.bio.caltech.edu ? Manager, sequence analysis facility, biology division, Caltech     ------------------------------  % Date: Fri, 12 May 2000 09:46:40 +0200 5 From: Oswald Knoppers <Oswald.Knoppers@whitehouse.nl> $ Subject: Re: DECserver 90M boot file- Message-ID: <391BB6E0.F9138F54@whitehouse.nl>    "Richard L. Dyson" wrote:   I > Is there anyway I can tell it to use MNENG2 instead of "3" and thus use J > the one it already has?  Some console terminal key combo to break out ofG > the boot load loop and allow some low level commands (like SET SERVER  > SOFTWARE MNENG2) to be sent?  F On the console (usually port 1) you cant type ctrl-b a couple of timesE to get on a boot prompt. You can then use 'b fla:mneng2' to boot this  image from flash.   B After it is booted use the priv'ed command 'define server software mneng2'.   Regards,   Oswald   ------------------------------  % Date: Fri, 12 May 2000 09:58:17 -0700 / From: Terry Marosites <TMarosites@unitedad.com>  Subject: DEFINE ? M Message-ID: <1137A4A23A51D311B2D600105A1D5213019AEE07@seantexch.unitedad.com>   
 Hello all,  L  I have been modifying some 3rd party DCL procedures for my company and keep' seeing the define statements like this   $ define myfile foo.tmp;0 L I have tested and played with it. It acts like the ;0 is not there. Is there: any effects that is different from a define without the ;0= This 3rd part software if full of strange DCL code like this.    Terry       5 *****************************************************     5 ***************************************************** 4 Any views or opinions are solely those of the author) and do not necessarily represent those of  United News& Media. 5 ***************************************************** 4 The information transmitted is intended only for the1 person or entity to which it is addressed and may 3 contain confidential and/or privileged material. If 3 you are not the intended recipient of this message, . please do not read, copy, use or disclose this3 communication and notify the sender immediately. It 0 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 is  prohibited. 5 *****************************************************  **   ------------------------------  % Date: Fri, 12 May 2000 13:13:06 -0400   From: norm.raphael@jamesbury.com Subject: Re: DEFINE ? 4 Message-ID: <C22568DD.005DC081.00@jklh21.valmet.com>   Nothing strange at all here.C Version ";0" is the default for version ";" and is the most recent. D Version ";-0" is the earliest.  Version ";-1" is the one just before the most recent, etc.   5 Someone was just using a complete file specification.         1 TMarosites@unitedad.com on 05/12/2000 12:58:17 PMa   To:   Info-VAX@mvb.saic.comf cc:  Subject:  DEFINE ?        
 Hello all,  L  I have been modifying some 3rd party DCL procedures for my company and keep& seeing the define statements like this $ define myfile foo.tmp;0 L I have tested and played with it. It acts like the ;0 is not there. Is there: any effects that is different from a define without the ;0= This 3rd part software if full of strange DCL code like this.    TerryS    5 *****************************************************e    5 *****************************************************S4 Any views or opinions are solely those of the author) and do not necessarily represent those of  United News& Media.t5 ***************************************************** 4 The information transmitted is intended only for the1 person or entity to which it is addressed and mayX3 contain confidential and/or privileged material. IfX3 you are not the intended recipient of this message, . please do not read, copy, use or disclose this3 communication and notify the sender immediately. It 0 should be noted that any review, retransmission,2 dissemination or other use of, or taking action in- reliance upon, this information by persons ori- entities other than the intended recipient is  prohibited. 5 *****************************************************  **   ------------------------------  % Date: Fri, 12 May 2000 13:17:18 -0400h/ From: "Moore, John D" <john_d_moore@reyrey.com>  Subject: RE: DEFINE ? J Message-ID: <C12E81FC6CF2D211956100A0C9E0FE8B01CE6DA4@oh15ex04.reyrey.com>   Just signed on to the list...-  9 This is an easy one.  That's a relative version number.  0     ;0  = top-most version   ;-0 = bottom-most version    ;-n = n versions from top   7 Lots of other DCL quirks.  I suppose this could start a 6 thread of stupid DCL tricks everyone's heard a million2 times.  Are such things posted anywhere and if so,- would anyone care to share the URL?  Fun Fun.r   -John M. Sr. Vax/Unix System Admin  Reynolds & Reynolds Co.W   > -----Original Message-----6 > From:	Terry Marosites [SMTP:TMarosites@unitedad.com]% > Sent:	Friday, May 12, 2000 12:58 PMe > To:	Info-VAX@Mvb.Saic.Comk > Subject:	DEFINE ?t >  > Hello all, > I >  I have been modifying some 3rd party DCL procedures for my company anda > keep) > seeing the define statements like this M > $ define myfile foo.tmp;0 H > I have tested and played with it. It acts like the ;0 is not there. Is > there < > any effects that is different from a define without the ;0? > This 3rd part software if full of strange DCL code like this.J > 	 > Terry  l >  > 7 > *****************************************************9 >  > 7 > *****************************************************:6 > Any views or opinions are solely those of the author+ > and do not necessarily represent those of. > United News& Media.i7 > *****************************************************n6 > The information transmitted is intended only for the3 > person or entity to which it is addressed and maya5 > contain confidential and/or privileged material. Ift5 > you are not the intended recipient of this message,t0 > please do not read, copy, use or disclose this5 > communication and notify the sender immediately. It 2 > should be noted that any review, retransmission,4 > dissemination or other use of, or taking action in/ > reliance upon, this information by persons ort/ > entities other than the intended recipient iss
 > prohibited.v7 > *****************************************************  > **   ------------------------------  # Date: Fri, 12 May 2000 14:31:19 GMTo2 From: kaplow_r@eisner.decus.org.mars2 (Bob Kaplow) Subject: HSG/Fibre training???+ Message-ID: <5fFArcNA0JCH@eisner.decus.org>i  J We just got an ES40 with Fibrechannel, a pair of switches, and a rack fullK of HSG80 subsystems. We've got previous experience with HSJ, HSZ, CI, DSSI, I SCSI, etc, but all this fibre stuff is both new and different. Has anyone L found any good training courses on HSG/Fibre technology and SAN? Either from% Compaq, Global, or some other vendor?0  J For those already using HSG/Fibre, what kind of things should I be looking; to learn? I don't even know the right questions to ask yet.s   	Bob Kaplow	  E SPAM:	spamrecycle@ChooseYourmail.com	uce@ftc.gov	postmaster@127.0.0.1:   ------------------------------  % Date: Fri, 12 May 2000 15:38:36 +0200e, From: "Bart Zorn" <B.Zorn@TrueBit.nospam.nl>" Subject: Re: HSG/Fibre training???0 Message-ID: <8fh1g6$3i7$1@nereid.worldonline.nl>   Hi,n  L We have a cluster of 2 ES40's and 1 DS20 with a fully dual redundant FC disk configuration.  K I have no prior experience with HSJ or HSZ configurations, but I managed tolJ get things running using the supplied docs and using SWCC which makes it a% lot easier to see what you are doing.   J The most important information is found in "Guidelines for OpenVMS cluster" configurations", chapters 6 and 7.   A few points of interest:c  @ - HSG80 controllers must use MULTIBUS failover, not TRANSPARANT.  I - I suggest that you examine the connections which the HSG80's "see", and L rename them to something a little bit more comprehensible, at least for you.  J - In a fully redundant configuration, every host has 4 paths to each disk.I If you use any form of access control, you should allow or deny access toW all 4 paths equally.  J - The ES40 console does not see any FC attached disks by default. You haveI to use the wwidmgr console program to make them visible. You need to make+I the virtual disk from which you want to boot, visisble. The other virtualaG disks are automatically seen by VMS. I have a  "WWIDMGR Users's manual" / (PDF) but I don't remember where I got it from.   D Hope this helps a little. Send me mail if you need more information.   Regards,  	 Bart Zorna OpenVMS consultant TrueBit B.V. B.Zorn at TrueBit dot nl  ? "Bob Kaplow" <kaplow_r@eisner.decus.org.mars2> wrote in message2% news:5fFArcNA0JCH@eisner.decus.org...aL > We just got an ES40 with Fibrechannel, a pair of switches, and a rack fullG > of HSG80 subsystems. We've got previous experience with HSJ, HSZ, CI,u DSSI, K > SCSI, etc, but all this fibre stuff is both new and different. Has anyonetI > found any good training courses on HSG/Fibre technology and SAN? Eithern from' > Compaq, Global, or some other vendor?  > L > For those already using HSG/Fibre, what kind of things should I be looking= > to learn? I don't even know the right questions to ask yet.i >t > Bob Kaplow >eG > SPAM: spamrecycle@ChooseYourmail.com uce@ftc.gov postmaster@127.0.0.1    ------------------------------  # Date: Fri, 12 May 2000 15:47:45 GMTe- From: young_r@eisner.decus.org (Robert Young)s" Subject: Re: HSG/Fibre training???+ Message-ID: <13G6ovh+1ZH9@eisner.decus.org>a  ` In article <5fFArcNA0JCH@eisner.decus.org>, kaplow_r@eisner.decus.org.mars2 (Bob Kaplow) writes:L > We just got an ES40 with Fibrechannel, a pair of switches, and a rack fullM > of HSG80 subsystems. We've got previous experience with HSJ, HSZ, CI, DSSI,-K > SCSI, etc, but all this fibre stuff is both new and different. Has anyonecN > found any good training courses on HSG/Fibre technology and SAN? Either from' > Compaq, Global, or some other vendor?g > L > For those already using HSG/Fibre, what kind of things should I be looking= > to learn? I don't even know the right questions to ask yet.l >   B 	Good fibre channel docs on line at www.openvms.digital.com:8000 ,% 	of course the manuals are very good.n  = 	One word of caution... I spent 3 days working with HSG80s so,@ 	don't have a ton of experience but one thing I learned is there? 	is a nice GUI piece that works with the HSG80s  (follow-on to >G 	SWCC I believe, not sure setup when I got there.) and another Windows rG 	based piece that gives you a command line on the controller...  I was hG 	working off a laptop ran both, bored quickly with the GUI and ran the  E 	command line piece , SHOW THIS, SHOW UNIT, etc... then RUN VTDPY... oD 	couldn't get out of VTDPY, control-c/control-y was not hitting the C 	controller... spent 10 minutes trying to dig up a VT , gave up on  ? 	that and rebooted the controller (non-production environment).w   	Give me a VT any old day.   				Robn   ------------------------------  % Date: Fri, 12 May 2000 12:01:11 -0500d1 From: "Dave Gudewicz" <david.gudewicz@abbott.com>N" Subject: Re: HSG/Fibre training???8 Message-ID: <8fhd6a$mb4$1@fizban.fizban.pprd.abbott.com>  F Back in January, I took a Fibre Channel course (not specific to Comapq
 stuff) at:       Infinity I/O       www.infinityio.com  J The guy that runs the company is on the FC ANSI committee and is very well versed in this technology.   Dave...r  = Bob Kaplow <kaplow_r@eisner.decus.org.mars2> wrote in message % news:5fFArcNA0JCH@eisner.decus.org...<L > We just got an ES40 with Fibrechannel, a pair of switches, and a rack fullG > of HSG80 subsystems. We've got previous experience with HSJ, HSZ, CI,m DSSI,lK > SCSI, etc, but all this fibre stuff is both new and different. Has anyonegI > found any good training courses on HSG/Fibre technology and SAN? EitherI from' > Compaq, Global, or some other vendor?l >tL > For those already using HSG/Fibre, what kind of things should I be looking= > to learn? I don't even know the right questions to ask yet.  >l > Bob Kaplow >lG > SPAM: spamrecycle@ChooseYourmail.com uce@ftc.gov postmaster@127.0.0.1    ------------------------------   Date: 12 May 2000 08:19:48 GMT* From: helbig@astro.rug.nl (Phillip Helbig). Subject: Re: Is "The GNU on VMS Project" dead?. Message-ID: <8fger4$kao$1@info.service.rug.nl>  4 In article <391B71DD.248D406C@mci.com>, Roger Tucker <roger.tucker@mci.com> writes: >  7 >GNV includes most of the GNU products including a BASHhE >shell, make,  and many other Unix utilities.  I think all we need isn= >an autoconfig and most Unix software would port to VMS usingAG >the standard Unix build scripts.  At least that's the goal.  We shouldnH >all help out this effort where we can and all the linux software should# >easily port to VMS when it's done.:  G What's the point of running unix utilities on VMS?  I can see the need tF for stuff like tar etc for compatibility with the unix world, but why  bash as opposed to DCL?e   ------------------------------  % Date: Fri, 12 May 2000 10:48:16 +0200W= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> . Subject: Re: Is "The GNU on VMS Project" dead?) Message-ID: <391BC550.38499061@gtech.com>o   Phillip Helbig wrote:Z6 > In article <391B71DD.248D406C@mci.com>, Roger Tucker  > <roger.tucker@mci.com> writes:9 > >GNV includes most of the GNU products including a BASHoG > >shell, make,  and many other Unix utilities.  I think all we need iso? > >an autoconfig and most Unix software would port to VMS using I > >the standard Unix build scripts.  At least that's the goal.  We shoulddJ > >all help out this effort where we can and all the linux software should% > >easily port to VMS when it's done.D > H > What's the point of running unix utilities on VMS?  I can see the needG > for stuff like tar etc for compatibility with the unix world, but why  > bash as opposed to DCL?   : To execute long Unix scripts that is difficult or take too long time to convert to DCL.  = Make life easier for those that dream in Unix shell commands.    Etc.etc.   Arne   ------------------------------  # Date: Fri, 12 May 2000 15:52:16 GMT ) From: Roger Tucker <roger.tucker@mci.com>L. Subject: Re: Is "The GNU on VMS Project" dead?' Message-ID: <391BD472.61CDCE6C@mci.com>   @ If you want to spend the rest of your life converting Unix shellA scripts to DCL and unix make files to MMS, go ahead.  I've done aiB few of theses when porting Unix software to VMS, and it's not much fun.  E VMS needs to support the Unix build environment so that we can easily-? port such Open Source applications as Mozilla, GIMP, GNOME, andtB many/many others, to VMS.  There is a whole host of software beingG developed under "Free Software" or "Open Source" that VMS is being left F out of because all the build scripts are written for Unix and not VMS.D Even such things as JAVA would port easier and quicker and VMS wouldE be as far beind in the software world if the Unix build scripts would-5 execute unchanged or with very little changes on VMS.T  D Just take a look at a Linux distribution from Red Hat for example of$ some of the free software available:$ http://www.redhat.com/apps/download/? Wouldn't it be great if all this software was as easy as FTP it-< down, Unzip it, Un-tar it, and execute the build scripts!!!!  D Don't get me wrong, I love VMS, but VMS is being left behind becauseB all the Hackers have moved away to Linux and they are working veryE very hard as a community to create software that everyone can use andw. where the software code is available for free.# (GNOME is a great example of this.)t  @ Also, more third party software might be available on VMS if the< porting effort was made easy by supporting the build scripts that they used on Unix.   E I have thought for a long time now that the Unix utilities (availableiE from such places as http://gnv.sourceforge.net/) should be a standardhC part of VMS and SHIP with the operating system.  This would includec? a Bash shell, make, autoconfig, ls, grep, and all the librariestE (GTK+, GDK, GLIB, IMLIB, etc).  If it takes a lot of work for a thirdvD party or Open Source project to port to VMS, it just won't get done!D Digital had a Posix layer for VMS but they tried to make money on itD so not very many people used it and they retired it.  It's time this was a standard part of VMS.:  D Now who want's to port GNOME and GIMP without some unix utilities to help?R   ------------------------------   Date: 12 May 2000 15:51:13 GMT2 From: mathog@seqaxp.bio.caltech.edu (David Mathog). Subject: Re: Is "The GNU on VMS Project" dead?, Message-ID: <8fh99h$4s2@gap.cco.caltech.edu>  S In article <391B71DD.248D406C@mci.com>, Roger Tucker <roger.tucker@mci.com> writes:e/ >Also check out the site "GNV - GNU's Not VMS!") >http://gnv.sourceforge.net/ >s7 >GNV includes most of the GNU products including a BASHgE >shell, make,  and many other Unix utilities.  I think all we need isg= >an autoconfig and most Unix software would port to VMS usingeG >the standard Unix build scripts.  At least that's the goal.  We should-H >all help out this effort where we can and all the linux software should# >easily port to VMS when it's done.c  J Unfortunately there is no "typical" unix build.  I've used GNV a bit, and H it helped to the extent that I could run a "make -n" and then work from 9 that.   In addition to autoconfigure it would also need: m  M 1. tcsh to handle those builds that depend on a variety of /bin/csh scripts. tJ The NCBI toolkit, for instance, runs a custom csh script and does a seriesE of make operations out of that.   Since the script won't run in bash, ; that's pretty much it for using GNV to help with the port. *  % 2. some sort of translator to convert*  U     cc -I . -I../foo -I../../boo -DHAVE_WOMBAT_H -DHAVE_PLATYPUS.H -o silly.o silly.ch    into  ]     cc/include=([],[-],[--.boo])/define=(HAVE_WOMBAT_H,HAVE_PLATYPUS.H)/obj=silly.obj silly.c*  A Don't know about you folks, but many is the time I've wished for:f      $ define/job dcl$case_asis b    $ cc/unix_format -I . -I../foo -I../../boo -DHAVE_WOMBAT_H -DHAVE_PLATYPUS.H -o silly.o silly.c  K I suppose that it is too much to hope for, but now that Compaq is supplyingsG compilers for OpenVMS, Tru64, Linux, Windows, and Tandem they are in a hF position to take the lead in developing a truly platform neutral buildK mechanism.  Build it into all of their own compilers and they'll save theiraJ OWN developers a lot of time.  They could also add it to gcc, since that'sB open source, and voila, instant cross platform compiler standard.    Regards,   David Mathog mathog@seqaxp.bio.caltech.edus? Manager, sequence analysis facility, biology division, Caltech 0   ------------------------------   Date: 12 May 2000 14:16:15 GMT6 From: DAVISM@er6.eng.ohio-state.edu (Michael T. Davis)< Subject: Looking for recording of VT200-series terminal beep: Message-ID: <8fh3nf$q8u$1@charm.magnus.acs.ohio-state.edu>  @ 	Can anyone provide a pointer to a recording of the VT200-seriesC terminal "beep"?  I would like to incorporate this into my terminal C emulator under Windows, to give it a more distinctive beep than the I standard Windows fare.  (The terminal emulator I'm using provides a meanshG to specify a sound [WAV] file to be played when an ASCII code 7 is sent 
 by the host.)n   Thanks,s  Mike  --K              Michael T. Davis              |    Systems Specialist: ChE,MSEeN   E-mail: davism@er6.eng.ohio-state.edu    | Departmental Networking/ComputingJ            -or- DAVISM+@osu.edu            |     The Ohio State UniversityJ http://www.er6.eng.ohio-state.edu/~davism/ |     197 Watts, (614) 292-6928   ------------------------------  % Date: Fri, 12 May 2000 10:46:09 +0200*= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>t" Subject: Re: Marketing opportunity) Message-ID: <391BC4D1.3AADC3CF@gtech.com>X   Bruce Vinson wrote:a > Arne Vajhj wrote:, > > Andrew Harrison SUNUK Consultancy wrote:- > > > Netscape mail client running on OpenVMS  > >sE > > Can you give please give detailed instruction on how to do that ?d > >o= > > I have tried with both Navigator Gold 3.03 on VMS 7.1 ande= > > Mozilla M15 on VMS 7.2-1 and I can not get any of them tor > > execute code ! > J > Since I also tried all of those combos, I'm waiting for the explanation, > too!  $ It looks as if we can wait forever !  E What is the 3 letter abbreviation for the phenonomen where one vendor 4 spread false rumours about another vendors product ?   Arne   ------------------------------  / Date: Fri, 12 May 2000 09:14:36 +0200 (MET DST)e& From: Rudolf Wingert <win@FOM.FGAN.DE># Subject: New FORTRAN documentation?r/ Message-ID: <200005120614.IAA05296@fom.fgan.de>m   Hello,  @ we do have an documentation service contract with Compaq for the= FORTRAN documention. Since version 6.4 we did not get any news> documentation. The actual FORTRAN version is 7.3. Does anybody@ know, why there are no newer documentations out? AFAIK there are2 a lot of new features within the FORTRAN compiler.   TIA and regards Rudolf Wingert   ------------------------------  % Date: Fri, 12 May 2000 11:21:37 -0500 , From: Howard S Shubs <hshubs@mindspring.com>' Subject: Re: New FORTRAN documentation?,> Message-ID: <hshubs-409046.11213712052000@news.mindspring.com>  ? In article <200005120614.IAA05296@fom.fgan.de>, Rudolf Wingert M <win@FOM.FGAN.DE> wrote:  > >FORTRAN documention. Since version 6.4 we did not get any new? >documentation. The actual FORTRAN version is 7.3. Does anybodyfA >know, why there are no newer documentations out? AFAIK there are   , Have you looked on the documentation CD-ROM? -- *; Howard S Shubs      hshubs@mindspring.com    hshubs@bix.com*? The Denim Adept     Which is better, Maryann or pickled Ginger?o> SPAM: uce@ftc.gov   postmaster@[127.0.0.1]   abuse@[127.0.0.1]   ------------------------------   Date: 12 May 2000 17:35:24 GMT0 From: "Dale A. Dellutri" <ddellutr@enteract.com>' Subject: Re: New FORTRAN documentation? - Message-ID: <8fhfcs$1ker$1@news.enteract.com>   U On Fri, 12 May 2000 09:14:36 +0200 (MET DST), Rudolf Wingert <win@fom.fgan.de> wrote:rB > we do have an documentation service contract with Compaq for the? > FORTRAN documention. Since version 6.4 we did not get any new @ > documentation. The actual FORTRAN version is 7.3. Does anybodyB > know, why there are no newer documentations out? AFAIK there are4 > a lot of new features within the FORTRAN compiler.  * Along with FORTRAN 7.3 CD-ROM, I received:; 1. AA-PUA3F-TE Installation Guide for OpenVMS Alpha Systems-4 2. AA-QJRWB-TE User Manual for OpenVMS Alpha Systems( 3. AA-Q66SD-TK Language Reference Manual= Each of them for Compaq FORTRAN 7.3.  I've received a similar ) set for every FORTRAN I've ever received.    -- E& Dale Dellutri -- ddellutr@enteract.com   ------------------------------  % Date: Fri, 12 May 2000 16:04:42 +0530 & From: Champs Onweb <champs@pol.net.in>= Subject: Open VMS connectivity problem- Urgent please respond ; Message-ID: <000a01bfbbff$2396c040$c78241ca@pol.pol.net.in>t  , This is a multi-part message in MIME format.  + ------=_NextPart_000_0007_01BFBC2D.3D4EFC40d Content-Type: text/plain;i 	charset="iso-8859-1"v+ Content-Transfer-Encoding: quoted-printableB   From   CHAMPS ON web (P) Ltdh  	 Hyderabadc   Indiac   Dear sir  F We would highly appreciate if you could co-operte with us to solve a =# problem we are facing with OPEN VMSB  ) I have some questions and information.=20b         Probleme  0 OpenVMS Alpha Multiple Database Connection Issue        I CHAMPS Software has developed a tool called (RDL), that generates DEC C = D with embedded SQL. Each module within the application (Work Order, =6 Equipment, BOM) has associated to it four executables:   ES_*.EXE   PG_*.EXE   TR_*.EXE   FR_*.EXE  4 For example for Equipment module the file names are:  
 ES_EQM.EXE
 PG_EQM.EXE  
 TR_EQM.EXE  
 FR_EQM.EXE  J The ES_*.EXE is an executable that maintains the escape routines invoked = by DECForms shareable images.U  & The FR_*.EXE is th=EC=A5=C1 =04 =04=16          J A driver program AD_101.EXE is used for application execution. So when a =A user logs on to CHAMPS Application this is the program that the =f3 operating system executes to start the application.t  I On the Alpha machines as each user transfers from one module to another = G a connection is made to the Oracle Rdb database. Therefore, if a user =CI goes to 3 different modules he will have three different connections to = 
 the database.l  ' On the VAX machine this does not occur.   J The only difference with the application running on the Alpha versus the =I VAX is how the executables are linked. The Alpha box requires something =rG called SYMBOL VECTORS and different PSECT Attributes when linking the =e above executables.  H So the question is, where does the extra connections come from and why =4 is doesn=92t occur on the VAX, but only on Alpha?=20  F First of all, the linking methodology that was used on the Alpha was =G recommended by Digital at the time we developed this product in 1992. =fF This was about the time the Alpha machine was first released and was =I running version 1.5 of OpenVMS. Since then, we have upgraded to version =aI 7.1 of OpenVMS and wonder if there have been any new methodologies that =EF we should use for linking. I wasn=92t sure from your fax whether you =J were eluding to another way of linking these executables to make it work =J like the VAX or that this issue is inherent to the Alpha. Please provide =A any other information you may have in regards to the linking of =. executables on the Alpha.-      H I have some other questions and information. First of all, the linking =J methodology that was used on the Alpha was recommended by Digital at the =E time we developed this product in 1992. This was about the time the = J Alpha machine was first released and was running version 1.5 of OpenVMS. =F Since then, we have upgraded to version 7.1 of OpenVMS and wonder if =I there have been any new methodologies that we should use for linking. I =,I wasn=92t sure whether there is another way of linking these executables =nD to make it work like the VAX or that this issue is inherent to the =H Alpha. Please provide any other information you may have in regards to =( the linking of executables on the Alpha.      
 Thank you,  	 A. Josephn    + ------=_NextPart_000_0007_01BFBC2D.3D4EFC40o Content-Type: text/html; 	charset="iso-8859-1"a+ Content-Transfer-Encoding: quoted-printable   0 <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"> <HTML> <HEAD>  0 <META content=3Dtext/html;charset=3Diso-8859-1 = http-equiv=3DContent-Type>8 <META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR> </HEAD>e <BODY bgColor=3D#ffffff> <DIV><FONT size=3D2> <P>From</P>r <P>CHAMPS ON web (P) Ltd</P> <P>Hyderabad</P> <P>India</P> <P>Dear sir</P>rI <P>We would highly appreciate if you could co-operte with us to solve a =a
 problem=20 we are facing with OPEN VMS</P>t. <P>I have some questions and information. </P> <P align=3Dcenter></P> <P align=3Dcenter>&nbsp;</P>  <P align=3Dcenter>Problem</P><U>> <P align=3Dcenter>OpenVMS Alpha Multiple Database Connection =
 Issue</P></U>o <P align=3Dcenter></P>
 <P>&nbsp;</P> J <P>CHAMPS Software has developed a tool called (RDL), that generates DEC =	 C with=20 J embedded SQL. Each module within the application (Work Order, Equipment, = BOM)=20?* has associated to it four executables:</P> <P>ES_*.EXE</P>  <P>PG_*.EXE</P>I <P>TR_*.EXE</P>n <P>FR_*.EXE</P>p; <P>For example for Equipment module the file names are:</P>n <P>ES_EQM.EXE<BR>PG_EQM.EXE</P>  <P>TR_EQM.EXE</P>h <P>FR_EQM.EXE</P> E <P>The ES_*.EXE is an executable that maintains the escape routines =<
 invoked by=20. DECForms shareable images.</P>9 <P>The FR_*.EXE is th&igrave;&yen;&Aacute; =04 =04=16</P>n
 <P>&nbsp;</P>e
 <P>&nbsp;</P> F <P>A driver program AD_101.EXE is used for application execution. So = when a user=20F logs on to CHAMPS Application this is the program that the operating =	 system=20r& executes to start the application.</P>D <P>On the Alpha machines as each user transfers from one module to = another a=20J connection is made to the Oracle Rdb database. Therefore, if a user goes = to 3=20 C different modules he will have three different connections to the =k
 database.</P>o. <P>On the VAX machine this does not occur.</P>I <P>The only difference with the application running on the Alpha versus = 
 the VAX=20E is how the executables are linked. The Alpha box requires something =:	 called=20eG SYMBOL VECTORS and different PSECT Attributes when linking the above=20> executables.</P>G <P>So the question is, where does the extra connections come from and = 	 why is=20u7 doesn&rsquo;t occur on the VAX, but only on Alpha? </P>aJ <P>First of all, the linking methodology that was used on the Alpha was=20G recommended by Digital at the time we developed this product in 1992. =d This was=20 E about the time the Alpha machine was first released and was running =c version 1.5=20H of OpenVMS. Since then, we have upgraded to version 7.1 of OpenVMS and = wonder if=20J there have been any new methodologies that we should use for linking. I=20I wasn&rsquo;t sure from your fax whether you were eluding to another way =- of=20-E linking these executables to make it work like the VAX or that this =e issue is=20?J inherent to the Alpha. Please provide any other information you may have = in=20a7 regards to the linking of executables on the Alpha.</P> 
 <P>&nbsp;</P> C <P>I have some other questions and information. First of all, the =e
 linking=20J methodology that was used on the Alpha was recommended by Digital at the =
 time we=20C developed this product in 1992. This was about the time the Alpha =g machine was=20G first released and was running version 1.5 of OpenVMS. Since then, we =  have=20tJ upgraded to version 7.1 of OpenVMS and wonder if there have been any new =  C methodologies that we should use for linking. I wasn&rsquo;t sure =  whether there=20J is another way of linking these executables to make it work like the VAX =
 or that=20? this issue is inherent to the Alpha. Please provide any other =  information you=20C may have in regards to the linking of executables on the Alpha.</P>C
 <P>&nbsp;</P>  <P>Thank you,</P>a+ <P>A. Joseph</P></FONT></DIV></BODY></HTML>   - ------=_NextPart_000_0007_01BFBC2D.3D4EFC40--    ------------------------------  # Date: Fri, 12 May 2000 10:16:24 GMTL+ From: Chris Doran <chris_doran@my-deja.com>a= Subject: Re: Problem with Seagate disk on VAXstation 4000 VLCs) Message-ID: <8fgllg$gb5$1@nnrp1.deja.com>s  + In article <391B47D8.FFBD9F3E@bigpond.com>,,0   David B Sneddon <dbsneddon@bigpond.com> wrote: > "Bart Z. Lederman" wrote:i > >o? > > In article <3919EFBA.B1BE5090@bigpond.com>, David B Sneddono <dbsneddon@bigpond.com> writes:p > > >c@ > > >It is not a duplicate ID, I install the disk internally and
 terminate the 0 > > >SCSI - this is the only device on the SCSI. > > >> > > >r > > >show config gives meb > > >       A/1/0b > > >       A/1/1d > > >        ... > > >       A/1/7  > > >like it sees 8 devices.  G Your suspicion of the cable voiced earlier _is_ a possibility -- I oncerE saw spurious multiple devices like this with a faulty plug (bent pin)y on an external SCSI cable.   ...k4 > The question I really want to get an answer for is9 > "what does the 0034 value mean in ?? 110 10 SCSI 0034".d  F but I can't remember whether I also got 0034 (and don't intend to bend a pin again to find out :).t   Chrisi    & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  % Date: Fri, 12 May 2000 14:08:49 +0100a, From: "Adrian Lumsden" <A.Lumsden@xdt.co.uk>= Subject: Re: Problem with Seagate disk on VAXstation 4000 VLCw/ Message-ID: <8fh052$btv$1@newsg1.svr.pol.co.uk>   ) I think that when the SHOW CONFIG gives:-    > > >       A/1/0w > > >       A/1/1b > > >        ... > > >       A/1/7m  = it means that it can see a device on SCSI controller A with a < SCSI ID of 1 and LUNs of 0 through to 8. This is the sort of7 response I get from a Pioneer DRM-604X CD mini-jukebox.n  9 This has a six CD changer and responds with A/1/0 throughr8 A/1/5. VMS "sees" these as DKA100:, DKA101: ... DKA105:.  ; I have seen this problem when connecting certain devices toM8 certain systems. I've got around it by using a different3 combination of device and system as necessary. I'veg5 never resolved properly what's going on. I'll asks myi4 SCSI wizard friend and see if he can shed any light.  5 BTW since you are only putting one SCSI device on ther/ Alpha do you have termination set up correctly?M   Adrian   --( Adrian Lumsden, XDT Computer Systems, UK" A dot Lumsden at xdt dot co dot uk      8 David B Sneddon <dbsneddon@bigpond.com> wrote in message% news:391B47D8.FFBD9F3E@bigpond.com...j > "Bart Z. Lederman" wrote:9 > >@? > > In article <3919EFBA.B1BE5090@bigpond.com>, David B Sneddono <dbsneddon@bigpond.com> writes:  > > >eJ > > >It is not a duplicate ID, I install the disk internally and terminate the 0 > > >SCSI - this is the only device on the SCSI. > > >> > > >e > > >show config gives men > > >       A/1/0i > > >       A/1/1  > > >        ... > > >       A/1/7  > > >like it sees 8 devices. > >dC > > This is indeed one of the common symptoms of having two devicesh > > with the same ID.r >e> > There is only ONE device, SCSI ID 1, the controller ID is 6. >'G > > >The disk was removed from a functioning VAXstation 4000-90 and wasV > > >fine in that box. > >eE > > Some VAX systems have the controller at ID 7, while some have thedD > > ID at 6, and the VLC is one of them.  If your disk is at ID 6 itC > > could have worked in the 4000-90 but still give you problems inoC > > the VLC.  Try changing it's ID to 0 or 1 and see if that helps.kB > > (Also check to see that none of the little jumpers that select? > > the ID didn't drop off or come lose when you moved the disks  > > from one system to another.) > F > None of the jumpers have come loose or fallen off, the ID was set toG > 1 since I already had a 0 and 4 on the VLC.  As I stated before, this_E > problem happens even when this disk is the ONLY device on the SCSI.u >l4 > The question I really want to get an answer for is9 > "what does the 0034 value mean in ?? 110 10 SCSI 0034".I > >/ > > --, > >  B. Z. Lederman   Personal Opinions Only >  >  > --
 > Regards, > Dave. K > ------------------------------------------------------------------------- K > David B Sneddon (dbs)  OpenVMS Systems Programmer   dbsneddon@bigpond.comlK > DBS software at ...   http://www.users.bigpond.com/dbsneddon/software.htmoK > "Life is what happens to you while you're busy making other plans" Lennonl >l   ------------------------------  % Date: Fri, 12 May 2000 14:57:31 +0100oB From: Andrew Harrison SUNUK Consultancy <andrew.nospam@uk.sun.com>' Subject: Re: S80 competitor of E10000?!s* Message-ID: <391C0DCB.A30AD218@uk.sun.com>   Larry Kilgallen wrote:  Z > In article <200005090548.HAA32169@fom.fgan.de>, Rudolf Wingert <win@fom.fgan.de> writes:
 > > Hello, > >fM > > today I red that, as the Information Week and GigaGroup say, the S80 willnM > > be the competitor of the E10000. IBM is happy, that they did sold the S80TJ > > three times (720) of Sun's E10000 (255). I am hoping that the WildfireI > > soon and will be a competitor of both and well sold better then both.  >n: > Well Apple has sold more iMacs than Sun has sold E10000.0 > At a 1:1000 price to price ratio, they should. >dG > For some situations the Compaq ES40 might be the proper competitor to H > the IBM S80, rather than Wildfire.  On the other hand, based on what IH > saw at the San Diego DECUS Symposium, it will be possible to configureD > a Wildfire so that it is _less_ powerful than a fully loaded ES40. >n  < The ES40 and and workgroup/mid range servers from Sun and HPE would be a proper competitor for most of the IBM S80's that have been A sold. This is because most of them according to IBM's own figurese; provided to IDC were discounted entry level 6 CPU machines.s  : IBM have been making a fuss about the number of S80's that8 they have sold and comparing this number with the number8 of Sun E10K's sold. According to the IDC numbers however; 94% of the S80's sold have been configured as low-mid rangeh> servers and they have resulted in a corrosponding reduction in/ sales of the S70 IBM's 12 CPU mid range server.2  ? IBM however will probably not continue with this tactic becausec> they are about to announce new mid range servers that are moreD competitive than their current rather lack lustre range of machines.  < When that happens and they are shipping, discounting the S80B and selling entry configs to cover deficiencies in their workgroup, /mid range servers will not be so necessary.  9 The minimum configuration on the S80 is 6 CPU's and afterN9 that it can be expanded in 6 CPU steps up to 24 CPU's but04 I don't see much value in them selling 6 CPU systems7 except to people who are going to dramatically increase ; their resource requirements. This is also true for WildFires; which will support 1 CPU configs if you are prepared to payo" a vast pemium over a DS10 or ES40.   regards  Andrew Harrisona Enterprise IT Architect    ------------------------------  % Date: Fri, 12 May 2000 15:03:47 +0100-- From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>1< Subject: Re: sharing large amounts of data between processes) Message-ID: <391C0F43.C20AF5CC@bbc.co.uk>e   Phillip Helbig wrote:1  I > This is related to a completely different problem than my last few "biggF > file" posts.  However, some of the responses hint that the solutions > might be similar.  >dI > Imagine a program which needs several hundred MB of memory, which needs F > to be updated (new items entered, perhaps some sort of sorting, someG > items deleted, some modified) once a minute or so.  In principle, thesE > program could update itself, but it might be better to have anothercG > program do this.  Thus, one needs some memory (global section?) to be[F > shared between processes, which might be run by completely differentA > users.  I have used logicals to transfer data between processesrH > (creating a special table for this), but this is probably not the best3 > approach if one adds, say, 1 kB per minute or so.:  F I did see some stunning logical name translation rates from one bit ofG simulation code on a 3000-400 alpha, once, but you are correct, logicaltH names are great for small amounts of data updated infrequently, a global section C is the way to go for maximum throughput (lock the section in RAM ifa9 you have enough and really want to maximize performance).t  I > Since I have a third program which really needs to access the same data3F > simultaneously (say, once every few minutes), the global section (ifB > that's what it is) seems the best way to go.  The amount of dataF > prevents updating it on disk, restarting the program with fresh data > read from the disk etc.e > I > In contrast to my previous "big file" posts, the main point here is not-J > the size, but the on-the-fly updating.  Also, this will only ever run onJ > VMS, so I might be willing to use some non-standard VMS-specific FortranJ > for this.  (There are related DCL procedures interacting with this, so I@ > don't mind doing things in DCL.)  I really have practically noH > experience exchanging data in RAM between processes.  Where's the bestJ > place to learn about this?  It would be nice to do everything in Fortran
 > and/or DCL.e  I Global sections are great! Try the System Services overview docs and theneE $crmpsc and $MGBLSC. If you have one or more processes writing to thee sectionsJ you will need some sort of synchronization layer (lock manager is probably theo best solution for this).  J I don't know if there is a C RTL call to do this, I'd call system services direct* from Fortran myself, its the way I learnt.  J If you are using CERNLIB there is some code for mapping the HBOOK  commons as global sections in there.  A HTH, if I had a fortran compiler I might knock up a few examples.S   --6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.ukh  A I speak for myself only and my views in no way represent those ofo MedAS or the BBC.t   ------------------------------  % Date: Fri, 12 May 2000 10:56:33 +0200a= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> < Subject: Re: Suggest a better file serving solution than NT?) Message-ID: <391BC741.2344620F@gtech.com>    Gord Coulman wrote:eM > I know this is a bit off topic, but my primary NT file server is driving mecI > nuts with unexplained system hangs and I need to repair/replace it with L > something approaching the reliability of my OpenVMS machine.  I am open toL > all suggestions, not just another NT box, although the clients are all WinL > 98 and other NT servers, which narrows things a bit.  I have run Pathworks. > in the past, but I'm not going back there...  ? This is how NT works (or more precise: not works) in practice !h  A You say you do not want VMS/PathWorks. What about Linux/Samba (or  maybe VMS/Samba) ?   Arne   ------------------------------  % Date: Fri, 12 May 2000 07:27:59 -0400  From: Ken Peck <kenp@trlab.com>l< Subject: RE: Suggest a better file serving solution than NT?B Message-ID: <F845F0DC678AD311989D0008C7E6FD63229422@DED-EXCHANGE1>  E I'm very puzzled at your experience with NT...  I run a shop with NT, H Novell, VMS (clustered 7.2-1), Linux, and SCO Unix and have 4 NT ServersJ that haven't EVER experienced a 'crash'.  I also have 150 remote locationsD with NT workstation.  My NT webservers/workstations, SQL server, andI Exchange Server don't even get rebooted often enough to remember the lastnJ time I did reboot them.  Of course, I should also say that my VMS cluster,D Novell servers and Linux boxes don't 'crash' either, nor do they get	 rebooted.a  , What kind of hardware are you running NT on?   Ken Peck   > -----Original Message-----: > From: Gord Coulman [mailto:nospam_gcoulman@ccinet.ab.ca]& > Sent: Thursday, May 11, 2000 7:55 PM > To: Info-VAX@Mvb.Saic.Comn> > Subject: Re: Suggest a better file serving solution than NT? >  > ? > Thanks for the input so far.  The NT box crashed three times n > today.  I am: > switching all important services over to another NT box  > tonight and I just# > changed out the video card, FWIW.o > > > I hate to just change out components and try to fix this by  > the process of9 > elimination, but without any kind of crash dump or log 3 > entries, that's what= > I'm reduced to.  Next is the motherboard.  I'm not looking q > forward to that,= > since NT positively hates having the motherboard changed.  > > Will keep you= > posted.... >  > Gord.8 >  >    ------------------------------  % Date: Fri, 12 May 2000 07:27:38 -0500E) From: "John E. Malmberg" <wb8tyw@qsl.net>>< Subject: Re: Suggest a better file serving solution than NT?7 Message-ID: <019901bfbc0d$78078a20$020a0a0a@xile.realm>P  $ Ken Peck <kenp@trlab.company> wrote:  G > I'm very puzzled at your experience with NT...  I run a shop with NT,PJ > Novell, VMS (clustered 7.2-1), Linux, and SCO Unix and have 4 NT ServersL > that haven't EVER experienced a 'crash'.  I also have 150 remote locationsF > with NT workstation.  My NT webservers/workstations, SQL server, andK > Exchange Server don't even get rebooted often enough to remember the lastlL > time I did reboot them.  Of course, I should also say that my VMS cluster,F > Novell servers and Linux boxes don't 'crash' either, nor do they get > rebooted.b  J With the number of NT systems I have, I can say that if you do run certainK product mixes at certain loads, you will not see much problems with WindowsX= NT.  Some combinations have never given much problems at all.P  J However, it is very possible with other enviroments to trip many confirmed3 by Microsoft bugs that will take your machine down.X  J Service Pack 5 fixed most of the ones that the load I have introduced, andK is the lowest that I can run, Except for RAS clients, they do not work witha SP5, you must have SP6a.  K I would recommend reading the release notes for SP6a as to what it fixed in D SP6.  That should be a good warning about Microsoft testing methods.  L Prior to NT 4.0 SP5, heavy loads on the NTFS file system would cause a BSOD.J If your hardware was not capable of that performance, or your load was notK high enough, no problem.  Please read in the SP5 release notes the detailedn$ description of what they had to fix.  L Also prior to NT 4.0 SP5, any changes to your SAM user database caused it toI expand.  This required schedule reboots of the Domain Controllers to keepdC them from hanging when it runs out of registry quota.  This bug wasaK reported, and got a response of "*NOT REPRODUCABLE*", until it was fixed inc SP5.  K Since SP5 has only been out since last summer, how long have you been lucky?6 enough to have these systems with steller performance?  . > What kind of hardware are you running NT on?  < The post you quoted originally had the hardware description.   -Johnh wb8tyw@qsl.network   ------------------------------  % Date: Fri, 12 May 2000 14:23:30 +0000c/ From: Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk>S< Subject: re: Suggest a better file serving solution than NT?7 Message-ID: <009E9FA6.1C437A35.12@maxwell.ph.kcl.ac.uk>m  R > "Gord Coulman" <nospam_gcoulman@ccinet.ab.ca> wrote on Thu, 11 May 2000 18:48:17 > GMT: >  > <snip> > >  I have run Pathworkss/ > >in the past, but I'm not going back there...  > E > How far in the past? Maybe you should give Advanced Server a try...c > R > Samba with 200 clients might have performance problems - I don't have first handN > experience, but have heard several times that it's a great system in a small& > network, but doesn't scale too well. >   M PW 5 was the real PITA. Needed to be one of DEC's best products, was actuallya3 one of their worst. PW4 was pretty good in its day.p  D The benchmarks I've seen suggest that Samba outperforms NT for largeJ nunbers of users where the server is driven to saturation. More important J it doesn't fall over when driven hard! Can't speak for 200 users, but it'sM fine for 50 running on a somewhat elderly dual P2/233. (caveat: users aren't   a standardised commodity :-)  @ Samba runs on Unixes other than Linux, so it's available on "bigG iron" as well as PCs. HP sell it (and presumably support it) under some<E completely forgettable corporate-approved name as HP's equivalent of 0K Pathworks. (Yes, that's allowed ... see the Samba web pages, www.samba.org)1   	Yours,1
 		Nigel Arnotr- 		NRA@MAXWELL.PH.KCL.AC.UK                   j  7 		"In the beginning there was nothing, which exploded."    ------------------------------   Date: 12 May 2000 17:39:30 GMT) From: leslie@clio.rice.edu (Jerry Leslie)d< Subject: Re: Suggest a better file serving solution than NT?' Message-ID: <8fhfki$9f7$1@joe.rice.edu>p  0 Nigel Arnot (sysmgr@maxwell.ph.kcl.ac.uk) wrote:  B : Samba runs on Unixes other than Linux, so it's available on "bigI : iron" as well as PCs. HP sell it (and presumably support it) under someSG : completely forgettable corporate-approved name as HP's equivalent of  M : Pathworks. (Yes, that's allowed ... see the Samba web pages, www.samba.org).   CIFS...s  3  http://www.unixsolutions.hp.com/products/cifs.html-L  HP Announces Industry-Leading UNIX/Windows Interoperability with CIFS/9000   4 --Jerry Leslie     (my opinions are strictly my own)   ------------------------------  % Date: Fri, 12 May 2000 09:21:39 +0200?> From: "Jean-Franois Marchal" <jean-francois.marchal@x9000.fr>B Subject: System halts after %EWA0, Twisted-Pair mod set by console2 Message-ID: <8fgbct$jo4$1@s2.feed.news.oleane.net>  ) I've just installed the following patches-$ (not absolutely sure of the order) : - VMS721_SYS v5.0  - VMS721_LAN v1.0@ on my pws433au under vms 7.2-19 (had installed VMS721_PCSI and VMS721_UPDATE just before,h# but systeme had rebooted correctly)   / Since the installation, the system reboot halts  after displaying the message' %EWA0, Twisted-Pair mode set by console   
 halt code = 5c
 PC = 7b073864   0 I already tried (under cd standalone version) to9 rename sys$ewbtdriver.exe to exe_new and .exe_old to .exe ( rename sys$ewdriver_de500ba the same way but system halts as well ...  + As you may imagine, it is quite urgent ....h   Jean-Franois Marchal. X9000 - LYON   ------------------------------  % Date: Fri, 12 May 2000 05:50:48 -0400m' From: "Bill Todd" <billtodd@foo.mv.com>t& Subject: Re: the latest billybox virus( Message-ID: <8fgk1t$fkv$1@pyrite.mv.net>  J Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> wrote inJ message news:y4em78df6k.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de...+ > "Bill Todd" <billtodd@foo.mv.com> writes:n > G > > My fault:  I should have said "Microsoft could help by setting up a  *second*E > > intermediate cautionary dialog box...", since there's already one4
 containingE > > a virus warning that you have to pass through before executing an9 > > attachment.i >nK > But that box is almost useless, because it's analogous to "The Little BoysI > that Called `Wolf'." Doesn't is have a "permanent disable" tick-box? If  so, L > most users will tick it after the third or fifth time it comes up in total6 > disregard for the contents of file it is looking at. >. > Jan   K If you'll take a look, you'll see that the disable check-box states "AlwayshJ ask before opening this type of file" - and that's exactly what's disabledJ if you un-check it:  warnings for *that type* of file.  So you can say youI don't want to be asked for .doc, .txt, ... files as you encounter them asaK attachments, but unless you've said at some point that you don't want to bevJ asked about .vbs files, the warning dialog box will appear when you try to execute one.  L That gives people a way to screen out the warnings they know they don't careI about to avoid the 'boy who cried wolf' effect without losing the others, H and there aren't so many common file attachment types that the screening# process should be all that tedious.r  H [Should you wish to verify this, you might want a way to reestablish theK warning for the file type after you disable it.  I did, and it took a while L to find it (though I probably could have edited the Registry):  in Explorer,L Folder Options, File Types, you can edit each type - and there's a check-boxL you can check to 'confirm after download' that re-enables the warning dialog box.]d  I Microsoft reportedly has issued some kind of patch that does something to-F increase the prominence of the warning, though I have no idea what the details are.   - bill   ------------------------------    Date: 12 May 2000 13:01:47 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> & Subject: Re: the latest billybox virusH Message-ID: <y4puqsf2w4.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  ) "Bill Todd" <billtodd@foo.mv.com> writes:i  M > If you'll take a look, you'll see that the disable check-box states "AlwaysEL > ask before opening this type of file" - and that's exactly what's disabledL > if you un-check it:  warnings for *that type* of file.  So you can say youK > don't want to be asked for .doc, .txt, ... files as you encounter them asW > attachments,  [...]t  L Now that is somewhat unexpected, Microsoft software actually doing The RightJ Thing! The question remains why Outlook security is tied to IE, but that's
 a quibble.   	Jan   ------------------------------  % Date: Fri, 12 May 2000 13:13:43 +0000 / From: Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk>E& Subject: re: the latest billybox virus6 Message-ID: <009E9F9C.5C3CF969.8@maxwell.ph.kcl.ac.uk>  P > > My fault:  I should have said "Microsoft could help by setting up a *second*P > > intermediate cautionary dialog box...", since there's already one containingE > > a virus warning that you have to pass through before executing an  > > attachment.. > K > But that box is almost useless, because it's analogous to "The Little BoypM > that Called `Wolf'." Doesn't is have a "permanent disable" tick-box? If so,sL > most users will tick it after the third or fifth time it comes up in total6 > disregard for the contents of file it is looking at. >  Yes -- if it works that way.  E The right thing to do is to make the second box one that tells you to'L do something completely different to continue, rather than one that does it. Something like  I  "This is an untrustworthy executable attachment, which could very easily B   be a virus or other malicious attack on your system. If you have)   any doubts, do not run this attachment.a  D  "If you are certain that you want to trust it, click "Run selected M   untrustworthy attachment" from the "Executables" tab of the "Options" menu.   D Preferably in bright red. Unthinking clicking will result in nothingH happening -- only reading of the warning will result in  the attachment G being executed. And you can't turn it off, though in the unlikely event H that your job involves executing dozens of mailed scripts daily, you may9 learn to singleclick and go straight to the options menu.e  D And yes ... make it possible for system administration to completelyF disable both "Run untrustworthy attachment" and saving-to-file of such# attachments, at installation time! u  K This isn't new stuff, it goes back to before electronics. Safety interlocks N have to force users to jump out of their usual routine. The override has to beG required infrequently, or it becomes part of the usual routine and getsoM overridden from habit. The install disable corresponds to a padlock, to whichh! only the supervisor has the key. e   	Yours,c
 		Nigel Arnotr- 		NRA@MAXWELL.PH.KCL.AC.UK                   t  7 		"In the beginning there was nothing, which exploded."    ------------------------------  # Date: Fri, 12 May 2000 13:30:14 GMT 4 From: "Michael D. Ober" <mdo.@.wakeassoc.com.nospam>& Subject: Re: the latest billybox virusE Message-ID: <GHTS4.54141$g4.1516030@newsread2.prod.itd.earthlink.net>e  K The patch you are referring to is total garbage.  Specifically, it prevents K Outlook from running WinZIP directly, instead forcing users to save the ziph file to disk before opening it.h  
 Mike Ober.  2 "Bill Todd" <billtodd@foo.mv.com> wrote in message" news:8fgk1t$fkv$1@pyrite.mv.net... >eL > Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> wrote inL > message news:y4em78df6k.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de...- > > "Bill Todd" <billtodd@foo.mv.com> writes:i > >dI > > > My fault:  I should have said "Microsoft could help by setting up a 
 > *second*G > > > intermediate cautionary dialog box...", since there's already onef > containingG > > > a virus warning that you have to pass through before executing anm > > > attachment.) > > I > > But that box is almost useless, because it's analogous to "The Little  BoyuK > > that Called `Wolf'." Doesn't is have a "permanent disable" tick-box? Ifa > so,)H > > most users will tick it after the third or fifth time it comes up in totale8 > > disregard for the contents of file it is looking at. > >e > > Jann >nE > If you'll take a look, you'll see that the disable check-box statesh "AlwaysuL > ask before opening this type of file" - and that's exactly what's disabledL > if you un-check it:  warnings for *that type* of file.  So you can say youK > don't want to be asked for .doc, .txt, ... files as you encounter them astJ > attachments, but unless you've said at some point that you don't want to beL > asked about .vbs files, the warning dialog box will appear when you try to > execute one. >yI > That gives people a way to screen out the warnings they know they don'te careK > about to avoid the 'boy who cried wolf' effect without losing the others,oJ > and there aren't so many common file attachment types that the screening% > process should be all that tedious.  >tJ > [Should you wish to verify this, you might want a way to reestablish theG > warning for the file type after you disable it.  I did, and it took a. whileyD > to find it (though I probably could have edited the Registry):  in	 Explorer, D > Folder Options, File Types, you can edit each type - and there's a	 check-boxmG > you can check to 'confirm after download' that re-enables the warningA dialog > box.]t >dK > Microsoft reportedly has issued some kind of patch that does something tolH > increase the prominence of the warning, though I have no idea what the > details are. >t > - bill >- >- >-   ------------------------------  % Date: Fri, 12 May 2000 08:52:04 -0700=5 From: Richard  <maher_rjNOmaSPAM@hotmail.com.invalid>j( Subject: Re: Unsolicited OpenVMS/NT book9 Message-ID: <065f8722.078445ec@usw-ex0109-070.remarq.com>    Example VMS TCP/IP clinet:-w  < ************************************************************ ************************ *e                        *7 *         COPYRIGHT (c) 1994 BY TIER3 SOFTWARE LTD. ALLe RIGHTS RESERVED.           * *                         *: *    THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED ONLY    *v9 *    IN ACCORDANCE  WITH THE TERMS AND CONDITIONS OF SUCHn LICENSE AND  WITH THE    *8 *    THE INCLUSION  OF THE ABOVE COPYRIGHT NOTICE.  THIS SOFTWARE  OR ANY OTHER    *o7 *    COPIES  THEREOF MAY NOT  BE PROVIDED  OR OTHERWISEb MADE AVAILABLE  TO  ANY    *9 *    OTHER  PERSON.  NO  TITLE TO  AND OWNERSHIP  OF  THE  SOFTWARE  IS  HEREBY    *  *  TRANSFERRED.                   *: *g                        *5 *    THE INFORMATION  IN THIS SOFTWARE  IS SUBJECT TO0 CHANGE WITHOUT NOTICE AND    *5 *    SHOULD NOT BE CONSTRUED AS A COMMITMENT BY TIER3  SOFTWARE LTD.                * *t                        *< ************************************************************ ************************ *+! * Facilility:  DEMO_CLIENT_TCP_IP  *N9 * Abstract:    This is an example of a VMS client program   communicating with a remote task6 *              via TIER3. This program accepts a queue$ entry number from the user and sends: *              it to the remote Tier3 communication server for this application (T3_DEMO).h5 *              After Tier3 has allocated an execution # server to perform the operation them: *              USER_RECV routine is called to retrieve the  job entry information and return) *              the results to the client.: *g7 * Overview:    Due to the fact that client programs canh$ communicate with Tier3 servers using; *              standard TCP/IP Socket Level programming, not Tier3 specific software need beo4 *              installed on the client node. In this% example the client will execute underu5 *              the VMS operating system so VMS system ' services have been used for client taska *              development.t *' * Build example:- *              $COBOL/LIST DEMO_CLIENT_TCP_IPi* *              $MACRO/LIST DEMO_TCP_IP_DEF8 *              $LINK DEMO_CLIENT_TCP_IP, DEMO_TCP_IP_DEF$ *              $SET TERM/WIDTH = 132& *              $RUN DEMO_CLIENT_TCP_IP *- identification division." program-id.    demo_client_tcp_ip. data division. working-storage section.8 01  io$_setmode                     pic s9(9)       comp$ value   external        io$_setmode.8 01  io$_writevblk                   pic s9(9)       comp& value   external        io$_writevblk.8 01  io$_readvblk                    pic s9(9)       comp% value   external        io$_readvblk.h8 01  io$_access                      pic s9(9)       comp# value   external        io$_access..8 01  lib$_normal                     pic s9(9)       comp$ value   external        lib$_normal.8 01  ss$_linkdiscon                  pic s9(9)       comp' value   external        ss$_linkdiscon. 8 01  ss$_bufferovf                   pic s9(9)       comp& value   external        ss$_bufferovf.8 01  ss$_abort                       pic s9(9)       comp" value   external        ss$_abort.8 01  ss$_reject                      pic s9(9)       comp# value   external        ss$_reject.i8 01  ss$_nopriv                      pic s9(9)       comp# value   external        ss$_nopriv.c8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal.t9 01  sys_status                      pic s9(9)       comp.  *t9 01  net_chan                        pic s9(4)       comp. 	 01  iosb.s9     03  cond_val                    pic s9(4)       comp. 9     03  byte_count                  pic s9(4)       comp.o9     03                              pic s9(9)       comp.. *P 01  create_socket.8     03                              pic s9(4)       comp" value   external        ucx$c_tcp.8     03                              pic s9(4)       comp- value   external        inet_protyp$c_stream.i *o 01  local_sock_desc.8     03                              pic s9(9)       comp value   16. ;     03                                              pointerD# value   reference       local_addr.  01  local_addr.u8     03                              pic s9(4)       comp& value   external        ucx$c_af_inet.     03  local_port_number.)         05  low_byte                pic xm value   low-values.u)         05  high_byte               pic xw value   low-values.c8     03                              pic s9(9)       comp) value   external        ucx$c_inaddr_any.r-     03                              pic x(8).  *- 01  rem_sock_desc.8     03                              pic s9(9)       comp value   16.s;     03                                              pointere! value   reference       rem_addr.- *+9 * In this example the T3_DEMO server is listening on portl 1024 at node address 1.2.3.49 * NB: The port number is specified in network byte order.i *-
 01  rem_addr. 8     03                              pic s9(4)       comp& value   external        ucx$c_af_inet.     03  rem_port_number.)         05  low_byte                pic xm value   x"04".)         05  high_byte               pic x  value   x"00".     03  rem_node_addr.)         05                          pic xw value   x"01".)         05                          pic xI value   x"02".)         05                          pic x  value   x"03".)         05                          pic x  value   x"04".-     03                              pic x(8).e *u 01  sock_opt_desc.8     03  sock_opt_len                pic s9(4)       comp value   24.v8     03                              pic s9(4)       comp& value   external        ucx$c_sockopt.;     03                                              pointeri! value   reference       sock_opt.r
 01  sock_opt. 8     03                              pic s9(4)       comp
 value   4.8     03                              pic s9(4)       comp( value   external        ucx$c_reuseaddr.;     03                                              pointerw value   reference       opt_on.e8     03                              pic s9(4)       comp
 value   4.8     03                              pic s9(4)       comp0 value   external        ucx$c_full_duplex_close.;     03                                              pointerR value   reference       opt_on.s8     03                              pic s9(4)       comp
 value   4.8     03                              pic s9(4)       comp( value   external        ucx$c_keepalive.;     03                                              pointery value   reference       opt_on.e *y 01  tcp_opt_desc.a8     03                              pic s9(4)       comp
 value   8.8     03                              pic s9(4)       comp% value   external        ucx$c_tcpopt.m;     03                                              pointerd  value   reference       tcp_opt. 01  tcp_opt.8     03                              pic s9(4)       comp
 value   4.8     03                              pic s9(4)       comp- value   external        ucx$c_tcp_probe_idle.x;     03                                              pointer ( value   reference       connect_timeout. *f8 01  opt_on                          pic s9(9)       comp
 value   1.8 01  opt_off                         pic s9(9)       comp
 value   0.8 01  connect_timeout                 pic s9(9)       comp value   10.S *+9 * The Access Control Information buffer must be the first  buffer transmitted ton: * the communication server. This buffer will not be passed to an execution server6 * and is the only data message buffer whose format and content will be scrutinizedo * by Tier3.o *e: * Each field must contain ascii coded text and may be null terminated or space0	 * filled.e *- 01  aci_buffer.s.     03  aci_username                pic x(40)..     03  aci_password                pic x(40). *+4 * The Tier3 Identification buffer is returned to the client, once access has been: * authorized. The first three bytes will contain "T3$" and the next two bytes willD: * contain the major and minor version numbers of the Tier3 software installed atr * the target node. *- 01  t3_id_buffer.7,     03  t3_id                       pic xxx.*     03  maj_vers                    pic x.*     03  min_vers                    pic x.-     03  scsnode                     pic x(6). -     03  logfails                    pic 9(5).x     03  last_login_i.e-         05  yyyy                    pic 9(4).y-         05  mt                      pic 9(2). -         05  dd                      pic 9(2).e-         05  hh                      pic 9(2).s-         05  mn                      pic 9(2).m-         05  ss                      pic 9(2).s-         05  cc                      pic 9(2).c     03  last_login_n.r-         05  yyyy                    pic 9(4)..-         05  mt                      pic 9(2).e-         05  dd                      pic 9(2).s-         05  hh                      pic 9(2).s-         05  mn                      pic 9(2).w-         05  ss                      pic 9(2).y-         05  cc                      pic 9(2).. *l 01  time_vector_binary.a9     03  yyyy                        pic s9(4)       comp.y9     03  mt                          pic s9(4)       comp.i9     03  dd                          pic s9(4)       comp.g9     03  hh                          pic s9(4)       comp. 9     03  mn                          pic s9(4)       comp.w9     03  ss                          pic s9(4)       comp. 9     03  cc                          pic s9(4)       comp. 9 01  vms_binary_time                 pic s9(18)      comp.m. 01  vms_ascii_date                  pic x(17). 01  day_names_table.,     03                              pic x(9) value   "Monday".p8     03                              pic 9(4)        comp
 value   6.,     03                              pic x(9) value   "Tuesday".8     03                              pic 9(4)        comp
 value   7.,     03                              pic x(9) value   "Wednesday".8     03                              pic 9(4)        comp
 value   9.,     03                              pic x(9) value   "Thursday".-8     03                              pic 9(4)        comp
 value   8.,     03                              pic x(9) value   "Friday".R8     03                              pic 9(4)        comp
 value   6.,     03                              pic x(9) value   "Saturday".m8     03                              pic 9(4)        comp
 value   8.,     03                              pic x(9) value   "Sunday". 8     03                              pic 9(4)        comp
 value   6. 01  day_names_array.  redefines       day_names_table.:     03  day_of_week                                 occurs 7.-         05  day_name                pic x(9).t9         05  day_name_len            pic 9(4)        comp.h9 01  day_number                      pic 9(9)        comp.E. 01  welcome_string                  pic x(65).9 01  welcome_string_len              pic 9(4)        comp. . 01  last_login_msg                  pic x(62). 01  logfails_msg.e.     03  out_logfails                pic z(8)9.-     03                              pic x(37) 0 value   " failures since last successful login". *+9 * The following buffers are application specific. In thisi DEMO example a maximum; * buffer size of 510 bytes has been selected, and the first  two bytes of every8 * message have been reserved for message identification. Note that this is purely8 * an application convention that needs to be observed by the programmers of the3 * client and server components of DEMO and is not ah requirement of Tier3.m *- 01  reply_buffer.g+     03  msg_type                    pic xx..         88  valid_replyt values  "00", "11", "99".          88  error_msgc
 value   "00".t         88  entry_data
 value   "11".          88  end_of_filet
 value   "99".a/     03  reply_body                  pic x(508).t *t 01  error_buffer redefines       reply_buffer. +     03                              pic xx.o,     03  error_msg_len               pic 999./     03  error_msg_text              pic x(505).  *  01  entry_info_buffer  redefines       reply_buffer. +     03                              pic xx. -     03  entry_number                pic 9(4).n.     03  job_name                    pic x(39)..     03  job_status                  pic x(15)..     03  que_name                    pic x(31)..     03  que_type                    pic x(10)..     03  que_status                  pic x(10). *i 01  get_entry_buffer.r*     03                              pic xx
 value   "10".n-     03  user_entry                  pic 9(4).a,     03  max_entries                 pic 9(4) value   12.e * 9 01  reply_body_len                  pic 9(4)        comp.m *+' * Application specific working-storage.  *- 01  screen_line_table.:     03  screen_line                                 occurs 12.e-         05  entry_number            pic 9(4).,.         05  job_name                pic x(39)..         05  job_status              pic x(15)..         05  que_name                pic x(31)..         05  que_type                pic x(10)..         05  que_status              pic x(10). 01  screen_header.,     03                              pic x(9) value   " Entry#".-     03                              pic x(40)M value   "Job Name". -     03                              pic x(16): value   "Job Status".r-     03                              pic x(32)d value   "Queue Name".t-     03                              pic x(13)a value   "Queue Type".t-     03                              pic x(22)y value   "Queue Status".o 01  out_entry.+     03                              pic xx..-     03  entry_number                pic zzz9.m,     03                              pic xxx..     03  job_name                    pic x(39).*     03                              pic x..     03  job_status                  pic x(15).*     03                              pic x..     03  que_name                    pic x(31).*     03                              pic x..     03  que_type                    pic x(10).,     03                              pic xxx..     03  que_status                  pic x(10). *v) 01  user_exit                       pic x  value   "N".9 01  line_count                      pic 9(9)        comp.a9 01  screen_index                    pic 9(9)        comp.n- 01  end_key                         pic x(4).  *o procedure division.l kick_off section.  00.      perform socket_and_connect.a.     if sys_status not = ss$_normal go to fini.       perform application_logon.     if t3_id not = "T3$"$         move ss$_abort to sys_status         go to fini.s       perform display_welcome.  3     perform get_entry_info until user_exit = "Y" orh sys_status not = ss$_normal..     if sys_status not = ss$_normal go to fini.       perform socket_close.. *l fini.o.     call "sys$exit" using by value sys_status. *' get_entry_info section.t 00.d:     display "Enter job entry number (zero = wild, ctrl/z = exit): "6             line 1 column 1 erase screen no advancing.&     accept user_entry with  conversion$                             reversed                              bold%                             protected +                             default is zeron1             at end          move "Y" to user_exit '                             go to fini.  *+ * Call my USER_RECV routine. *-     call    "sys$qiow"0             using   by value        0, net_chan,
 io$_writevblk (                     by reference    iosb(                     by value        0, 04                     by reference    get_entry_buffer2                     by value        10, 0, 0, 0, 0             giving  sys_status.-;     if sys_status = ss$_normal move cond_val to sys_status.t.     if sys_status not = ss$_normal go to fini.       move zeros to line_count.e(     perform load_entries with test after4             until not entry_data or sys_status not = ss$_normal.-.     if sys_status not = ss$_normal go to fini.       if error_msg/             display "Error retrieving job entryu
 information,"l3             display error_msg_text(1:error_msg_len)c4     else    display screen_header at line 1 column 1 reversed erase screen*:             perform varying screen_index from 1 by 1 until screen_index > line_count ;                     move corr screen_line (screen_index) toE	 out_entry %                     display out_entry              end-perform.  5     display "Press RETURN to continue." no advancing.D*     accept key in end_key at end continue. *H fini.R *A socket_and_connect section.S 00.      call "sys$assign"E$         using   by descriptor "_BG:"&                 by reference  net_chan%                 by value      0, 0, 0I         giving  sys_status.L;     if sys_status not = ss$_normal call "lib$stop" using byN value sys_status.O *A     call    "sys$qiow"<             using   by value        0, net_chan, io$_setmode(                     by reference    iosb(                     by value        0, 0;                     by reference    create_socket, omitted,R local_sock_desc %                     by value        0 1                     by reference    sock_opt_desc*%                     by value        0*             giving  sys_status.T;     if sys_status = ss$_normal move cond_val to sys_status.n;     if sys_status not = ss$_normal call "lib$stop" using byv value sys_status.r *+6 * Set the connect timeout to 10 secs. TCPWARE requires privilege to do this.r *-     call    "sys$qiow"<             using   by value        0, net_chan, io$_setmode(                     by reference    iosb4                     by value        0, 0, 0, 0, 0, 00                     by reference    tcp_opt_desc%                     by value        0r             giving  sys_status.r;     if sys_status = ss$_normal move cond_val to sys_status.t1     if sys_status not = ss$_normal and ss$_nopriv 2         call "lib$stop" using by value sys_status. *+0 * Request a logical link connection to the Tier3* communication server for this application. *-     call    "sys$qiow";             using   by value        0, net_chan, io$_accessn(                     by reference    iosb.                     by value        0, 0, 0, 01                     by reference    rem_sock_descA+                     by value        0, 0, 0K             giving  sys_status.D;     if sys_status = ss$_normal move cond_val to sys_status.      if sys_status = ss$_reject9         display "Access denied or the DEMO application isd not running on remote node."     else&         if sys_status not = ss$_normal6             call "lib$stop" using by value sys_status. *_ fini.l *  application_logon section. 00.o *+/ * Once a logical link has been established, thee communication server will be5 * expecting access control information so that it canh authorize client access  * to the application.  * 9 * The aci_buffer allocates 40 bytes each for the username  and password fields but98 * as VMS is currently the only supported server platform for Tier3 you should limit, * usernames to 12 bytes and passwords to 32. *-&     display "Username: " no advancing.;     accept aci_username protected size 12 editing at end gos to fini.&     display "Password: " no advancing.9     accept aci_password protected size 32 editing no echo1 at end go to fini.       call    "sys$qiow"0             using   by value        0, net_chan,
 io$_writevblk (                     by reference    iosb(                     by value        0, 0.                     by reference    aci_buffer2                     by value        80, 0, 0, 0, 0             giving  sys_status.9;     if sys_status = ss$_normal move cond_val to sys_status.9.     if sys_status not = ss$_normal go to fini. *+9 * To complete the hand-shaking sequence the communication  server will reply90 * to a successfull access attempt with the Tier3 identification buffer. * 3 * If the access control information was invalid the  communication server7 * will break the connection and the following read will  return ss$_linkdiscon.2 * Before retrying a failed access attempt you must therefore re-connect: * (io$_access) the communication server. The communication server's log7 * file will contain detailed information describing any 
 authorizatione * failures.e *e7 * The Tier3 Identification buffer for handshake 1 is 48  bytes long.  *-     call    "sys$qiow"0             using   by value        0, net_chan, io$_readvblk(                     by reference    iosb(                     by value        0, 00                     by reference    t3_id_buffer2                     by value        48, 0, 0, 0, 0             giving  sys_status.c;     if sys_status = ss$_normal move cond_val to sys_status.)"     if sys_status = ss$_linkdiscon0             display "User authorization failure"*             move ss$_normal to sys_status. *  fini.  *  load_entries section.  00.e *+: * As terminal i/o can take an indefinite amount of time to complete, once; * entry information is retrieved from the remote node it iss deferred toe8 * working-storage rather than being sent directly to the screen. This9 * strategy removes a potential cause of buffer starvationi in the communication; * server. If it is impractical to set a limit on the amount  of information to : * be returned from the execution server then the developer should consider 4 * deferring output to a temporary file, or expanding available memory via * a routine such as LIB$GET_VM.2 * 9 * Furthermore, if it is a requirement of your application  that the association4 * between client and execution server persist during terminal i/o it may be; * necessary to modify the application's parameter record in 	 the Tier396 * configuration file so that the "maximum servers" and "maximum links"4: * parameters are set to the same value. This configuration would effectively 9 * dedicate a seperate execution server to each client and  avoid potentialo- * delays in the servicing of client requests.i *-     call    "sys$qiow"0             using   by value        0, net_chan, io$_readvblk(                     by reference    iosb(                     by value        0, 0,                     by reference    msg_type1                     by value        2, 0, 0, 0, 0              giving  sys_status. ;     if sys_status = ss$_normal move cond_val to sys_status.n.     if sys_status not = ss$_normal go to fini. *+9 * TCP/IP is a stream oriented protocol and has no concepte of record boundries,3 * therefore if you wish to exchange variable lengthp records/messages (as is the 7 * case with the DEMO example) then you have to read thel first two bytes (ie: the9 * record header) of each message first, as this will telly us how many more bytes; * we need to receive to complete a SINGLE message transfer.  * ; * If this convention was not observed then a single network  read of 510 bytes (the8 * maximum buffer size for the demo example) could return multiple messages in a5 * single buffer, resulting in trailing messages being  ignored. *-     evaluate    true:         when    entry_data      move 109 to reply_body_len:         when    end_of_file     move   3 to reply_body_len:         when    error_msg       move 508 to reply_body_len     end-evaluate.        call    "sys$qiow"0             using   by value        0, net_chan, io$_readvblk(                     by reference    iosb(                     by value        0, 0.                     by reference    reply_body9                     by value        reply_body_len, 0, 0,S 0, 0             giving  sys_status.b;     if sys_status = ss$_normal move cond_val to sys_status.n-     if entry_data and sys_status = ss$_normal              add 1 to line_countt6             move corr entry_info_buffer to screen_line
 (line_count).e *  fini.e *o socket_close section.  00.i *+; * Break logical connection and dassign the network channel.d * 8 * The communication server will automatically deallocate
 any resources : * maintained on behalf of the client and will call, at AST
 level, the8 * interrupt routine specified in the Tier3 configuration file if thed: * client is currently associated with an execution server. *-4     call "sys$dassgn" using by value net_chan giving sys_status.3 *o display_welcome section. 00.g     call "sys$fao"4         using   by descriptor   "Welcome to the DEMO- application via TIER3 V!@UB.!@UB on node !AS".2                 by reference    welcome_string_len.                 by descriptor   welcome_string2                 by reference    maj_vers, min_vers'                 by descriptor   scsnode          giving  sys_status.5;     if sys_status not = ss$_normal call "lib$stop" using by  value sys_status.)2     display welcome_string (1:welcome_string_len).  1     move corr last_login_i to time_vector_binary.      perform cvt_lastlogin.1     string      "    Last interactive login on ",i5                 day_name (day_number) (1:day_name_len  (day_number)),#                 " ", vms_ascii_date !                 delimited by size      into        last_login_msg.      display last_login_msg.   1     move corr last_login_n to time_vector_binary.i     perform cvt_lastlogin.5     string      "    Last non-interactive login on ", 5                 day_name (day_number) (1:day_name_len  (day_number)),#                 " ", vms_ascii_datey!                 delimited by size      into        last_login_msg.      display last_login_msg.i       if logfails > zeros3         if logfails = 1 1             display "        1 failure since last  successful login"4         else)             move logfails to out_logfails9!             display logfails_msg.   5     display "Press RETURN to continue." no advancing.t*     accept key in end_key at end continue.       go to fini.  *  cvt_lastlogin. *73     call "lib$cvt_vectim" using time_vector_binary, " vms_binary_time giving sys_status.9     if sys_status not = lib$_normal call "lib$stop" using  by value sys_status.       call "sys$asctim" !         using   by value        03.                 by descriptor   vms_ascii_date/                 by reference    vms_binary_time !                 by value        0          giving  sys_status. ;     if sys_status not = ss$_bufferovf call "lib$stop" using  by value sys_status.  1     call "lib$day_of_week" using vms_binary_time,  day_number giving sys_status. ;     if sys_status not = ss$_normal call "lib$stop" using byF value sys_status.  *  fini.  *  end program demo_client_tcp_ip.a  # External MACRO symbol definitions:-   8             .title          DEMO_TCP_IP_DEF Demo example tcp/ip external data ; : ;  If the macro file sys$library:ucx$inetdef.mar exists on your VMS server system3 ;  then you can uncomment the following commands by  removing the semi-colons, ande; ;  delete the DEMO example specific symbols - starting frome inet_protyp$c_stream.  ;;+ 7 ;;  The following command can be used to create a macro( library INET in your default( ;;  area if one does not already exist:- ;;+ ;;           $library/create/macro inet.mlbp sys$library:ucx$inetdef  ;;- " ;           .library        /inet/" ;           $inetsymdef     GLOBAL" ;           $siocdef        GLOBAL" ;           $inetacpfsymdef GLOBAL" ;           $inetacpsymdef  GLOBAL" ;           $ineterrdef     GLOBAL ;   ,             inet_protyp$c_stream    ==     1,             ucx$c_tcp               ==     6,             ucx$c_af_inet           ==     2,             ucx$c_inaddr_any        ==     0,             ucx$c_sockopt           ==     1,             ucx$c_reuseaddr         ==     4,             ucx$c_full_duplex_close ==  8192,             ucx$c_keepalive         ==     8,             ucx$c_tcpopt            ==     6,             ucx$c_tcp_probe_idle    ==   128               .end         * Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautiful0   ------------------------------  # Date: Fri, 12 May 2000 14:45:43 GMTa& From: "gadtec" <gadtec@bigpond.net.au> Subject: VMS backup on PC < Message-ID: <rOUS4.1439$Kc3.8330@news-server.bigpond.net.au>  A     Does anyone know of s/w that can read files from a VMS Backup      tape (DAT) into Windoze.               Thanks in advance.   ------------------------------  # Date: Fri, 12 May 2000 17:11:15 GMT / From: "John Nixon" <jorlnixon@worldnet.att.net> + Subject: Re: Wildfire and the future of VMS F Message-ID: <TWWS4.5226$XO1.301358@bgtnsc06-news.ops.worldnet.att.net>  K I don't know if I got the "official" invitation, bu in my invitation, there K were three references to unix, and two references to VMS.  (I hope I am note- violating any copyrights;  I didn't see any).   8 1.  " This event will debut Compaq's new high-end CompaqJ  AlphaServer GS Series (code name Wildfire) system...the fastest RISC/UNIXE  Server in the industry!   It is also the fastest OpenVMS system ever 	  built. "   < 2.  "These new systems offer unprecedented flexibility, withJ  support for multiple operating systems, including Tru64 UNIX, OpenVMS and  Linux."  =   3. "Anyone considering the purchase of a high-end RISC/UNIX.8  system must consider the Compaq GS Series AlphaServer!"  J #3 does not mention VMS, but it does suggest reconsidering ordering a High end RISC/UNIX system.u  L Personally, I think this is pretty good compared to what we have seen in the past. $  Are these examples specific enough?        B "David J. Dachtera" <djesys.nospam@earthlink.net> wrote in message' news:391B7F9A.1ED764E5@earthlink.net...  > Clair Grant wrote: > >  > > E > > I have seen most of the official announcement material and VMS is  > > prominently mentioned. >   > To quote my 5th grade teacher: >  > "Be specific, cite examples".  >u > -- > David J. Dachterau > dba DJE Systems $ > http://home.earthlink.net/~djesys/ >3< > Unofficial Affordable OpenVMS Home Page and Message Board:- > http://home.earthlink.net/~djesys/vms/soho/    ------------------------------   End of INFO-VAX 2000.265 ************************