2.13.2 Disk space requirements

Organization of this subsection

(1) Amount of disk space required for execution modules and libraries
(2) Amount of disk space required for each directory

(1) Amount of disk space required for execution modules and libraries

#	Environment	OS	Formula for estimating
1	Execution environment	Linux	34 MB
2		AIX	32 MB
3		HP-UX	50MB
4		Solaris	31 MB
5		Windows	34 MB^#1
6	Development environment	Windows	17 MB^#2

#1: Depending on the type of Windows OS, the actual value might be smaller than this value. During installation, a maximum of an additional 112 MB of disk space will be temporarily used.
#2: Depending on the type of Windows OS, the actual value might be smaller than this value. During installation, a maximum of an additional 62 MB of disk space will be temporarily used.

To Page Top

(2) Amount of disk space required for each directory

(a) System execution log

The default is as follows, but you can change it via the environment file.

Location

#	Environment	OS	Location
1	Execution environment	Linux	/opt/jp1as/log (LOG_DIR parameter)
2		AIX	/opt/jp1as/log (LOG_DIR parameter)
3		HP-UX	/opt/jp1as/log (LOG_DIR parameter)
4		Solaris	/opt/jp1as/log (LOG_DIR parameter)
5		Windows	`shared-documents-folder`\Hitachi\JP1AS\JP1ASE\log (LOG_DIR parameter)
6	Development environment	Windows	`shared-documents-folder`\Hitachi\JP1AS\JP1ASD\log (LOG_DIR parameter)

Size

#	Environment	OS	Size
1	Execution environment	Linux	2MB × 5 (LOG_FILE_CNT parameter)
2		AIX	2MB × 5 (LOG_FILE_CNT parameter)
3		HP-UX	2MB × 5 (LOG_FILE_CNT parameter)
4		Solaris	2MB × 5 (LOG_FILE_CNT parameter)
5		Windows	2MB × 5 (LOG_FILE_CNT parameter)
6	Development environment	Windows	2MB × 5 (LOG_FILE_CNT parameter)

(b) Trace log

The default is as follows, but you can change it via the environment file.

Location

#	Environment	OS	Location
1	Execution environment	Linux	/opt/jp1as/trace (TRACE_DIR parameter)
2		AIX	/opt/jp1as/trace (TRACE_DIR parameter)
3		HP-UX	/opt/jp1as/trace (TRACE_DIR parameter)
4		Solaris	/opt/jp1as/trace (TRACE_DIR parameter)
5		Windows	`common-application-data-folder`\Hitachi\JP1AS\JP1ASE\trace (TRACE_DIR parameter)
6	Development environment	Windows	`common-application-data-folder`\Hitachi\JP1AS\JP1ASD\trace (TRACE_DIR parameter)

Size

#	Environment	OS	Size
1	Execution environment	Linux	2MB × 4 (TRACE_FILE_CNT parameter)
2		AIX	2MB × 4 (TRACE_FILE_CNT parameter)
3		HP-UX	2MB × 4 (TRACE_FILE_CNT parameter)
4		Solaris	2MB × 4 (TRACE_FILE_CNT parameter)
5		Windows	2MB × 4 (TRACE_FILE_CNT parameter)
6	Development environment	Windows	2MB × 4 (TRACE_FILE_CNT parameter)

(c) Spool

Default is as follows, but the location can be changed via the environment file.

Location

#	Environment	OS	Location
1	Execution environment	Linux	/var/opt/jp1as/spool (SPOOL_DIR parameter)
2		AIX	/var/opt/jp1as/spool (SPOOL_DIR parameter)
3		HP-UX	/var/opt/jp1as/spool (SPOOL_DIR parameter)
4		Solaris	/var/opt/jp1as/spool (SPOOL_DIR parameter)
5		Windows	`shared-documents-folder`\Hitachi\JP1AS\JP1ASE\spool (SPOOL_DIR parameter)
6	Development environment	Windows	`shared-documents-folder`\Hitachi\JP1AS\JP1ASD\spool (SPOOL_DIR parameter)

Size

Calculate the disk space (in KB) required for each job to be executed, by totaling the calculation results of the formulas in the File size column in the table below.

Note that the total of the calculation results of the following formulas will be larger than the disk space required for a typical job. This is to tolerate the variation of the disk space required for the spool because the required space varies due to various causes (for example, the length of the path name of the job definition script file and the number of environment variables).

#	Output Information	File Information	File Size
1	Fixed information (such as the header information)	-	500.0KB
2	Log information for each step to be executed(^#)	Job execution log (JOBLOG)	Count of execution of the command or control statement of the script to be executed × 0.2KB + Number of `#-adsh_step_start` commands × 0.4KB
3	Information about the script to be executed	File in which SCRIPT is included in File Name	The size of the job definition script file
4	Information stored in the program output data file	File assigned by the #-adsh_spoolfile command	The amount of data to be output to the file assigned by the #-adsh_spoolfile command

#:As for this data, you can restrain the output of the specified information message to the job execution log by using the environment setting parameter JOBLOG_SUPPRESS_MSG.

In execution environment, the value calculated according to the formula in the File size column in the table below must be added to the required disk space in the table above.

#	Output Information	File Information	File Size
1	Information about the standard output and standard error output	Files for which names contain STDOUT and STDERR	The amount of data output by commands and user applications
2	Operation information (^#)	File for which the name contains EVENTFILE	Number-of-commands-and-control-statements-of-the-script-to-be-executed * 2.5 KB

#:As for this data, you can restrain creation of operation information by setting the environment setting parameter EVENT_COLLECT to NO.

Calculate the estimated disk space required for the spool for one operation by multiplying the value (in KB) calculated from the above formulas and the number of jobs to be executed.

Concept of the number of commands and control statements

The number of commands and control statements means the number of commands or instructions that are executed when the job definition script is actually executed. The following shows examples.

Example 1:
```
commandA
commandB 
varA="paramA"
commandC $varA
```
For the aforementioned script, the count of the execution of the command or control statement will be as follows.
- commandA
- commandB
- Assignment expression (varA="paramA")
- commandC
Therefore, the number of commands and control statements is 4.

Example 2:
```
lop=1 
while [ $lop -le 5 ] ; do
  echo "Loop count: $lop"
  ((lop+=1))
done 
```
The commands and control statements for the above script are as follows:
- Assignment expression (lop=1)
- Condition evaluation ([ $lop -le 5 ]) <--+
- echo command <--+-- Equivalent to 15 steps,
- Arithmetic operation ( ((lop+=1)) ) <--+ because 5 loops are repeated.
- Condition evaluation ([ $lop -le 5 ]) <----- Final determination processing to break out of the loop
Therefore, the number of commands and control statements is 17.

For loop processing such as in example 2, the number of loops might be dynamically determined depending on the operational status. We recommend that you allow a margin for values, based on the possible maximum.

(d) User-reply function management daemon start-up log (UNIX only)

The size and location of user-reply function management daemon start-up log is as follows:

Location
```
/opt/jp1as/system
```
Size

maximum of 1 MB (usually under 1 KB)

To activate the user-reply function management daemon of the logical host, multiply the size by the number of user-reply function management daemons that are running. The size decreases to 0 when the user-reply function management daemon restarts.

While the user-reply function management daemon is stopped, if a reply-request message that is awaiting a reply is canceled, the size increases. If an error occurs, the size increases.

(e) Log of the application-execution agent functionality (Windows only)

The size and location of log of the application-execution agent functionality is as follows:

Location

shared-documents-folder\Hitachi\JP1AS\JP1ASE\appexec

Size

maximum of 6MB+1KB(CONF file)

To Page Top