Xref: utzoo comp.os.vms:38599 comp.lang.c:39068
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!bloom-picayune.mit.edu!news
From: seaotter@athena.mit.edu (The Groovy Horn Dog)
Newsgroups: comp.os.vms,comp.lang.c
Subject: VAXC, IO$_SENSEMODE, and TT*DEF.H
Message-ID: <1991May7.121040.21899@athena.mit.edu>
Date: 7 May 91 12:10:40 GMT
Sender: news@athena.mit.edu (News system)
Organization: Massachusetts Institute of Technology
Lines: 41

Here's a question for you VMS C wizards:

I wish to use sys$qiow(...,IO$_SENSEMODE,...) to determine the charac-
teristics of a terminal (and the IO$_SETMODE, but ignore that for now).
Now in the examples I have seen, after assigning a channel via
sys$assign we might have a code fragment like this:


	unsigned long status;
	int iosb[2], ttx[3];

	/* I forget where all
	 * the args go but I
	 * can look that up
	 * later
	 */

	status = sys$qiow(0, iochan, IO$_SENSEMODE,
		... iosb, ... ttx, sizeof(ttx), ... );

So far so good.  But now I have all the #define's in <ttdef.h> and
<tt2def.h> to sort through -- which parameters are in which ttx index?
I know for instance that TT$M_NOECHO is looked for int ttx[1] and
TT2$M_PASTHRU in ttx[2], but what about things like TT$C_BAUD_xxx, etc.?
In the limited documentation I have access to I have not seen any run-
down on what is where.

Furthermore, in the examples I have seen, TT2$M_PASTHRU has been used as
a synonym for the UNIX idea of "[no]cbreak"; is this valid?  And what
would then be the appropriate ttdef for the UNIX idea of "[no]nl"?  And
where is it located?


Thanks for your help,
   Mike

--
Mike Zraly
(the old ssrat)                       If the King's English was good enough
mzraly@ldbvax.dnet.lotus.com          for Jesus, it's good enough for me!
or c/o seaotter@athena.mit.edu        -- Tex. Gov. Ma Ferguson, ca 1920