Environment "name" failed on the command "command"

Synopsis
An environment (ie, Subcom Handler) named name triggered an ERROR or FAILURE condition after it was passed command.

You can explicitly send a command to an environment with the ADDRESS instruction. But also anything that Reginald doesn't recognize as a REXX instruction, Reginald automatically sends to the current environment (set with the ADDRESS instruction) as command (unless you use ADDRESS NULL).

Cause
You misspelled some REXX instruction or subroutine name, resulting in something that Reginald doesn't recognize as either an instruction or subroutine call. So, Reginald passed it off to the current environment as the command to process. That environment raised the ERROR or FAILURE (for some reason) upon receiving this.

Cure
Be sure that you use only legal REXX instructions, and reference only subroutines that exist in your program or as REXX scripts on disk somewhere.

Cause
You didn't want to do anything with the return value from a function, but you forget to use the CALL keyword. Therefore, Reginald passed the function's return data to the current environment as command. That environment raised the ERROR or FAILURE (for some reason) upon receiving this.

Cure
If you wish to "throw away" the data return from a function, use the CALL keyword. Here, we throw away the return of my_func: \par

CALL my_func
Otherwise, Reginald would send my_func()'s returned data to the current environment as its command to process.

Alternately, you can use the instruction ADDRESS NULL to automatically toss away any returns that you don't use from functions, without needing to otherwise use CALL. Reginald's Administration Tool also allows setting this for all scripts you run. (But be sure that no scripts you run will assume their commands are automatically directed to the operating system shell, if you utilize the Administration Tool's setting).