I have a request from an operator to have a job "Stand up and dance" for
various abnormal conditions.
(File length = 0, or ftp failure) etc.
I put in a STOPJOB non-command and it fails accordingly. However,
STOPJOB reads as an UNKNOWN COMMAND and this tends to be "interpreted"
by the operators as a problem with the JOB and not a problem with DATA
or  FTP or whatever.  LIKE THIS:

:
:IF FTPLASTERR <> 0
*** EXPRESSION TRUE
:   TELL MGR.AIHWORK !HPJOBNAME Did not receive data . . . job ended.
:   TELL MGR.AIHWORK !HPJOBNAME Try job again.
:   STOPJOB
Unknown command name. (CIERR 975)
REMAINDER OF JOB FLUSHED.

Question: Is there a "real" command that will give a flush the job
accordingly(giving warning, etc.) and give a more descriptive response.

(Remember, even though the TELL Message PLAINLY states WHY the job
ended, If the operators aren't told in the last 2 lines that the job
ended because of an FTP error, they interpret it as a programming error
and call some poor working stiff in the middle of the night.  TELLOP is
equally ignored)
Scott Gates
Contract Programmer
Trigon BC/BS of VA
804-354-7625
MPE/iX HP31900 C.05.08 r: C.55.00
SUPRTOOL/iX/(Version 4.1.04 VAR)
PH 7.29.C6 -- AMISYS v9.4