We strongly recommend that all failure recovery actions are logged, even if they do not warrant immediate notification to the responsible person.  Normally, it is simplest to do this from a command file (batch file) initiated by OMACHECK.

Where you write the log file will depend on whether OMACHECK is running on a processing node, on the fileserver, or elsewhere.  Since most processing nodes will have defined a GFAX environment variable, your batch file could include the lines:

cd /D %GFAX%

time /t >>omalog.txt

date /t >>omalog.txt

echo OMA triggered for machine=%1 node=%2 >>omalog.txt

In addition to a local log on the machine running OMACHECK, you may also want to append to a central file, say in FAXFACTS\LOG.  Of course this depends on the CopiaFacts application data area still being visible from the machine running OMACHECK when the failure occurs.

If your command file is run from COPIAFACTS, rather than from OMACHECK, the 'current folder' may be the network folder \\nodename\COPIA\FAXFACTS.  CMD.EXE and COMMAND.COM will not run properly from such a folder, so you must always ensure that your command file either sets a suitable folder or specifies fully-qualified path names.

CopiaFacts can be used to send a e-mail to notify you of a failure.  You can of course copy a pre-written FS file into the TOSEND folder, which will send you an e-mail. But the better method is to run either the EMTO or the EMDIRECT utility, which allows you to add parameters and, if necessary, attachments to the e-mail:

EMTO.EXE steve@copia.com subject="OMA Triggered for %1 %2"

EMDIRECT.EXE c:\tmp\emdirect.ini "machine=%1" "node=%2"

You should of course ensure that the folder containing EMTO or EMDIRECT is on your PATH before adding the above command to your command file.  If not, and if you need to specify a full path in the command file, use (including the double-quotes) "%PROGRAMFILES%\EMTO.EXE" on 32-bit systems, and "%PROGRAMFILES(x86)%\EMTO.EXE" on 64-bit systems.

You can also use an e-mail to SMS service to send you a text message instead of an e-mail, for example:

EMTO.EXE 4255551212@vtext.com subject="OMA Triggered for %1 %2"

EMDIRECT.EXE c:\tmp\emdirect.ini to=6305551212@txt.att.net 

The supplied OMACK.BAT file which is installed in the Program Files\Copia folder includes some of the above examples: This file will need modification before use, to suit your configuration and circumstances.

Note that EMTO operates by writing an FS file into the TOSEND folder, so successful notification depends on there being a CopiaFacts e-mail node still running which is configured for e-mail, and on the ability to see the TOSEND folder on the fileserver. EMDIRECT on the other hand sends an e-mail direct by logging in to your normal e-mail provider's SMTP server.

After setting up notification actions, you should test them by initiating various failure scenarios.

Any issues with notification or OMA triggering can be investigated by running FFTRACE with OMACHECK emabled under File/Applications.