1. RUN with passing a National field causes seg fault if you run it repeatedly. * FIXED* July 4 engine
2. RUN with passing a Unicode field causes strange & inconsistent things to happen if you run it repeatedly. * FIXED* July 4 engine
3. PASSing a unicode field via RUN doesn't seem to work, ie, echo $1 >some.file where $1 was a unicode field containing "This is Uni data\u03a3" does not give the expected result in the file (should contain a Σ symbol). * FIXED* July 4 engine

1. RUN with passing a National field causes seg fault if you run it repeatedly.
   (KAD - should be fixed)
2. RUN with passing a Unicode field causes strange & inconsistent things to happen if you run it repeatedly.
   (KAD - should be fixed)
3. PASSing a unicode field via RUN doesn't seem to work, ie, echo $1 >some.file where $1 was a unicode field containing "This is Uni data\u03a3" does not give the expected result in the file (should contain a Σ symbol).
   (KAD - should be fixed)

1. Implementation difference. The command is always encoded into UTF-8, not the the encoding of the OS shell.
2. RUN with passing a National field causes seg fault if you run it repeatedly.
3. RUN with passing a Unicode field causes strange & inconsistent things to happen if you run it repeatedly.
   

1. RUN with passing any field of any type causes problems (C-asserts, or * glibc detected * free(): invalid next size (normal): 0x09d4ae20 ***g) if you run it twice. Run the RUN subroutine in TST to see the errors.
2. PASSing a unicode field via RUN doesn't seem to work, ie, echo $1 >some.file where $1 was a unicode field containing "This is Uni data\u03a3" does not give the expected result in the file (should contain a Σ symbol).

1. Implementation difference. The command is always encoded into UTF-8, not the the encoding of the OS shell.

1. Test RUN with literals
2. Test RUN with literals & unicode characters (should not transcode)
3. Test RUN with raw field
4. Test RUN with National field
5. Test RUN with Unicode field
6. Test RUN with passing raw field
7. Test RUN with passing National field
8. Test RUN with passing Unicode field
9. Test RUN with passing various combinations of raw, National & Unicode
10. Test --- STREAM OPEN with a pipe (implied RUN)

1. Unable to test 4 - 10 due to bugs in APPEND command. Seem to be limited to 20 characters in a National/Unicode field, so can't construct useful RUN commands.

RUN Statement

Overview

The alpha operand of the RUN statement will be transcoded to the encoding of the OS shell environment before being “executed”.

The RUN statement may optionally have a list of passed values (created by executing PASS statements) that are provided to the shell as arguments when the command is run. All alpha values that are to be passed must be transcoded to the encoding of the OS shell environment before being passed to the shell command.

Command

• RAW Alpha field or Literal value
  • An operand of this type will be transcoded from the 8859-15 encoding to the encoding of the OS shell environment.
  • Unicode escape sequences are NOT honored when executing a RUN command that is entered as a literal value.
• UNICODE Alpha field or NATIONAL Alpha field
  • The characters in the RUN commands referenced alpha field will be transcoded from their UTF-32 internal encoding to the encoding of the OS shell environment.

Arguments

• RAW Alpha field or Literal value
  • Alpha arguments of this type will be transcoded from the 8859-15 encoding to the encoding of the OS shell environment before being passed.
  • Unicode escape sequences are NOT honored when passing an argument that is a literal value.
• UNICODE Alpha field or NATIONAL Alpha field
  • Alpha arguments of this type will be transcoded from their UTF-32 internal encoding to the encoding of the OS shell environment before being passed.

Test Plan

Do each of the encoding types work correctly as the Command string and Argument strings?

Bugs

-- PeteBrower - 2011-03-17