Unknown conversation ID
An unknown conversation ID is most likely to occur because the ID is specified incorrectly.
Alternatively this problem could be caused by the task that issued
the
command not owning the conversation, because:
- The conversation has been ended
- The conversation has been passed to another task
- FEPI ALLOCATE with PASSCONVID has not been issued.
If the error occurs on a FEPI ALLOCATE command with PASSCONVID, the conversation was probably not “unowned”. Where the CONVID was obtained from FEPI start data, it is possible that between FEPI scheduling the task and it starting, a resource used by the conversation has been discarded, or CICS has started shutdown.