Article View: comp.protocols.ibm
Article #1752Re: Running VAX/VMS application over IBM SNA network
From: Chris Cebelenski
Date: Tue, 24 Nov 1992 16:40
Date: Tue, 24 Nov 1992 16:40
40 lines
3100 bytes
3100 bytes
In article <1992Nov23.161012.75@dymaxion.ns.ca> bg@dymaxion.ns.ca writes: >We are trying to determine our options for making use of an existing >IBM SNA network for users to access an application on a VAX to eliminate >having to install another leased line network. The network connects 100+ >schools so it would be expensive to duplicate. > >It would be nice if the existing 3270 terminals could be used, ideally but >necessarily emulating VT100 terminals. An approach requiring separate >terminals would be fine since the department that would be accessing our >application is going to need another terminal, or PC emulating a VT100, >in most cases anyways > [...] >Dymaxion Research Ltd., fax: (902)421-1267 >Halifax, Nova Scotia, Canada B3J 1R2 Internet: bg@dymaxion.ns.ca At Sprint we're taking this approach: DEC Gateway-CT to physically connect the SNA & DECNET sides DEC's VT emulator to emulate VT terminals on IBM 3270 type terminals. This is just about the best solution you can hope for given those restraints. Given the inherent differences in hardware you can imagine that there are some compromises to be made, and some problems you will have to live with. NOTHING can make an IBM 3270 type terminal into a VT, but these products can at least achieve an uneasy truce. The first obstacle to overcome will be network mapping. If your information Systems depts (or whatever) is as closed and thick headed as this one, you could be in a long uphill battle. The second major problem is that only terminals that support EAB (extended attribute buffers) can be used. Any other type terminal (such as an IBM 3191, et al) will get you nowhere. The next problem is keyboard mapping. We try and get around this by mapping the keyboard for one specific applications, but this is not ideal. Note that things like the TAB key need to be mapped to an IBM PF-key in order to function properly. Again this is less than ideal and has caused much hair pulling. Let me know if you decide to embark on this (mis)adventure and maybe I can smooth the path a bit. cpc@shell.portal.com
Technical Details
Message-ID:
<By8Bn8.2yy@unix.portal.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!portal!cpcReferences:
<1992Nov23.161012.75@dymaxion.ns.ca>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f7344,8aac5da107806e6a X-Google-Attributes: gidf7344,public X-Google-Thread: 10fc0e,8aac5da107806e6a X-Google-Attributes: gid10fc0e,public X-Google-Thread: f6425,8aac5da107806e6a X-Google-Attributes: gidf6425,public X-Google-Thread: fce9c,8aac5da107806e6a X-Google-Attributes: gidfce9c,public X-Google-ArrivalTime: 1992-11-26 11:20:49 PST Newsgroups: comp.protocols.ibm,bit.listserv.snamgt-l,comp.os.vms,vmsnet.networks.misc Path: arc1-ca.pugleaf.net!sparky!uunet!portal!cpc From: cpc@shell.portal.com (Chris Cebelenski) Subject: Re: Running VAX/VMS application over IBM SNA network Message-ID: <By8Bn8.2yy@unix.portal.com> Sender: news@unix.portal.com Nntp-Posting-Host: jobe Organization: Portal Communications Company -- 408/973-9111 (voice) 408/973-8091 (data) References: <1992Nov23.161012.75@dymaxion.ns.ca> Date: Tue, 24 Nov 1992 16:40:19 GMT Lines: 40