Command-Line Options

The following table lists the command options available to you when you run Enterprise Server as a command prompt program.

Note: Some features are only available through the command-line interface.




Runs Enterprise Server in interactive mode as a Windows dialog box.

CACHE sourcename

[PASSWORD [ = ] "password"]

[ startafn [[ - ] endafn | + ] ]

If caching is enabled for the base source, writes the updates from all DMSII audit files for this base source to local disk drives. If local sources are configured, the filtered updates from each audit file are also saved.

The PASSWORD option specifies the password to be used when accessing the remote source. The password must match the KEY option in the DATABridge Server SOURCE.

After cache files exist, the next run of the cache command starts reading DMSII audit files from the number specified in the file LastAFN.txt located in the Cache subdirectory.

The cache command can specify an AFN range to indicate where caching should start and stop, which will override the value specified in the LastAFN.txt file. If only the startafn is specified, only that file will be cached.

cache bankdb 460 % only 460

cache bankdb 460 - 488 % beginning of 460 through end of 488

cache bankdb 460 +  % beginning of 460 to end of audit

CODE "filtername" updatelevel

Writes the filtering pseudo-code to the log file. filtername is usually the same as the source name. updatelevel is the desired database update level. This command is intended for Attachmate support's diagnostic purposes.

CONFIGURE "configfilename"

Loads a configuration text file into Enterprise Server to define sources and filters. It is equivalent to using the Import button on the DATABridge Enterprise window.

CONNECT socketnumber "ipaddress"

Used by DATABridge Director to get Enterprise Server to accept the connection from a DATABridge Client or DATABridge Server.

COPY "localname" { TO | AS } (usercode)MCPName [ ON familyname ]

[ { FROM | VIA } ipnameoraddress ] [ PORT portnbr ]


COPY (usercode)MCPName [ ON familyname ] { TO | AS } "localname"

[ { FROM | VIA } ipnameoraddress ] [ PORT portnbr ]


Used to transfer files to or from an MCP disk. Use keywords, as follows:

  • TO indicates the folder or directory destination.
  • AS indicates the filename destination. Use this keyword to specify a desired target name. For example, use AS if you want to retain ON <familyname> in the name of a file that is copied from the MCP environment to Windows. If the source is multiple files, the AS keyword is treated as TO and the destination will be a folder or a directory.
  • FROM or VIA indicates the host name or IP address of the DBServer. The keywords are synonymous.
  • TEXT translates the file contents between ASCII and EBCDIC and adds or removes carriage returns and line feeds
  • BINARY prevents any translation.

DUMP sourcename afn

Writes every update from a cache file to the log file.

sourcename is the name of a cached base or local (filtered) source, and afn is the cache audit file number.

This command is intended for diagnostic use upon request of Attachmate support.

LOAD "configfilename"

LOAD is a synonym for the CONFIGURE command.

MIRROR remotesourcename

[ PASSWORD [ = ] "password" ]
[ startafn [[ - ] endafn | + ] ]

Mirrors audit files from a remote source. Optionally, a range or just a beginning audit file number can be specified.

The PASSWORD option specifies the password to be used when accessing the remote source. The password must match the KEY option in the DATABridge Server SOURCE.

Mirroring must be configured within Enterprise Server before command line mirroring can occur. See Mirroring DMSII Audit Files.

PRINTAUDIT remotesourcename [startafn [ - ] endafn ] [ RECORDS ]

Displays mirrored audit information in human-readable form. Shows sectioned audit files one section at a time. The RECORDS option causes the report to list one line for each audit record showing the structure number, record type, and other information.


dbenterprise printaudit bankdb 357 – 359 records

VALIDATE sourcename DATABASE [=] ODBCsourcename

[ USER [=] username ] [ PASSWORD [=] "password" ]

[ TABLE [=] tablename ]

Compares a cloned database to the original flat files from a JADE database. Enterprise Server will write any differences to the log file.

sourcename is the Enterprise Server source name.

ODBCsourcename is the name of an ODBC source that provides access to the client database.

username and password are used to sign on to that ODBC source.

If a tablename is specified, only that table will be validated. The default is to validate the entire client database.


[ (usercode)MCPdirectory [ ON family ] ]

[ FROM ipnameoraddress ]

[ PORT portnbr ]

[ TO localdirectory ]



Transfers a file or directory of files from an MCP disk to the local computer. The DATABridge host computer must be configured to allow file transfers using XFER. For details, see Configure XFER.

Note: This feature is available as an additional Enterprise Server component. Contact your sales representative for details.

MCPdirectory is a directory or filename in normal MCP format. It must include either the user code in parentheses or *. For example: (PROD)DBBD/RUN ON PRINTPACK

ipnameoraddress is the host name or IP address of the MCP host system where DATABridge Server is running. For example: FROM GALILEO or FROM ""

portnbr is the TCP/IP port number that DATABridge Server uses.

localdirectory is the path where Enterprise Server should place the files transferred from the host system. For example: TO d:\data\MCPFiles

BINARY copies file(s) as-is. TEXT translates all characters from EBCDIC to ASCII and inserts CR-LF (except for STREAM files). For print files, TEXT translates from EBCDIC to ASCII, substituting a form feed character (0x0C) for page breaks, and inserting LF characters for line spacing.

INDIRECT forces Enterprise Server to read the source files using Indirect Disk rather than Direct Disk. This is required when Enterprise Server has visibility to MCP disks but for the wrong MCP Server.

A list of files copied by the XFER command is placed in the same directory as the corresponding log file. More information about the XFER command appears in the next section.