Skip to content

ABAP Keyword Documentation →  ABAP - Reference →  Obsolete Language Elements →  Obsolete data and communication interfaces →  CPI-C Interface →  COMMUNICATION 

COMMUNICATION - cpic_options

Short Reference

Other versions: 7.31 | 7.40 | 7.54

Obsolete Syntax

... [RETURNCODE rc]
    [LENGTH leng]
    [RECEIVED rec]
    [HOLD] ...

Extras

1. ... RETURNCODE  rc

2. ... LENGTH leng

3. ... RECEIVED rec
4. ... HOLD

Effect

Additional additions for the statement COMMUNICATION.

Addition 1

... RETURNCODE  rc

Effect

This addition can be specified for any communication steps and receives the return code in rc. rc expects the data type i. The meaning of the return codes is encoded 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 codes.

rc Data Object from 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 codes are also written to the system field sy-subrc.

Addition 2

... LENGTH leng

Effect

This addition can only be specified in the communication steps SEND and RECEIVE. As a result, the data buffer buffer is only sent or received in the length leng. The length leng expects a data object of the data type i.

Addition 3

... RECEIVED rec

Effect

This addition can only be specified for the communication 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.

Addition 4

... HOLD

Effect

This addition can only be specified for the communication step RECEIVE. It prevents the internal session being changed when receiving data to avoid the possible loss of the database cursor. In this case, the current work process waits until all data has been received.