|
|
|
|
|
|
You can specify multiple path names, delimit them with a colon (:). For example,
JOBREPOSITORY=<path1>:<path2>:<path3>
To find job to submit, Batch Runtime searches from these paths in the order that you specify (in JOBREPOSITORY). When finding a job name match, Batch Runtime stops searching, and submits this matched job.Specifies whether and how to enable the user substitution (See TuxJES User Substitution). The values are:NONE: Default value. Indicates jobs are executed by the OS user who starts JES system. This is compatible with all previous implementations on JES system.USER_IDENTICAL: Indicates jobs are executed by the Oracle Tuxedo user with which JES client joins JES system. Make sure that each Oracle Tuxedo user corresponds to an existing OS user before you choose this value.USER_MAPPING: When this value is specified, the JES system looks up the TuxJES user mapping file and finds out the OS user corresponding to the Oracle Tuxedo user with which JES client joins JES system, and then appoints this OS user as the job executor.The full path where TuxJES user mapping file is stored. It is used along with PRIVILEGE_MODE when its value is USER_MAPPING.OFF: Specifies no logs.ON: Specifies writing to SYSLOG. Default value. The SYSLOG is entitled "jessys.log". You can change its path from the default "$JESROOT/jessys.log" to other directories by using SYSLOG_PATH.DAILY: Specifies writing to SYSLOG. A new log file is created daily. The SYSLOG is entitled "jessys.log.<mmddyy>". For example, the SYSLOG entitled "jessys.log.032715" stands for the log file created for the day of March 27, 2015. You can change its path from the default "$JESROOT/jessyslog/jessys.log.<mmddyy>" to other directories by using SYSLOG_PATH.WEEKLY: Specifies writing to SYSLOG. A new log file is created weekly. The SYSLOG is entitled "jessys.log.<mmddyy>", where the "dd" means the first day of current week (Sunday is the first day of the week). For example, the SYSLOG entitled "jessys.log.032215" stands for the log file created for the week from March 22, 2015 (Sunday) to March 28, 2015 (Saturday). You can change its path from the default "$JESROOT/jessyslog/jessys.log.<mmddyy>" to other directories by using SYSLOG_PATH.MONTHLY: Specifies writing to SYSLOG. A new log file is created monthly. The SYSLOG is entitled "jessys.log.<mmddyy>", where the "dd" means the first day of current month. For example, the SYSLOG entitled "jessys.log.030115" stands for the log file created for the month of March 2015. You can change its path from the default "$JESROOT/jessyslog/jessys.log.<mmddyy>" to other directories by using SYSLOG_PATH.Specifies the path of SYSLOG files.When SYSLOG=ON is set, you get the SYSLOG entitled "$SYSLOG_PATH/jessys.log" and located in the directory where you specify through this SYSLOG_PATH.When SYSLOG=DAILY,WEEKLY,MONTHLY is set, you get the SYSLOG entitled "$SYSLOG_PATH/jessys.log.<mmddyy>" and located in the directory where you specify through this SYSLOG_PATH. The "jessys.log.<mmddyy>" confirms to the naming rules for SYSLOG=DAILY,WEEKLY,MONTHLY.If you do not specify SYSLOG_PATH, the SYSLOG files are still located in $JESROOT/jessyslog (when SYSLOG is set to DAILY, WEEKLY, or MONTHLY) or $JESROOT (when SYSLOG is set to ON) by default.0: Disable the automatic purging. Default value.N(>=1): Enable the automatic purging and purge the first finished N Jobs one time.ON: Backup folder <JESROOT>/<JOB_ID> to <JESROOT>/<JOB_ID>.bak while automatic purging, just delete the relevant message from "OUTPUT" queue.If AUTOPURGE=0, this item is ignored. Default value.OFF: Delete all the files belong to the job (in folder <JESROOT>/<JOB_ID>) while automatic purging.Listing 4 jesconfig Example
-j jobid: purge a particular job
-c job class: purge jobs with given job class
-s job status: purge jobs with given job status
-a: purge all jobsCompleted jobs in the DONE or FAIL status are moved to the purge queue. For other jobs, purgejob has same effect as canceljob. The purgejob command does not purge the job directly. The ARTJESPURGE server deletes the job from the TuxJES system.You can display the number of maximum concurrent ARTJESINITIATOR server executing jobs using the artjesadmin subcommand printconcurrent:You can change the number of maximum concurrent ARTJESINITIATOR server executing jobs using the artjesadmin subcommand changeconcurrent:-n concurrent_num: the number of maximum concurrent executing jobsYou can display the number of ARTJESINITIATOR server executing jobs using the artjesadmin subcommand showjobexec:The Tuxedo logic machine name running ARTJESINITIATOR server.The Tuxedo group id of the ARTJESINITIATOR serverThe Tuxedo server id of the ARTJESINITIATOR server
- User name should not contain a semicolon (;).
- User name should not be just an asterisk (*).
Multiple users are separated by ":". An asterisk (*) means all Oracle Tuxedo users. Wildcards are not supported in this field. For example, tpuser* does not mean all users that have name starting with tpuser.
For Oracle Tuxedo's naming requirements, see Oracle Tuxedo Command Reference.Specifies job operations. The job operations could be SUBMIT, CANCEL, PURGE, HOLD, and RELEASE.
Among these five kinds of job operation, SUBMIT is the most important one and is the prerequisite of the following four kinds of job operation because if a user wants to cancel, purge, hold or release a job, TuxJES firstly checks whether the user is the owner of the job (only if the user is granted as SUBMIT and successfully submit a job, that user becomes the owner of this job and will own this job until it is purged out of TuxJES system).
Multiple operations are separated by ":". An asterisk (*) means all of these operations (equals to SUBMIT:CANCEL:PURGE:HOLD:RELEASE). Wildcards are not supported in this field. This field is case insensitive.Specifies job names. The job name is not the file name of the job; it is the internal job name specified in m_JobBegin and translated from //<NAME> JOB statement in JCL.
Multiple job names are separated by ":". Wildcards "*" (for zero or more characters) and "?" (for only one character) are supported.If you set JES_ACL_FILE_TYPE=ENCRYPTED, you must configure the JES_ACL_FILE file as an encrypted file. This encrypted file can be generated by the genjesacl tool.If no rule is found to match the user, operation and job, the configuration of JES_ACL_MODE in JESCONFIG file takes effect. If JES_ACL_MODE is not set, its default value JES_ACL_MODE=MAC takes effect, meaning that the operation is denied.Listing 15 shows an example.Listing 15 Example for Processing RulesThough the above two rules are both matching rules, the first matching rule takes precedence, meaning that user tpuser1 is authorized to operate on JOBA and the second matching rule does not take effect.If you want user tpuser1 to operate all the jobs except for JOBA, exchange the sequence of the above two rules.The lines (ignoring leading space) starting with character # are considered as comments. For example:Do not write comments right after the rule in the same line. For example, the #C in the following line is not considered as a comment.Suppose jobs whose names start with JOBAA, JOBBB and JOBCC need to be protected. You want to grant tpuser1 and tpuser2 for jobs whose names start with JOBAA, and grant tpuser3 and tpuser4 for jobs whose names start with JOBBB and JOBCC. All other jobs do not need to be protected.Suppose there are three Oracle Tuxedo users in the system: tpuser1, tpuser2, tpuser3; there are 30 jobs in the system: JOBX01-JOBX10, JOBY01-JOBY10, and JOBZ01-JOBZ10.You want to grant tpuser1 and tpuser2 to operate all jobs, and grant tpuser3 to only operate 12 jobs: JOBX10, JOBY10, and JOBZ01-JOBZ10.If user tpuser1 wants to submit JOBB and user tpuser2 wants to submit JOBA, there is no matching rule for these requirements; then the settings for JES_ACL_MODE take effect.By default, JES_ACL_MODE is MAC, meaning that these actions would be denied; however, if you specify JES_ACL_MODE to DAC, the above operations will be allowed.You can dynamically change job access authorization, using artjesadmin command.You can also use artjesadmin sub command.For example, to change the rule file of job access authorization to another file (aclrule.new) with DAC mode, you can use artjesadmin command as Listing 16 or use artjesadmin sub command as Listing 17.