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 runtime to identify the data being received from the MCP server. Refer to Planning the Data Identification Strategy in Preparing To Use the MCP COBOL Data Source Wizard.
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 necessary, indicate whether the data is sent to or received from the MCP server by selecting one of the following from the Server Message Direction list.
| Selection | Description |
|---|---|
| Input sent to MCP Server | Indicates that data is sent to Transaction Server on the MCP server. The MCP COBOL application issues a Transaction Server RECEIVE statement into the data area that matches the server message and COBOL record image just added to the data source project. |
| Output received from MCP Server | Indicates that data is received from Transaction Server. The unique identifier chosen is used to correctly identify the data stream to the saved record. The COBOL application issues a Transaction Server SEND statement of the data description just added to the data source project. |
| Both Input and Output | Indicates that data is expected to be sent to or received from Transaction Server. |
Identifying the Server Output Data
If the data is received from Transaction Server, you can either manually define the unique identifier, or use orchestration. Perform one of the following procedures to identify the server message:
Manually Defining a Unique Identifier
Define a unique identifier for a server message as follows:
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.
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, and click Next.
After you identify the server output data, perform the following steps:
If more data descriptions need to be added during this session, select Select another COBOL data description to add to the project? check box.
Click Finish.
Note: You can add data identification fields later or change the data identification fields. Refer to Changing the COBOL Data Identifier.