... [RETURNCODE rc]
[LENGTH leng]
[RECEIVED rec]
[HOLD] ... .
1. ... RETURNCODE rc
2. ... LENGTH leng
3. ... RECEIVED rec
4. ... HOLD
Additional additions for the statement
COMMUNICATION.
... RETURNCODE rc
This addition can be specified in all connection steps. The data type i is expected for rc. The meaning of the return values is coded in the
include program RSCPICDF. Here, data objects with descriptive names and
start values are declared and can be
compared with rc. The following table contains a list of possible return values.
| rc | Data Object in RSCPICDF |
| 0 | CM_OK |
| 1 | CM_ALLOCATE_FAILURE_NO_RETRY |
| 2 | CM_ALLOCATE_FAILURE_RETRY |
| 3 | CM_CONVERSATION_TYPE_MISMATCH |
| 6 | CM_SECURITY_NOT_VALID |
| 8 | CM_SYNC_LVL_NOT_SUPPORTED_PGM |
| 9 | CM_TPN_NOT_RECOGNIZED |
| 10 | CM_TP_NOT_AVAILABLE_NO_RETRY |
| 11 | CM_TP_NOT_AVAILABLE_RETRY |
| 12 | CM_DEALLOCATED_ABEND |
| 13 | CM_DEALLOCATED_NORMAL |
| 14 | CM_PARAMETER_ERROR |
| 15 | CM_PRODUCT_SPECIFIC_ERROR |
| 16 | CM_PROGRAM_ERROR_NO_TRUNC |
| 18 | CM_PROGRAM_ERROR_NO_TRUNC |
| 19 | CM_PROGRAM_ERROR_TRUNC |
| 26 | CM_RESOURCE_FAILURE_NO_RETRY |
| 27 | CM_RESOURCE_FAILURE_RETRY |
| 28 | CM_UNSUCCESSFUL |
The same return values are also written in the system field sy-subrc.
... LENGTH leng
This addition can only be specified in the connection steps SEND and RECEIVE. As a result, the data buffer buffer is only sent or received in the length leng. A data object of data type i is expected for the length specification leng.
... RECEIVED rec
This addition can only be specified in the connection step RECEIVE. The data object rec contains the number of bytes received by the partner program. Only byte-like data objects of length 4 are allowed for rec.
... HOLD
This addition can only be specified using the connection step RECEIVE. It prevents the internal session being changed during the receiving process to avoid the possible loss of the database cursor. In this case, the current work process waits until the data transfer is complete.