Return codes for the Subcommand Interface are as follows:
────────────────────────────────────────────────────────────────────────
0x01 RXSUBCOM_ERROR An error in subcommand processing
has occurred; the interpreter raises
an ERROR condition.
──────────────────────────────────────────────────────────────────────
0x02 RXSUBCOM_FAILURE A failure in subcommand processing
has occurred; the interpreter raises
a FAILURE condition.
──────────────────────────────────────────────────────────────────────
0 RXSUBCOM_OK A subcommand has executed
successfully.
──────────────────────────────────────────────────────────────────────
10 REXSUBCOM_DUP A duplicate handler name has been
successfully registered. There is
either an EXE handler with the same
name registered in another process,
or a DLL handler with the same name
registered in another DLL. (To
address this subcommand you must
specify its library name.)
──────────────────────────────────────────────────────────────────────
30 RXSUBCOM_NOTREG Registration was unsuccessful due to
duplicate handler and dynalink names
(RexxRegisterSubcomExe or
RexxRegisterSubcomDll); the
subroutine environment is not
registered (other REXX subcommand
functions).
──────────────────────────────────────────────────────────────────────
40 RXSUBCOM_NOCANDROP The subcommand handler has been
registered as "not droppable."
──────────────────────────────────────────────────────────────────────
50 RXSUBCOM_LOADERR An error has occurred while loading
a dynalink library; most commonly, a
missing dynalink library file causes
the error.
──────────────────────────────────────────────────────────────────────
1002 RXSUBCOM_NOEMEM There is insufficient memory to
complete this request.
────────────────────────────────────────────────────────────────────────