Use the TPPCC general macro with the PREPARE_TO_RECEIVE verb specified to
change the conversation from send to receive state in
preparation to receive data. The change to receive state is
completed as part of this verb. The execution of this verb includes the
function of the FLUSH or CONFIRM verb.
Format
- label
- A symbolic name can be assigned to the macro statement.
- PREPARE_TO_RECEIVE
- Directs the TPPCC macro to perform the PREPARE_TO_RECEIVE verb
function.
- RESID
- Specifies the symbolic name of a field or a register pointing to a
field. This is a 4-byte field in which the resource ID is
supplied. This resource ID must be the one assigned on the initial
ALLOCATE for this conversation or one that was assigned by an incoming
ATTACH.
- TYPE
- Specifies the type of PREPARE_TO_RECEIVE to be done on this
conversation. The allowed values are:
- CONFIRM
- Performs the function of the CONFIRM verb. When the
PREPARE_TO_RECEIVE request completes successfully, the conversation enters
receive state.
- FLUSH
- Performs the function of the FLUSH verb. When the
PREPARE_TO_RECEIVE request completes successfully, the conversation enters
receive state.
- SYNC
- Performs the function of the FLUSH verb or the CONFIRM verb based on the
synchronization level of the conversation. If the synchronization level
is NONE, a FLUSH is performed. If the synchronization level is CONFIRM,
a CONFIRM is performed.
- LOCKS
- SHORT is the only allowed value. This parameter has meaning only
when the CONFIRM option is used on TYPE and causes control to be returned only
after the confirmation reply has been received. TPF does not support
the LONG option defined by the LU 6.2 architecture.
- RCODE
- Specifies the symbolic name of a field or a register pointing to a
field. This is a 6-byte field in which the return code is
placed. The return code consists of a 2-byte primary return code
followed by a 4-byte secondary return code. The actual values returned
are listed in Return Conditions.
Entry Requirements
- The conversation must be in send state.
- See Entry Requirements for the entry requirements relating to the TPPCC macro in
general.
Return Conditions
- The results of the verb are indicated by the value returned in
RCODE. The valid return codes are listed in the following section,
"Return Codes".
- See Return Conditions for the return conditions relating to the TPPCC macro in
general.
- The following table contains a list of the primary and secondary return
codes that can be returned to the program that issued the PREPARE_TO_RECEIVE
verb. A complete list of return codes and their definitions can be
found in Table 11 and in Table 12.
Symbolic Name
| Primary Code
| Secondary Code
|
LU62RC_OK
| 0000
|
|
LU62RC_PARAMETER_CHECK
| 0001
|
|
LU62RC_PK_BAD_TCBID
| ....
| 00000001
|
LU62RC_PK_BAD_CONVID
| ....
| 00000002
|
LU62RC_PKPTRCV_INVTYPE
| ....
| 000000A1
|
LU62RC_STATE_CHECK
| 0002
|
|
LU62RC_SKPTRCV_BADSTATE
| ....
| 000000A3
|
LU62RC_ALLOC_ERROR
| 0003
|
|
LU62RC_TP_NOT_AVAIL_RETRY
| ....
| 084B6031
|
LU62RC_TP_NOT_AVAIL_NO_RETRY
| ....
| 084C0000
|
LU62RC_TPN_NOT_RECOGNIZED
| ....
| 10086021
|
LU62RC_PIP_NOT_SPECIFIED_CORRECTLY
| ....
| 10086032
|
LU62RC_CONV_TYPE_MISMATCH
| ....
| 10086034
|
LU62RC_SYNLVL_NOTSUPORT
| ....
| 10086041
|
LU62RC_DLLOC_ABEND_PGM
| 0006
|
|
LU62RC_DLLOC_ABEND_SVC
| 0007
|
|
LU62RC_DLLOC_ABEND_TMR
| 0008
|
|
LU62RC_PGMERR_PURGING
| 000E
|
|
LU62RC_CONVFAIL_RETRY
| 000F
|
|
LU62RC_CONVFAIL_NORETRY
| 0010
|
|
LU62RC_SVCERR_PURGING
| 0013
|
|
LU62RC_TPF_ABEND
| FFFF
|
|
Programming Considerations
- If you specify a register for a keyword value, the register must be
enclosed in parentheses and in the range R1-R7.
- The value supplied in RESID must be the resource ID returned by the
ALLOCATE verb or one that was assigned by an incoming ATTACH.
- If TYPE=CONFIRM is specified, TPF's EVENT and POST facility is used
to suspend the ECB until the program receives the confirmation reply.
Since the ECB is suspended, all unnecessary resources should be released
before this verb is issued. Failure to do so can cause serious system
degradation.
- Note:
- You can avoid the problem of suspended ECBs by using the
ACTIVATE_ON_CONFIRMATION verb instead of PREPARE_TO_RECEIVE. See TPPCC ACTIVATE_ON_CONFIRMATION for more information.
- If the program does not receive a confirmation reply within a certain
amount of time, the TPF/APPC support issues a DEALLOCATE TYPE=ABEND to
terminate the conversation. The amount of time that the system waits is
determined by the value you specify for the TPRECV parameter on the SNAKEY
macro. See TPF ACF/SNA Network Generation for
information about the SNAKEY macro.
- This verb can be issued only when the conversation is in send
state. Upon successful completion of this verb, the conversation is in
receive state.
- The remote transaction program enters the corresponding send
state when it receives the SEND indication in the WHAT_RECEIVED (WHATRCV)
parameter (refer to TPPCC RECEIVE). The remote transaction program can then send data
to the local TPF transaction program.
- See Programming Considerations for the programming considerations relating to the TPPCC
macro in general.
Examples
SYMB100 TPPCC PREPARE_TO_RECEIVE, X
RESID=EBW004, X
TYPE=SYNC, X
LOCKS=SHORT, X
RCODE=(R5)