Return codes
Note that currently, Mosaic Rexx commands are soft about their
arguments. If you specify an argument that isn't used for the
specific command you issued (i.e. you get an
item that doesn't need a stem, but provide one), it will
return 0. This may all change later, will will probaly change other
things as well.
Mosaic Rexx commands return one of the following values:
- 0
- Indicates that the command completed successfully.
- 1
- Indicates that the command completed successfully, but there is
some condition that might be of interest.
- 5
- Indicates that the command was valid, but could not be completed
for some reason. Usually, this is a request for something that doesn't
exist.
- 10
- The command is unknown, or unsupported on this version of the
operating system.
- 15
- The arguments were invalid. However, see the note.
- 20
- The command does not exist, is not implemented, or is not
supported under this version of the operating system. However, see
the note.
MUI does the first phase of the command parsing, and
there really isn't any way to avoid that. It's return codes are
undocumented, and seem to vary from invocation to invocation. If you
see a return code other than the ones in this document, you can assume
the command was erroneous some way, and that MUI caught it. Likewise,
any non-zero return code may be MUI catching an error of some kind and
returning that value.
Up to the manual, on to examples, or back to objects.
Mike W. Meyer