#854 rxqueue Does Not Work on Linux

v4.0
closed
nobody
None
5
2012-08-14
2009-11-03
David Ashley
No

Environment:
Fedora Linux 11
ooRexx v4.0 (GA release)

Rxqueue does not work. It does not matter what command line options you specify, nothing is ever queued.

Additionally, the following command line raises an error.
rexx -v > rxqueue myqueue
The error is
REX0003E: Error 3: Failure during initialization
REX0534E: Error 3.901: Failure during initialization: Program "myqueue" was not found

The error is not raised when you replace the ">" redirection operator with the "|" operator.

Discussion

  • Rick McGuire
    Rick McGuire
    2009-11-04

    rxqueue definitely is working on linus, there are even unit tests for it. It will not work with the > redirection symbol....pipe stages require the "\" to work.

     
  • Mark Miesfeld
    Mark Miesfeld
    2010-08-10

    David, I'm closing this as invalid.

    Rxqueue works on Linux with a build from trunk. This program produces the expected output when using the rexx -v | rxqueue form, on both Windows and Linux:

    queue_name = rxqueue("Create", "myqueue")
    say 'queue_name:' queue_name

    qObj = .RexxQueue~new(queue_name)
    --"rexx -v > rxqueue myqueue"
    "rexx -v | rxqueue myqueue"
    say 'lines' queue_name qObj~queued
    say
    do while qObj~queued > 0
    say qObj~linein
    end

    ret = rxqueue("delete", queue_name)
    say
    say 'delete' queue_name 'ret:' ret

    The ">" symbol writes the stdout from the process on the left of the symbol to the file (or device) on the right of the symbol. Therefore, the expected output of:

    rexx -v > rxqueue myqueue

    would be a file named rxqueue containing the output of rexx -v. This is what I get on both Windows and Linux.

    This error:

    rexx -v > rxqueue myqueue
    The error is
    REX0003E: Error 3: Failure during initialization
    REX0534E: Error 3.901: Failure during initialization: Program "myqueue" was not found

    comes from, if I remember correctly, an old bug where if the -v arg was specified with a following argument, the interpreter printed the version and then executed the following arg as a Rexx program. That bug has been fixed.

     


Anonymous


Cancel   Add attachments