The Dsl folder

This section describes the structure and elements of the Dsl folder of an FTM SWIFT message. The Dsl folder is a subfolder of the ComIbmDni folder. Its MERVAFieldList folder contains data that was retrieved from or is to be stored into the system fields or user-defined fields, but not the SWIFT fields, of a MERVA ESA message:

• When the MERVA Bridge passes a MERVA ESA message to FTM SWIFT, it can copy data from the system fields or user-defined fields of the message and place it into the MERVAFieldList folder of the corresponding FTM SWIFT message.
• When the MERVA Bridge passes an FTM SWIFT message to MERVA ESA, it can copy data from the MERVAFieldList folder and place it into the system fields or user-defined fields of the corresponding MERVA ESA message, which is located in a structure called the TOF.

The action taken by the MERVA Bridge depends on the setting of the SYSFLDS parameter of the DSLKPROC process that is used:

• If SYSFLDS=YES or SYSFLDS=UMR is specified for the DSLKPROC send process that passes a MERVA ESA message to FTM SWIFT, the MERVA Bridge creates a MERVAFieldList folder for that message.
• If SYSFLDS=YES is specified for the DSLKPROC receive process that passes an FTM SWIFT message to MERVA ESA, the MERVA Bridge copies the contents of the MERVAFieldList folder to the TOF for that message.
• Otherwise, the MERVA Bridge does not create or process a MERVAFieldList folder for a message.

Examples of ways in which the contents of the MERVAFieldList folder can be used:

• For messages passed from MERVA ESA to FTM SWIFT (ISN messages), to record MERVA ESA processing data and thereby influence how FTM SWIFT routing flows process messages received from MERVA ESA
• For messages passed from FTM SWIFT to MERVA ESA (OSN messages or responses to ISN messages), to record FTM SWIFT processing data and thereby influence MERVA ESA routing