Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!ucbvax!mtxinu!sybase!shalom!ben From: ben@shalom.sybase.com (ben ullrich) Newsgroups: comp.databases Subject: Re: Sybase still around? Message-ID: <10235@sybase.sybase.com> Date: 24 Jul 90 01:40:41 GMT References: <113619@linus.mitre.org> <10175@sybase.sybase.com> <1990Jul20.155344.17236@ddti.com> Sender: news@Sybase.COM Distribution: usa Organization: sybase, inc., emeryville, ca Lines: 69 In article <1990Jul20.155344.17236@ddti.com> maples@ddti.com (Greg Maples) writes: >Well, all this self-congratulaion by sybase folks on the merits >of their product is all well and good, but a few pertinant facts >should be mentioned as well. Yes, and I would like to also add some ``facts,'' since that's what we're talking about ... ?! > [...] >really common terminals like the wyse 60 are not supported, the tech >support people tell us. Even though ``really common'' is a matter of opinion, Sybase does in fact support the wyse 50 in most front end products. I know the wyse support came in a bit later than the long standing support for vt100/220, hds, sun, etc.., so I am not completely sure which release it was introduced, but version 4 should have it. You can check by looking in your $SYBASE/termdef/w directory. Setting your TERM environment variable to the filename in this directory should yield you a working front end upon invocation of the command image for that front end. I'm also assuming that a wyse 60 can emulate a wyse 50, and thus the current support of wyse 50 will do. > [...] VT100 emulation across our ethernet from >macs requires a another vendors product, not Apple's, nor will Sybase >work with MacTCP. NCSA Telnet wont work either. The native rlogin or >telnet sessions cannot support ANY mac-native screen definition. All >this is true, even though the host machine understands termcap and >terminfo for all these connections. That's funny, all the vt100 emulations I have used to run Sybase front ends, from macs, xterms, vt100-compatible terminals, and PC's never yields a font end that doesn't work. NCSA Telnet happens to be the product about 150 users in our corporate and sales offices around the world use to run the Sybase DataWorkbench and Sybase APT-based applications every day. This is only possible because the host machine understands termcap entries. To expect the Sybase front ends to understand ``mac-native screen definition'' when the bridging utility (NCSA Telnet? which one you mean is not clear.) doesn't isn't really fair. Since the vt100 doesn't have a mouse, Sybase will not recognize one. This is true of any software that emulates a vt100, and is not a Sybase shortcoming. I admit I'm not very clear on your question, since it is not clear what is not working, and what ``mac-native screen definition'' means. >What's the problem? Sybase has invented yet another custom term >database capability. They will not 1) tell you how to make your >own 2) make one for you 3) SELL you a new termdef 4) SELL you the >termdef compiler, etc. This is patently absurd. The custom terminal definitions were created for two reasons that I recall: we needed info about terminals which is not available from termcap/terminfo, and we needed them to be consistent across platforms. If we depended on termcap, for example, what would we do on VMS? Stratus? ... the whole world does not run UNIX, (unfortunately!). Suffice it to say that I personally agree that a termdef compiler would be a very useful tool. A feature request for this item has already been logged. I don't know what its demise will be... I'm not close to product plans. I hope I have cleared the waters at least a little. ..ben ---- ben ullrich only i do the talking here -- not my employer. sybase, inc., emeryville, ca ``broccoli not bombs'' ben@sybase.com {pyramid,pacbell,sun,lll-tis}!sybase!ben