Setup >  Usage  >  Batch server >  Batch server parameters  

Display all Hide all

Your Sage X3 software includes an integrated batch server which is 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. 

 Sage advise that you read the following documentation before setting or changing the batch server parameters: Explanation of batch server operation.

Screen management

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

Entry screen

Presentation

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

Close

 

Fields

The following fields are present on this tab :

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.

  • Next query number (field NUMREQ)

This number identifies the current task (query/request) number. It is a sequential number assigned automatically but can be amended.

  • 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'.

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

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

This group of parameters defines the different directories that are used for the management of tasks (queries/requests) submitted from a file. Each directory should be on the application server, by default. A different server on the network is possible, with the syntax server@directory.

 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.

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

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

This group of parameters defines the different directories that are used for the management of tasks (queries/requests) submitted from a file. Each directory should be on the application server, by default. A different server on the network is possible, with the syntax server@directory.

 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.

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

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

 

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

This group of parameters defines the different directories that are used for the management of tasks (queries/requests) submitted from a file. Each directory should be on the application server, by default. A different server on the network is possible, with the syntax server@directory.

 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.

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

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

 

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

This group of parameters defines the different directories that are used for the management of tasks (queries/requests) submitted from a file. Each directory should be on the application server, by default. A different server on the network is possible, with the syntax server@directory.

 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.

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

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

 

Close

 

Error messages

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

Maximum : N

An attempt has been made to submit too many simultaneous batch tasks. Please refer to the field Maximum no. active queries (field NBTACHE) to view the number of batch tasks that can be executed simultaneously on this application server.

Tables used

SEEREFERTTO Refer to documentation Implementation