SCAN Statement

Overview

The SCAN statement should allow Unicode and National field types to be used as both a source and a destination.

Test Plan

1. SCAN a National field from a file into a Raw work field (with/without transcode error) and a Unicode field
2. SCAN a Unicode field from a file into a Raw work field (with/without transcode error) and a National field (with/without transcode error)
3. SCAN a Raw field from a file into a National field (with/without transcode error) and a Unicode field

Bugs

1. SCAN display does not correctly display National characters. * FIXED * 7/27/11 via changes to NSCAN processes. Changed SCANDISP REC to a Label GA.
2. SCAN display does not show any records from a Unicode keyed file * Tested Ok - 3/1/13 *
3. When entering a starting key, display starts one record after the expected value. Run the (VIEW) BEGNAT process, go into key entry, then SCAN. For a starting value, enter Æ. Records will be displayed starting with Ç, which is the next value.* Tested Ok - 3/1/13 *
4. The display does not line up properly. Run any report & scan on the Form field. The data from the Form file does not line up with the headings. * Tested Ok - 3/1/13 *
5. The starting fields displays the Unicode Replacement Glyph for blanks. Same example as above, scan for a form name, and enter PDF as a starting value, it will display as "PDF�?��X" - * FIXED * in Dec 10 engine
6. Unable to scan on field names in ILF editor, (VIEW NSCAN SETUP (FULL) crashes. * Tested Ok - 3/1/13 *