Please enable JavaScript to view this site.

CopiaFacts™ Reference Manual

The following considerations apply to the Enhanced FS Handling feature:

Locked Rename limitations

Three techniques for locked rename operations may be used, in decreasing order of efficiency:

•a Windows API available only on Windows Vista, Server 2008 and later, both on the active node and the file server holding the COPIA\CALLBACK share.

•a 'copy and delete' operation which may be required when a non-Windows operating system is in use on the file server, for example in a network filesystem.  This can be selected as an override by including the string COPY in the value of $environment variable LRN_OPTIONS for each node.

When testing a non-standard file server you can also include the string CHECKRESULT in the value of $environment variable LRN_OPTIONS for each node.  This ensures that the original file is no longer present and the new file is present after each rename operation.

CLEARACTIVE limitations

The CLEARACTIVE functionality is built in to the COPIAFACTS engine program to recover FS files left in the WORK folder for the node after an abnormal termination of the engine.  This function needs to know to which folder the FS file is to be moved.  Three techniques to determine the destination are in use:

•if the engine has already written the final WORK file but not moved it, the first line of the file will contain a comment which contains the destination pathname.

•if the server filesystem is NTFS, the FS file will have an alternate data stream containing the destination TOSEND queue number.

•otherwise, the $fax_tosend command in the FS if present, will be used to determine the destination folder, and TOSEND will be used if there is no such command.

Free-Channel stack limitations

The stack of free channels is loaded at start-up with the lowest-numbered channel the first to be used. The $channel_priority command is ignored for this operation.

FS MSMQ Limitations

When there are no records available in the node's designated MSMQ, the channels in the node will use the configured non-queue mechanism to find work.

Error Handling and Warnings

The renaming operations and the free-channels stack are subject to extensive checking and any issues will be reported in the trace, and notified by e-mail if the Enhanced FS Processing trigger is set in EMSETUP.