OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/J

[Contents][Index][Back][Next]

2.14 Receive port fixing facility

TP1/Client/J allows you to fix the receive port for an RPC that uses the scheduler direct facility and an RPC that uses the name service. This is called the receive port fixing facility.

When you send an RPC's response from TP1/Server to TP1/Client/J, you use this facility to filter out notifications other than those approved for the receive port of TP1/Client/J by means of a firewall positioned between TP1/Server and TP1/Client/J.

To use this facility, specify the dccltcuprcvport operand in the TP1/Client/J environment definition.

The following describes when the receive port fixing facility is not used and when this facility is used.

Organization of this section
(1) When the receive port fixing facility is not used
(2) When the receive port fixing facility is used

(1) When the receive port fixing facility is not used

There is no filtering for the receive port in the RPC's response communication. The OS automatically allocates an undefined port as the receive port for the RPC in TP1/Client/J.

The following figures show when the receive port fixing facility is not used.

Figure 2-39 When the receive port fixing facility is not used (RPC using the scheduler direct facility)

[Figure]

Figure 2-40 When the receive port fixing facility is not used (RPC using the name service)

[Figure]

(2) When the receive port fixing facility is used

The port specified in the dccltcuprcvport operand in the TP1/Client/J environment definition is used as the receive port for response communication to the RPC, and other communication is subject to filtering. This method enables you to use the firewall to filter response communications from TP1/Server for unauthorized service requests.

The following figures show when the receive port fixing facility is used.

Figure 2-41 When the receive port fixing facility is used (RPC using the scheduler direct facility)

[Figure]

Figure 2-42 When the receive port fixing facility is used (RPC using the name service)

[Figure]