Thank you. Your VIPA conversion is correct. I just tested on my Test LPAR. According to IBM IUTSAMEH can stay were it in the TCPIP parms definition and it will not be required by V3.1 TCP/ip to be converted. And yes, it apparently do get defined by VTAM automagically by specifying IPCONFIG DYNAMICXCF. I am going to leave it right where it is for now.
Finally, yes we do have the OSA defined also. I converted that to: INTERFACE OSAL8000 DEFINE IPAQENET IPADDR 10.64.14.68/24 PORTNAME OSA8000 NONROUTER Thanks for y'alls help. Example: IPCONFIG DYNAMICXCF 10.64.14.65 255.255.255.0 15 On Thu, Apr 18, 2024 at 2:09 PM John S. Giltner, Jr. < [email protected]> wrote: > For: > ;DEVICE VIPA00 VIRTUAL 0 > ;LINK VIPAL00 VIRTUAL 0 VIPA00 > > I think all you need is: > > INTERFACE VIPAL00 > DEFINE VIRTUAL > IPADDR 10.64.14.106 > > That is basically all we have. I don't think VIPA's have port names. I > thought portnames were used to map to TRLE definition in VTAM. > > For IUTSAMEH, I thought this was automatically created by VTAM. I know we > don't have a INTERFACE definition for it and from old copies of our > pre-INTERFACE definitions we never defined IUTSAMEH at all. > > For the issue with OSA8100, are you sure you have that defined in VTAM? > > On Wed, 17 Apr 2024 17:21:59 -0600, Albertus de Wet <[email protected]> > wrote: > > >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://www.ibm.com/docs/en/zos/2.5.0?topic=cnha-steps-converting-from-ipv4-ipaqenet-device-link-home-definitions-ipv4-ipaqenet-interface-statement > >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 > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
