The manual mentions how to convert VIPA as well. One minor "gotcha" is that we 
had AUTORESTART on our DEVICE statement and that isn't supported in the 
INTERFACE statement so we had to strip it.  

Rex

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Pommier, Rex
Sent: Thursday, April 18, 2024 9:36 AM
To: [email protected]
Subject: Re: [EXTERNAL] Fwd: Converting TCPIP DEVICE and LINK statements in 
preparation for z/OS 3.1

We're currently going thru the same migration.  IP configuration guide has a 
section on converting DEVICE/LINK to INTERFACE statements.  It is actually a 
pretty good cookbook for it.  

We don't use VIPA but IIRC there's a sub section in the book about how to 
convert VIPA links.

Rex

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Albertus de Wet
Sent: Wednesday, April 17, 2024 6:22 PM
To: [email protected]
Subject: [EXTERNAL] Fwd: Converting TCPIP DEVICE and LINK statements in 
preparation for z/OS 3.1

We are on z/OS 2.4 and need to goto 3.1. We never did the z/OS 2.5 upgrade and 
as I understood, this was an action item for zOS 2.5. So, how do we convert the 
"DEVICE", "LINK" and "HOME" statements for TCPIP V3.1 *This is what we 
currently use in TCPIP:* ; VIPA definition (EE)
*DEVICE* VIPA00     VIRTUAL 0
*LINK*   VIPAL00    VIRTUAL 0 VIPA00
;

; Enterprise Extender Definitions (EE)
*DEVICE* IUTSAMEH MPCPTP
*LINK  * IUTSAMEHL MPCPTP IUTSAMEH
;

; OSA8100 is a OSA Express feature (CHPID=01) *DEVICE *OSA8000 MPCIPA NONROUTER 
AUTORESTART
*LINK*   OSAL8000 IPAQENET OSA8000
;

According to:
https://urldefense.com/v3/__https://www.ibm.com/docs/en/zos/2.5.0?topic=cnha-steps-converting-from-ipv4-ipaqenet-device-link-home-definitions-ipv4-ipaqenet-interface-statement__;!!KjMRP1Ixj6eLE0Fj!tkOoU5b8fT9PCVQu41SK1CXSlwCZL8mfpyUaoLw3EZ3-Bf-b4A_Wwx7g0fvyotb9GdghBKy5FXX17C8ZXWeJ7TyMyp8OK8SfZ8kc$
I come up with this, but obviously miss something:
; VIPA definition (EE)
;DEVICE VIPA00     VIRTUAL 0
;LINK   VIPAL00    VIRTUAL 0 VIPA00
INTERFACE VIPAL00
  DEFINE VIRTUAL
  IPADDR 10.64.14.106
  PORTNAME VIPA00
  VIRTUAL 0
;
; Enterprise Extender Definitions (EE)
;DEVICE IUTSAMEH MPCPTP
;LINK   IUTSAMEHL MPCPTP IUTSAMEH
INTERFACE IUTSAMEHL
  DEFINE MPCPTP
  IPADDR 10.64.14.107
  PORTNAME IUTSAMEH
;
;DEVICE OSA8100 MPCIPA NONROUTER AUTORESTART
;LINK   OSAL8100 IPAQENET OSA8100
INTERFACE OSAL8100
  DEFINE IPAQENET
  IPADDR 10.64.14.105
  PORTNAME OSA8100
  NONROUTER AUTORESTART
and I commented out the HOME statements.

I cannot seem to get this to work. What is confusing to me is the VIRTUAL 0 
part and we also do not have any "additional parameters" as per the 
documentation.
I created another TCPIPX proc, pointing to the new PROFX member.
When I stopped the original TCPIP and start TCPIPX, it comes up, but not happy 
with these messages:













*EZZ0162I HOST NAME FOR TCPIPX IS LP2
EZZ0300I OPENED PROFILE FILE DD:PROFILE
 EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE EZZ0401I SYNTAX ERROR IN 
FILE: DD:PROFILE ON LINE: 180 AT:
'PORTNAME'EZZ0324I UNRECOGNIZED STATEMENT PORTNAME FOUND ON LINE 180
    EZZ0318I MPCPTP WAS FOUND ON LINE 187 AND INTERFACE TYPE WAS 
EXPECTEDEZZ0324I UNRECOGNIZED STATEMENT AUTORESTART FOUND ON LINE 197  EZZ0328I 
DEVICE OSA8100 ON LINE 385 HAS NOT BEEN DEFINED OR HAS BEEN DELETED EZZ0328I 
DEVICE IUTSAMEH ON LINE 386 HAS NOT BEEN DEFINED OR HAS
BEEN DELETED                                                     EZZ0316I
PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE             EZZ0303I
INITIAL PROFILE FILE CONTAINS ERRORS                        EZZ0641I IP
FORWARDING NOFWDMULTIPATH SUPPORT IS ENABLED             EZZ0351I
SOURCEVIPA SUPPORT IS ENABLED                               EZZ0338I TCP
PORTS 1 THRU 1023 ARE RESERVED                          EZZ0338I UDP PORTS
1 THRU 1023 ARE RESERVED                          EZZ4248E TCPIPX WAITING
FOR PAGENT TTLS POLICY*



*EZZ4202I Z/OS UNIX - TCP/IP CONNECTION ESTABLISHED FOR TCPIPX  EZB6473I
TCP/IP STACK FUNCTIONS INITIALIZATION COMPLETE.       EZAIN11I ALL TCPIP
SERVICES FOR PROC TCPIPX ARE AVAILABLE.*



*EZD1313I REQUIRED SAF SERVAUTH PROFILE NOT FOUND
  EZB.INITSTACK.MANZANA.TCPIPX                                    EZD1176I
TCPIPX HAS SUCCESSFULLY JOINED THE TCP/IP SYSPLEX GROUP EZBTCPCS*

And it also did not start TN3270 as the original TCPIP did.

Any ideas, as I am obviously missing something?
Also, how can I test this new parms without stopping and starting TCPIP address 
space each time? I knew my predessor used something like "OBEYFILE", but I am 
not sure if this would be the best way to change these definitions - after I 
figured out what needs to change to what.

Thank you.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to