Re: TCPIP Device/Link to Interface question???

2023-07-27 Thread Shaffer, Terri 
Thanks.  I think what I have is correct, its just looks different now, because 
a plain hometest, shows loopback first, but if you NETSTAT HOME under FLG is my 
primary INTERFACE.

Ms Terri E Shaffer
Senior Systems Engineer,
z/OS Support:
ACIWorldwide - Telecommuter
H(412-766-2697) C(412-519-2592)
terri.shaf...@aciworldwide.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Colin Paice
Sent: Thursday, July 27, 2023 3:54 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TCPIP Device/Link to Interface question???

EXTERNAL EMAIL: Do not click links or open attachments unless you know the 
content is safe.


Terri,

The HOME is only used for DEVICE/LINK.  You specify the "home address-es"
on the interface.
For example
INTERFACE IFPORTCP6
DEFINE IPAQENET6
CHPIDTYPE OSD
PORTNAME PORTA
INTFID 2:2:2:2

* IPADDR FC00:2::2:2:2 *

INTERFACE IFPORTCP6
ADDADDR 2001:DB8::9

The doc also says
*PRIMARYINTERFACE*






*Restriction: The PRIMARYINTERFACE statement applies to IPv4 only.Use the 
PRIMARYINTERFACE statement to specify which interface is to be designated as 
default localhost for use by the GETHOSTID() functionIf the 
PRIMARYINTERFACE statement is not specified, then the first address in the HOME 
list isdesignated as the default local host. If no HOME statements are defined 
in the profile,PRIMARYINTERFACE defaults to the first IPv4 INTERFACE statement 
listed in the profile.*

Which sounds like changing the statement to point to your interface should 
work.  If PRIMARYINTERFACE is not specified it will point to one of your HOME 
statements (if any)

Colin


On Wed, 26 Jul 2023 at 17:02, Shaffer, Terri < 
017d5f778222-dmarc-requ...@listserv.ua.edu> wrote:

> Hi,
>   Was wondering if someone could answer a question?
>
> I am converting my DEVICE/LINK statements to INTERFACE in my TCPIP
> configuration on my test lpar.
>
> I recycled my TCPIP and everything works, except I tripped an error on
> my HOME statement, because I think it uses LINK name, not Interface name?
>
> My PRIMARYINTERFACE is my primary INTERFACE statement , again
> everything seems to work.
>
> However, when I did a hometest, it looked okay with my primary IPADDR
> first, then Secondary and then loopback address which it should be.
>
> But to stop the error from my HOME link name from occurring, I
> commented my HOME statement out.
>
> That fixed my error message, but now LOOPBACK is first, then Primary
> IPADDRESS and then Secondary.
>
> So my question is do I need the HOME STATEMENT, or what replaces it,
> if anything when using INTERFACE statement?
>
> And/or how do I get the PRIMARY IPADDRESS first again?
>
> Ms Terri E Shaffer
> Senior Systems Engineer,
> z/OS Support:
> ACIWorldwide - Telecommuter
> H(412-766-2697) C(412-519-2592)
> terri.shaf...@aciworldwide.com
>
>
> 
>  [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] <
> http://www.aciworldwide.com> This email message and any attachments
> may contain confidential, proprietary or non-public information. The
> information is intended solely for the designated recipient(s). If an
> addressing or transmission error has misdirected this email, please
> notify the sender immediately and destroy this email. Any review,
> dissemination, use or reliance upon this information by unintended
> recipients is prohibited. Any opinions expressed in this email are
> those of the author personally.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 
<http://www.aciworldwide.com>
This email message and any attachments may contain confidential, proprietary or 
non-public information. The information is intended solely for the designated 
recipient(s). If an addressing or transmission error has misdirected this 
email, please notify the sender immediately and destroy this email. Any review, 
dissemination, use or reliance upon this information by unintended recipients 
is prohibited. Any opinions expressed in this email are those of the author 
personally.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TCPIP Device/Link to Interface question???

2023-07-27 Thread Colin Paice 
Terri,

The HOME is only used for DEVICE/LINK.  You specify the "home address-es"
on the interface.
For example
INTERFACE IFPORTCP6
DEFINE IPAQENET6
CHPIDTYPE OSD
PORTNAME PORTA
INTFID 2:2:2:2

* IPADDR FC00:2::2:2:2 *

INTERFACE IFPORTCP6
ADDADDR 2001:DB8::9

The doc also says
*PRIMARYINTERFACE*






*Restriction: The PRIMARYINTERFACE statement applies to IPv4 only.Use the
PRIMARYINTERFACE statement to specify which interface is to be designated
as default localhost for use by the GETHOSTID() functionIf the
PRIMARYINTERFACE statement is not specified, then the first address in the
HOME list isdesignated as the default local host. If no HOME statements are
defined in the profile,PRIMARYINTERFACE defaults to the first IPv4
INTERFACE statement listed in the profile.*

Which sounds like changing the statement to point to your interface should
work.  If PRIMARYINTERFACE is not specified it will point to one of your
HOME statements (if any)

Colin


On Wed, 26 Jul 2023 at 17:02, Shaffer, Terri <
017d5f778222-dmarc-requ...@listserv.ua.edu> wrote:

> Hi,
>   Was wondering if someone could answer a question?
>
> I am converting my DEVICE/LINK statements to INTERFACE in my TCPIP
> configuration on my test lpar.
>
> I recycled my TCPIP and everything works, except I tripped an error on my
> HOME statement, because I think it uses LINK name, not Interface name?
>
> My PRIMARYINTERFACE is my primary INTERFACE statement , again everything
> seems to work.
>
> However, when I did a hometest, it looked okay with my primary IPADDR
> first, then Secondary and then loopback address which it should be.
>
> But to stop the error from my HOME link name from occurring, I commented
> my HOME statement out.
>
> That fixed my error message, but now LOOPBACK is first, then Primary
> IPADDRESS and then Secondary.
>
> So my question is do I need the HOME STATEMENT, or what replaces it, if
> anything when using INTERFACE statement?
>
> And/or how do I get the PRIMARY IPADDRESS first again?
>
> Ms Terri E Shaffer
> Senior Systems Engineer,
> z/OS Support:
> ACIWorldwide - Telecommuter
> H(412-766-2697) C(412-519-2592)
> terri.shaf...@aciworldwide.com
>
>
> 
>  [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] <
> http://www.aciworldwide.com>
> This email message and any attachments may contain confidential,
> proprietary or non-public information. The information is intended solely
> for the designated recipient(s). If an addressing or transmission error has
> misdirected this email, please notify the sender immediately and destroy
> this email. Any review, dissemination, use or reliance upon this
> information by unintended recipients is prohibited. Any opinions expressed
> in this email are those of the author personally.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TCPIP Device/Link to Interface question???

2023-07-26 Thread Grant Taylor 

On 7/26/23 9:45 PM, Jon Perryman wrote:

"HOME" was not in UNIX TCP so z/OS is the only doc available.


Based on a previous comment about HOME controlling the IP address that 
remote systems saw newly initiated connections coming from, this concept 
is in, and has been for a long time, Linux.  This is the source IP 
chosen as part of routing.  --  This very much so became a thing with 
policy based routing in the early 2000s if not before.



There is in fact many features that were (and probably still are)
specific to z/OS


I'll give you "were".  I question "still are".


(e.g. HOME, VIPA, port balancing, port forwarding, sysplex
workload balancing and much more).


By default Linux uses what is called the weak host model which means 
that the IP addresses belong to the kernel (IP stack) and not to an 
interface.  It's trivial to move any given IP address around to 
different interfaces.  --  There's some minutia to moving IPs, but I 
assume there is minutia to VIPA too.


Port balancing seems to be quite similar to what is usually called "load 
balancing" in Open Systems.  Linux kernel has this capability built in 
in at least a couple of different ways.


I don't know what "port forwarding" means in z/OS context, but port 
forwarding connections from one IP address and port pair to another is 
so common that $75 dollar routers running Linux / *BSD have been doing 
it for 25 years.  I can't even successfully do a search for what it 
means on the mainframe because of all the other collissions that I find 
in IBM i, AIX, and that's on top of all the other non-IBM related results.


I don't know if sysplex workload balnacing has a counter part, but I 
strongly suspect that load balancers described above and / or clusters 
of servers account for much of this all be it likely in a different way.



z/OS needed a more robust TCP because of sysplex.


I would never have considered using z/OS for a networking Swiss Army 
Knife.  Linux and *BSD or a Cisco / Juniper router jump to the top of 
that list.



Linux, Windows, Unix and others are single machines with unique resources.


That is their most common configuration.  But Linux and *BSD in 
particular can do so much more if you want them to.



For instance, DB2 on z/OS can be accessed from any z/OS within a sysplex


Sure.

Depending on the middleware, you can get the same IP / service instance 
to be accessible from multiple machines in a cluster.



but DB2 on Linux is available
from a single machine which cannot be transferred to another Linux.
I don't know about DB2, but I an quite certain that there are multiple 
ways to have the same IP be accessible from multiple machines.


There are even ways to transfer the connections between machines.

There are ways to synchronize firewall state between multiple machines.

I'm quite certain that how things would be done on the mainframe are 
different than how they would be done on Linux.


But I'm also fairly certain that Linux can do most of, if not all of, 
what you have mentioned.


Thank you for the additional information Jon.



Grant. . . .

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TCPIP Device/Link to Interface question???

2023-07-26 Thread Jon Perryman 
 > On Wednesday, July 26, 2023 at 04:31:33 PM PDT, Grant Taylor wrote:

>> On 7/26/23 2:18 PM, Jon Perryman wrote:

>> The order should not matter in my opinion. z/OS TCP has a lot more

>> features than TCP on other platforms.


> Would you please elaborate on that statement?

"HOME" was not in UNIX TCP so z/OS is the only doc available. There is in fact 
many features that were (and probably still are) specific to z/OS (e.g. HOME, 
VIPA, port balancing, port forwarding, sysplex workload balancing and much 
more). z/OS needed a more robust TCP because of sysplex. Linux, Windows, Unix 
and others are single machines with unique resources. For instance, DB2 on z/OS 
can be accessed from any z/OS within a sysplex but DB2 on Linux is available 
from a single machine which cannot be transferred to another Linux. 

On Wednesday, July 26, 2023 at 04:31:33 PM PDT, Grant Taylor 
<023065957af1-dmarc-requ...@listserv.ua.edu> wrote:  
 
 On 7/26/23 2:18 PM, Jon Perryman wrote:
> Take this with a grain of salt because it's been a long time.

Obligatory salt dose taken.

> The order should not matter in my opinion. z/OS TCP has a lot more 
> features than TCP on other platforms.

Would you please elaborate on that statement?

> Finding the Unix equivalent is 
> often impossible when z/OS does not have clearly defined
> terminology.

Agreed.  Having a clear explanation of what a feature does is required 
to be able to compare features, even if the nomenclature therefor differs.

> z/OS HOME addresses doc was not clear when I last
> looked. My interpretation was that it's the home IP address for a
> sent TCP packet. In other words, when the packet is processed at the 
> destination, HOME is where the response will be sent. I could easily 
> be wrong and you will need to determine HOME current functionality.
Grant. . . .

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
  

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TCPIP Device/Link to Interface question???

2023-07-26 Thread Grant Taylor 

On 7/26/23 2:18 PM, Jon Perryman wrote:

Take this with a grain of salt because it's been a long time.


Obligatory salt dose taken.

The order should not matter in my opinion. z/OS TCP has a lot more 
features than TCP on other platforms.


Would you please elaborate on that statement?

Finding the Unix equivalent is 
often impossible when z/OS does not have clearly defined

terminology.


Agreed.  Having a clear explanation of what a feature does is required 
to be able to compare features, even if the nomenclature therefor differs.



z/OS HOME addresses doc was not clear when I last
looked. My interpretation was that it's the home IP address for a
sent TCP packet. In other words, when the packet is processed at the 
destination, HOME is where the response will be sent. I could easily 
be wrong and you will need to determine HOME current functionality.

Grant. . . .

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TCPIP Device/Link to Interface question???

2023-07-26 Thread Jon Perryman 
 > On Wednesday, July 26, 2023 at 10:13:52 AM PDT, Shaffer, Terri  wrote:
> not sure if I can change this order of not, because it displays differently 
>with just HOMETEST

Take this with a grain of salt because it's been a long time. The order should 
not matter in my opinion. z/OS TCP has a lot more features than TCP on other 
platforms. Finding the Unix equivalent is often impossible when z/OS does not 
have clearly defined terminology. z/OS HOME addresses doc was not clear when I 
last looked. My interpretation was that it's the home IP address for a sent TCP 
packet. In other words, when the packet is processed at the destination, HOME 
is where the response will be sent. I could easily be wrong and you will need 
to determine HOME current functionality.


On Wednesday, July 26, 2023 at 10:13:52 AM PDT, Shaffer, Terri 
<017d5f778222-dmarc-requ...@listserv.ua.edu> wrote:  
 
 Thanks.

I don't use VIPA here, but I think I am okay, as I did a NETSTAT  HOME

And my PRIMARY is designated correctly with the FLG  P

EZZ2350I MVS TCP/IP NETSTAT CS V2R5      TCPIP Name: TCPIP          17:09:31
EZZ2700I Home address list:
EZZ2701I Address          Link            Flg
EZZ2702I ---                      ---
EZZ2703I 127.0.0.1        LOOPBACK

EZZ2704I Address          Interface        Flg
EZZ2704I ---          -        ---
EZZ2703I 10.5.23.231      OSA0F0QDI        P
EZZ2703I 10.5.23.240      OSA180QDI

But not sure if I can change this order of not, because it displays differently 
with just HOMETEST

Ms Terri E Shaffer
Senior Systems Engineer,
z/OS Support:
ACIWorldwide - Telecommuter
H(412-766-2697) C(412-519-2592)
terri.shaf...@aciworldwide.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Marshall Stone
Sent: Wednesday, July 26, 2023 12:36 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TCPIP Device/Link to Interface question???

EXTERNAL EMAIL: Do not click links or open attachments unless you know the 
content is safe.


We have a static VIPA first with the same IP as the old HOME IP. Then the rest 
of the interfaces: OSA, Hipersockets, VIPA's DVIPA's . Comment out the HOME 
statement. Make sure your start statements are correct.  The OBEY file the 
whole updated profile.

Marshall Stone
Mainframe Engineer, Technical Services
-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Shaffer, Terri
Sent: Wednesday, July 26, 2023 12:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TCPIP Device/Link to Interface question???

Hi,
  Was wondering if someone could answer a question?

I am converting my DEVICE/LINK statements to INTERFACE in my TCPIP 
configuration on my test lpar.

I recycled my TCPIP and everything works, except I tripped an error on my HOME 
statement, because I think it uses LINK name, not Interface name?

My PRIMARYINTERFACE is my primary INTERFACE statement , again everything seems 
to work.

However, when I did a hometest, it looked okay with my primary IPADDR first, 
then Secondary and then loopback address which it should be.

But to stop the error from my HOME link name from occurring, I commented my 
HOME statement out.

That fixed my error message, but now LOOPBACK is first, then Primary IPADDRESS 
and then Secondary.

So my question is do I need the HOME STATEMENT, or what replaces it, if 
anything when using INTERFACE statement?

And/or how do I get the PRIMARY IPADDRESS first again?

Ms Terri E Shaffer
Senior Systems Engineer,
z/OS Support:
ACIWorldwide - Telecommuter
H(412-766-2697) C(412-519-2592)
terri.shaf...@aciworldwide.com



 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 
<http://www.aciworldwide.com> This email message and any attachments may 
contain confidential, proprietary or non-public information. The information is 
intended solely for the designated recipient(s). If an addressing or 
transmission error has misdirected this email, please notify the sender 
immediately and destroy this email. Any review, dissemination, use or reliance 
upon this information by unintended recipients is prohibited. Any opinions 
expressed in this email are those of the author personally.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 
<http://www.aciworldwide.com>
This email message and any attachments may contain confidential, proprietary or 
non-public information. The information is intended solely for the designated 
recipient(s). If an addressing or transmission error

Re: TCPIP Device/Link to Interface question???

2023-07-26 Thread Shaffer, Terri 
Thanks.

I don't use VIPA here, but I think I am okay, as I did a NETSTAT  HOME

And my PRIMARY is designated correctly with the FLG  P

EZZ2350I MVS TCP/IP NETSTAT CS V2R5   TCPIP Name: TCPIP   17:09:31
EZZ2700I Home address list:
EZZ2701I Address  Link Flg
EZZ2702I ---   ---
EZZ2703I 127.0.0.1LOOPBACK

EZZ2704I Address  InterfaceFlg
EZZ2704I ---  ----
EZZ2703I 10.5.23.231  OSA0F0QDIP
EZZ2703I 10.5.23.240  OSA180QDI

But not sure if I can change this order of not, because it displays differently 
with just HOMETEST

Ms Terri E Shaffer
Senior Systems Engineer,
z/OS Support:
ACIWorldwide - Telecommuter
H(412-766-2697) C(412-519-2592)
terri.shaf...@aciworldwide.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Marshall Stone
Sent: Wednesday, July 26, 2023 12:36 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TCPIP Device/Link to Interface question???

EXTERNAL EMAIL: Do not click links or open attachments unless you know the 
content is safe.


We have a static VIPA first with the same IP as the old HOME IP. Then the rest 
of the interfaces: OSA, Hipersockets, VIPA's DVIPA's . Comment out the HOME 
statement. Make sure your start statements are correct.  The OBEY file the 
whole updated profile.

Marshall Stone
Mainframe Engineer, Technical Services
-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Shaffer, Terri
Sent: Wednesday, July 26, 2023 12:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TCPIP Device/Link to Interface question???

Hi,
  Was wondering if someone could answer a question?

I am converting my DEVICE/LINK statements to INTERFACE in my TCPIP 
configuration on my test lpar.

I recycled my TCPIP and everything works, except I tripped an error on my HOME 
statement, because I think it uses LINK name, not Interface name?

My PRIMARYINTERFACE is my primary INTERFACE statement , again everything seems 
to work.

However, when I did a hometest, it looked okay with my primary IPADDR first, 
then Secondary and then loopback address which it should be.

But to stop the error from my HOME link name from occurring, I commented my 
HOME statement out.

That fixed my error message, but now LOOPBACK is first, then Primary IPADDRESS 
and then Secondary.

So my question is do I need the HOME STATEMENT, or what replaces it, if 
anything when using INTERFACE statement?

And/or how do I get the PRIMARY IPADDRESS first again?

Ms Terri E Shaffer
Senior Systems Engineer,
z/OS Support:
ACIWorldwide - Telecommuter
H(412-766-2697) C(412-519-2592)
terri.shaf...@aciworldwide.com



 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 
<http://www.aciworldwide.com> This email message and any attachments may 
contain confidential, proprietary or non-public information. The information is 
intended solely for the designated recipient(s). If an addressing or 
transmission error has misdirected this email, please notify the sender 
immediately and destroy this email. Any review, dissemination, use or reliance 
upon this information by unintended recipients is prohibited. Any opinions 
expressed in this email are those of the author personally.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 
<http://www.aciworldwide.com>
This email message and any attachments may contain confidential, proprietary or 
non-public information. The information is intended solely for the designated 
recipient(s). If an addressing or transmission error has misdirected this 
email, please notify the sender immediately and destroy this email. Any review, 
dissemination, use or reliance upon this information by unintended recipients 
is prohibited. Any opinions expressed in this email are those of the author 
personally.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TCPIP Device/Link to Interface question???

2023-07-26 Thread Marshall Stone 
We have a static VIPA first with the same IP as the old HOME IP. Then the rest 
of the interfaces: OSA, Hipersockets, VIPA's DVIPA's . Comment out the HOME 
statement. Make sure your start statements are correct.  The OBEY file the 
whole updated profile. 

Marshall Stone
Mainframe Engineer, Technical Services
-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Shaffer, Terri
Sent: Wednesday, July 26, 2023 12:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TCPIP Device/Link to Interface question???

Hi,
  Was wondering if someone could answer a question?

I am converting my DEVICE/LINK statements to INTERFACE in my TCPIP 
configuration on my test lpar.

I recycled my TCPIP and everything works, except I tripped an error on my HOME 
statement, because I think it uses LINK name, not Interface name?

My PRIMARYINTERFACE is my primary INTERFACE statement , again everything seems 
to work.

However, when I did a hometest, it looked okay with my primary IPADDR first, 
then Secondary and then loopback address which it should be.

But to stop the error from my HOME link name from occurring, I commented my 
HOME statement out.

That fixed my error message, but now LOOPBACK is first, then Primary IPADDRESS 
and then Secondary.

So my question is do I need the HOME STATEMENT, or what replaces it, if 
anything when using INTERFACE statement?

And/or how do I get the PRIMARY IPADDRESS first again?

Ms Terri E Shaffer
Senior Systems Engineer,
z/OS Support:
ACIWorldwide - Telecommuter
H(412-766-2697) C(412-519-2592)
terri.shaf...@aciworldwide.com



 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 
<http://www.aciworldwide.com> This email message and any attachments may 
contain confidential, proprietary or non-public information. The information is 
intended solely for the designated recipient(s). If an addressing or 
transmission error has misdirected this email, please notify the sender 
immediately and destroy this email. Any review, dissemination, use or reliance 
upon this information by unintended recipients is prohibited. Any opinions 
expressed in this email are those of the author personally.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

TCPIP Device/Link to Interface question???

2023-07-26 Thread Shaffer, Terri 
Hi,
  Was wondering if someone could answer a question?

I am converting my DEVICE/LINK statements to INTERFACE in my TCPIP 
configuration on my test lpar.

I recycled my TCPIP and everything works, except I tripped an error on my HOME 
statement, because I think it uses LINK name, not Interface name?

My PRIMARYINTERFACE is my primary INTERFACE statement , again everything seems 
to work.

However, when I did a hometest, it looked okay with my primary IPADDR first, 
then Secondary and then loopback address which it should be.

But to stop the error from my HOME link name from occurring, I commented my 
HOME statement out.

That fixed my error message, but now LOOPBACK is first, then Primary IPADDRESS 
and then Secondary.

So my question is do I need the HOME STATEMENT, or what replaces it, if 
anything when using INTERFACE statement?

And/or how do I get the PRIMARY IPADDRESS first again?

Ms Terri E Shaffer
Senior Systems Engineer,
z/OS Support:
ACIWorldwide - Telecommuter
H(412-766-2697) C(412-519-2592)
terri.shaf...@aciworldwide.com



 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 

This email message and any attachments may contain confidential, proprietary or 
non-public information. The information is intended solely for the designated 
recipient(s). If an addressing or transmission error has misdirected this 
email, please notify the sender immediately and destroy this email. Any review, 
dissemination, use or reliance upon this information by unintended recipients 
is prohibited. Any opinions expressed in this email are those of the author 
personally.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN