Using Batch Mode 157
Batch mode processing can run in either stop mode (the default) or
non-stop mode (the user-MAC command line includes the --non-stop
qualifier). For both modes, during the initial parse, the input file is
validated for format but not for content validity. If the parse encounters a
formatting error (for example, an angle bracket (>) is missing in an XML
file), processing stops.
■In stop mode, if an error is found after the initial parse is complete,
processing stops.
■In non-stop mode, if an error is found after the initial parse is
complete, the offending transaction is dumped, but processing
continues to the next transaction in the file.
Console output provides a running indication of progress and an action
summary on completion.
Command processing generates two log files, whose names and
locations are displayed on your console. One file contains a summary of
command actions. The second file contains debug information that is
useful if processing fails. If the log files cannot be created, command
processing halts. See Files and Directories for location information.
Managing User
Accounts with an
XML File
You can use an XML file as input to the user-MAC command. Transactions
in the file can add, modify, or delete user accounts. 3Com Corporation
recommends that an XML file contain no more than 5000 transactions.
While this is not a hard limit, exceeding 5000 transactions may cause
performance issues.
Use the following syntax to specify an XML file as input to the user-MAC
command (and get the return code displayed on your console):
./user-MAC –-xml InputFileName.xml --non-stop; echo “RET:$?”
The XML support files are located in the /opt/3com/VCX/vcxdata/conf
directory, and are described in subsequent sections.
XML Input File DTD
The DTD file that specifies XML format for user-MAC command input is
named user-MAC-transactions.dtd and has the following structure:
<!ELEMENT user-MAC-transactions (transaction+) >
<!ELEMENT transaction (
uname,
phone?,