Problem

--CFT commands stay in the com file

--One or more commands is never executed by the monitor

Resolution

*set UCONF variable cft.server.com.rescan.enable to yes

*check CFTCOM WSCAN and UCONF cft.server.com.rescan.wscan_factor

Explanation:

When an issue occurs on a system or if the monitor is forced kill, you can get a command registered without the 'next to read' command indicator updated in the header.

Above UCONF variables ensure we are rescanning the com file on a regular basis to automatically fix that condition.

These variables allow CFT to re-compute 'the next to read' command indicator in the com file header each (CFTCOM WSCAN) x (cft.server.com.rescan.wscan_factor) AND when no new activity is detected, no new command enterred.

Attention, it fixes one issue at a time, it may take long to fix many holes and/or unread commands laying in the com file.

--important note:

When issue is reported without being related to a side issue on the system, it has been proven in ALL cases reported so far that it is related to the bad management of file locks (ENQs) and directly related to the File System and mount options used when open systems or, on z/OS systems, the fact that QNAME CFTSHARE has not been propagated on all GRS rings..

All write operations to the communication file MUST be serialized and the mandatory serialization rely on the system ENQ or lock on the file.