Automatic Editing and Error Handling › Automatic Editing at Runtime › Mapin Operations › Automatic Editing on Mapin for Pageable Maps

Automatic Editing on Mapin for Pageable Maps

Automatic editing on mapin occurs as soon as the GET DETAIL statement in the process code is initiated. The code must check automatic editing for the results. The previous illustrated procedure is implemented however, it takes place after the GET DETAIL statement is encountered in the process code.

Additionally, automatic editing error messages found on input (mapin - after the GET DETAIL statement has been issued) are immediately moved into the message buffer area and cannot be suppressed.

How the Online Compiler Responds to Errors

If input is found to be in error during editing, the online compiler responds as follows:

1. The field is identified as being in error.
2. Automatic editing ends for the field.
3. Automatic editing either continues with the next appropriate field on the map or relinquishes control to the program that requested the mapin, as described:
   • If there is another data field on the map to be edited, editing begins for that field.
   • If there are no more fields on the map to be edited, control returns to the CA ADS dialog or the application program:
     • Control returns to the CA ADS dialog that requested the mapin, as instructed by the EXECUTE ON EDIT ERRORS specification for the dialog.

       If EXECUTE ON EDIT ERRORS is YES, control passes to the appropriate response process.

       If EXECUTE ON EDIT ERRORS is NO, control does not pass to the response process until the operator either corrects all input errors detected by automatic editing or terminates the dialog.

     • Control returns to the application program that requested the mapin.

     Note: For more information about how dialogs and programs respond to input errors in maps, see Error Handling at Runtime.

Considerations

The following considerations apply to runtime automatic editing:

• Automatic editing does not evaluate data in a response field
• Only data fields for which the MDT is set on are transmitted to program variable storage. The MDT can be set:
  • If the operator has entered a value in the field
  • If the program has been modified
  • If the MDT option was specified for the field at map definition
• Input must be supplied in a required field; failure to supply input constitutes an input error
• Input does not have to be supplied in a field that is not a required field

Determining if a Field is Changed or Erased

Map inquiry statements issued by the CA ADS dialog or application program that uses the map determine that data is changed or erased when the ERASE EOF key is pressed:

• A field is identified as changed when ERASE EOF erases the contents of the field in either of the following cases:
  • A pad character is defined for an alphanumeric field
  • ZEROED WHEN NULL is specified for a numeric field
• A field is identified as erased when ERASE EOF is pressed for the field while the cursor is at the first position of an alphanumeric field for which no pad character is defined.