Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2

2.9 Setting up JP1/AJS3 shared information

The same settings for JP1/AJS3 shared information can be used for the manager environment (JP1/AJS3 - Manager) and for the agent environment (JP1/AJS3 - Agent).

The table below lists the environment setting parameters to be used to set JP1/AJS3 shared information in the manager environment (JP1/AJS3 - Manager) and in the agent environment (JP1/AJS3 - Agent).

To determine whether an environment setting parameter is to be set in Windows or UNIX, see the Applicable OS column.

Table 2-9 Environment setting parameters (JP1/AJS3 shared information)

No.	Definition key	Environment setting parameter	Definition	Applicable OS	Applicable product
1	[{JP1_DEFAULT|logical-host-name}\JP1AJS2COMMON]#	"LARGEFILEUSE"=	Operation for large files	Windows UNIX	M, A
2		"SYSLOGJOBMSG"=	Setting for whether the error messages for jobs are also to be output to syslog	UNIX	M, A
3		"MACROCHANGEFAIL"=	Operation if an attempt to expand a macro variable specified in an event job fails when the job is registered for execution registration	Windows UNIX	M, A

Legend:

M: JP1/AJS3 - Manager

A: JP1/AJS3 - Agent

#

Specify JP1_DEFAULT for the physical host. For logical-host-name, specify the name of a logical host.

The following describes each of the environment setting parameters.

Parameters that are not described here are used for maintenance purposes. Do not change their values.

The default value is used whenever a value is not specified for an environment setting parameter.

Organization of this section

(1) "LARGEFILEUSE"="{yes|no}"

(2) "SYSLOGJOBMSG" ="{none|error}"

(3) "MACROCHANGEFAIL"="{yes|no}"

(1) "LARGEFILEUSE"="{yes|no}"

Use this parameter to specify whether the file monitoring job monitors large files and the judgment job determines if there are any large files.

For details, see 14.3.12 Enabling monitoring of a large file in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

yes

The file monitoring job monitors files larger than 2 GB and the judgment job determines if there are any files larger than 2 GB.

no

The file monitoring job cannot monitor files that are larger than 2 GB. If you specify no, but specify a file larger than 2 GB as a monitoring target, an error message is output to the integrated trace log when execution of the file monitoring job terminates abnormally. For this reason, do not specify a file larger than 2 GB as a monitoring target.

The judgment job cannot determine if there are any files larger than 2 GB. If you specify a file larger than 2 GB in a judgment condition when you have specified no, the judgment job determines that there are no large files.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After JP1/AJS3 is restarted

(2) "SYSLOGJOBMSG" ="{none|error}"

Use this parameter to specify whether to also output error messages appearing during the execution of jobs to syslog.

For details, see 14.6.1 Settings for outputting error messages for jobs to syslog in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

none

Error messages appearing during the execution of jobs are not output to syslog. The status of JP1/AJS3 is monitored by the integrated trace log.

error

Error messages appearing during the execution of jobs are output to the syslog file, which is used to monitor the error status of JP1/AJS3. However. even if you specify this value, you must not stop the integrated trace log process.

If you specify error for this parameter, a message reporting abnormal job termination (KAVS0265-E) is output to syslog, regardless of whether the scheduler service setting contains JOBSYSLOG (outputs, to syslog, messages related to starting and ending a job).

The following table lists the messages that are output based on the values specified for the SYSLOGJOBMSG and JOBSYSLOG environment setting parameters.

Table 2-10 Messages to be output based on the values specified for SYSLOGJOBMSG and JOBSYSLOG

Value specified for SYSLOGJOBMSG	Value specified for JOBSYSLOG
	none	abend	warning	hold	enddelay	all
none	--	KAVS0265-E	KAVS0269-W	KAVS0271-I	KAVS0248-I	KAVS0263-I KAVS0264-I KAVS0265-E KAVS0266-I KAVS0269-W KAVS0271-I
error	KAVS0265-E	KAVS0265-E	KAVS0265-E KAVS0269-W	KAVS0265-E KAVS0271-I	KAVS0265-E KAVS0248-I	KAVS0263-I KAVS0264-I KAVS0265-E KAVS0266-I KAVS0269-W KAVS0271-I

Default value

none

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

(3) "MACROCHANGEFAIL"="{yes|no}"

Use this parameter to specify whether to set Failed to start as the status if expansion of the passing information in a macro variable fails when a job is executed.

For details, see 6.2.10 Setting the action to be taken if the value of a macro variable cannot be passed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 14.2.10 Setting the action to be taken if the value of a macro variable cannot be passed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

Specifiable values

yes

If the expansion of the passing information in a macro variable fails when a job is executed, the status set is Failed to start, and an error message is output to the Hitachi integrated log and as execution result details so that you can check the macro variable that could not be expanded.

no

Even if the expansion of the passing information in a macro variable fails when a job is executed, the system treats the information defined in the macro variable as a character string and continues processing.

Default value

no

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

[Contents][Back][Next]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.