Designing Maps › Choosing Menu Maps › User-Defined Menu Maps › Design a Menu/Dialog

Design a Menu/Dialog

The user has the option of designing and generating an entirely new menu with the online mapping facility. This map must be defined as a menu/dialog function of the application.

To design a menu/dialog function

1. Design and generate the map using the online mapping facility. Observe the following rules when generating the map:
   • ADSO-APPLICATION-MENU-RECORD must be one of the records associated with the map.
   • The AMR-RESPONSE field is required for all menus. The number of required occurrences depends on the number of responses per page (to a maximum of 50) specified on the ADSA Menu Specification screen. The first response name on the map must map to the first occurrence of AMR-RESPONSE; each subsequent occurrence must map to the next corresponding occurrence of AMR-RESPONSE.
   • The AMR-USER-ID and AMR-PASSWORD fields are required for signon maps. The user id data field must map to AMR-USER-ID, and the password data field must map to AMR-PASSWORD.
   • All other fields on the .hw ADSO--APPLICATION--MENU--RECORD are optional. The map data fields used must be associated with the appropriate fields on the record (for example, heading data must map to AMR-HEADING).
2. Add the process source to the dictionary in an IDD session. (The dialog associated with the menu does not have to include any process code, although the choice of a menu/dialog function suggests that some processing is intended.)
3. Compile the dialog in an ADSC session, associating the map and any processes with the dialog using the ADSC Dialog Definition screen. Note that the dialog must be compiled to include the map before the application can be executed at run time.
4. Define the dialog as a menu/dialog function for the application.

An installation can develop standard map templates and the associated boilerplate code for site-specific menu/dialogs. When a menu is needed, programmers can obtain a copy of the template/boilerplate, fill in the appropriate fields and the edit/code tables needed for those fields, and submit it to the data administrator for approval.