8.11.2.1 JES Configuration File

A JES configuration file is used by the TuxJES administration server ARTJESADM. You can configure the following JES configuration file parameters:

  • JES Base Directory

    The base JESROOT directory. If it is not set, the base directory is $APPDIR.

  • JESROOT

    The root repository to store job information. This directory is created under the path set in JES Base Directory. For example, if JESROOT is set to jesroot and JES Base Directory is set to $APPDIR the full path of the JESROOT directory is {$APPDIR}/jesroot.

    If ART Batch related servers are configured on two Tuxedo machines, they must share the same JESROOT repository; only an absolute JESROOT path is acceptable and the directory should exist in the Network File System.

  • DEFAULTJOBCLASS

    Optional. The default job class if the job class has not been set in JCL. The default job class is A if this option is not set.

  • DEFAULTJOBPRIORITY

    Optional. The default job priority if the job priority has not been set in JCL. The default job priority is 0 if this option is not set.

  • DUPL_JOB

    If NODELAY is not checked, only one job can be in execution status per job name. When it is checked, NODELAY removes the dependency check.

  • EVENTPOST

    Specifies events posted for a job at particular stages.

    • S: Job submission event.
    • C: Job conversion complete event.
    • E: Job execution complete event.
    • P: Job purge event.
    • A: All supported events

      If EVENTPOST is not specified, no event is posted. The data buffer with event post is FML32 type. The fields are defined in tuxjes/include/jesflds.h.

  • JOBREPOSITORY

    The path of the stored job repository. The job submitting script file path may be a relative path in JOBREPOSITORY if it is set.

  • PRIVILEGE MODE

    Specifies whether and how to enable the user substitution (See TuxJES User Substitution).

    • NONE: Default value. Indicates jobs are executed by the OS user who starts the JES system. This is compatible with all previous JES system implementations
    • USER_IDENTICAL: Indicates jobs are executed by the Oracle Tuxedo user where the JES client joins JES system. Make sure that each Oracle Tuxedo user corresponds to an existing OS user before you choose this option.
    • USER_MAPPING: The JES system looks up the TuxJES user mapping file and finds the OS user corresponding to the Oracle Tuxedo user where JES client joins JES system, and then appoints this OS user as the job executor.
  • USER MAPPING FILE

    This option is enabled when you choose USER_MAPPING as Privilege Mode. Specify the user mapping file name. User mapping file is under the $APPDIR directory by default.

    The owner of the User Mapping File created by Resource Broker is root, and its file permission is "-rw-------".

Note:

The User Mapping File name cannot be:
  • one of the following: Logs, QUE, TLOG, UBBCONFIG, acc, crlog, data, data_source, jesconfig, jesqinit, tools, tpacl, tpgrp, tpusr, and tuxconfig
  • the same as JESROOT if JESROOT is under the $APPDIR directory.

    For the existing domain, since security is not supported, the user mapping file cannot be introspected and parsed.

  • USER MAPPING Table

    The user mapping table displays the mapping relationship between Oracle Tuxedo users and OS users. When Privilege Mode is set to USER_MAPPING, the user mapping table is enabled allowing you to add, edit, or delete a user mapping entry Every line in the mapping table is in the following format:

    tuxedousername OSusername

Note:

  • Duplicated user pairs are not allowed.
  • One Oracle Tuxedo user can only be mapped to one OS user.

Parent topic: JES Configuration