Steve
If "WD/z and its z/OS System Explorer" can use APPC/APPN it almost certainly
means that they have chosen to use the logical unit (LU) type 6.2 API[1] as,
possibly just one of, the means to exchange data between, I am assuming, a
"server" environment and a "client" environment. This would mean only that
the underlying "transport" was SNA and it could be old, legacy subarea SNA
as easily as bright shiny new APPN or indeed, the intermediate Low Entry
Networking (LEN) - or any combination thereof.
Given that SNA and actually specifically APPN is used, it means that one of
the logical SNA links between the assumed "server" and "client" can be an IP
network[2] supported by RFC 2353, a set of protocols originally offered by
IBM using the name "Enterprise Extender" (EE).
Making the assumptions I have about "WD/z and its z/OS System Explorer", I
can't see that TN3270 will be in any way involved.
I'm now going to take a look at
http://www-05.ibm.com/il/news/events/mf/downloads/03-Productive-Developer-Tools.pdf -
after the chore I have been instructed to perform - so I may be back later
with some clarifications.
Chris Mason
[1] They may have chosen specifically to limit their choice of API to that
defined by "Common Programming Interface for Communications" (CPI-C), a
formal "standard" for SNA-based communication.
[2] *Not* using "TCP" as the "transport" over the IP network since EE uses
"UDP" as the "transport".
----- Original Message -----
From: "Steve Comstock" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Saturday, June 16, 2007 5:31 PM
Subject: Re: Multiple TSO logons
Chris Mason wrote:
Tom
There's some confused thinking here which I can't quite put my finger on.
As John McKown has indicated, there is a very simple way that the
otelnetd server creates an environment which allows, in effect, line-mode
TSO commands.
If the proposed "z/OS System Explorer" is what I think it is - judging
from the use of the Microsoft "Explorer" word - it approaches the file
handling which may be compared to what the *TSO extension* ISPF does.
In other words, what "z/OS System Explorer" replaces is ISPF. "z/OS
System Explorer" exploits some lower level environment in the client
platform which may be equated to 3270 data stream analysis and
construction in the server platform in the case of ISPF sitting on top of
TSO.
In other words it's rather tricky to draw parallels even if the end-user
is performing much the same functions with the proposed "z/OS System
Explorer" as with ISPF.
I'm not sure "remov(ing) the need for VTAM in the middle of things" is
much of a key distinction to mention compared to all the other necessary
changes.
Chris Mason
Chris,
I'm not any kind of a network guy. But I've worked with WD/z
and its z/OS System Explorer. It seems to use APPC / APPN.
How does that tie to VTAM / TCP/IP / TN3270?
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
303-393-8716
http://www.trainersfriend.com
z/OS Application development made easier
* Our classes include
+ How things work
+ Programming examples with realistic applications
+ Starter / skeleton code
+ Complete working programs
+ Useful utilities and subroutines
+ Tips and techniques
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
