Welcome
Know the data descriptions that you want to update.
Select the Don't show this welcome screen again check box to skip this screen in the future.
Click Next to display the next screen.
Select the COBOL Source File
In the Source File box, browse to or type the location of the complete COBOL source file or the data description. The browse option can be used if a Windows share has previously been created. Refer to Procedure 1 (Optional) - Mapping a Drive to the OS 2200 Server.
Select Source File Encoding from the dropdown menu. This specifies the character encoding that is used by the file containing the COBOL source.
Click Next to display the next screen.
Found Data Descriptions
The list of available data descriptions in the COBOL code appears
Select the COBOL data description that needs to be updated in the project.
Click View Source File… to view the source.
Click Next to display the next screen.
Select COBOL Data Identifier
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 OS 2200 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 OS 2200 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 OS 2200 server and does not contain REDEFINES statements, 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 OS 2200 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 OS 2200 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.
Note: You can add data identification fields later or change the data identification fields. Refer to Changing the COBOL Data Identifier.
Warning Screen
This page appears if the server message to be updated contains REDEFINES statements and is either an input/output or an output server message.
Click OK.
After the update process is done, you can, optionally, specify one or more data identification fields. Refer to Changing the COBOL Data Identifier for more information.
Note: If you do not provide a unique identifier, you must use orchestration to specify the server message that ePortal receives. Refer to Using Orchestration to Identify an Output Server Message for more information.
Finish Page
Click OK. The changed OS 2200 application data description is now added to the project.