Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!mimsy!oddjob!hao!boulder!sunybcs!rutgers!lll-lcc!pyramid!hplabs!well!mjr From: mjr@well.UUCP (Matthew Rapaport) Newsgroups: comp.databases,comp.unix.questions Subject: Re: Access to database on IBM/MVS from UNIX ? Message-ID: <3898@well.UUCP> Date: Sat, 5-Sep-87 18:46:17 EDT Article-I.D.: well.3898 Posted: Sat Sep 5 18:46:17 1987 Date-Received: Sun, 6-Sep-87 09:52:23 EDT References: <463@ambush.UUCP> <321@oracle.UUCP> <3589@zen.berkeley.edu> Reply-To: mjr@well.UUCP (Matthew Rapaport) Organization: Whole Earth 'Lectronic Link, Sausalito, CA Lines: 95 Xref: mnetor comp.databases:465 comp.unix.questions:3915 A very brief and cursory search in Knowledge Index's COMP4 database turned up the following three references on linking UNIX to IBM's VM and MVS under SNA. I do not know if any of the technologies described here are actually implemented in off the shelf products, but the articles themselves probably contain other references. If you need to find products, consultants, etc., I do this for a living (at least in part) so send me mail -- 'ptsfa!mjr!well' or 'mjr@well' if you know a good domain server! 1156562 DCM85H0111 Bringing Unix Machines within an IBM Network. Mendelsohn, M.P. AT&T Information Systems , Lincroft, NJ Data Communications Vol.14, No.9, Aug. 1985, P. 111-115. 5 Pages. COUNTRY OF PUBLICATION: U.S.A. LANGUAGE: English CODEN: DACODM ISSN: 0363-6399 DOCUMENT TYPE: Journal ARTICLE TYPE: Technology; How-To SPECIAL FEATURES: includes Chart UNIX-based machines can be linked to both BSC (binary synchronous communications) and SNA (system network architecture) protocols without altering the five UNIX system calls. Transmission between asynchronous terminals occurs one character at a time, contrasted to half-duplex protocols which are batch oriented and pass files in logical groups in one direction at a time. Both devices can request permission to transmit at the same time; one device designated as winner, one as loser, with the winner then going into a receive mode. Half-duplex protocols should have point-to-point arrangements which are either leased or switched with that information then passed on to the device driver. A 2780/3780 terminal can function as three devices: the card reader is used as the transmission device, the line printer and card punch are used as the two output devices. The biggest problem in implementing half-duplex contention protocols in the UNIX system is passing enough information to manage communication links between the user and the device driver. The solution is in four areas: building a structure to hold information that must be present before communications can begin; using an IOCTL system call to pass and obtain information not available on any other system call; having an information header precede all data passed between user and device driver; and expanding the set of return values for all system calls indicating to the user what action must be provided. Charts listing sequences between devices for both protocols are included. OPERATING SYSTEM: UNIX DESCRIPTORS: UNIX; Operating Systems; Communications Modes; Asynchronous; Half Duplex; Receive-Only; Send/Receive; Protocol; Networks; SNA; Interface; How-to Information 3/L/2 1144764 UNW84L0090 Pseudo-Device Provides SNA Communications for the Unix System. Heath, R.A. NCR Corp. , UNIX World Vol.1, No.7, Dec. 1984, P. 90-93. 3 Pages. COUNTRY OF PUBLICATION: U.S.A. LANGUAGE: English ISSN: 0739-5922 DOCUMENT TYPE: Journal ARTICLE TYPE: Technology SPECIAL FEATURES: includes Diagrams IBM's Systems Network Architecture (SNA) is not a component of the Unix operating system. The integration of both systems requires application software and kernel pseudo-devices. A diagram compares the interdependent SNA layers with the layers of Unix. Five layers of SNA must be distributed within three layers of Unix. Layers must be able to communicate without using pipes. A diagram shows how a pseudo-device bridges the SNA layers within Unix. Data flows in and out of a kernel when it crosses the SNA layers. A diagram shows how batch and interactive traffic can be combined over a single communications line. Such a technique greatly reduces line costs. A SDLC device driver controls the SDLC functions for SNA. Other standard protocols can be combined in a similiar way. OPERATING SYSTEM: UNIX DESCRIPTORS: SNA; Protocol; Networks; Data Communications; UNIX; Micro-Mainframe Communication; Network Architecture; Technology 3/L/3 1124247 MIC85A0038 SNA to UNIX; UNIX to SNA. Wise, T.; Forgetta, V. Pathway Design , Wellesley, MA Micro Communications Vol.2, No.1, Jan. 1985, P. 38-42. 3 Pages. COUNTRY OF PUBLICATION: U.S.A. LANGUAGE: English DOCUMENT TYPE: Journal ARTICLE TYPE: Technology SPECIAL FEATURES: includes Diagrammatic Models UNIX needs a connection to the IBM mainframe environment in order to achieve a long term presence. In order to ensure a consistency of operation and data sharing and integrity, UNIX-based systems must be able to communicate with IBM hosts. Pathway Design examined four approaches in designing a UNIX-to-SNA connection. The approaches differ due to the organization of the SNA layers as they are incorporated into the UNIX architecture. Diagrammatic models of the SNA models, application implementation approaches, and future alternatives are included. Layers are grouped into three categories: the device driver, the deamon and the user layer. Approach one includes only the comms layer in the device driver. Approach two includes the comms and SDLC layers in the device driver. Approach three includes the PC,SDLC and comms layers in the device driver. Approach four places all SNA and SDLC layers within the kernel. The optimal approach for designing a UNIX gateway is difficult to select. OPERATING SYSTEM: UNIX PRODUCT NAME: uniPath , , Pathway Design , Network Control Processors DESCRIPTORS: Micro-Mainframe Communication; Multiuser Microcomputers; Distributed Systems; Kernels; UNIX; Network Architecture; SNA; SDLC; Protocol; Networks; Presentation Layer Control