

Designing Maps › Choosing Menu Maps › User-Defined Menu Maps › Regenerating the System-Defined Menu
Regenerating the System-Defined Menu
When regenerating a menu map with the online mapping facility, the following rules must be observed:
- ADSO-APPLICATION-MENU-RECORD is a required map record. Optionally, the menu can map to additional records, but it must always map to the .hw ADSO--APPLICATION--MENU--RECORD.
- The menu must contain the same number of responses per page as the number of responses for the selected map (that is, 30 for ADSOMUR1, 15 for ADSOMUR2, or 12 for ADSOMSON).
- The AMR-RESPONSE field of the .hw ADSO--APPLICATION--MENU--RECORD record is a required field. The first response name on the map must map to the first occurrence of AMR-RESPONSE. Each subsequent response name must map to the next corresponding occurrence.
- The AMR-USER-ID and AMR-PASSWORD fields of the .hw ADSO--APPLICATION--MENU--RECORD are required on a signon menu map. 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 that are used must be associated with the appropriate fields on the record (for example, heading data must map to AMR-HEADING).
- If using the AMR-KEY field, note that this field appears as a single byte (the AID byte) in the .hw ADSO--APPLICATION--MENU--RECORD. The AMR-KEY field is associated with a code table (ADSOAIDM) that translates the AID byte to more easily readable characters (for example, 1 translates to PF1, percentage translates to PA1).
For more information on using online mapping facility to regenerate a map, refer to CA IDMS Mapping Facility Guide.
Copyright © 2013 CA.
All rights reserved.
 
|
|