On Nov 21,  7:33am, Michael Berkowitz wrote:
...
> Be aware that there
> are some new problems with this patch.  For example, if you do a listf,8
> or 9 on a file that you lack permission to see the accessors you will get
> CIWARN 194.  A bug causes this and some other warnings from listf to
> get and END OF FILE (FSERR 0) on the list file (CIERR 425) and cause a
> job to flush if there is no CONTINUE in front of the listf.  This is
addressed
> in SR 5003-397489.  Also listf, anymode may get a new "lockcontention
> warning" and not show on the listf.  This error has nothing to do with
> anyone using the file, so the "lock" is misleading.  It also sets a warning
> that causes FSERR 0, CIERR 425, and a job to blow.  It is addressed in
> SR 5003-394221.

The lock contention warning is CIWARN 9169 and is a result of changes made to
LISTF and LISTFILE to not wait infinitly for certain file system (internal)
semaphores.  This affects all formats except 0 and 6.  Also, my understanding
is that you need a reasonable file system load to encounter this problem.
I will begin fixing these problems next week and they will (hopefully) be
accepted into 6.0 and be available as a 5.5 patch.

Regards,
Jeff Vance, CSY

--