Format of the correlation token for synchronous callout messages from IMS applications
The output messages from the IMS Connect message exit for synchronous callout requests include a correlation token to correlate the reply to the callout request with the IMS application that issued the request.
The correlation token is the first structure in a synchronous callout request and can be followed by the optional request mod message (RMM) structure and the application data.
The following table shows the structure of the correlation token on output from IMS Connect, as mapped by the CORMask DSECT in the HWSIMSCB macro:
| Field | Length | Meaning |
|---|---|---|
| COR_Len | 2 bytes | Length of correlation structure, including the structure header and the correlation token |
| COR_Rsvd | 2 bytes | Reserved (set to binary zeros) |
| COR_Id | 8 bytes | Character value of *CORTKN* |
| COR_LL | 2 bytes | Length of the correlation token |
| COR_PSTNR | 2 bytes | Region ID for the synchronous callout message |
| COR_IMSID | 4 bytes | ID of the IMS system in which the IMS application program that issued the callout request is running |
| COR_MEMTK | 8 bytes | OTMA TMEMBER token |
| COR_AWETK | 8 bytes | OTMA message token |
| COR_TPIPE | 8 bytes | OTMA Tpipe name |
| COR_USERID | 8 bytes | User ID included in the ICAL call by the IMS application that issued the callout request |