Consistency of Conversation Type

The conversation type you use, designated by the ALLOCATE verb, must be consistent for the entire conversation. You cannot use basic conversation verbs for some requests and mapped conversation verbs for other requests. LU 6.2 rejects the verbs if you change from one type of verb to another within a conversation. A remotely initiated transaction program can issue the GET_TYPE verb to determine the conversation type.

A program can issue only basic conversation verbs for a basic conversation. A program using a mapped conversation can issue either basic or mapped verbs. It must, however, issue verbs of only one format, either basic or mapped.

You can provide your own mapped conversation support using only basic conversation verbs for a conversation designated as mapped. If you choose to provide your own mapped conversation support, your program must conform to the mapped conversation formats and protocols.

See the SNA Format and Protocol Reference Manual: Architecture Logic for LU Type 6.2 and the Systems Network Architecture LU 6.2 Reference: Peer Protocols for more information on mapped conversation formats and protocols.