Issue a positive response to a SEND CONFIRM on an APPC mapped conversation.
ISSUE CONFIRMATION (APPC)
>>-ISSUE CONFIRMATION--+--------------+--+-------------+-------><
'-CONVID(name)-' '-STATE(cvda)-'
Conditions:
INVREQ,
NOTALLOC,
SIGNAL,
TERMERR
Description
ISSUE CONFIRMATION allows an application program to respond positively
when the CONFIRM option has been specified on a SEND command executed by a
partner transaction.
Options
- CONVID(name)
- identifies the conversation in which to send the response. The 4-character
name identifies either the token returned by a previously executed ALLOCATE
command in EIBRSRCE in the EIB, or the token representing the principal facility
(returned by a previously executed ASSIGN command).
For compatibility with
earlier releases, SESSION is accepted as a synonym for CONVID. New programs
should use CONVID.
If both CONVID and SESSION are omitted, the principal
facility is assumed.
- STATE(cvda)
- gets the state of the current conversation. The cvda values returned
by CICS® are:
- ALLOCATED
- CONFFREE
- CONFRECEIVE
- CONFSEND
- FREE
- PENDFREE
- PENDRECEIVE
- RECEIVE
- ROLLBACK
- SEND
- SYNCFREE
- SYNCRECEIVE
- SYNCSEND
Conditions
- 16 INVREQ
- RESP2 values:
- 200
- A distributed program link server application specified the function-shipping
session on the CONVID option.
also occurs (RESP2 not set) in any of the following situations:
- ISSUE CONFIRMATION is used on a conversation that is either of the following:
- Sync level 0
- Not APPC mapped
Default action: terminate the task abnormally.
- 61 NOTALLOC
- occurs if the specified CONVID value relates to a conversation that
is not owned by the application.
Default action: terminate the task
abnormally.
- 24 SIGNAL
- occurs when an inbound SIGNAL data-flow control command is received
from a partner transaction. EIBSIG is always set when an inbound signal is
received.
Default action: ignore the condition.
- 81 TERMERR
- occurs for a session-related error. Any action on that conversation
other than a FREE causes an ATCV abend.
A CANCEL TASK request by a user
node error program (NEP) may cause this condition if the task has an outstanding
terminal control request active when the node abnormal condition program handles
the session error.
Default action: terminate the task abnormally
with abend code ATNI.