NJE over BSC was obsolete 20 years ago.
However IMHO it's easier to use NJE over TCPIP than over CTC/VTAM. NJE
over TCPIP is also not new, probably 10+ years.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 2019-05-29 o 03:30, Tony Thigpen pisze:
I am talking about JES2 controlled CTCs for NJE, not VTAM controlled
CTCs, which I expect you are thinking about and using. That is really
NJE over VTAM, just like using NJE over TCP/IP, both of which use a
third-party (VTAM or TCP/IP) as the actual traffic carrier. That
third-party carrier may allow multiple types of paths (one of which
*may* be a CTC), but JES2 does not know or care about the path selected.
Specifically, JES2 can no longer talk directly to a CTC.
Tony Thigpen
Jesse 1 Robinson wrote on 5/28/19 7:00 PM:
I'm not sure what Tony T. means. We have only FICON CTC throughout
the enterprise. All of our JES2 NJE connections use them. There was
no configuration change when we moved from ESCON to FICON.
Maybe BSC? We abandoned that protocol decades ago.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On
Behalf Of Tony Thigpen
Sent: Tuesday, May 28, 2019 3:17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: CTC (FCTC) usage
FYI, JES2/NJE does not support FICON CTC connections. They only
support ESCON/BASIC CTC connections, which you don't have on a z14.
Tony Thigpen
Munif Sadek wrote on 5/28/19 10:40 AM:
we are getting new z14 and time to revisit our CTC configuration.
Is there a complete documentation on FICON CTC implementation and
its potential usage / configuration for various subsystems e.g.
VTAM, TCP/IP, GRS, NJE, XCF etc . we are single CPC SYSPLEX
environment and just exploring where all CTCs can be used.
Currently we us it only for VTAM (TRL) and IP.
regards
Munif
======================================================================
Jeśli nie jesteś adresatem tej wiadomości:
- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza)
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać
karze.
mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st.
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237,
NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
01.01.2018 r. wynosi 169.248.488 złotych.
If you are not the addressee of this message:
- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have
printed out or saved).
This message may contain legally protected information, which may be used
exclusively by the addressee.Please be reminded that anyone who disseminates
(copies, distributes) this message or takes any similar action, violates the
law and may be penalised.
mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital
City of Warsaw, 12th Commercial Division of the National Court Register, KRS
0000025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN
169,248,488 as at 1 January 2018.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
