1 INFO-VAX	Fri, 29 Dec 2000	Volume 2000 : Issue 727       Contents:3 Re: ??== Examples of TCPIP socket FORTRAN programs.  RE: ACMS & Codasyl database 6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."6 Re: Bug - NLB0: crash, was: "NLA0: the null device..."	 Re: echo? 	 Re: echo? 	 Re: echo? 	 Re: echo?  Re: FTP is waiting to long!  RE: FTP is waiting to long! ( Re: Happy Holidays - From Rich Marcelllo& Re: Monitor on a AXP running VMS 7.2-1 tcpip show host error  Re: tcpip show host error   F ----------------------------------------------------------------------  % Date: Fri, 29 Dec 2000 09:00:29 +0100 - From: "Roland Hauk" <roland.hauk@indramat.de> < Subject: Re: ??== Examples of TCPIP socket FORTRAN programs.- Message-ID: <92hg1d$kvn1@sunny.mannesmann.de>    Hello Hans,    I hope this URL will help you.  L http://adcon.fnal.gov/conan/sys$common/syshlp/helplib.hlb?key=CC~/DECC~Run-tL ime_functions&title=Library%20/sys%24common/syshlp/helplib.hlb&referer=http%2 3a//adcon.fnal.gov/sys%24common/syshlp/helplib.hlb   Roland Hauk  Rexroth Indramat      ? "Hans M. Aus" <aus@vim.uni-wuerzburg.de> schrieb im Newsbeitrag > news:aus-2712001114130001@wvia78.virologie.uni-wuerzburg.de...I > Are there any PD examples available of programming TCPIP sockets either 3 > directly in FORTRAN or using calls to C programs?  > " > OpenVMS 7.2-1, Alpha, TCPIP 5.0a >  > --D > Cheers, Hans M. Aus, Wuerzburg, Germany,  aus@vim.uni-wuerzburg.de   ------------------------------  % Date: Fri, 29 Dec 2000 10:31:28 -0600 + From: "Main, Kerry" <Kerry.Main@compaq.com> $ Subject: RE: ACMS & Codasyl databaseN Message-ID: <910612C07BCAD1119AF40000F86AF0D805284B5E@kaoexc3.kao.cpqcorp.net>   Francis,  B >>> I would like to get all ACMS manuals (reference, user's guide,4 administration, system programming, ...) on a CDROM.  K I just checked my OpenVMS documentation CDrom and the ACMS files are not on 	 that CD.    0 However, the ACMS files are available online at:E <http://www.openvms.compaq.com:8000/index.html#acms> (V4.3 documents) ? http://www.openvms.compaq.com:8000> Main OpenVMS documents page    Regards,  
 Kerry Main Senior Consultant  Compaq Canada Inc. Professional Services  Voice: 613-592-4660  Fax  :  819-772-7036 Email: Kerry.Main@Compaq.com     -----Original Message-----5 From: Francis ANDRE [mailto:francis.andre@easynet.fr]  Sent: December 21, 2000 3:29 PM  To: Info-VAX@Mvb.Saic.Com $ Subject: Re: ACMS & Codasyl database     Roland  > I would like to get all ACMS manuals (reference, user's guide,4 administration, system programming, ...) on a CDROM.     Francis   * yyyc186.illegaltospam_@flashcom.net wrote: > 0 > In <3A3E0BD9.F811E111@easynet.fr>, on 12/18/00@ >    at 02:06 PM, Francis ANDRE <francis.andre@easynet.fr> said: > @ > ACMS has been here for a long time.  What do you wish to know? >  > Roland >  > >Hello There > F > >I am looking for information about ACMS and a Codasyl database that > >should have2 > >been implemented on VMS. Anyone could help me?? >  > >Thank you in advance  >  > >Francis ANDRE >  > --= > ----------------------------------------------------------- F > yyyc186@flashcom.net              To Respond delete ".illegaltospam"8 >                             MR/2 Internet Cruiser 2.2a: >                             For a Microsoft free univers= > -----------------------------------------------------------    ------------------------------  # Date: Fri, 29 Dec 2000 13:10:31 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) ? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." 0 Message-ID: <009F54F7.464BE58C@SendSpamHere.ORG>  j In article <92fjfh$a5$1@mailint03.im.hou.compaq.com>, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes: > n >In article <hshubs-D6B366.20471427122000@news.mindspring.com>, Howard S Shubs <hshubs@mindspring.com> writes:M >:In article <Pine.LNX.4.21.0012272342080.17395-100000@irys.stanpol.com.pl>,  = >:"Gotfryd Smolik, VMS lists" <gotfryd@stanpol.com.pl> wrote:  >:5 >:> Fortunatelly have access to a testing machine(s). A >:> Unfortunatelly the (testing) one has not fiber optic or other / >:>like-this-interesting stuff installed :( -;)  >:O >:So do I.  Tried it today since I had some time.  Created NLB0, tried copying  L >:from it: crash.  Tried modifying it (SET DEVICE/AVAILABLE): crash.  Tried L >:copying to it: crash.  Didn't try creating an NLC0: while I had the NLB0:  >:around.  Hm. >:P >:Kind of an obscure bug.  Has anyone put in a SPR (or whatever they're calling  >:it these days) about this? >  > L >  "Caution: Use extreme care when issuing SYSGEN CONNECT and LOAD commands J >  because the system does little error checking.  An incorrect vector or I >  misspelled device name, for example, will damage the I/O database and  8 >  could cause the system to fail."  -SysMan Essentials. > O > --------------------------- pure personal opinion --------------------------- M >   Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   F I thought you would have pointed out the major faux pas in this effortG described in this thread.  NLDRIVER does not exist -- neither on VAX or G Alpha.  The null device driver is built into the executive, thus insur-  ing its existance.  F I suspect that SYSGEN or SYSMAN would get awful confused attempting toG connect a device for which it has no driver or to one that has not been ) designed to have more than a single unit.    --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              O city, n., 1. a place where trees are cut down and streets are named after them.    ------------------------------  # Date: Fri, 29 Dec 2000 13:21:51 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) ? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." 0 Message-ID: <009F54F8.DBDBB9C2@SendSpamHere.ORG>  m In article <hshubs-C414D0.23525128122000@news.mindspring.com>, Howard S Shubs <hshubs@mindspring.com> writes: 7 >In article <92fjfh$a5$1@mailint03.im.hou.compaq.com>,  % >hoffman@xdelta.zko.dec.nospam wrote:  > M >>  "Caution: Use extreme care when issuing SYSGEN CONNECT and LOAD commands  K >>  because the system does little error checking.  An incorrect vector or  J >>  misspelled device name, for example, will damage the I/O database and 9 >>  could cause the system to fail."  -SysMan Essentials.  > P >Sure, however I don't see anything wrong with the idea of a second null device. >--  >Howard S Shubs E >"Run in circles, scream and shout!"  "I hope you have good backups!"   J Then write your own null driver.  Fairly simple.  You don't need much moreI than a simple shell of a driver with basic FDT handlers all returning via H FINISHIOC with some status you desire -- typcally, SS$_NORMAL.  In fact,I you can write your own null device driver and provide no-ops for serveral J other $QIO functions besides those handled by the VMS NL device -- namely, reads and writes.       --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              O city, n., 1. a place where trees are cut down and streets are named after them.    ------------------------------  + Date: Fri, 29 Dec 2000 16:06:29 +0100 (CET) : From: "Gotfryd Smolik, VMS lists" <gotfryd@stanpol.com.pl>? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." J Message-ID: <Pine.LNX.4.21.0012291551230.24529-100000@irys.stanpol.com.pl>  9 On Fri, 29 Dec 2000, Brian Schenkenberger, VAXman- wrote:   D +In article <>, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes: [...] M +>  "Caution: Use extreme care when issuing SYSGEN CONNECT and LOAD commands  K +>  because the system does little error checking.  An incorrect vector or  J +>  misspelled device name, for example, will damage the I/O database and 9 +>  could cause the system to fail."  -SysMan Essentials.   F  To be fair - all "looks" correct (except the non-existant driver -:))   [...] G +I thought you would have pointed out the major faux pas in this effort H +described in this thread.  NLDRIVER does not exist -- neither on VAX orH +Alpha.  The null device driver is built into the executive, thus insur- +ing its existance.   >  Yes, but b.ex. I was not aware of the fact that SYSGEN/SYSMAN@ can CONNECT only to explicite driver -:) althought the fact that; some drivers "compiled into" I am aware. Something new from $ time to time is required, really -:)  G +I suspect that SYSGEN or SYSMAN would get awful confused attempting to , +connect a device for which it has no driver  
  Probably.7  Have check a crash with MBDRIVER -:) (the non-existant ; but reported MB device driver) and second with OPB): device  (also "inline" OPERATOR driver) ;  In opposite the MPB device, loaded in startup with "real"  8 driver works correctly (with the  capability of "clone" 7 when OPEN to MPB0), some time ago have check LTB0: etc.   F +or to one that has not been designed to have more than a single unit.  B  Looks as the first: MB & OP can have multiple units, but will not work with second "controller".    Regards - Gotfryd   --  E ===================================================================== F $ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") - 		THEN EXCUSE/OBJECT=ME . $!                        GS@stanpol.zabrze.plE =====================================================================    ------------------------------   Date: 29 Dec 2000 17:17:16 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." 6 Message-ID: <92igus$dn8$1@mailint03.im.hou.compaq.com>  R In article <G6AI0z.MF8@spcuna.spc.edu>, Terry Kennedy <terry@gate.tmk.com> writes:5 :Hoff Hoffman <hoffman@xdelta.zko.dec.nospam> writes: N :>   "Caution: Use extreme care when issuing SYSGEN CONNECT and LOAD commands L :>   because the system does little error checking.  An incorrect vector or K :>   misspelled device name, for example, will damage the I/O database and  : :>   could cause the system to fail."  -SysMan Essentials. : M :  Sure. But I don't think either of those apply here. If NLA0: is one of the O :dedicated, sacred device names, then SYSGEN and friends should have a complete M :set of "you can't do that" errors for trying to clone it. From earlier posts K :here, it looks like they check for non-zero units on NLA but not making a  O :second controller (NLB). If I get some spare time (hah!) I'll look at the code  :to see why it is barfing.  H   Um, it has been my experience that users are quite creative with theirK   approaches to things where "you can't do that".  It is also my experience K   that users can be (are) affected when OpenVMS Engineering alters various  <   existing internal behaviours, whether undocumented or not.  H   In this particular case, as has been discussed elsewhere, there existsE   at least one product which (erroneously, IMO) loads a custom device I   driver under the NL prefix.  Consider that we could lock out all access J   to the "NL" prefix, but we would break this product.  (The most extreme L   approach, where all access to unregistered product device driver prefixes 4   is locked out, would definitely break things.  :-)  I   The null device itself is one of a few very special and select devices  H   on OpenVMS, as the driver is built directly into OpenVMS itself; it isI   not resident in a separately-loaded image.  In other words, this device %   driver is already somewhat unusual.   J   Yes, there are comparatively few "blade guards" within the device driverF   subsystems of SYSGEN and SYSMAN IO.  That said, errors in the input I   specifications central to the correct and normal operation of the tool  G   are very difficult to detect and defend against.  (We can and should  H   clearly look to special-case common cases of errors when feasible, andG   we can and should and do document that errors can lead to corruptions I   and crashes, but folks running with CMKRNL do need to be careful.  The  I   first-line protection against this particular potential OpenVMS system  5   crash is the CMKRNL privilege itself, of course...)   L   Though I suspect a general solution will be difficult to achieve at best, J   I am certainly interested in suggestions around how we can improve upon J   the current integrity checks within the existing CONNECT/LOAD support...  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 29 Dec 2000 17:22:03 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." 6 Message-ID: <92ih7r$dn8$2@mailint03.im.hou.compaq.com>  m In article <hshubs-C414D0.23525128122000@news.mindspring.com>, Howard S Shubs <hshubs@mindspring.com> writes: 7 :In article <92fjfh$a5$1@mailint03.im.hou.compaq.com>,  % :hoffman@xdelta.zko.dec.nospam wrote:  : M :>  "Caution: Use extreme care when issuing SYSGEN CONNECT and LOAD commands  K :>  because the system does little error checking.  An incorrect vector or  J :>  misspelled device name, for example, will damage the I/O database and 9 :>  could cause the system to fail."  -SysMan Essentials.  : P :Sure, however I don't see anything wrong with the idea of a second null device.  F   If you are interested, I'll see if I can adjust the existing volume D   shadowing support to permit the shadowing (mirroring) of multiple G   null devices, though served path failover would require an MSCP-aware F   null device driver or the use of the upcoming QIOserver support. :-)  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------    Date: 29 Dec 2000 12:56:10 -0500/ From: brooks@cuebid.zko.dec.nospam (Rob Brooks) ? Subject: Re: Bug - NLB0: crash, was: "NLA0: the null device..." - Message-ID: <u8Kf55n31TPo@cuebid.zko.dec.com>   k In article <92ih7r$dn8$2@mailint03.im.hou.compaq.com>, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes: H >   If you are interested, I'll see if I can adjust the existing volume F >   shadowing support to permit the shadowing (mirroring) of multiple I >   null devices, though served path failover would require an MSCP-aware H >   null device driver or the use of the upcoming QIOserver support. :-)  B Right -- and I'll look into the feasibility of a multipathed null 
 device :-)    M Rob Brooks    VMS Engineering -- I/O Exec Group     brooks@cuebid.zko.dec.com    ------------------------------  % Date: Fri, 29 Dec 2000 08:47:43 -0600 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>  Subject: Re: echo?- Message-ID: <3A4CA40F.92025EAD@earthlink.net>    "Alan E. Feldman" wrote: > [snip] > Start with the User's Manual:  > > > http://www.openvms.compaq.com:8000/72final/6489/6489pro.html  E If you're behind a firewall that blocks non-standard HTTP ports, try:   ; http://www.openvms.compaq.com/doc/72final/6489/6489pro.html    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  % Date: Fri, 29 Dec 2000 10:14:25 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca>  Subject: Re: echo?, Message-ID: <3A4CAA4D.6A8F2C06@videotron.ca>   $echo :== "write sys$output " ) $echo "Navel lint overload, please clean"  $echo ""( $echo "--------------------------------"   etc etc    ------------------------------  % Date: Fri, 29 Dec 2000 22:58:42 +0800 # From: "Tycoon" <tycoon@i-cable.com>  Subject: Re: echo?* Message-ID: <92i8jg$m286@rain.i-cable.com>   At DCL prompt :  $ say = "write sys$output" $ say "Happy new year !" Happy new year !   ------------------------------  # Date: Fri, 29 Dec 2000 15:49:19 GMTa* From: Alan E. Feldman <alan48@my-deja.com> Subject: Re: echo?) Message-ID: <92ibpt$fsj$1@nnrp1.deja.com>   ) In article <92gqlg$c20$1@nnrp1.deja.com>,u-   Alan E. Feldman <alan48@my-deja.com> wrote:"1 > In article <3a4bccd7.53294502@news1.telia.com>,e! >   asgd@sverige.nu (Asgd) wrote:NB > > I trying to learn VMS (at the univerity) as a part in a bigger course..D > > But now Im stuck and cant find the right command. Dont winkle your7 > > nose to much...the command is at Unix and Dos: echoF1 > > I want to print a line of text on the screen!S [...] ' > To do the equivalent of MS-DOS @ECHO:s --1 Uh, make that the equivalent of MS-DOS @ECHO OFF:-   >- > $ !'F$VERIFY(0)'  F NOTE: If you wish to e-mail me, please do NOT use the deja address. ItE is broken. Instead, use one of the addresses below, removing the longo wrong part first. Thanks.$   Disclaimer: JMHO Alan E. Feldman  &-)+ w: afeldman@gfigroup.ButItSaidItPrinted.coma5 h: alan48@dellnet.YouCantBelieveEverythingYouRead.comC     Sent via Deja.comi http://www.deja.com/   ------------------------------  % Date: Fri, 29 Dec 2000 09:01:02 +0100o- From: "Roland Hauk" <roland.hauk@indramat.de>n$ Subject: Re: FTP is waiting to long!- Message-ID: <92hg2e$kvo1@sunny.mannesmann.de>a   Hy, thanks too all,a  " 1. I don't have problems with DNS.J     My problem is that FTP server on the other side is down, but the IP is
 reachable.L     In this case UCX is connecting to IP and waits to logon fore some hours.6     I get no error, FTP is still waiting hour by hour!  8 2. if I connect to a unknown IP with "ftp 127.222.100.5"J     I get this answer:    %TCPIP-E-FTP_NETERR, I/O error on network deviceJ                                  -SYSTEM-F-UNREACHABLE, remote node is not currently reachable4          E "Bochnik, William J" <BochnikWJ@bernstein.com> schrieb im NewsbeitragaD news:2B37459189B0D211BE710000F8EF9D8508908A78@nts0147.beehive.com...D > good point - his client should almost immediately return an error. Roland,sF > what happens if you try ftp'ing to a addr. that doesnt exist (or the machinet
 > is down)???. >p > -----Original Message----- > From: Barry Treahy, Jr.w" > Sent: December 28, 2000 11:15 AM > To: Bochnik, William J > Cc: Info-VAX@Mvb.Saic.Comn& > Subject: Re: FTP is waiting to long! >S >iH > Perhaps I did miss something, but if there isn't an active TCP service	 > running-I > on the port, I do not know of any ftp client that takes five minutes to.K > 'timeout', you should see a connection refused message returned or on VMSR > you'll< > see a error related to being unable to create the circuit. >a > Barrye >, > "Bochnik, William J" wrote:  >tF > > I think you missed his point - he knows that the server end is not
 > running,J > > but he wants his ftp to timeout (indicating the problem).  I think (at > leastnH > > on several implementations) that the timeout is set to 5 min, and he isnt > > waiting that long....k > >  > > >From: Barry Treahy, Jr.% > > >Sent: December 28, 2000 10:47 AM  > > >To: Info-VAX@mvb.saic.com) > > >Subject: Re: FTP is waiting to long!  > > >  > > >c6 > > >Hi Roland, I can see several reasons for a delay. > > >DG > > >1. The target machine has problems with their DNS server or cannot-L > > >reverse DNS lookup your IP because of a DNS configuration error on your  
 > > >machine.  > > > G > > >2. They are blocking FTP access (TCP port 21) and not allowing forf< > > >rejection notification but simply dropping the packets. > > >-J > > >3. The target system is failing during process creation of the remote > > >TCP process.m > > >aL > > >If you do a netstat on both systems, what do you see for the connection > > >state between the two?  > > >g
 > > >Barry > > >B > > >Roland Hauk wrote:  > > >c/ > > >> We have OpenVMS7.2 and TCPIP (UCX) V5.0.f > > >>' > > >> - Now I connect to a FTP server. : > > >> - The IP is reachable, but the FTP program is down. > > >>* > > >> I start FTP:  $ FTP 111.222.333.444< > > >> and FTP is now waiting for login without any timeout. > > >>' > > >> What must I do to get a timeout?s > > >> > > >> Roland Hauk > > >> Rexroth Indramatl > > >  > >s > > -- > > C > > Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIOc > >tE > > E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028  >e > -- >yA > Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIOc >hC > E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028n >o   ------------------------------  % Date: Fri, 29 Dec 2000 12:41:50 -0500 4 From: "Bochnik, William J" <BochnikWJ@bernstein.com>$ Subject: RE: FTP is waiting to long!J Message-ID: <2B37459189B0D211BE710000F8EF9D8508908A8E@nts0147.beehive.com>  K Something must be up with his client install - on our system, when I try to F connect to a machine that is up, but no ftp service running, I get the
 following:  * %FTP-E-NETERR, I/O error on network device4 -SYSTEM-F-REJECT, connect to network object rejected     -----Original Message----- From: Roland Hauk- Sent: December 29, 2000 3:01 AMp To: Info-VAX@mvb.saic.comn$ Subject: Re: FTP is waiting to long!     Hy, thanks too all,e  " 1. I don't have problems with DNS.J     My problem is that FTP server on the other side is down, but the IP is
 reachable.L     In this case UCX is connecting to IP and waits to logon fore some hours.6     I get no error, FTP is still waiting hour by hour!  8 2. if I connect to a unknown IP with "ftp 127.222.100.5"J     I get this answer:    %TCPIP-E-FTP_NETERR, I/O error on network deviceJ                                  -SYSTEM-F-UNREACHABLE, remote node is not currently reachable    ------------------------------  + Date: Fri, 29 Dec 2000 12:25:53 +0000 (UTC)e' From: Osmo Kujala <kujala@tukki.jyu.fi>-1 Subject: Re: Happy Holidays - From Rich Marcelllom, Message-ID: <92hvsh$ms7$1@mordred.cc.jyu.fi>  . Warren Spencer <wspencer@ap.nospam.org> wrote:% > In a multi-platform world, perhaps DL > the Christmas message would have been best rendered in multiple formats.    * Very funny. :-(  Never heard of standards?  E > But if you want the OpenVMS message to spread easily and widely in oK > management circles, it had better be in a format a Microsoft desktop can x/ > inhale - Windows "owns" our managers (today).o  F Windows doesn't understand HTML, GIF, MPEG, PS... (and ASCII!)  ??????   > I'd also like to e+ > offer this:  OpenVMS ain't a desktop OS. e  J I don't like that opinion. I've used VMS as desktop OS 10 years. It's beenI better that those Wintel PC:s used around here. Some problems nowadays ofu> course, because of proprietary MS formats like Word and Excel.H ( see: http://www.jyu.fi/~juhtolv/mswordmail.html , sorry about finnish)   > All the high-end features G > that make it so scalable and reliable differentiate it from Windows. l  E Yes (for some time still), but it doesn't make VMS worse for desktop.NH I think the high-end features are must, but the real potential of VMS isD scaleability to every size of installations. Strong points for small@ devices are small code size of VMS and easy diskless booting andI easy using of "idle" time for batch and easy maintaining and coordinating ' of workstations and reliability and... s  F > I'd hate to see the OpenVMS team re-direct their efforts to desktop  > applications.   C No need to re-direct. Do both. VMS is worth that. (Remember $4000M)sF Our university has spent millions to VMS as all purpose OS. (History.)  @ Maybe there is not so much needed for desktop. If VMS were knownJ OS, someone would do the applications. Maybe porting from Linux is enough.  @ >  There are significantly larger and more strategic challenges I > that need to be addressed in a wired world, like IFD (Immense Freakin' GK > Databases) and IFUB:  ten million interactive users pounding on your web k$ > site (Immense Freakin' User Base).  A Okay. These fine features may temporarily make VMS high end niche I stronger, but it's hard to sell that to world that doesn't know much more D than Windows and understands that soon that same OS - Windows - willB handle fine all high end systems too (and that's true). No need to know anything of archaic VMS.   J This high end niche approach has been on for a long time and it has barelyJ kept VMS alive. If there's nothing else to come, VMS is as good as dead to me at least.  K > If you want to run OpenVMS as your desktop - my hat's off to you. If you )B > want to communicate with your management, uhmmmm, use the phone.  I No problem with OpenVMS in communicating. Phone is good too. Talking faceY to face even better.   regardsn           Osmo Kujalac   ------------------------------  % Date: Fri, 29 Dec 2000 18:05:52 +1100s/ From: "Phil Howell" <phowell@snowyhydro.com.au>t/ Subject: Re: Monitor on a AXP running VMS 7.2-1 . Message-ID: <HGW26.38$m87.1681@ozemail.com.au>  4 Shawn <sfm1115@bjcmail.carenet.org> wrote in message* news:3a436082.76217725@news.starnet.net...F > I know how to run Monitor System and Monitor System/all.  Is there aE > way I can re-direct the output to a file rather than the system.  ILE > have tried within monitor to do a SET_DEFAULT /FILENAME=mon.log butw > this has not worked. > B > I looked through my manuals and was unable to locate the correct; > parameter to set.  Any help would be greatly appreciated.I >,- > I am running OpenVMS 7.2-1 on an Alpha 2100C >/I As others have mentioned you can monitor /record and then replay it later=9 If you just want to capture the terminal output you could-1 either set host /log 0 and record a whole session7 or use @tt/out=<filename>d0 then at the $ prompt enter your monitor commands5 then $exit and all the output should be in <filename>s Phil   ------------------------------  % Date: Fri, 29 Dec 2000 11:10:04 +0100n> From: "Jean-Franois Marchal" <jean-francois.marchal@x9000.fr> Subject: tcpip show host error. Message-ID: <92hnod$liv$1@reader1.imaginet.fr>   Bonjour  tous !     When issuing a       $ tcpip show hosts  2 I get the list of my LOCAL database, followed by :  ,     %TCPIP-W-NORECORD, information not found,     -NONAME-E-NOMSG, Message number 0764960A   When issuing  "     $ tcpip show host www.x9000.fr  2 I get the correct BIND database entry from the DNS) which is is held by my Internet Provider.d  ; When I try to ping www.x9000.fr, ping finds the ip address, 6 but falls in timeout. However, I can ping this address from outside my lan.  9 I'm connected through a CISCO 1401 router performing NAT.u     Any hint will be appreciated !   Merci et bonne anne Jean-Francois Marchalo X9000 - LYON (FR)    ------------------------------  + Date: Fri, 29 Dec 2000 16:22:39 +0100 (CET)e: From: "Gotfryd Smolik, VMS lists" <gotfryd@stanpol.com.pl>" Subject: Re: tcpip show host errorJ Message-ID: <Pine.LNX.4.21.0012291618180.24529-100000@irys.stanpol.com.pl>  3 On Fri, 29 Dec 2000, Jean-Fran=E7ois Marchal wrote:o   +Bonjour =E0 tous !t +l +c +When issuing ad +u +    $ tcpip show host +s3 +I get the list of my LOCAL database, followed by :d + - +    %TCPIP-W-NORECORD, information not foundC- +    -NONAME-E-NOMSG, Message number 0764960Ao +e
 +When issuingu +e# +    $ tcpip show host www.x9000.fr  +r3 +I get the correct BIND database entry from the DNSo* +which is is held by my Internet Provider.  7  Probably "your IP" is not allowed to list the database 9 (but allowed to check separate record). The "proctection" 8 work like Read vs. Execute for DIRECTORY file in VMS -;)$ and really is set on some providers.@  Ask the admin. of (providers) DNS if you are allowed to "list".  < +When I try to ping www.x9000.fr, ping finds the ip address,7 +but falls in timeout. However, I can ping this addressY +from outside my lan.a  .  Hm... can be a separate problem with routing,  : +I'm connected through a CISCO 1401 router performing NAT.   =2E..especially with NAT...f    Regards - Gotfryd   --=20dC =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=lC =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=oC =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=e	 =3D=3D=3DTF $ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") = -t =09=09THEN EXCUSE/OBJECT=3DMEv. $!                        GS@stanpol.zabrze.plC =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=cC =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= C =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=.	 =3D=3D=3D-   ------------------------------   End of INFO-VAX 2000.727 ************************