Connection security
Most communication between Developer for z/OS® client and host goes through RSE, thus utilizing the connection security provided by z/OS Explorer.
Some Developer for z/OS services use a
separate external (client-host) communication path:
- The Remote Connect Emulator on the client connects to a TN3270 server on the host. The encryption details are controlled by an Application Transparent Transport Layer Security (AT-TLS) policy.
- Remote (host-based) actions in z/OS UNIX subprojects use an REXEC or SSH server on the host. SSH communication is always encrypted.