RSE returns message RSEG1242 on connection attempt
The Developer for z/OS® message RSEG1242 Daemon failed to launch server on host using port port can have the following details: CONNECTION REFUSED or SERVER FAILURE.
Symptom
When you attempt to connect to a remote system, you receive error message RSEG1242.Diagnosing the problem
When you see CONNECTION REFUSED with the message, the Remote System Explorer daemon is not active. When you see SERVER FAILURE with the message, your client contacted the remote system but became disconnected.Resolving the problem
- CONNECTION REFUSED
- Check RSED job output in SDSF (Spool Display and Search Facility) for an indication that the RSE daemon is not using the port that is specified by the client. The RSE daemon is not running.
- Check console message FEK002I (syslog or RSE daemon job output) for an indication that a firewall or other network issue is blocking the client from accessing the RSE daemon port. (Port 0 in the RSEG1242 message normally indicates the RSE daemon).
- Try telnet from the client workstation to the RSE daemon port
(the connection hangs for 30 seconds if successful, but a firewall
displays a message).
telnet host port
- If the client can access the RSE daemon, but not the RSE server due to firewall issues (typically indicated by a nonzero port number in the RSEG1242 message), alter the _RSE_PORTRANGE in rse.env.
- SERVER FAILURE
- The detailed remote system logs show the error message that is
shown in rseserver.log (only if the RSE daemon
or server was reached):
ERROR RseDaemon: server failure: password revoked
- In this case, view the detailed remote system logs to see which part of the code failed.
- Set debug_level=2 in /etc/zexpl/rsecomm.properties and restart the
RSE daemon or use the operator commands to dynamically activate tracing:
F RSED,APPL=RSL ON and F RSED,APPL=RCL ON
- After you re-create the problem, customize and run FEK.SFEKSAMP(FEKLOGS).
- Create a service request PMR and send the output to your IBM® customer support representative.