Gasboy CFN III Manager Manual V3.6 - Manual (Page 205)

MDE-4871 CFN III Manager’s Manual for Windows® XP Embedded - Version 3.6 · August 2010 Page 19-7
Command Files at Sign On Making Your Own Commands
Command Files at Sign On
You can set up a sequence of commands to be executed whenever a user signs on. The
commands can differ, depending on whether you are signing on to the local or remote port.
The command file is R:SIGNON?.CMD, where ? is 1 for local port sign on and 2 for remote
port.
The SIGNON?.CMD file cannot be activated by a user at the console or by a cron file.
How to Save Output from a Command File
Output of a Single Command
For a single command, you can save the output to a file by using the > or >> options. The >
option overwrites any existing file with the specified filename. The >> option appends data
to the end of an existing file with the specified filename.
[P:]* P PU;>PUMP.LST
↵
[P:]*
This example saves the output of the PRINT PUMP command to a file named PUMP.LST.
Output of Several Commands
You can have the output of several commands redirected to a file by using the ENABLE
DUMP or E DU command and specifying a filename. This is mostly used in command files
to have the output of the commands in the file redirected to a file. Use DISABLE DUMP or
DI DU to terminate redirection.
[P:]* TYPE PR_SALES.CMD
↵
ENABLE DUMP SALE_OUT
PRINT SALES
PRINT TOTALS
PRINT PRODUCT
[P:]*
The ENABLE DUMP command normally overwrites the specified file if it exists. With the
A option, the command appends to the specified file, if it already exists.
The >, >>, and < options work when ENABLE DUMP is in effect. They override output
dumping.
The command file in the above example puts the output of the commands PRINT SALES,
PRINT TOTALS, and PRINT PRODUCT in the file SALE_OUT.