7.2.2 Environment settings for executing queueless jobs

The following describes the environment settings for executing queueless jobs.

Use the jbssetcnf command to change the values of environment setting parameters. For details about this command, see the Job Management Partner 1/Base User's Guide.

For details about the environment setting parameters for an execution environment for queueless jobs, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

Also consider the following issues.

• When queueless jobs are executed in an environment where the manager host and the agent host use different character code sets

  If the manager host and the agent host use different character code sets, you must specify the language code in the AJSQL_CHARCODE environment setting parameter.

  This environment setting parameter is used for the character code conversion shown in the following figure.

  Figure 7‒6: Character code conversion for queueless jobs

  (1) Scheduler service and queueless agent service

  The value of the AJSCHARCODE environment setting parameter specified for the scheduler service is used as the character code set. Character codes are not converted for the scheduler service.^#

  (2) Queueless agent service

  The following data is converted to the character code set specified for the AJSQL_CHARCODE environment setting parameter.

  - Data accepted from the scheduler service

  - Transfer file data

  The following data is converted to the character code set specified for the AJSCHARCODE environment setting parameter of the scheduler service that issued the request:

  - Reply data to the scheduler service

  - Result file data

  The default value of AJSQL_CHARCODE is none. If none is set, character codes are not converted.

  If the manager and the agent use different character code sets, you must specify AJSQL_CHARCODE for the queueless agent service to which the request is sent.

  (3) Queueless agent service and queueless file transfer service

  The data in the transfer file is sent from the queueless file transfer service to the queueless agent service where it is converted to the character code set used by the queueless agent service. The data in the result file is converted to the character code set used by the queueless agent service, and is then sent to the queueless file transfer service. Character codes are not converted in the queueless file transfer service^#.

  #

  If UTF-8 is specified for the QLMANCHARCODE environment setting parameter for the manager, character codes are converted.

• When queueless jobs are executed on the manager host in a UTF-8 environment

  To use the manager in a UTF-8 environment to execute a queueless job on an agent host that does not support UTF-8, you must specify UTF-8 for the QLMANCHARCODE environment setting parameter.

  This environment setting parameter can be set only when the character code set (value of the AJSCHARCODE environment setting parameter) of the manager is UTF-8. Do not set this environment setting parameter if UTF-8 is not the character code set of the manager.

  The following shows the scope of the QLMANCHARCODE environment setting parameter.

  Figure 7‒7: Scope of the QLMANCHARCODE environment setting parameter

  (1) Scheduler service

  If UTF-8 is specified for both the AJSCHARCODE and QLMANCHARCODE environment setting parameters, character codes are converted. The conversion applies to the job definition items.

  The AJSCHARCODE setting is specified for each scheduler service whereas the QLMANCHARCODE setting is specified for a machine. To use queueless jobs, make sure that the AJSCHARCODE setting is the same for all the scheduler services.

  (2) Queueless file transfer service

  If UTF-8 is specified for the QLMANCHARCODE environment setting parameter, character codes are converted. The conversion applies to the transfer file and result file (execution result details).

For details about the language types that you can use in the system, see 2.4.3 Language type of the system.

To Page Top