What Is a Batch?

This section contains conceptual information batches and describes the batch infrastructure.

The infrastructure software features the CATUTIL batch monitor for running and monitoring batches. Certain batches are provided as part of the core package, others are part of specific configurations/products. Note that certain batches can only be run if you have the corresponding license.

You can run the batch monitor using a variety of methods to launch the batches installed with your software. The batches can be:

  • run locally on the machine on which you are using the batch monitor
  • or submitted to a remote machine to be run on the remote machine.

The batches can be either those provided with the software, or your own customized batches.

This page discusses:

Communications Backbone

This section describes the communications backbone.

With the first implementation, the batch monitor requires no external software as a prerequisite since it can work using the communications backbone packaged with the core software; the backbone is used for both local and remote batch execution.

This implementation is described in Configuring Batch Monitoring for the Communications Backbone.

What Is the Batch Infrastructure?

This section describes the batch infrastructure.

The batch infrastructure is part of the infrastructure allowing:

  • V6 Batch submission
  • Remote capabilities: inputs upload, submission, outputs download
  • Process Monitoring: interrupt, completion state, error reports, execution log
  • Batch environment and licensing management.

What Is a Batch?

This section describes what a batch is. A batch is a non-interactive program.

It has with the following characteristics:

  • it is described in an XML file referred to as the descriptor file
  • its inputs and outputs are described in an XML file referred to as the parameter file
  • it provides processing via a lib/symbol format instead of a standard executable file.

Role of the Descriptor File

This section describes the role of the descriptor file.

So that each batch can be listed and recognized, a descriptor file is delivered for each batch on Windows in:

C:\Program Files\Dassault
          Systemes\B424\win_b64\code\bin\resources\batchdesc

The descriptor file must NOT be modified by the batch monitor administrator.

Role of the Parameter File

This section describes the role of the parameter file.

The syntax of the parameter file for each batch is provided in an empty file.

The person who runs the batch must fill in this XML file to specify the inputs to be passed to the batch.

If the batch is submitted using the interactive Batch Monitor tool, the file is generated from the user input specified by using the batch user interface.List of Batches

A list of batches along with their description is displayed in the Type column of the CATUTIL program. This list may vary according to the licenses you set up during installation.

Note that not all batches can be run on a remote machine. Furthermore, data containing links to other data cannot be processed in remote batch mode.

Using the Communications Backbone

This section discusses the use of the communications backbone. You can use the communications backbone in both local and remote mode.

In Local Mode

This section discusses the use of the communications backbone in local mode.

To submit batches for execution on your local machine using the communications backbone, no administration tasks are necessary: the backbone is the default communication driver. The batch will be run as long as the required license is available.

In Remote Mode

This section discusses the use of the communications backbone in remote mode.

On the remote mode:

  • the core software containing the communications backbone must be installed
  • the configuration installed on the remote machine must allow end users to run the desired batch
  • a license for the appropriate configuration must be either installed on the remote machine, or be accessible from the remote machine
  • you must start the backbone server monitor, as explained in Configuring Batch Monitoring for the Communications Backbone.