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...

NON-EXPERT OPINION. Your program is making extensive use of the HALT condition. To get your program to produce some output you type a Control-C, which your program traps. The Control-C is the same as the OS sending a SIGINT, which is what happens when you close a window. (Actually I think it is a SIGHUP, but is treated by Rexx as SIGINT.) So I think the program is doing what your are requesting it todo, that is ignoring SIGINT requests. Or more accurately, choosing to handle them rather than taking...

Unable to reproduce on Mac OS 10.12.6 (Sierra). I downloaded and built a fresh copy from the svn repository, and then ran the command 'rexxcps.rexx 1000 1000' while monitoring in Activity Monitor. When I closed the window, and confirmed terminate the running rexx process immediately disappeared from the monitor. Plesase submit a sample program that reproduces the problem.

Unable to reproduce on 32bit Linux.

Let see if I can do better explaining this. It doesn’t matter what shell you use as your terminal shell, or which shell the OS sets up for you when you define a new user. We aren’t talking about terminal shells, we are talking about shells that are invoked in a non-terminal environment. In that case the UNIX specification which binds the actions of SUN Solaris, IBM AIX, and MacOS, is to invoke the shell named ’sh’. For example here is the POSIX definition of the system() function. The system() function...

It turns out that bash does the same thing as ksh when invoked via /bin/sh, it enters POSIX mode.

So I've done a little more reading. POSIX defines as the default system shell, a strict subset of Korn Shell. I'm guessing that this is the subset that most closely aligns with the original Bourne Shell. This is why ksh has different functionality if it is invoked as /bin/sh or /bin/ksh. Ubuntu has two default system shells. I believe that if you type /bin/sh you get dash, while the default terminal shell is indeed bash. On my Mac 10.10.5 the default system shell /bin/sh reports itself as GNUBash....

So I've done a little more reading. POSIX defines as the default system shell, a strict subset of Korn Shell. I'm guessing that this is the subset that most closely aligns with the original Bourne Shell. This is why ksh has different functionality if it is invoked as /bin/sh or /bin/ksh. Ubuntu has two default system shells. I believe that if you type /bin/sh you get dash, while the default terminal shell is indeed bash. On my Mac 10.10.5 the default system shell /bin/sh reports itself as GNUBash....