Note: This page only appears if the HostApplicationUse property value of the associated server message is output or input/output.
Each COBOL data description that is received from the MCP application (an output or input/output description) can optionally have a unique text string. This unique string is used at run time to identify the data being received from the MCP server. Refer to Planning the Data Identification Strategy.
For instance, if the COBOL data description has a field with the value DEPOSIT and the text string is unique among all the COBOL data descriptions of the project, selecting just this field is acceptable. However, if other data descriptions of the project also have a field with the value DEPOSIT and such a field is selected as a data identifier, then a second or even a third field of the data description needs to be selected to differentiate this data description from the other data descriptions.
If the data description is received from the MCP server and does not contain REDEFINES statements, you can either manually define a unique identifier, or use orchestration to identify the server message as follows:
Manually Defining a Unique Identifier
Check the box next to Select a Field or Fields to Uniquely Identify this Data Description (optional).
Select a field containing text that is unique to the entire project or that combined with another field of the data description creates a unique set of data values for the data being received from the MCP server.
Click Select. The field and its value appear in the Selected Fields box.
If you need more than one text string for this data description in order to create a unique text string for the data being received from the MCP server, repeat steps 2 and 3.
To modify a data identifier, select the field in the Selected Fields box, click Modify, and make the modification.
To remove a field, select the field in the Selected Fields box, and click Remove.
Click Next.
Using Orchestration
If an output data description does not contain a unique identifier, and it is impractical to add one as described above, then you can elect not to provide an identifier when you import the data description. If you do not provide a unique identifier, you must use orchestration to identify the server message that you expect ePortal to receive. Refer to Using Orchestration to Identify an Output Server Message for more information.
To skip defining a unique identifier, uncheck the Select a Field or Fields to Uniquely Define this Data Description (optional) check box.
Note: You can add data identification fields later, or change the data identification fields. Refer to Changing the COBOL Data Identifier.