#1547 RXQUEUE() issues

[Erich]

I'm seeing a few issues with builtin-function RXQUEUE()

rxqueue("exists", "session") always returns 0, but should return 1

rxqueue("create", "SESSION") returns the nullstring, but for consistency should return a new unique name

If name doesn't yet exist, rxqueue("create", name) returns name in original casing, but for consistency should return it in uppercase

rxqueue('open', 'SESSION') returns undocumented 1, whereas
rxqueue('open', name) with any other name always returns 0, giving no indication whether name had already existed or was just created with this call.

rxqueue() accepts queue names up to 249 chars, but should accept up to 250 chars as documented

[Bruce]

when using the rxqueue program (/usr/bin/rxqueue) the following error messages are returned.

REX121: Storage for data queues is exhausted.
This message is misleading in that it appears when the rxapi daemon isn't started.

REX124: The queue MYQ does not exist.
It doesn't seem to matter if the queue name is specified in the command line, i.e. 'ls | rxqueue MYQ /LIFO" or if the queue name is in an environmental variable, i.e. export RXQUEUE=MYQ. All options, /LIFO /FIFO /CLEAR return the same error message.

This was on Raspbian/Debian Stretch V9.6, Linux Kernel version 4.14.50-v7+ , SVN Revision Number is 11521

[Erich]

REX124: The queue MYQ does not exist.
Bruce, you will need to create the external queue first, like e. g.

rexx -e "call rxqueue 'O', 'MYQ'; 'ls | rxqueue MYQ /LIFO'"

[Erich]

Committed revision [r11622]
Adds tests for RXQUEUE built-in function
Tests for some issues reported above are suppressed during normal operation.
Run with higher verbosity (-V) to display:
-V 3 will display known-bug statistics only,
-V 7 will make suppressed tests fail

[Rick McGuire]

Code committed [r11624]
Suppressed test cases removed in [r11625]