3.4.3 Estimating the size of the log information output by event jobs

[definition-key]
"environment-setting-parameter" = definition-details
"environment-setting-parameter" = definition-details
   :

(1) Log setting configuration definition parameters for event jobs

The following table shows the environment setting parameters.

Table 3‒16: List of log setting configuration definition parameters for event jobs

Definition Key	Environment setting parameter	Definition details
For scheduler service (common) [{JP1_DEFAULT|logical-host-name}\JP1AJS2\SCHEDULER\EV\MANAGER\LOG] For scheduler service (individual) [{JP1_DEFAULT| logical-host-name}\JP1AJSMANAGER\ scheduler-service-name \EV\MANAGER\LOG]	"LogSize"=	Log size (Common to all event job managers)
	"LogNumFiles"=	Number of log files (Common to all event job managers)
	"LogSize_jpomanager"=	Log size (Applies to individual event job manager processes)
	"LogSize_jpomgrsub"=
	"LogNumFiles_jpomanager"=	Number of log files (Applies to individual event job manager processes)
	"LogNumFiles_jpomgrsub"=
[{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT\LOG]	"LogSize"=	Log size (Common to all event job agents)
	"LogNumFiles"=	Number of log files (Common to all event job agents)
	"LogSize_jpoagent"=	Log size (Common to all event job agents)
	"LogSize_jpoagtsub"=
	"LogSize_jpocwtflMain"=
	"LogSize_jpoeventwatch"=
	"LogSize_jpoevsearch"=
	"LogSize_jpocwttmMain"=
	"LogSize_jpocwtmlmain"=
	"LogSize_jpomldsk"=
	"LogSize_jpomlsrv"=
	"LogSize_jpomlapisend"=
	"LogSize_jpomlapisend2"=
	"LogSize_jpomlapirec"=
	"LogSize_jpomlapirec2"=
	"LogSize_jpomailrecv"=
	"LogNumFiles_jpoagent"=	Number of log files (Applies to individual processes at event job agents)
	"LogNumFiles_jpoagtsub"=
	"LogNumFiles_jpocwtflMain"=
	"LogNumFiles_jpoeventwatch"=
	"LogNumFiles_jpoevsearch"=
	"LogNumFiles_jpocwttmMain"=
	"LogNumFiles_jpocwtmlmain"=
	"LogNumFiles_jpomldsk"=
	"LogNumFiles_jpomlsrv"=
	"LogNumFiles_jpomlapisend"=
	"LogNumFiles_jpomlapisend2"=
	"LogNumFiles_jpomlapirec"=
	"LogNumFiles_jpomlapirec2"=
	"LogNumFiles_jpomailrecv"=

Details on each item in the table are given below.

"LogSize"=dword:log-size

Specify the size of one log file in byte units, in hexadecimal. Make the setting within the range 20,000 (128 kilobytes) to 40,000,000 (1 gigabyte).

The value specified here affects all event job manager processes or agent processes.

"LogNumFiles"=dword:number-of-log-files

Specify the file count that triggers a log wrap (number of log files) in hexadecimal. Make the setting within the range 2 to 10 (in decimal form, 2 to 16).

The value specified here affects all event job manager processes or agent processes.

"LogSize_process name"=dword:log-size

Specify the size (in bytes, hexadecimal) of one log file when you want to change the log size for any single process at an event manager or agent. Make the setting within the range 20,000 (128 kilobytes) to 40,000,000 (1 gigabyte).

For details on the log sizes (rough values) set for each process, see (2) Calculating the log size for each process below.

"LogNumFiles_process name"=dword:number-of-log-files

Specify the number of log files, in hexadecimal, when you want to change this number for any single process at an event manager or agent. Make the setting within the range 2 to 10 (in decimal form, 2 to 16).

When each event job process starts, the log size and number of files are determined according to the following order of priority.

1. Specification for each process

   Value specified for LogSize_process-name or LogNumFiles_process-name

2. Event job common specification

   Value specified for LogSize or LogNumFiles

3. Default values for each process

   Process-specific default values like those shown in the table below

Table 3‒17: Default values for event job processes and logs

Type	Process name	Platform		Default values for logs (values in parentheses are set at JP1/AJS3 installation and setup)
		Windows	UNIX	Log size	Number of log files
Manager	jpomanager	E	E	640 kilobytes (4,096 kilobytes)	8 (13)
	jpomgrsub	E	E	640 kilobytes (3,072 kilobytes)	6 (8)
Agent	jpoagent	E	E	384 kilobytes (3,072 kilobytes)	8 (8)
	jpoagtsub	E	E	384 kilobytes (2,048 kilobytes)	8 (16)
	jpocwtflMain	E	E	1,280 kilobytes (2,048 kilobytes)	6 (13)
	jpoeventwatch	E	E	640 kilobytes (9,216 kilobytes)	4 (8)
	jpocwttmMain	E	E	128 kilobytes (256 kilobytes)	2 (6)
	jpocwtmlmain	E	E	128 kilobytes (128 kilobytes)	2 (2)
	jpoevsearch	E	E
	jpomldsk	E	--
	jpomlsrv	E	--
	jpomlapisend	E	--
	jpomlapisend2	E	--
	jpomlapirec	E	--
	jpomlapirec2	E	--
	jpomailrecv	--	E

Legend:

E: Process exists

--: No process

The filenames of event job logs are decided as follows.

process-name[1|2|3|...].log

The filenames of event job logs are decided as follows.

jpoagent1.log
jpoagent2.log
     :
jpoagent8.log

For details about log types, see 1.2.5 List of log files and directories in the manual JP1/Automatic Job Management System 3 Troubleshooting.

To Page Top

(2) Calculating the log size for each process

The calculations to determine rough values for the log size to set for each process are shown in the following table.

The values determined with these calculation formulae are for guidance only. They could change depending on the operating environment and other factors.

Table 3‒18: Log size (rough values) for each event job process

Process name	Calculation formulae (units: bytes)
jpomanager	See Table 3-19.
jpomgrsub	See Table 3-19.
jpoagent	See Table 3-20.
jpoagtsub	See Table 3-20.
jpocwtflMain	See Table 3-21.
jpoeventwatch	number-of-executions-of-JP1-event-reception-monitoring-job x 4,000 number-of-JP1-events-that-occur-on-logical-host-running-JP1/AJS3 x 1,200 number-of-monitoring-conditions-established-for-JP1-event-reception-monitoring-job x 3,800 number-of-monitoring-conditions-established-for-JP1-event-reception-monitoring-job x (number-of-macro-variables x (macro-variable-size + macro-variable-data-size (the upper limit is 1,024)))
jpoevsearch	number-of-executions-of-a-JP1-event-reception-monitoring-job-using-the-event-search-functionality-before-execution x 700
jpocwttmMain	See Table 3-22.
jpocwtmlmain (Windows only)	Only created when using mail system linkage for Windows. number-of-satisfactions-of-email-reception-monitoring-job-monitoring-conditions x 2,800
jpocwtmlmain (UNIX only)	Only created when using mail system linkage for UNIX. number-of-satisfactions-of-email-reception-monitoring-job-monitoring-conditions x 7,400
jpomldsk	Only created when using mail system linkage (on a desktop) for Windows. (number-of-executions-of-email-sending-jobs x 200) + (each-mail-monitoring-interval x 400)
jpomlsrv	Only created when using mail system linkage (at a service) for Windows. (number-of-satisfactions-of-email-reception-monitoring-job-monitoring-conditions x 400) + (number-of-executions-of-email-sending-jobs x 200)
jpomlapisend#1	Only created when using mail system linkage for Windows. Number-of-executed-email-sending-jobs x 2,800
jpomlapisend2#2	Only created when using mail system linkage for Windows. Number-of-executed-email-sending-jobs x 2,800
jpomlapirec#1	Only created when using mail system linkage for Windows. 2,800 (if email reception monitoring jobs are executed, once per monitoring interval)
jpomlapirec2#2	Only created when using mail system linkage for Windows. 2,800 (if email reception monitoring jobs are executed, once per monitoring interval)
jpomailrecv	Only created when using mail system linkage for UNIX. number-of-mails-that-reach-the-mail-server x 1,200

#1

When the mail system linkage function is used in the JP1/AJS3 Mail service

#2

When the mail system linkage function is used on the desktop

Table 3‒19: Manager log output size

Phenomenon			Calculation formula (units: bytes)
			jpomanager	jpomgrsub
Event job	Registration		3,350	2,300
	Occurrence		1,900	1,550
Start condition	Registration		1,150 + (2,600 x number-of-events-in-the-start-condition#)	750 + (750 x number-of-events-in-the-start-condition#)
	Occurrence	Start condition not satisfied	3,400	2,250
		Start condition satisfied	3,850	2,250

#

The number of events in the start condition is the number of event jobs defined within the start condition.

Table 3‒20: Agent log output size (per job)

Phenomenon		Calculation formula
		jpoagent	jpoagtsub
Event job	Registration	2,104	1,285
	Occurrence	735	1,356
Start condition	Occurrence	2,104	1,285
	Start condition satisfaction	735	1,356

Table 3‒21: File monitoring log output size (per job)

Phenomenon		Calculation formula (units: bytes)
		When you specify the full name of the monitored file	When you specify a wildcard (*)
Event job	Registration	3,300	5,000
	Event occurrence	4,500 + (macro-variable-size + macro-variable-data-size (the upper limit is 1,024))	4,500 + (macro-variable-size + macro-variable-data-size (the upper limit is 1,024))
Start condition	Registration	3,300	5,000
	Event occurrence	2,800 + (macro-variable-size + macro-variable-data-size (the upper limit is 1,024))	(2,800 + (macro-variable-size + macro-variable-data-size (the upper limit is 1,024))) x number-of-event-occurrences
	End	1,000	1,000

Table 3‒22: Execution interval control log output size (per job)

Phenomenon		Calculation formula (units: bytes)
Event job	Registration	2,600
	Event occurrence	2,300
Start condition	Registration	2,600
	Event occurrence	2,300 x number-of-event-occurrences
	End	1,000
When a time-out period is specified for an event job#	Registration	1,200
	Event occurrence	2,300

#

If a time-out period is set for each event job including execution interval control jobs, a log of the values indicated above is output to the execution interval control log.

To Page Top

(3) Estimating the log size of email sending jobs that do not use Outlook

The following table lists the environment setting parameter used to change the log size of email sending jobs that do not use Outlook:

Table 3‒23: Environment setting parameter that defines log settings for email sending jobs that do not use Outlook

Definition key	Environment setting parameter	Definition
[{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT\mail_link]#	"LogSize_EmbeddedMail"=	Log size (Applies to individual profiles)

#

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:

"LogSize_EmbeddedMail"=dword:log-size

Specify the size of one log file in byte units, in hexadecimal. Make the setting within the range 80000 (512 kilobytes) to 9C3C00 (9,999 kilobytes).

The value specified for this environment setting parameter affects all of the log information of the email sending jobs that do not use Outlook.

The following table lists the formula for calculating the (estimated) log size of email sending jobs that do not use Outlook. Note that the value obtained by the formula is an approximation, and can vary depending on operating environment or other factors.

Table 3‒24: Log size (estimated value) of email sending jobs that do not use Outlook

Job name	Calculation formula (units: bytes)
Send mail job	Created only when email sending jobs that do not use Outlook are used. number-of-executions-of-send-mail-job x 3,500

To Page Top

(4) Changing the size of the common log for events and actions

To change the size of the common log for events and actions:

1. Create a size specification file (jpocommonerr.dat) for the common log for events and actions.

   The save location is as follows:

   In Windows, if the installation folder is the default installation folder or is in a folder protected by the system:

   %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\jpocommonerr.dat

   The default %ALLUSERSPROFILE% value is system-drive\ProgramData.

   A folder protected by the system is the path to a folder in any of the following:

   - system-drive\Windows

   - system-drive\Program Files

   - system-drive\Program Files (x86)

   In Windows, if the installation folder is other than the above:

   JP1/AJS3 - Manager:

   JP1/AJS3-Manager-installation-folder\log\jpocommonerr.dat

   JP1/AJS3 - Agent:

   JP1/AJS3-Agent -installation-folder\log\jpocommonerr.dat

   In UNIX:

   /var/opt/jp1ajs2/log/jpocommonerr.dat

2. Define the log size in the size specification file (jpocommonerr.dat) for the common log for events and actions.

   In the size specification file (jpocommonerr.dat) for the common log for events and actions, specify the log size according to the following format. The specified log size will be applied immediately.

   LogSize: log-size

   Specify the log size, in bytes, in decimal format between 8,388,608 and 2,147,483,647. If a value less than the lower limit (8,388,608 bytes) is specified, the default value (8,388,608 bytes) is used. If a value more than the upper limit (2,147,483,647 bytes) is specified, the upper limit (2,147,483,647 bytes) is used.

   The following is an example for the common log for events and actions, for when the log size is 16,384 kilobytes.

   LogSize: 16777216

Note that even in a cluster configuration, since the common log for events and actions is output to the log files on the physical hosts, you must set the size on both physical hosts. To revert the size setting to the default (8,192 kilobytes), delete the size specification file (jpocommonerr.dat). The changes will be applied immediately.

The following table shows formulas for estimating the output size of the common log for events and actions.

Table 3‒25: Output size of the common log for events and actions (per processing item)

Phenomenon		Calculation formula (units: bytes)
Event job	Registration	1,024
	Event occurrence	512
	Forced termination	1,024
Start condition	Registration	(3 + number-of-event-jobs-defined-in-the-start-condition x 2) x 512
	Start condition formation	For AND: ( 4 + number-of-event-jobs-defined-in-the-start-condition x 2) x 512 For OR: 4,096
	Forced termination	2,048
JP1/AJS3 start and stop	Manager host restart	(number-of-scheduler-services + number-of-jobnets-with-all-start-conditions-being-registered x 6 + number-of-all-event-jobs-being-registered x 2) x 512
Action job	Registration	1,024

Note

Even in a cluster configuration, output is performed to the default directory. As a result, for the output size of the common log for events and actions, use the sum of the values above for both the logical host and physical host.

To Page Top