We now need to define interface fields to accommodate the returned data. We have already identified and grouped the fields we need on the DEMO92 screen, which simplifies this process a great deal.
Fields that originate as input/output fields are by default created as input fields in their Interface Field equivalents. Therefore, each of these fields is now defined as an input field. However, in this case, we want them to be output fields. We also want to rename each of the fields to something more meaningful. The names we assign here appear as field labels in our generated client.
Now let's turn our attention to the Mappings pane. The Interface Mapper has automatically generated mappings for these two fields. Notice that the Interface Field column shows the fields with an asterisk appended to the end of each field name. The asterisk tells us that these fields each represent an array and that all occurrences of the field are included.
The COBOL Field column shows the field from the originating IMS screen that corresponds to the interface field we've created. Field names in this column are qualified by the group parent name we assigned when we grouped the fields in the Screen Editor, and also have an asterisk in parentheses appended to them. Again, this asterisk tells us that all fields on the originating screen are included.
The Map column shows us the direction that data travels. Here, because we have defined our interface fields as output fields, data moves from the COBOL fields to the interface fields as is represented by the left-pointing arrow.