You can enter the local system as a "remote" system in your own partner list. However, when performing file transfers with this system, you should note that files can be destroyed by being copied to themselves.
It is advisable to store the FTADDPTN commands required for the entries in the partner list in a PS data set or in a PO/PDSE data set member. This facilitates the transition to a new partner list. You can generate such a file for an existing network description file using the parameter LAYOUT=*ZOS-PROC in the FTSHWPTN command.
In large networks, especially in client-server configurations, it is a considerable effort to enter individually in the partner list all the partner systems which are to communicate with the local system. In order to reduce this effort, openFT provides with the dynamic partners option for handling file transfer and file management jobs initiated in partner systems, but which have no separate entry in the partner list (see openFT manual "Concepts and Functions").