Your Sage X3 software includes an integrated batch server used to launch tasks on the application server in batch mode.

Use this function to modify the parameters that launch the batch server and control the execution of the batch tasks.

Read the Explanation of batch server operation documentation before setting or changing the batch server parameters.

Screen management

The Batch server parameters function displays a single screen into which you enter your batch server information.

Entry screen

Use this screen to define the parameters for your batch server.

Batch server

Server name (field APPLI)

This field displays the name of the folder where the batch server is used. The name is associated with the software, for example, SERVX3 for Sage X3.
Use of batch files (field JOB)

Click this check box to launch tasks (queries/requests) from files created in a specified directory.

You are only authorized to perform this function if your user parameter EXTBATCH-Batch file management (SUP chapter, AUZ group) is set to Yes.

Consult the corresponding technical appendix for information on the submission of queries by file.

Block number 2

Directory of query start files (.job) (field REPJOB)

This group of parameters defines the different directories used to manage tasks (queries/requests) submitted from a file. Each directory should be on the application server by default. It is possible to have a different server on the network with the server@directory syntax.

A directory must not be on a client workstation.

The extension used for the processed files is specified between brackets in the header of the column.

Consult the corresponding documentation for further information on the submission of queries by file.

Block number 3

Directory of template files (.mod) (field REPMOD)

This group of parameters defines the different directories used to manage tasks (queries/requests) submitted from a file. Each directory should be on the application server by default. It is possible to have a different server on the network with the server@directory syntax.

A directory must not be on a client workstation.

The extension used for the processed files is specified between brackets in the header of the column.

Consult the corresponding documentation for further information on the submission of queries by file.

Block number 4

Directory of status files (.sta) (field REPSTA)

Block number 5

Directory of in-process query files (.run) (field REPRUN)

This group of parameters defines the different directories used to manage tasks (queries/requests) submitted from a file. Each directory should be on the application server by default. It is possible to have a different server on the network with the server@directory syntax.

A directory must not be on a client workstation.

The extension used for the processed files is specified between brackets in the header of the column.

Consult the corresponding documentation for further information on the submission of queries by file.

Block number 6

Directory of pending query files (.req) (field REPREQ)

Block number 7

Directory of query stop files (.kil) (field REPKIL)

This group of parameters defines the different directories used to manage tasks (queries/requests) submitted from a file. Each directory should be on the application server by default. It is possible to have a different server on the network with the server@directory syntax.

A directory must not be on a client workstation.

The extension used for the processed files is specified between brackets in the header of the column.

Consult the corresponding documentation for further information on the submission of queries by file.

Block number 8

Directory of request start archive files (.old) (field REPOLD)

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Maximum: N

An attempt to submit too many simultaneous batch tasks was made. Refer to the Maximum no. active queries field (NBTACHE) to view the number of batch tasks you can execute simultaneously on this application server.

Tables used

SEEREFERTTO Refer to documentation Implementation