Internal communication

Several Developer for z/OS® host services run in separate threads or address spaces and are using TCP/IP sockets as communication mechanism, using your system’s loopback address. All these services use RSE for communicating with the client, making their data stream confined to the host only. For some services any available port will be used, for others the system programmer can choose the port or port range that will be used:

• (z/OS Explorer) JES Job Monitor for JES-related services, default port 6715. The port can be set in the FEJJCNFG configuration member and is repeated in the rse.env configuration file.
• CARMA communication uses by default an ephemeral port, but a port range can be set in the CRASRV.properties configuration file.
• (z/OS Debugger) Debug Manager for debug related services, default port 5336. The port can be set in the DBGMGR started task JCL.
• Host-based code coverage, which is a batch job, allocates an ephemeral port to allow the z/OS Debugger to communicate with it and deliver data needed for the code coverage report.