Batch Job Setup

There are several processes that an administrator may want to run on a regular basis at night to maintain the project on a regular cadence without being hindered by underlying user claims or user activity.

Typical examples might be regular Data Integrity Reports (DICE) on the project databases, or spatial map builds in the model, as well as possibly project specific requirements like weekly progress reporting, regular exports of E3D models for consumption outside E3D, and clash runs.

It is useful/logical to separate batch files into operations that only read data model but don’t write, and those that require write access. Reading batch operations can typically be run at any time, as they are not impacted by users being logged-in and can be run concurrently.

The batches that write data typically require all users to be logged out preventing any user claims and would be run at time when the project was inactive (typically at night and at weekends). These writing batches typically start by expunging all users from the project. Careful consideration should be given to sequencing these writing operations sequentially or at least in a way that removes the chance of two operations trying to claim the same item at the same time.

The application is triggered by a DOS script typically launched by a scheduled task in Windows. All batch files must set up an environment (paths to projects and foreign projects as required), call the application (the start command) passing arguments to select user credentials, MDB, Mode, and finally the Macro to be run.

By default, the shortcut that starts E3D looks like this,

"C:\Program Files\AVEVA\product nameX.X\mon.exe" PROD E3D init "C:\Program Files\product name\launch.init"

AVEVA products exist under 3 broad product areas with the following applications in each:

• E3D

  • Model

  • Draw

  • Isodraft

  • Spool

  • Paragon (Catalogues)

• Engineering

  • Engineering

• Administration

  • Administration

  • Lexicon.

To launch the product by DOS batch first a path to the correct product area monitor (mon.exe needs to be defined), either E3D or Engineering or Administration. The correct product to match the path, PROD E3D (for E3D), PROD ADMIN (for Administration) and PROD ENGINEERING (for Engineering).