Article View: bit.listserv.asm370
Article #1563Re: MVS Interprocess Communication
From: Rob Miller
Date: Fri, 10 Jul 1992 17:50
Date: Fri, 10 Jul 1992 17:50
44 lines
2662 bytes
2662 bytes
Rob van Hoboken <RCOPROB@HDETUD2.TUDELFT.NL> writes:
>
>Also, I remember reading about unauthorized inter address space functions
>being announced for MVS/ESA SP 4.3
>
I believe you're referring to the APPC/MVS Server Facilities support.
This will allow a server address space to manage multiple, concurrent
conversations with client programs using a set of callable services.
Appended below are excerpts from the announcement letter regarding
APPC/MVS Server Facilities.
-Rob Miller
------------------------------------------------------------------------
OVERVIEW HIGHLIGHTS
o MVS/ESA SP Version 4 Release 3 enables system growth by providing
additional APPC/MVS support for application development. In
addition, APPC/MVS enhancements simplify resource management by
enabling the creation of logical unit (LU) 6.2 server programs
that can manage resources on behalf of many clients.
DESCRIPTION
GROWTH ENABLEMENT
With the addition of APPC/MVS Server Facilities, MVS
strengthens its support for client/server programming. APPC/MVS
Server Facilities provide installations with the high-level language
callable services needed to write APPC/MVS servers (programs that
manage multiple LU 6.2 inbound conversations from multiple clients
concurrently.)
Because the new callable services are available to
unauthorized MVS application programs, APPC/MVS Server Facilities
provide a convenient method for unauthorized programs to establish
cross-memory communications.
A client/server application can use APPC/MVS Server Facilities
to establish multiple, concurrent conversations between a client and
its server. With this capability, the application could, for
example, dedicate one conversation in each direction (sending or
receiving).
Technical Details
Message-ID:
<ASM370%92071013564186@UCF1VM.BITNET>Path:
arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!auvm!POKVMCR3.VNET.IBM.COM!RMILLERShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fcdcb,d39366754ce64a24
X-Google-Attributes: gidfcdcb,public
X-Google-ArrivalTime: 1992-07-10 23:46:08 PST
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Path: arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!auvm!POKVMCR3.VNET.IBM.COM!RMILLER
Message-ID: <ASM370%92071013564186@UCF1VM.BITNET>
Newsgroups: bit.listserv.asm370
Date: Fri, 10 Jul 1992 13:50:54 EDT
Sender: IBM 370 Assembly Programming Discussion List <ASM370@UGA.BITNET>
From: Rob Miller <RMILLER@POKVMCR3.VNET.IBM.COM>
Subject: Re: MVS Interprocess Communication
Comments: To: Assembler 370 Discussion list
<ASM370%UCF1VM.BITNET@cunyvm.cuny.edu>
Lines: 44