Determining problems with REXEC

If you detect a problem when using the REXEC server, you can use the REXEC flow chart and cause lists to identify potential problems.

However, if you are having problems with general TCP/IP connectivity, it might be beneficial to first use the TCP/IP troubleshooting topic collection to identify basic TCP/IP problems. Use the REXEC flow chart for more localized problems.

Figure 1. REXEC Server Problem Analysis

Cause List A
1. Check to see that the REXEC server is running. If not, start it with the STRTCPSVR SERVER(*REXEC) command.
2. If the message "Connection refused" is returned to the REXEC client, check the exit program associated with the exit point QIBM_QTMX_SERVER_REQ. This exit program has either specified that the connection should be rejected, returned a value that is not correct for the Allow Operation parameter, or ended abnormally. Examine the REXEC server job log for messages. Resolve any problems with the exit program and install the corrected version.
Cause List B
1. Check your user ID and password by logging on to the system. If you are unable to do so, contact the system administrator to verify that your user ID and password are correct.
2. Check the exit program associated with exit point QIBM_QTMX_SERVER_LOGON (if any). This exit program has either specified that the connection should be rejected, returned a value this is not correct for the Allow Operation parameter, or ended abnormally. Examine the REXEC server job log for messages.
Cause List C
1. Check for any job log messages returned to the REXEC client. Resolve any indicated problems and try the command again.
2. If the message "Command Rejected" is returned to the REXEC client, check the exit program associated with the exit point QIBM_QTMX_SERVER_REQ. This exit program may be specifying that the command should be rejected, returning a value this is not correct for the Allow Operation parameter, or ending abnormally. Examine the REXEC server job log for messages. Resolve any problems with the exit program and install the corrected version.
3. Verify that the correct ASCII CCSID is configured for the REXEC server. If not, set the correct CCSID with the CHGRXCA command.

Materials required for reporting REXEC problems
You need to provide some specific information, such as the error data or server job logs, when reporting REXEC problems.
Getting a copy of a REXEC server job log
To get a copy of the REXEC server job log, you need to create it.
Tracing the REXEC server
The REXEC server can be traced by creating a data area. Note that running the REXEC server with trace running may cause a significant performance impact.

Parent topic:

REXEC