Using a CONTINUE command just before another command you think will flush the
job is one way to handle it...another way you could handle this is to use finfo
with a 0 parameter for "EXISTS":

!IF FINFO("FILENAME",0)  THEN
.
.
.
!ENDIF

Jon Temple wrote:

> I have a job stream which I want to close or abort "naturally" if a file is
> no found.  I know if I do a listf on the file in the job, it will abort
> before processing, but  our operations people see that and call someone in
> the middle of the night.
>
> How can I do the lists, the if it can't find the file, then stop processing
> and end the job without getting the "job flushed" stuff.  If it finds the
> file, I would like the job to continue on.
>
> Thanks,
>
> Jon