Remove the  > $null and let the full text of the error display and you will see
that the first two are CIERR 909 and the third is CIWARN 929.

Warnings don't need a CONTINUE only Errors.

#need CONTINUE here
:LISTF MYFILE
Non-existent file. (CIERR 907)

#don't need it here
:LISTFILE MYFILE
Non-existent MPE named file "MYFILE.PUB.VISTICA". (CIWARN 920)

#don't need it here either
:PURGE MYFILE
       ^
File "MYFILE.PUB.VISTICA" not found.  No purge done. (CIWARN 383)

Sorry, I can't answer the philosophical reason why LISTF reports an Error and
LISTFILE reports a Warning for the same non-existent file. ;-)


Ken Paul wrote:

> Hi,
>
> Does anyone know why the following command file needs a CONTINUE before the
> LISTACCT and LISTF commands but not before the LISTFILE command?  Should the
> LISTFILE command exit the command file like a failed LISTACCT and LISTF
> command if it does not have a CONTINUE?  Is this a bug or a feature?  We are
> on 6.0 PP1.
>
> setjcw cierror 0
> continue
> listacct garbage > $null
> echo !cierror
> setjcw cierror 0
> continue
> listf @[log in to unmask] > $null
> echo !cierror
> setjcw cierror 0
> listfile ./GARBAGE > $null
> echo !cierror
>
> Thanks,
>
> +---------------+
> |               |
> |            r  |  Ken                             [log in to unmask]
> |          e    |                           http://www.adager.com
> |        g      |  Ken Paul                      Tel 208 726-9100
> |      a        |  Customer Support              Fax 208 726-2822
> |    d          |  Adager Corporation
> |  A            |  Sun Valley, Idaho 83353-3000            U.S.A.
> |               |
> +---------------+