The RSARFCEX is executable from transaction code SE38/SA38. This report is used to execute call that are not yet executed.
You can use this program to execute SM58 entries according to your own selection criteria. You can select by user, period, and entry status.
- Communication errors
- LUWs in which a communication error occurred during transmission.
- Recorded
- LUWs that have been recorded but not yet sent, because the system was switched off after the recording.
- System error
- A serious error has occurred in the target system (short dump, error message)
- Being transmitted
- The LUW is currently being transmitted. If this status lasts for hours, a transmission error has occurred (roll file full, out of memory, system stopped). You should only transmit these entries using this program unless the “No entries younger than” selection is considerably greater than the processing time for a single entry. Otherwise, you risk selecting and sending entries for a second time. As a rule, 30 minutes is sufficient. You must not, under any circumstances, choose this option if the report is scheduled as a background job. When large amounts of data are transmitted, it can often occur that the report starts even though the old job is not finished. This can lead to multiple transmission!
- Terminated due to system overload
- If an LUW has been recorded but not yet sent due to system overload (all dialog work processes are occupied), a background job is scheduled for immediate dispatch. If this background job has been cancelled (for example because system has been restarted), you can use this option to restart all LUWs cancelled due to overload.
- Temporary application error
- A temporary error (for example, a lock problem) has been reported by the application from the target system. This error is treated as a connection error.
- Serious application error
- A serious error has been reported by the application from the target system. This error is treated as a system error.
