Asynchronous output delivery
When creating a message destined for an LU 6.2 application program, IMS establishes conversation characteristics.
- LU 6.2 descriptor
- DL/I Change call option list
- DFSAPPC message switch options
If IMS cannot extract a particular
conversation characteristic from this list, IMS uses the defaults that are shown in the following
table. If a side table name is extracted, the default mode name is
not used. IMS assumes that side
table entries contain a mode table entry name. If an /ALLOCATE command
for a particular LUNAME - TPNAME destination specifies
a mode table entry name, that entry name overrides the mode table
name specified for the message.
IMS uses the information in the following table to initiate a conversation with the LU 6.2 application program that is associated with the alternate PCB. Certain fields, such as LU name, are application specific. Default values are provided but can be overridden by parameters associated with the message. A default value is used by IMS only if no value is provided by any other source. The application program can modify the default conversation characteristics using an expanded interface to the DL/I CHNG call.
| Characteristics | Default value |
|---|---|
| Conversation_Type | Mapped |
| Deallocate_Type | Deallocate_Sync_Level |
| Error_Direction | Receive_Error |
| Fill | Fill_LL |
| Log_Data | Null |
| Log_Data_Length | 0 |
| Mode_Name | 'DFSMODE' IMS uses the same mode name provided by the inputting LU 6.2 partner to allocate the outbound conversation. That is, whatever mode name the inputting conversation uses, IMS also uses it for outbound allocates. |
| Mode_Name_Length | 7 |
| Partner_LU_Name | 'DFSLU' |
| Partner_LU_Name_Length | 5 |
| Prepare_to_receive_type | Prep_To_Receive_Sync_Level |
| Receive_type | Receive_and_Wait |
| Return_Control | When_Session_Allocated |
| Send_Type | Buffer_Data |
| Sync_Level | Confirm |
| TP_Name | 'DFSASYNC' |
| TP_Name_Length | 8 |