Distribution of public key files to your partner systems should take place using reliable means, for example by
distributing them via cryptographically secure by e-mail
distributing them on a CD (by courier or by registered mail).
distributing them via a central, openFT file server, whose public key is in the partners’ possession.
You must ensure that your public key files are re-coded (e.g. by transferring them as text files via openFT), if you transfer them to a partner with a different operating system (e.g. BS2000 system).
The public key file of your local openFT instance is stored in the partner system in the following location:
For partners using openFT (BS2000) as type D, PLAM elements in the library SYSKEY on the configuration user ID of the partner instance. The partner name allocated to your openFT instance in the remote partner list SYSPTF must be selected as the element name.
For partners using openFT (Unix systems) in the directory syskey of the instance file tree. In the case of the standard instance the path name is /var/openFT/std/syskey. The instance ID of your local openFT instance must be selected as the file name. The file name must not contain any uppercase characters. If the instance ID contains any uppercase characters, they must be converted to lowercase characters in the file name.
For partners using openFT (Windows) in the directory syskey of the instance file tree. In the case of the standard instance the path name under Windows 10 is
%ProgramData%\Fujitsu Technology Solutions\openFT\var\std\syskey.The instance ID of your local openFT instance must be selected as the file name.
For partners using openFT (z/OS) as a PO element in the library
admuser.instance.SYSKEY, where instance is the name of the instance. The partner name allocated to your openFT instance in the remote partner list SYSPTF must be selected as the element name.