If you have been providing the address information to date using TNS entries, then you have only entered in the UTM generation the application name, possibly the host name of the communication partner, and the name of your UTM application. You must specify these names in TNS as GLOBAL NAMES. The host name/IP address associations are determined by the TNS entry.
When converting from TNS entries to KDCDEF, the only information you still need to specify is the port number.
It is recommended that you always administer the full generation information for a UTM application centrally. To do this, proceed as follows:
Include the address information of the TNS entries that are of relevance for the UTM application in the KDCDEF generation.
Delete these TNS entries, including those from the TNS directory.
Based on the LU6.1 connection from section "Providing address information with KDCDEF" the following presents an example of the changes you will need to make when converting:
LU6.1 connection
In the following example, port number 10010
is used in the local application BSPLU61
and port number 12010
is used in the remote application LU61PART
. The remote application is running on the computer named CENTRAL2
.
Before conversion
KDCDEF: |
|
TNS entries: |
|
After conversion
When converting you must specify
for the local application name
the port number in the LISTENER-PORT parameter of the KDCDEF statement BCAMAPPL instead of the port number in the TNS entry (TSEL LANINET).for the remote partner
the processor name of the partner computer in the PRONAM parameter and the port number in the LISTENER-PORT parameter of the KDCDEF statement CON instead of the address and port number in the transport address of the TNS entry (TA).
In order to be able to determine the IP address of the partner computer, the name CENTRAL2
must be known to the DNS.
KDCDEF: |
|
LU6.1 connection using symbolic names
In the following example, port number 10010
is used in the local application BSPLU61
and port number 12010
is used in the remote application LU61PART
. The remote application is running on the computer named CENTRAL2
.
Before conversion
KDCDEF: |
|
TNS entries: |
|
After conversion
In contrast to the example "LU6.1 connection", you must also change the BCAMAPPL name and the CON name in the TSEL parameters of the TNS entries. In this case this means you must use the real names instead of the symbolic names.
When converting you must
change the name of the local application
in the BCAMAPPL parameter to the value you used in the local TNS entry (TSEL RFC1006).for the local application name
as in the example "LU6.1 connection", specify the port number in the LISTENER-PORT parameter of the KDCDEF statement BCAMAPPL instead of the port number in the TNS entry (TSEL LANINET).the name of the remote application
change the value in the CON statement to the value you used in the remote TNS entry (TA).for the remote partner
as in the example "LU6.1 connection", the processor name of the partner computer in the PRONAM parameter and the port number in the LISTENER-PORT parameter of the KDCDEF statement CON instead of the address and port number in the transport address of the TNS entry (TA)
In order to be able to determine the IP address of the partner computer, the name CENTRAL2
must be known to the DNS.
KDCDEF: |
|