Example of an REXECD trace of a client using the SEND command

Figure 1 shows a portion of an example of an REXECD trace of a client using a SEND command. Short descriptions of numbered items in the trace follow the figure.

Figure 1. Example of an REXECD trace of a client using a SEND command

EZA4801I MVS TCP/IP REXEC CS V1R10
 1 
EZA4437I SSCSARAY[0] JOB00043 40 WAITING
 2 
EZA4436I SSCSARAY[0] JOB00043 80 ACTIVE
EZA4436I SSCSARAY[0] JOB00043 80 ACTIVE
 3 
EZA4438I SSCSARAY[0] JOB00043 20 COMPLETED
EZA4385I SSSORT(CTRL): 00000000
 4 
EZA4392I S99ret: 00000000, A RSHD NEWALTON.RSHD5.JOB00043.D0000105.?
 5 
TIME-12:04:12 PM. CPU-00:00:00 SERVICE-1157 SESSION-00:00:01 APRIL 1,2008
EZA4393I S99ret: 00000000  
 6 
EZA4442I SSSORT(next): 00000004 NO MORE OUTPUT ON JES SPOOL

Following are short descriptions of the numbered items in the trace:

1

JOB00043 is the JES job number. The number 40 indicates that the job is waiting for execution. This means that the remote execution server has processed the REXEC client request, created a JES job, and has submitted the JOB to JES. The server continues to check the status.

Guidelines: If the status does not change from 40, this could indicate one of the following problems:

A JES initiator has not started to process the submitted job class.
Other jobs might be running in this class that are inhibiting this job from starting.

Make a note of the job number and check JES activity, or check any other jobs that might be running at the same time.

2

The number 80 indicates that the job is currently active. This means that the remote execution server has checked with JES on the job status and was informed that the job is running.

Guideline: If the status does not change from 80, this could indicate that the job is taking too long to run. REXEC was not intended to be used for long running jobs. Long running jobs should be submitted using FTP JES processing.

Tip: The FTP JES interface provides an alternate method of submitting a batch job remotely and retrieving the results.

3

The number 20 indicates that the job is on the output queue. This means that when the server checked with JES on the job status it discovered that the JES job has completed, and it has been placed on the output queue. The command output should be sent back to the client soon. See z/OS Communications Server: IP Messages Volume 1 (EZA) for more information about the individual messages in the trace.

4

This line shows the return code from the dynamic allocation of the JES data sent back to the client.

5

Actual command output sent to the client.

6

This line displays the return code that is expected when the process has completed.