Hello:

I was dealing with an AS/400 whose system name is different with the local CP name.   While trying to APING to a zOS host it failed with SNA sense code 08970015 which indicates no dynamic LU function is available for the partner zOS.  I noticed in the zOS console that the OLU (originated LU) of the request sent to the zOS is the system name instead of the local CP name.      Would it be required that the partner should  enable dynamic LU function so that APING can succeed?    And is it a common practice in the AS400 configuration that local CP name is identical with the system name so that the verification of the EE connection between AS/400 to other platform can be performed without any misleading?   

I also read some materials which said that the EEDIAG command from the z/OS is not supported on AS400, so the EEDIAG function will never be successful.    Is it still true up to current version? 

Hello

This is an old redbook but I am quite sure it is still relevant : Enterprise Extender Implementation Guide. There is a pretty detailed example to connect an IBM i (i5/OS in 2007!) to a zOS.

Checkout the chapter 9.

And, yes, this is quite common on an IBM i system for the system name to match the local control point name in the network attributes.

Hope it helps.

Hello Marc:

Thanks for the update.   Eventually the connection is established.   It seems that APING is the only way to test the connection with other EE-capable host, but it will fail if (1) the CP name and system name is different on AS400 side, and (2) other host doesn't enable dynamic LU capability on the definition of this AS/400.      I am just quite confused why the APING will not use the CP name as the source.