Changes to the ssh command that might require a migration action

Table 1 lists the changes to the ssh command that might require a migration action and the accompanying actions.

Table 1. Changes to the ssh command that might require a migration action
What changed	Migration action needed?
The -I option Previously, the argument was the device that ssh should use to communicate with a smart card used for storing the user's private RSA key. Now, the argument is the PKCS#11 shared library ssh should use to communicate with a PKCS#11 token providing the user's private RSA key.	No, because the option (-I `smartcard_device`) is not supported on z/OS systems.
The -R options Previously, the port argument "0" was not supported. Now, if the port argument is “0”, the listen port will be dynamically allocated on the server and reported to the client at run time.	No, setting the port argument to 0 was considered to be illegal in the previous version.