1 INFO-VAX	Tue, 13 Dec 2005	Volume 2005 : Issue 693       Contents:" Re: calloc() fails, no more memory/ Re: ESC sequence for Left Margin to less then 0 / Re: ESC sequence for Left Margin to less then 0 A Re: Question about SPAWN/INPUT table in the DCL Dictionary manual A Re: Question about SPAWN/INPUT table in the DCL Dictionary manual A Re: Question about SPAWN/INPUT table in the DCL Dictionary manual 8 Re: SDA> TCPIP SHO DEV/PORT=n/SOCK displays no BG device% Re: SHOW DEVICE: what should it show? % Re: SHOW DEVICE: what should it show? % Re: SHOW DEVICE: what should it show?  SRM memtest  Re: Time problem0 Re: Timeout strategy: terminal vs Telnet drivers0 Re: Timeout strategy: terminal vs Telnet drivers0 RE: Timeout strategy: terminal vs Telnet drivers0 Re: Timeout strategy: terminal vs Telnet drivers0 Re: Timeout strategy: terminal vs Telnet drivers0 Re: Timeout strategy: terminal vs Telnet drivers0 RE: Timeout strategy: terminal vs Telnet driversC Re: USB on OpenVMS (was: Re: DS10L hardware configuration question) C Re: USB on OpenVMS (was: Re: DS10L hardware configuration question)  WTB: VAX FT810 parts.   F ----------------------------------------------------------------------    Date: 13 Dec 2005 01:56:03 -08001 From: "hanblo@netscape.net" <hanblo@netscape.net> + Subject: Re: calloc() fails, no more memory B Message-ID: <1134467763.573507.87580@g44g2000cwa.googlegroups.com>   Hi all, & it grew to quite a thread. Thanks all.E I tried a loop calloc:ing 400000 pointers (1.6 Mb approx). The 383:rd 8 attempt fails. errno = %x0c, vaxc$errno = 0. I think theC programmer/developer should do a review of his program,  the calloc ? failing can't be the main problem, and then he is welcome back.    Thanks again all	 Hans Blom    ------------------------------    Date: 13 Dec 2005 05:19:30 -0800! From: Jesse.Chambless@acs-inc.com 8 Subject: Re: ESC sequence for Left Margin to less then 0C Message-ID: <1134479970.076048.145440@g44g2000cwa.googlegroups.com>    timf@ptd.net wrote: I > Does anyone know how the PCL for setting left margin to be less than 0. G > I tried negative number and the result was the same as 0. The printer  > is a LEXMARK.  >  > Tried: > 3 > <ESC>&a9                     ! Resets left margin  > <ESC>&a9, <ESC>&a0L  > <ESC>&a9, <ESC>&a-2L > I > The desired output is for the first character of each line is to start:  >  >  here. > / >     not here. Which seems  to be the default.  >  > 7 > The customer does not allow for any form definitions.  > # > Any input is greatly appreciated.   D Use the HMI and VMI control sequences to move the text once you have$ the left margin set.  That may work.  5 These are the <esc>&lxxxxU and <esc>&lxxxxZ commands.    ------------------------------  % Date: Tue, 13 Dec 2005 05:26:40 -0800 ( From: Jeff Cameron <roktsci@comcast.net>8 Subject: Re: ESC sequence for Left Margin to less then 00 Message-ID: <BFC40C10.18E91%roktsci@comcast.net>   On 12/12/05 8:42 PM, in article > 1134448945.360114.46340@g49g2000cwa.googlegroups.com.gnresend,$ "timf@ptd.net" <timf@ptd.net> wrote:  I > Does anyone know how the PCL for setting left margin to be less than 0. G > I tried negative number and the result was the same as 0. The printer  > is a LEXMARK.  >  > Tried: > 3 > <ESC>&a9                     ! Resets left margin  > <ESC>&a9, <ESC>&a0L  > <ESC>&a9, <ESC>&a-2L > I > The desired output is for the first character of each line is to start:  >  >  here. > / >     not here. Which seems  to be the default.  >  > 7 > The customer does not allow for any form definitions.  > # > Any input is greatly appreciated.  > J Here is a link for an HTML version of the VT220 programmer's manual, which# has all the escape sequences in it.   , http://vt100.net/docs/vt220-rm/contents.html   ------------------------------    Date: 13 Dec 2005 07:10:23 -0600 From: briggs@encompasserve.orgJ Subject: Re: Question about SPAWN/INPUT table in the DCL Dictionary manual3 Message-ID: <4osNBhHhlmTK@eisner.encompasserve.org>   j In article <1134423071.479544.144610@o13g2000cwo.googlegroups.com>, "AEF" <spamsink2001@yahoo.com> writes: > ! > briggs@encompasserve.org wrote: m >> In article <1134403065.283312.274140@z14g2000cwz.googlegroups.com>, "AEF" <spamsink2001@yahoo.com> writes: H >> > Apparently the confusion is coming from the NRO term. I thought allI >> > these examples you show use record-oriented devices. So what's going < >> > on? I think this term, NRO, is the crux of the problem. >>A >> Disk devices are not record oriented.  They are file oriented.  >>L >> Disk EISNER$DRA3:, device type 7 Member RAID 5, is online, mounted, file-R >>     oriented device, shareable, available to cluster, error logging is enabled. >>P >> Device MBA8964:, device type local memory mailbox, is online, record-oriented) >>     device, shareable, mailbox device.  >>R >> Terminal VTA2621:, device type VT200 Series, is online, record-oriented device, >>     carriage control. >>I >> Again, as I wrote in my first response, the issue is file positioning. G >> If you are trying to pass an open file complete with record position H >> to the subprocess, that's more difficult than simply passing a deviceH >> name.  And if you are trying to reposition the parent record positionG >> to reflect records consumed by the child, that's more difficult than M >> simply reading the next record from the mailbox/card reader/user keyboard.  >>N >> The important distinction is that record-oriented devices are non-seekable. > 5 > I goofed. I meant record-oriented files. Anyway,...   G What would you mean by a non record-oriented file on VMS?  If you don't B know then you have no business uttering the term "record-oriented"$ except in the context of a question.  B > The manual says NON-record-oriented process-permanent FILES. TheH > mailbox and terminal are record-oriented, so the table shouldn't applyI > to them. The disk is a device, not a file, so the table shouldn't apply  > to it.  H Files on disk are not record-oriented in the relevant sense of the term.   I explained why.  
 Deal with it.    	John Briggs   ------------------------------    Date: 13 Dec 2005 07:18:02 -0600 From: briggs@encompasserve.orgJ Subject: Re: Question about SPAWN/INPUT table in the DCL Dictionary manual3 Message-ID: <0h2pvlbow3d0@eisner.encompasserve.org>   q In article <ycyoQ1w5bc+m@eisner.encompasserve.org>, koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: V > In article <xlHiO2ZuCRsS@eisner.encompasserve.org>, briggs@encompasserve.org writes: >>  ( >> Now, what's a "record-oriented" file? >>  E >> A record-oriented file is a mailbox, or a card reader.  What other J >> platforms might call a "unit record" device.  It is a sequential device# >> that returns a record at a time.  > I >    Or a file on disk or tape, with attributes that make it a collection H >    of records.  And of course, if it isn't a collection of records butD >    your accessing it through RMS, it can look like a collection of >    records anyhow.  E We are trying to talk about NRO PPFs.  I do not believe that any file C on disk or tape can qualify as a RO PPF in this sense of the notion  of "record oriented".   A RMS cannot make a single file on disk manifest as a single record H stream for consumption by multiple competing processes.  Record position@ is not maintained in a shared fashion across process boundaries.   	John Briggs   ------------------------------    Date: 13 Dec 2005 07:29:55 -0800$ From: "AEF" <spamsink2001@yahoo.com>J Subject: Re: Question about SPAWN/INPUT table in the DCL Dictionary manualB Message-ID: <1134487795.605868.89250@g49g2000cwa.googlegroups.com>   briggs@encompasserve.org wrote: l > In article <1134423071.479544.144610@o13g2000cwo.googlegroups.com>, "AEF" <spamsink2001@yahoo.com> writes: > > # > > briggs@encompasserve.org wrote: o > >> In article <1134403065.283312.274140@z14g2000cwz.googlegroups.com>, "AEF" <spamsink2001@yahoo.com> writes: J > >> > Apparently the confusion is coming from the NRO term. I thought allK > >> > these examples you show use record-oriented devices. So what's going > > >> > on? I think this term, NRO, is the crux of the problem. > >>C > >> Disk devices are not record oriented.  They are file oriented.  > >>N > >> Disk EISNER$DRA3:, device type 7 Member RAID 5, is online, mounted, file-T > >>     oriented device, shareable, available to cluster, error logging is enabled. > >>R > >> Device MBA8964:, device type local memory mailbox, is online, record-oriented+ > >>     device, shareable, mailbox device.  > >>T > >> Terminal VTA2621:, device type VT200 Series, is online, record-oriented device, > >>     carriage control. > >>K > >> Again, as I wrote in my first response, the issue is file positioning. I > >> If you are trying to pass an open file complete with record position J > >> to the subprocess, that's more difficult than simply passing a deviceJ > >> name.  And if you are trying to reposition the parent record positionI > >> to reflect records consumed by the child, that's more difficult than O > >> simply reading the next record from the mailbox/card reader/user keyboard.  > >>P > >> The important distinction is that record-oriented devices are non-seekable. > > 7 > > I goofed. I meant record-oriented files. Anyway,...  > I > What would you mean by a non record-oriented file on VMS?  If you don't D > know then you have no business uttering the term "record-oriented"& > except in the context of a question.  F A file whose record format is undefined (see SET FILE/ATTR=RFM:UDF) orD some really bizarre file from a non-VMS system are the only things ID can think of, which is why I was confused in the first place. Hey, IF didn't right the doc. But if you do SHOW DEVICE SYS$INPUT/FULL you areF almost always going to get "record-oriented" in the output. (Actually,E I have yet to see otherwise.) I was trying to figure out what the DOC B meant by non-record-oriented. Since the output of SHOW DEVICE/FULLF SYS$INPUT has -- in my experience -- always indicated record-oriented,5 I was confused as to what a NRO PPF w.r.t. SYS$INPUT.    > D > > The manual says NON-record-oriented process-permanent FILES. TheJ > > mailbox and terminal are record-oriented, so the table shouldn't applyK > > to them. The disk is a device, not a file, so the table shouldn't apply 
 > > to it. > J > Files on disk are not record-oriented in the relevant sense of the term. >  > I explained why. >  > Deal with it.   G Fine. But this is a user manual and I wouldn't expect a typical user to E have such sophistication as to correctly get the meaning of NRO PPF's F in this case. I thought there had to be a simpler explanation. If I doE SHOW DEVICE SYS$INPUT/FULL and it says that it's record-oriented, how > am I supposed to make the leap to the fact that it is actuallyF non-record-oriented for this purpose? So I posted and you provided the answer. Thank you.   >  > 	John Briggs   AEF    ------------------------------    Date: 13 Dec 2005 04:07:02 -08002 From: "Gerald_Marsh" <gerald.marsh@barclays.co.uk>A Subject: Re: SDA> TCPIP SHO DEV/PORT=n/SOCK displays no BG device B Message-ID: <1134475622.884263.36100@g43g2000cwa.googlegroups.com>  ? Thank you for that, John. It allowed me to see exactly when the 7 offending socket was created and a lot of other things!   E My experiment over the weekend timed-out. I started another yesterday E with the Java client and the socket has now been in FIN_WAIT_2 for 24  hours and 20 minutes!   ? The "server" side now has the options set but it's not made any 
 difference...      Options:  KeepAlive,ReuseAddr B   State:    CantRcvMore,CantSendMore,FrcdLinger,NoFDRef,NoUCB,Priv   TCPstate: FIN_WAIT_2   TCPflags: SentFin,ReqScale   Special:  None   RCV Buff: None   SND Buff: None  G We have a messy workaround to address the original problem but I'll let ( the group know anything else I find out.  G (What were the gags you placed in the TCPIP module? Email them if you'd  rather.)  D Bye for now - I love Usenet for this type of stuff: Direct access to# the fella who wrote the SDA module!   
 Thanks again,      Gerald.        John Gemignani, Jr. wrote:H > A BG device will only be present if there is a channel assigned to the > socketG > by at least one process.  Adding /SOCKET to the TCPIP SHOW command is N > looking for the socket structure in the memory tables as opposed to scanning: > the BG device list and linking to the socket from there. > N > The socket structure often lingers after close to ensure that it catches all	 > packets I > no matter what path around the globe they took.  Setting REUSEADDR will M > allow your app to replace the socket before the normal timeout value, which  > I . > believe is SUPPOSED TO BE about two minutes. > 3 > You mentioned something about a terminal session?  > N > I did all of the work on the TCPIP SDA extension.  Some people bitched a fewM > years ago about some of the gags that I had put in there, so I removed them  > beforeN > I left HP and moved on.  A lot of the commands have a special (undocumented)E > /DEBUG qualifier that usually displays special information such as:  > ! >         .... SO at xxxxxxxx ...  > 4 > In this case, you can look at the structure using: > & >         FORMAT /TYPE=SOCKET xxxxxxxx > M > NOTE: Normally this would be /TYPE=SO, but for some reason the tables built  > with the netstack K > called them SOCKETS and not SO.  Check out "TCPIP SHOW MEMORY /TYPES" and  > you'll8 > see a list of types built into the kernel's knowledge. > J > (I'm starting to forget a lot of my VMS, so I hope that I got it right.) > J > If you want to see all of the socket structures and such, to see if your
 > unexplained ) > socket is somewhere in the system, use:  > D >         TCPIP SHOW MEMORY /TYPE=SOCKET /COMMAND="FORMAT /TYPE=SO " >  > John > ? > "Gerald_Marsh" <gerald.marsh@barclays.co.uk> wrote in message ? > news:1134143138.914035.319050@g47g2000cwa.googlegroups.com... I > > I've managed to replicate the problem on the OpenVMS system using the I > > noddy client and server programs supplied with TCPIP Services. I just F > > put a big wait in the client before closing the socket. The serverG > > sends the test string and exits ok - It's socket is in Closewt. The + > > client immediately goes into FIN_WAIT2.  > > H > > If I kill the terminal emulation session, the socket closes ok afterG > > going into TIME_WAIT for a few minutes. However, if I establish the I > > same situation from a PC (NT4) using a Java client then the FIN_WAIT2 * > > persists - even if I power off the PC!I > > (Java class was cross-compiled from OpenVMS - File transfer was a bit ' > > of a git but it worked eventually!) G > > Tried setting KEEPALIVE option but that hasn't made any difference.  > > B > > I'll have a look after the weekend to see if it has timed out. > > , > > Bye for now and thanks for the comments, > >  > > Gerald.  > >  > >  > >  > > Gerald Marsh wrote:  > >> Hello VMSers  > >>K > >> Here's a cracker which maybe should be targetted at the TCPIP brigade.  > >> > >> Scenario... > >>K > >> OpenVMS process running happilly receiving messages via TCP/IP from NT 	 > >> box.  > >>: > >> Process fails to respond to messages from NT system -0 > >> TCPIP> SHO DEV/PORT=n shows no such device. > >>D > >> After much web and newsgroups searching, a better command of... > >>I > >> SDA>TCPIP SHO DEV/PORT=n/SOCK shows some big hex number and a socket 3 > >> in FIN_WAIT_2. The BG device no longer exists.  > >>I > >> The OpenVMS listener can be STOP/ID'd and refuses to restart because 8 > >> of a"addrinuser" error - 48, if I recall correctly. > >>F > >> After some random time the situation resolves itselfs - somewhereI > >> between 42 mins (Hitchhiker's Guide to the Galaxy, springs to mind!) K > >> but can go up to over an hour. No TPCIP Services timer seems to relate H > >> to this and the supplier of the application - both OpenVMS and NT - > >> cannot explain it either! > >>D > >> My intellectual capacity cannot handle the well published stateF > >> diagrams and apply them to our situation.: The socket seems to beG > >> awaiting a FIN from the other side and then should send it an ACK. C > >> Some research of the relevant RFC's suggest the damn thing can H > >> legitimately stay in the FIN_WAIT_2 state for ever as the app couldF > >> expect to process real info. Cannot undertand that it the app has > >> called a close()! > >>K > >> The supplier - who is very responsive on this but a bit flummoxed - is G > >> going to go through formal channels but I'm hoping to contact that D > >> strange combination of a VMS Systems Manager and IP specialist!# > >> (One of the many black arts??)  > >> > >># > >> Keep theOpenVMS flag a'flying,  > >> > >> Gerald. > >> > >> Gerald Marsh  > >>9 > >> gerald -at_Sign- cyfer -dot- demon -dot- co -dot- uk 1 > >> (And I really get miffed having to do that!)  > >    ------------------------------    Date: 13 Dec 2005 07:55:22 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) . Subject: Re: SHOW DEVICE: what should it show?3 Message-ID: <um1MBMZfcJD9@eisner.encompasserve.org>   ^ In article <dnl1vg$k46$2@newslocal.mitre.org>, klewis@OMEGA.MITRE.ORG (Keith A. Lewis) writes: > helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes in article <dnkrr8$gnj$1@online.de> dated Mon, 12 Dec 2005 21:59:04 +0000 (UTC):K >>SHOW DEVICE shows a lot of devices, but not all.  For example, not NET*.  H >>Yes, with SHOW DEVICE NET you can see them, but not with no arguments. >> >>Bug or feature?  > * > Feature.  A relatively new one, I think.  :    Not new.  At least not new since VMS 2.5 on VAX 11/780.   ------------------------------    Date: 13 Dec 2005 07:54:14 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) . Subject: Re: SHOW DEVICE: what should it show?3 Message-ID: <goQyx1kOTL9I@eisner.encompasserve.org>   w In article <dnkrr8$gnj$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: K > SHOW DEVICE shows a lot of devices, but not all.  For example, not NET*.  H > Yes, with SHOW DEVICE NET you can see them, but not with no arguments. >  > Bug or feature?  > + > Is there an easy way to show ALL devices?  >   H    When you have a ton of MBA you are glad SHOW DEVICE assumes you don't,    want to see them unless you ask for them.   ------------------------------  % Date: Tue, 13 Dec 2005 11:04:02 -0500  From: norm.raphael@metso.com. Subject: Re: SHOW DEVICE: what should it show?Q Message-ID: <OF1CC71604.35BC25F7-ON852570D6.0058092D-852570D6.005842D9@metso.com>   > hoff@hp.nospam (Hoff Hoffman) wrote on 12/12/2005 05:55:43 PM:  E > In article <1134425458.095982.235660@g44g2000cwa.googlegroups.com>, 1 > "Allosaur" <ALLOSAUR@ATHENA.SITECH.COM> writes: I > :I note BG (TCP/IP) devices also do not appear, nor do MB mailboxes. It D > :must be that these virtual devices with no real hardware were not6 > :considered important for the "SHOW DEVICE" command. > J >   It was considered that there are usually a gazillion of these devices,I >   and the display of these wasn't something that (most) users wanted to G >   see.  (SHOW DEVICE also uses direct access into kernel mode, and it H >   passes a buffer back down to user mode for display, so there is alsoH >   a preference to fit the data within this buffer -- likely due to itsG >   sheer age, SHOW DEVICE does not work the way you might expect; it's G >   not a loop of $device_scan[w] and $getdvi[w] system service calls.)  > H >   Devices with the MBX bit set within the UCB are among those filteredH >   by the kernel-mode code, and this accounts for most of (all of?) the >   devices cited. > G >   Adding /SELECT, maybe, with a default of the current behaviour, and D >   some set of keywords to allow different selection criteria to beE >   requested, might well be a reasonable enhancement suggestion, for I >   those that wanted to see a list of every device name.  (Folks writing H >   DCL command procedures seeking devices should be using the availableI >   DCL lexical functions of course, and these can and do allow access to - >   the names of all of the devices present.)  > I >   (I thought about SHOW DEVICE/ALL here, but that would tend to collide , >   with the existing /ALLOCATED qualifier.)  
 Perhaps  SHOW E DEVICE/INCLUDE=(ALL|comma-separated-list)/EXCL=(comma-separated-list) E or minuses allowed in the /INCLUDE list as in the ACCOUNTING utility?    >  > 2 >  ---------------------------- #include <rtfaq.h> ----------------------------- 3 >     For additional, please see the OpenVMS FAQ --  www.hp.com/go/openvms/faq 4 >  --------------------------- pure personal opinion --------------------------- I >        Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[\0100]hp.com  >    ------------------------------  % Date: Tue, 13 Dec 2005 09:57:26 -0800 % From: J.C. Roberts <unknown@abac.com>  Subject: SRM memtest8 Message-ID: <np2up19eppppcs5ddh3qvk9j58u6e9fvm7@4ax.com>  G I noticed something odd on an Alpha Personal Workstation 433 that I got E off of eBay. The ARC/AlphaBIOS would occasionally report 256MB rather F than the usual 384MB. This weirdness was intermittent. I have reseatedG everything in the system to make sure there are no connection/connector B issues but I think it would be prudent to actually test the memory itself.   E I kicked the system into SRM Console mode and I've been trying to run D memtest to no avail. I believe *I* am the real problem since I don'tG know what the heck I'm doing in SRM in spite of the fact that I've read  the SRM Console user guide.   & The SRM version is v7.2-1  Mar 6, 2000  H Running even the most simple tests seems to basically lock up the systemH since the command fails to ever exit even if you let it run for a couple# hours to try completing two passes.        >>> memtest -rb -p 2  F If you background the memtest process and run show_status, it seems to pass at least once?    >>> memtest -rb -p 2 & >>> show_status > ID        Program   Device   Pass   Hard/Soft   Written   Read? -------- --------- -------- ------ ----------- --------- ------ ? 00000001      idle system       0      0    0         0      0  ? 0000004F   memtest memory       1      0    0         0      0      8 Using >>>kill_diags afterwards only locks up the system.  G I've searched around for more detailed instructions on the web. I found 2 a cryptic post to the DebianAlpha list about using  
 >>>dynamic -r   C to figure out values to use with memtest switches but I still don't  understand what was meant.  D I've reduced the system memory to 128MB (two DIMS) so I can test the pairs.  , When you guys use memtest, how do you do it?   Thanks,  JCR    ------------------------------  % Date: Tue, 13 Dec 2005 11:12:08 -0700  From: Kevin Handy <kth@srv.net>  Subject: Re: Time problem 8 Message-ID: <1134497160_88855@spool6-east.superfeed.net>   Kevin Handy wrote:( > A customer has a DS10 running VMS 7.2. > @ > I set the date (i.e. "set time=30-nov-2005:13:12", "set time")( > and everything is fine for the moment. > @ > I come back a day or so later, and the date/time is incorrect.3 > I set the time yesterday, today it is reported as # > 30-NOV-2005 14:30:55 (at 1:16PM).  > @ > I just set the time correctly, and after 1/2 hour it is off by@ > 5 minutes. Doing a bare "set time" seems to reset the clock to > the correct time.  > < > I added a que entry to "set time" every hour to try to get9 > somewhat correct times, but this doesn't make me happy.  > = > Any ideas as to what may be happening? Why would the system  > clock be running so slow?  > < > I haven't changed any parameters recently, and there isn't< > much running on the system (a couple low volume accounting. > entry programs at most, 99% idle time, etc.) >   > I've rebooted the system (ran shutdown, auto reboot), and time now flows normally.   Q ----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==---- S http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups K ----= East and West-Coast Server Farms - Total Privacy via Encryption =----    ------------------------------  % Date: Tue, 13 Dec 2005 03:12:01 -0800 = From: "John Gemignani, Jr." <john@nfw-invalid.cibtrikker.com> 9 Subject: Re: Timeout strategy: terminal vs Telnet drivers , Message-ID: <-cidnWVwsPkZMQPeRVn-uw@dls.net>  ; "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  & news:439D1F69.C2EC7417@teksavvy.com... > "John Gemignani, Jr." wrote:K >> 1) The $QIO/$SETIMR/$CANCEL mechanism ~does~ work and does not close the  > J > I have this implemented already to detect a dead link. But it isn't niceH > and clean like the terminal driver interface (you need some persistantI > structure specific to that link to keep the event flag number etc etc).  > F >> 2) You can use the TNQIO front end for the socket and get the same  >> behavior . >> that you described  with terminal timeouts. > J > That got my attention. Where do I find documentation on this TNQIO beastJ > ????? Is it available for TCPIP Servioces 5.3 ? (the last common version > for all VMS platforms).   L I believe it's in V5.3.  It was part of the TNDRIVER rewrite that I did.  I  believe thatM there is a chapter on it but the initial release may have ended up either as   an appendix  or a release note.  K The whole interface works rather well.   It came in really handy in my web   serverK where I used the TELNET command line to create a TNxxx: device in front of   the + socket.  This made my DCL work a lot nicer.   K If you have problems send me an email.  I now live in the Seattle area and   have not= set up my VMS systems (gasp!) as I don't do much VMS anymore.    John   ------------------------------    Date: 13 Dec 2005 07:45:12 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) 9 Subject: Re: Timeout strategy: terminal vs Telnet drivers 3 Message-ID: <AmxMupoFC8Ku@eisner.encompasserve.org>   ` In article <1134454677.069668.171280@o13g2000cwo.googlegroups.com>, dooleys@snowy.net.au writes:  8 > a telnet packet is sent for every keystroke (and echo)  ; What better argument could there be for DECnet's SET HOST ?    ------------------------------    Date: 13 Dec 2005 07:50:29 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 9 Subject: RE: Timeout strategy: terminal vs Telnet drivers 3 Message-ID: <EnzMMNGK69TZ@eisner.encompasserve.org>   ` In article <JFEPKAPBPMDFDBOIANGDMEIHHBAA.dallen@nist.gov>, "Dan Allen" <dallen@nist.gov> writes:  P > Now WRT reading a Telnet (TCP) stream. If you issue a read requesting one byteO > it doesn't return until one byte is received. If you ask for two it waits for  > two, etc.   D    That is not guarranteed and I have seen it not happen many times.E    Some environments provide a "read fully" option as a simple way to C    force it to happen.  For example, I wrote a Java FTP client that B    used a Java io package's "read fully" method to deal with this.   ------------------------------    Date: 13 Dec 2005 07:52:07 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 9 Subject: Re: Timeout strategy: terminal vs Telnet drivers 3 Message-ID: <xTEqAk3PRBVc@eisner.encompasserve.org>   b In article <dnlg6n$5eo$1@pcls4.std.com>, moroney@world.std.spaamtrap.com (Michael Moroney) writes: > J > A VMS QIO READVBLK with IO$M_TIMED specified, and time (P3 parameter, I H > think) equal to 0 will give you whatever is in the typahead buffer (upH > to the smaller of the buffer size/the typeahead size SYSGEN parameter)D > and not wait at all for anything further.  This is how to get the $ > nonblocking behavior through $QIO.  F    I think somebody already stated that UCX's BGDRIVER doesn't supportC    IO$M_TIMED.  I assumed they knew what they were talking about as ;    I haven't used it the days when DEC still called it UCX.    ------------------------------   Date: 13 Dec 2005 14:06:35 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)9 Subject: Re: Timeout strategy: terminal vs Telnet drivers , Message-ID: <4082rbF196t0sU1@individual.net>  3 In article <AmxMupoFC8Ku@eisner.encompasserve.org>, 0 	Kilgallen@SpamCop.net (Larry Kilgallen) writes:b > In article <1134454677.069668.171280@o13g2000cwo.googlegroups.com>, dooleys@snowy.net.au writes: > 9 >> a telnet packet is sent for every keystroke (and echo)  > = > What better argument could there be for DECnet's SET HOST ?   H Why?  First, it is not necessarily an accurate description of how telnet/ works and second, some applications require it.    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------    Date: 13 Dec 2005 09:14:34 -0600 From: briggs@encompasserve.org9 Subject: Re: Timeout strategy: terminal vs Telnet drivers 3 Message-ID: <+BcGlcL+twLj@eisner.encompasserve.org>   q In article <xTEqAk3PRBVc@eisner.encompasserve.org>, koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: d > In article <dnlg6n$5eo$1@pcls4.std.com>, moroney@world.std.spaamtrap.com (Michael Moroney) writes: >>  K >> A VMS QIO READVBLK with IO$M_TIMED specified, and time (P3 parameter, I  I >> think) equal to 0 will give you whatever is in the typahead buffer (up I >> to the smaller of the buffer size/the typeahead size SYSGEN parameter) E >> and not wait at all for anything further.  This is how to get the  % >> nonblocking behavior through $QIO.  > H >    I think somebody already stated that UCX's BGDRIVER doesn't supportE >    IO$M_TIMED.  I assumed they knew what they were talking about as = >    I haven't used it the days when DEC still called it UCX.   C Unless I'm mistaken, a user reading from a TELNET session using QIO D is not interacting directly with BGDRIVER.  They're using a terminal4 driver, possibly the generic class driver, TTDRIVER.  ? TTDRIVER supports IO$M_TIMED.  And there's no reason to suspect A that the telnet port driver cannot emulate timeout without making  use of IO$M_TIMED to BGDRIVER.   	John Briggs   ------------------------------  % Date: Tue, 13 Dec 2005 11:05:33 -0500 # From: "Dan Allen" <dallen@nist.gov> 9 Subject: RE: Timeout strategy: terminal vs Telnet drivers : Message-ID: <JFEPKAPBPMDFDBOIANGDIEINHBAA.dallen@nist.gov>   > -----Original Message-----F > From: bill@triangle.cs.uofs.edu [mailto:bill@triangle.cs.uofs.edu]On > Behalf Of Bill Gunshannon * > Sent: Tuesday, December 13, 2005 9:07 AM > To: Info-VAX@Mvb.Saic.Com ; > Subject: Re: Timeout strategy: terminal vs Telnet drivers  >  > 5 > In article <AmxMupoFC8Ku@eisner.encompasserve.org>, 2 > 	Kilgallen@SpamCop.net (Larry Kilgallen) writes:G > > In article <1134454677.069668.171280@o13g2000cwo.googlegroups.com>,  > dooleys@snowy.net.au writes: > > ; > >> a telnet packet is sent for every keystroke (and echo)  > > ? > > What better argument could there be for DECnet's SET HOST ?  > J > Why?  First, it is not necessarily an accurate description of how telnet1 > works and second, some applications require it.  >  > bill  O Exactly - the Telnet application may WRITE individual characters but the TCP/IP N layer may or may not send them as individual packets. TTBOMK applications haveP no control over that phase of the network exchange - and for good reason. I knowN of no application, including Telnet, that REQUIRES that behavior and I know ofM no way to force that behavior from within an application.  Of course ICBW, it  wouldn't be the first time ;-)   Dan    Dan    ------------------------------    Date: 13 Dec 2005 06:51:58 -0600B From: clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley)L Subject: Re: USB on OpenVMS (was: Re: DS10L hardware configuration question)3 Message-ID: <rtq6m++Tr1kB@eisner.encompasserve.org>   _ In article <05121214173666_2024716B@antinode.org>, sms@antinode.org (Steven M. Schweda) writes:  > I >    My guess is that any of the cheap Chinese cards which say "NEC chip" G > on them will be fine.  The (NEC) <mu>PD720101 seems to be the popular G > chip on all the cheap cards, and that's one of the approved chips, as  > reported in this forum.  >   J One thing to be aware of: as I understand it the VMS driver will only workJ with OHCI controllers, so if any of these cheap cards use other controller2 types, ie: UHCI, then they will not work with VMS.  0 (Forrest, does the VMS stack support EHCI yet ?)   Simon.   --  ; Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP I If Google's motto is "do no wrong", then how did we get Google Groups 2 ?    ------------------------------  % Date: Tue, 13 Dec 2005 10:27:38 -0500 , From: Forrest Kenney <Forrest.Kenney@hp.com>L Subject: Re: USB on OpenVMS (was: Re: DS10L hardware configuration question)& Message-ID: <439EE86A.9EE48114@hp.com>  L > One thing to be aware of: as I understand it the VMS driver will only workL > with OHCI controllers, so if any of these cheap cards use other controller4 > types, ie: UHCI, then they will not work with VMS. > A 	I said that all the cards mentioned were OHCI.  We have no plans  to ever pick up support UHCI.   2 > (Forrest, does the VMS stack support EHCI yet ?) > > 	Not yet still being worked on between lots of other things I G have to take care of.  Don't expect to see it in V8.3 we will see about . getting it out as soon after V8.3 as possible.     Forrest    ------------------------------  # Date: Tue, 13 Dec 2005 17:49:31 GMT  From: "Zoom" <zoom@zoom.com> Subject: WTB: VAX FT810 parts.* Message-ID: <LQDnf.2526$Bj4.2107@trndny01>  7 Looking to buy following VAX FT810 parts if applicable:     KA560-AA           FT810 CPU   KD560-AA           ATM I/O board" MS560-BA           64MB Memory kit SF35-BK             Hard disk  TF85C-BA           Tape Drive " 30-35415-01/    Power Distribution% H7884-AA           (FEU) Power Supply ( H7178-AA           (DC3.3V) Power Supply& H7179-AA           (DC5V) Power Supply% H7851-AA           (PCS) Power Supply   
 Thank you.   Young  EJ Tech Solutions  Email: youngjin_kim@verizon.net  phone: 1-978-632-9652    ------------------------------   End of INFO-VAX 2005.693 ************************