Discussion:
[hercules-390] IPV6 config
jln@stben.net [hercules-390]
2017-02-15 11:44:40 UTC
Permalink
Hi Everyone,


Did someone has already setup z/OS to use IPV6?
I am lost with the interface statment and the choice of
link into Hercules.
Tun or tap?


Thanks for your help.


Regards,
Jean-Louis
Ivan Warren ivan@vmfacility.fr [hercules-390]
2017-02-15 11:52:00 UTC
Permalink
Post by ***@stben.net [hercules-390]
Hi Everyone,
Did someone has already setup z/OS to use IPV6?
I am lost with the interface statment and the choice of
link into Hercules.
Tun or tap?
Although both tun and tap support IPv6, Neither CTCI nor LCS support IPV6.

The only network interface supporting supporting IPv6 is OSA QDIO/QETH
which hercules only very partially support (not enough for z/OS or z/VM
support).

--Ivan


[Non-text portions of this message have been removed]
jln@stben.net [hercules-390]
2017-02-15 12:42:05 UTC
Permalink
Hi Ivan,
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Although both tun and tap support IPv6, Neither CTCI nor LCS support IPV6.
I still have some difficulties to imagine the role of each entitie.


When a channel is created between z/OS and the TCP/IP stack in case of tun
and between z/OS and a virtual MAC in case of tap what is the role of Hercules?
I know it set up the channel but after doing so.
Ivan Warren ivan@vmfacility.fr [hercules-390]
2017-02-15 13:01:25 UTC
Permalink
Post by ***@stben.net [hercules-390]
Hi Ivan,
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Although both tun and tap support IPv6, Neither CTCI nor LCS support
IPV6.
I still have some difficulties to imagine the role of each entitie.
When a channel is created between z/OS and the TCP/IP stack in case of tun
and between z/OS and a virtual MAC in case of tap what is the role of Hercules?
I know it set up the channel but after doing so.
The role of hercules is to interface between the OS (which uses CCWs
(for CTCI and LCS) and whatnot (for QDIO) to communicate with a
devices/adapter) and the underlying network.

Compare this to an OS (say, Linux, Windows, AIX, HP/UX) on a computer
equipped with a PCI adapter. Depending on the PCI adapter used - the way
to talk to each different adapter will be different. The same way, the
way z/OS or z/VM or z/Linux will communicate will depend whether the
adapter is a CTC (CTCI emulates IP stacks communicating between OSes
using Channel to Channel adapters) and LCS (Which emulates a 3172)...
The tun and tap are only the method for hercules to act between those
device emulations and the actual host IP layer or network to which the
host is connected to.

--Ivan


[Non-text portions of this message have been removed]
jln@stben.net [hercules-390]
2017-02-15 13:40:21 UTC
Permalink
Hi Ivan,


Why I couldn't ask z/OS to interface directly on an virtual interface
without transiting by Hercules?
Maarten Hoes hoes.maarten@gmail.com [hercules-390]
2017-02-15 14:24:01 UTC
Permalink
Hi,


I'm not sure I fully understand the question, and perhaps this is already
very obvious to you, but ...

z/OS expects to run on real physical z/Arch hardware. So you *have* to have
an emulation layer, which is Hercules/Hyperion, to act *as if* it's z/Arch
hardware, and then translate that to the real OS and hardware (Linux,
Windows, PC, etc.) it's actually running on.


- Maarten
Post by ***@stben.net [hercules-390]
Hi Ivan,
Why I couldn't ask z/OS to interface directly on an virtual interface
without transiting by Hercules?
Ivan Warren ivan@vmfacility.fr [hercules-390]
2017-02-15 15:16:07 UTC
Permalink
Post by ***@stben.net [hercules-390]
Hi Ivan,
Why I couldn't ask z/OS to interface directly on an virtual interface
without transiting by Hercules?
How would you do that ?

This is like saying you want to run Windows and have it access a
network... Without a Network Interface Card...

tun and tap are like a virtual ethernet cables/network infrastructure...
You STILL need a network interface card (and in the S/370, ESA and
z/Arch world, they do not come in very many different shape and sizes).

Basically you have : (*) : Implemented/emulated in hercules

- A pair of CTC (Channel To Channel) linking 2 machines and which carry
IP only traffic (* - CTCI using tun)
- NCP/VTAM when connecting to a 3745 with a Token Ring adapter
- The 9370 Integrated Communication Adapter
- A RS/6000 CLAW workstation with a channel adapter
- A 3172 Lan Control Station (* - LCS using tap)
- An OSA or OSA/Express Adapter (* - Partial support/ z/Linux only)
- IUCV When running under VM

--Ivan


[Non-text portions of this message have been removed]
jln@stben.net [hercules-390]
2017-02-15 15:42:16 UTC
Permalink
Hi Ivan
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
How would you do that ?
; Dynamic Virtual Devices can be defined on this system. This system
; can serve as backup for Dynamic Virtual Devices on other systems.
; A predefined range will allow Dynamic Virtual Devices to be defined
; by IOCTL or Bind requests.
Ivan Warren ivan@vmfacility.fr [hercules-390]
2017-02-15 15:43:58 UTC
Permalink
Post by ***@stben.net [hercules-390]
Hi Ivan
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
How would you do that ?
; Dynamic Virtual Devices can be defined on this system. This system
; can serve as backup for Dynamic Virtual Devices on other systems.
; A predefined range will allow Dynamic Virtual Devices to be defined
; by IOCTL or Bind requests.
It's hard to tell without telling us where this portion of text comes from.

--Ivan


[Non-text portions of this message have been removed]
jln@stben.net [hercules-390]
2017-02-15 15:53:10 UTC
Permalink
Hi Ivan,
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
It's hard to tell without telling us
SC31-8775-14 page 223
Ivan Warren ivan@vmfacility.fr [hercules-390]
2017-02-15 16:25:22 UTC
Permalink
Post by ***@stben.net [hercules-390]
Hi Ivan,
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
It's hard to tell without telling us
SC31-8775-14 page 223
Ok got it.

That's to define *VIRTUAL* IPv6 addresses... You still need to have
access to an actual network that is IPv6 capable in order to do that.

Those virtual IPv6 addresses are there in order to provide redundancy...
Think IPv4 VRRP and whatnot.

What you are trying to do here is like having a box.. With no LAN access
- and by defining a virtual interface, that it will magically connect to
your LAN....

In order to define a virtual *anything* you still need a *real*
something, somewhere !

--Ivan


[Non-text portions of this message have been removed]
jln@stben.net [hercules-390]
2017-02-15 16:38:47 UTC
Permalink
Hi Ivan,


I have a real connection ipv4
Ivan Warren ivan@vmfacility.fr [hercules-390]
2017-02-15 16:48:57 UTC
Permalink
Post by ***@stben.net [hercules-390]
Hi Ivan,
I have a real connection ipv4
Your z/OS instance may have an IPv4 connection. It doesn't mean you have
an IPv6 connection.

--Ivan


[Non-text portions of this message have been removed]
jln@stben.net [hercules-390]
2017-02-15 17:31:40 UTC
Permalink
It's a real something inside of that box isn't it?
Ivan Warren ivan@vmfacility.fr [hercules-390]
2017-02-15 17:40:06 UTC
Permalink
Post by ***@stben.net [hercules-390]
It's a real something inside of that box isn't it?
Inside WHAT Box ?

--Ivan


[Non-text portions of this message have been removed]
jln@stben.net [hercules-390]
2017-02-15 15:34:18 UTC
Permalink
Hi Ivan,


MVS TCP/IP NETSTAT CS V1R10 TCPIP Name: TCPIP 15:51:38
Home address list:
LinkName: CTC1
Address: 10.149.86.1
Flags: Primary
LinkName: LOOPBACK
Address: 127.0.0.1
Flags:
IntfName: LOOPBACK6
Address: ::1
Type: Loopback
Flags:

Unavailable IPv6 Home addresses:
IntfName: MPC1IPV
Address: 2001:470:792a:1::1/64
Type: Global
Reason: Duplicate address detection pending start of interface


BOOOOHOOOOO!
Harold Grovesteen h.grovsteen@tx.rr.com [hercules-390]
2017-02-15 15:44:30 UTC
Permalink
Aside from QETH, there is the PTP driver supported by z/OS as a MPCCTC
devise driven by Comm Server. It uses a tun interface to the host and
supports IPv6.

It is only available with Hyperion.

There have been some successful uses of QETH with some releases of MVS.
YMMV.

Harold Grovesteen
Post by ***@stben.net [hercules-390]
Hi Everyone,
Did someone has already setup z/OS to use IPV6?
I am lost with the interface statment and the choice of
link into Hercules.
Tun or tap?
Thanks for your help.
Regards,
Jean-Louis
Ivan Warren ivan@vmfacility.fr [hercules-390]
2017-02-15 15:50:17 UTC
Permalink
Post by Harold Grovesteen ***@tx.rr.com [hercules-390]
Aside from QETH, there is the PTP driver supported by z/OS as a MPCCTC
devise driven by Comm Server. It uses a tun interface to the host and
supports IPv6.
It is only available with Hyperion.
There have been some successful uses of QETH with some releases of MVS.
YMMV.
I guess an IP stack may also implement a 6to4 tunnel... But I don't know
if z/OS or z/VM TCP/IP have those.

--Ivan



[Non-text portions of this message have been removed]
'Jean-Louis Noel' jln@stben.net [hercules-390]
2017-02-16 16:06:46 UTC
Permalink
Hi Harold,
Post by Harold Grovesteen ***@tx.rr.com [hercules-390]
there is the PTP driver supported by z/OS as a MPCCTC
devise driven by Comm Server. It uses a tun interface to the
host and supports IPv6.
OK, I tried to compile hyperion and succeeded without any problems.
But, I can’t find out how to explain to z/OS to use MPCPTP.

0460.2 PTP 10.149.86.1 10.149.86.2 2001:470:792a:1::101 2001:470:792a:1::102

tun0: flags=81<UP,POINTOPOINT,RUNNING> mtu 1500
inet 10.149.86.2 netmask 255.255.255.255 destination 10.149.86.1
inet6 2001:470:792a:1::102 prefixlen 128 scopeid 0x0<global>
inet6 fe80::6da3:ed8b:7e65:45c7 prefixlen 64 scopeid 0x20<link>
inet6 fe80::d422:3a56:f805:b73 prefixlen 64 scopeid 0x20<link>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 17 bytes 1616 (1.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

That seems OK and when I ping 10.149.86.1 the numbers of TX packets will increase.

IBM says:

;DEVICE and LINK for MPCPTP devices:

;

;DEVICE MPCPTP1 MPCPTP AUTORESTART
;LINK MPCPTPLINK MPCPTP MPCPTP1



So, I use it but it didn’t work I replaced MPCPTP by 460 and 0.
And all permutations possibles in vain.

Could you help me with that problem please?
Harold Grovesteen h.grovsteen@tx.rr.com [hercules-390]
2017-02-17 13:22:40 UTC
Permalink
Post by 'Jean-Louis Noel' ***@stben.net [hercules-390]
Hi Harold,
Post by Harold Grovesteen ***@tx.rr.com [hercules-390]
there is the PTP driver supported by z/OS as a MPCCTC
devise driven by Comm Server. It uses a tun interface to the
host and supports IPv6.
OK, I tried to compile hyperion and succeeded without any problems.
But, I can’t find out how to explain to z/OS to use MPCPTP.
Good news there.

<snip>
Post by 'Jean-Louis Noel' ***@stben.net [hercules-390]
.
;
;DEVICE MPCPTP1 MPCPTP AUTORESTART
;LINK MPCPTPLINK MPCPTP MPCPTP1
It has been a very long time since I worked directly with these files,
but, if memory serves at all, removing the leading semi-colon would
likely help. The semi-colon is a comment indicator. These statements
as written are being ignored.
Post by 'Jean-Louis Noel' ***@stben.net [hercules-390]
So, I use it but it didn’t work I replaced MPCPTP by 460 and 0.
And all permutations possibles in vain.
Could you help me with that problem please?
jln@stben.net [hercules-390]
2017-02-17 14:29:38 UTC
Permalink
Hi Harold,
removing the leading semi-colon would likely help
I know I'm dumb but, not that dumb!
I wrote IBM says not there is a part of my config.


OK, z/OS isn't P&P neither Richmond seems aware that Linux has an enum function.
So, material is described into a file: SYS1.IODF00 and that file says:


E20-E27 CTC Typically for 3172s that appear as CTC devices
E40-E47 CTC Typically for 3172s that appear as CTC devices


There isn't any other 'connection' devices defined.
IODFxx are binary files and before making some changes I need to understand
how hercules is behaving during those connections.
I am working on it and if someone did the same job I would have spare time.
jln@stben.net [hercules-390]
2017-02-17 14:30:00 UTC
Permalink
Hi Harold,
removing the leading semi-colon would likely help
I know I'm dumb but, not that dumb!
I wrote IBM says not there is a part of my config.


OK, z/OS isn't P&P neither Richmond seems aware that Linux has an enum function.
So, material is described into a file: SYS1.IODF00 and that file says:


E20-E27 CTC Typically for 3172s that appear as CTC devices
E40-E47 CTC Typically for 3172s that appear as CTC devices


There isn't any other 'connection' devices defined.
IODFxx are binary files and before making some changes I need to understand
how hercules is behaving during those connections.
I am working on it and if someone did the same job I would have spare time.
mcisho@yahoo.com [hercules-390]
2017-02-17 19:14:50 UTC
Permalink
Hercules config statement (see README.NETWORKING in Hercules source)

0E20.2 PTP 10.149.86.1 10.149.86.2 2001:470:792a:1::101 2001:470:792a:1::102


hlq.VTAMLST member (see CS SNA Resource Definition Reference)

HERCTRL VBUILD TYPE=TRL
TRLE0E20 TRLE MPCLEVEL=HPDT, +
LNCTL=MPC, +
READ=0E20, +
WRITE=0E21


TCPIP profile statements (see CS IP Configuration Reference)

DEVICE TRLE0E20 MPCPTP
LINK LINK0E20 MPCPTP TRLE0E20

INTERFACE FACE0E20 DEFINE MPCPTP6 TRLENAME TRLE0E20
IPADDR 2001:470:792a:1::101

HOME
10.149.86.1 LINK0E20

BEGINROUTES
ROUTE 2001:470:792a:1::102/128 = FACE0E20 MTU 1500
ROUTE 10.149.86.2/32 = LINK0E20 MTU 1500
ROUTE DEFAULT6 2001:470:792a:1::102 FACE0E20 MTU DEFAULTSIZE
ROUTE DEFAULT 10.149.86.2 LINK0E20 MTU DEFAULTSIZE
ENDROUTES

START TRLE0E20
START FACE0E20
jln@stben.net [hercules-390]
2017-02-17 19:57:25 UTC
Permalink
Many thanks Mcisho. I'll try it this week-end.
'Jean-Louis Noel' jln@stben.net [hercules-390]
2017-02-17 23:56:58 UTC
Permalink
Hi Mcisho,
Post by ***@yahoo.com [hercules-390]
hlq.VTAMLST member (see CS SNA Resource Definition Reference)
Is it ADCD.Z110.VTAMLST(HERCTL)?
Because I find there OSATRL1 that looks the same.

But, something is still wrong.

Hercules side seems OK:
tun0: flags=81<UP,POINTOPOINT,RUNNING> mtu 1500
inet 10.149.86.2 netmask 255.255.255.255 destination 10.149.86.1
inet6 2001:470:792a:1::102 prefixlen 128 scopeid 0x0<global>
inet6 fe80::b6d:ad81:f2cb:39be prefixlen 64 scopeid 0x20<link>
inet6 fe80::1563:4f12:9c03:565d prefixlen 64 scopeid 0x20<link>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4 bytes 584 (584.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

z/OS side not really:
EDIT ADCD.Z110.VTAMLST(HERCTRL) - 01.01 Columns 00001 00072
Command ===> Scroll ===> CSR
****** ***************************** Top of Data ******************************
==MSG> -Warning- The UNDO command is not available until you change
==MSG> your edit profile using the command RECOVERY ON.
000100 HERCTRL VBUILD TYPE=TRL
000200 TRLE0E20 TRLE LNCTL=MPC,READ=(0E20),WRITE=(0E21), X
000300 MPCLEVEL=HPDT

EZZ2350I MVS TCP/IP NETSTAT CS V1R10 TCPIP Name: TCPIP 00:54:58
EZZ2700I Home address list:
EZZ2701I Address Link Flg
EZZ2702I ------- ---- ---
EZZ2703I 10.149.86.1 LINK0E20 P
EZZ2703I 127.0.0.1 LOOPBACK
***

00.55.56 d net,trl
00.55.56 STC01022 IST097I DISPLAY ACCEPTED
00.55.56 STC01022 IST350I DISPLAY TYPE = TRL
IST924I -------------------------------------------------------------
IST1954I TRL MAJOR NODE = ISTTRL
IST1314I TRLE = IUTIQDIO STATUS = NEVAC CONTROL = MPC
IST1314I TRLE = IUTSAMEH STATUS = NEVAC CONTROL = MPC
IST1454I 2 TRLE(S) DISPLAYED
IST924I -------------------------------------------------------------
IST1954I TRL MAJOR NODE = OSATRL1
IST1314I TRLE = OSATRL1E STATUS = NEVAC CONTROL = MPC
IST1454I 1 TRLE(S) DISPLAYED
IST314I END

Did I miss something?

Thanks for your help.
Joe Monk joemonk64@gmail.com [hercules-390]
2017-02-18 00:56:31 UTC
Permalink
F NET,ACT,OSATRL1E

What happens?

Joe
Post by 'Jean-Louis Noel' ***@stben.net [hercules-390]
Hi Mcisho,
Post by ***@yahoo.com [hercules-390]
hlq.VTAMLST member (see CS SNA Resource Definition Reference)
Is it ADCD.Z110.VTAMLST(HERCTL)?
Because I find there OSATRL1 that looks the same.
But, something is still wrong.
tun0: flags=81<UP,POINTOPOINT,RUNNING> mtu 1500
inet 10.149.86.2 netmask 255.255.255.255 destination 10.149.86.1
inet6 2001:470:792a:1::102 prefixlen 128 scopeid 0x0<global>
inet6 fe80::b6d:ad81:f2cb:39be prefixlen 64 scopeid 0x20<link>
inet6 fe80::1563:4f12:9c03:565d prefixlen 64 scopeid 0x20<link>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500
(UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4 bytes 584 (584.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
EDIT ADCD.Z110.VTAMLST(HERCTRL) - 01.01 Columns 00001 00072
Command ===> Scroll ===> CSR
****** ***************************** Top of Data
******************************
==MSG> -Warning- The UNDO command is not available until you change
==MSG> your edit profile using the command RECOVERY ON.
000100 HERCTRL VBUILD TYPE=TRL
000200 TRLE0E20 TRLE LNCTL=MPC,READ=(0E20),WRITE=(0E21), X
000300 MPCLEVEL=HPDT
EZZ2350I MVS TCP/IP NETSTAT CS V1R10 TCPIP Name: TCPIP 00:54:58
EZZ2701I Address Link Flg
EZZ2702I ------- ---- ---
EZZ2703I 10.149.86.1 LINK0E20 P
EZZ2703I 127.0.0.1 LOOPBACK
***
00.55.56 d net,trl
00.55.56 STC01022 IST097I DISPLAY ACCEPTED
00.55.56 STC01022 IST350I DISPLAY TYPE = TRL
IST924I ----------------------------------------------------------
IST1954I TRL MAJOR NODE = ISTTRL
IST1314I TRLE = IUTIQDIO STATUS = NEVAC CONTROL = MPC
IST1314I TRLE = IUTSAMEH STATUS = NEVAC CONTROL = MPC
IST1454I 2 TRLE(S) DISPLAYED
IST924I ----------------------------------------------------------
IST1954I TRL MAJOR NODE = OSATRL1
IST1314I TRLE = OSATRL1E STATUS = NEVAC CONTROL = MPC
IST1454I 1 TRLE(S) DISPLAYED
IST314I END
Did I miss something?
Thanks for your help.
'Jean-Louis Noel' jln@stben.net [hercules-390]
2017-02-18 10:09:12 UTC
Permalink
Hi Joe,
Post by Joe Monk ***@gmail.com [hercules-390]
F NET,ACT,OSATRL1E
11.01.34 F NET,ACT,OSATRL1E

11.01.34 IEE341I NET NOT ACTIVE

11.03.20 d net,trl

11.03.20 STC01064 IST097I DISPLAY ACCEPTED

11.03.20 STC01064 IST350I DISPLAY TYPE = TRL

IST924I -------------------------------------------------------------

IST1954I TRL MAJOR NODE = ISTTRL

IST1314I TRLE = IUTIQDIO STATUS = NEVAC CONTROL = MPC

IST1314I TRLE = IUTSAMEH STATUS = NEVAC CONTROL = MPC

IST1454I 2 TRLE(S) DISPLAYED

IST924I -------------------------------------------------------------

IST1954I TRL MAJOR NODE = OSATRL1

IST1314I TRLE = OSATRL1E STATUS = NEVAC CONTROL = MPC

IST1454I 1 TRLE(S) DISPLAYED

IST314I END



But, the goal here is using HERTCL not OSATRL1E



EDIT ADCD.Z110.VTAMLST(HERCTRL) - 01.01 Columns 00001 00072

Command ===> Scroll ===> CSR

****** ***************************** Top of Data ******************************

==MSG> -Warning- The UNDO command is not available until you change

==MSG> your edit profile using the command RECOVERY ON.

000100 HERCTRL VBUILD TYPE=TRL

000200 TRLE0E20 TRLE LNCTL=MPC,READ=(0E20),WRITE=(0E21), X

000300 MPCLEVEL=HPDT



EDIT ADCD.Z110.VTAMLST(OSATRL1) - 01.00 Columns 00001 00072

Command ===> Scroll ===> CSR

****** ***************************** Top of Data ******************************

==MSG> -Warning- The UNDO command is not available until you change

==MSG> your edit profile using the command RECOVERY ON.

000100 OSATRL1 VBUILD TYPE=TRL

000200 OSATRL1E TRLE LNCTL=MPC,READ=(0400),WRITE=(0401),DATAPATH=(0402), X

000300 PORTNAME=ADM1ETP, X

000400 MPCLEVEL=QDIO
Joe Monk joemonk64@gmail.com [hercules-390]
2017-02-18 10:52:20 UTC
Permalink
Yep ... Your TRL is not active.

That's why its not working.

Joe
Post by 'Jean-Louis Noel' ***@stben.net [hercules-390]
Hi Joe,
Post by Joe Monk ***@gmail.com [hercules-390]
F NET,ACT,OSATRL1E
11.01.34 F NET,ACT,OSATRL1E
11.01.34 IEE341I NET NOT ACTIVE
11.03.20 d net,trl
11.03.20 STC01064 IST097I DISPLAY ACCEPTED
11.03.20 STC01064 IST350I DISPLAY TYPE = TRL
IST924I -------------------------------------------------------------
IST1954I TRL MAJOR NODE = ISTTRL
IST1314I TRLE = IUTIQDIO STATUS = NEVAC CONTROL = MPC
IST1314I TRLE = IUTSAMEH STATUS = NEVAC CONTROL = MPC
IST1454I 2 TRLE(S) DISPLAYED
IST924I -------------------------------------------------------------
IST1954I TRL MAJOR NODE = OSATRL1
IST1314I TRLE = OSATRL1E STATUS = NEVAC CONTROL = MPC
IST1454I 1 TRLE(S) DISPLAYED
IST314I END
But, the goal here is using HERTCL not OSATRL1E
EDIT ADCD.Z110.VTAMLST(HERCTRL) - 01.01 Columns 00001 00072
Command ===> Scroll ===> CSR
****** ***************************** Top of Data
******************************
==MSG> -Warning- The UNDO command is not available until you
change
==MSG> your edit profile using the command RECOVERY
ON.
000100 HERCTRL VBUILD TYPE=TRL
000200 TRLE0E20 TRLE LNCTL=MPC,READ=(0E20),WRITE=(0E21),
X
000300 MPCLEVEL=HPDT
EDIT ADCD.Z110.VTAMLST(OSATRL1) - 01.00 Columns 00001 00072
Command ===> Scroll ===> CSR
****** ***************************** Top of Data
******************************
==MSG> -Warning- The UNDO command is not available until you
change
==MSG> your edit profile using the command RECOVERY
ON.
000100 OSATRL1 VBUILD TYPE=TRL
000200 OSATRL1E TRLE LNCTL=MPC,READ=(0400),WRITE=(0401),DATAPATH=(0402),
X
000300 PORTNAME=ADM1ETP,
X
000400 MPCLEVEL=QDIO
mcisho@yahoo.com [hercules-390]
2017-02-18 10:07:23 UTC
Permalink
The TRL I suggested and OSATRL1 are completely different, for completely different devices.

As long as VTAM can find the TRL you can put it in whichever hlq.VTAMLST is convenient for you.

Looks like you didn't activate the TRL?
jln@stben.net [hercules-390]
2017-02-18 11:50:39 UTC
Permalink
Hi Mcisho,


Yes, you were right:


MVS TCP/IP NETSTAT CS V1R10 TCPIP Name: TCPIP 12:11:25
Home address list:
LinkName: LINK0E20
Address: 10.149.86.1
Flags: Primary
LinkName: LOOPBACK
Address: 127.0.0.1
Flags:
IntfName: FACE0E20
Address: 2001:470:792a:1::101
Type: Global
Flags:
Address: fe80::6063:8699:9870:5d7c
Type: Link_Local
Flags: Autoconfigured
IntfName: LOOPBACK6
Address: ::1
Type: Loopback
Flags:
***
That's looking better!


CS V1R10: Pinging host WWW.GOOGLE.BE
at IPv6 address 2a00:1450:4009:801::2003
Ping #1 response took 0.023 seconds.
***


You can't ask for more :-)


Thank you so much
mcisho@yahoo.com [hercules-390]
2017-02-18 12:10:31 UTC
Permalink
Good.

I would be interested to hear more about your hosts IPv6 setup. Though I use IPv6 to communicate between my host and Hercules guests, I don't have an IPv6 connection to the outside world.
jln@stben.net [hercules-390]
2017-02-18 13:27:16 UTC
Permalink
Hi Mcisho,


Take a look at:
https://tunnelbroker.net/ https://tunnelbroker.net/
jln@stben.net [hercules-390]
2017-02-18 13:36:12 UTC
Permalink
Hi Mcisho,


I would advise you to look at:
https://tunnelbroker.net/ https://tunnelbroker.net/

and claim one.

Loading...