23.1.1 Examining the embedded-database operating environment and operating method
This subsection describes considerations based on which the operating environment and operating method for an embedded database can be determined.
- Organization of this subsection
(1) Operating environment
Carefully consider the following environment conditions related to operation of the embedded database:
-
System configuration
-
Environment scale
-
System file area
-
Operating environment
-
Environment before an embedded database is installed
(a) System configuration
Decide whether to configure the embedded database in a non-cluster configuration (physical host) or in a cluster configuration (logical host). The environment conditions consist of both those related to embedded databases and those related to the overall JP1/AJS3 service configuration. Also, if you start multiple scheduler services, decide on the combination of scheduler services and embedded database to be set up.
Note that external client software cannot connect to an embedded database.
(b) Environment scale
Based on the scale of JP1/AJS3 operations, select small, medium, or large as the scale of the embedded database environment. The following table provides a guideline for selecting the scale. For details about how to estimate the database area required for the scale selected, see 23.2 Estimating the database area.
(c) System file area
Decide whether it is necessary to duplicate the system files used for the embedded database. Duplication of system files requires more disk space. However, if a failure occurs on one of two disks that contain the system files, the embedded database can be restored to the point at which the failure occurred by using the system files on the other disk.
The following table shows the required disk space for each type of embedded database operating environment. Select one of the possibilities.
- Cautionary note:
-
If the backup enhancement function is enabled, you cannot duplicate system files.
Table 23‒2: Disk space required for the embedded database operating environment No.
Operating environment
Required disk space (in megabytes)
Backup enhancement function
System configuration
Environment scale
System files duplicated
System area#1
Data area
System file area
Work area
Total#2
1
disabled
Non-cluster
Small
No
170#3
200
320
--
520
2
Yes
640
840
3
Medium
No
1,400
2,800
--
4,200
4
Yes
5,600
7,000
5
Large
No
6,700
14,000
--
20,700
6
Yes
28,000
34,700
7
Cluster
Small
No
170#3, #4
200
320
40 x 2#5
600
8
Yes
640
920
9
Medium
No
1,400
2,800
4,280
10
Yes
5,600
7,080
11
Large
No
6,700
14,000
20,780
12
Yes
28,000
34,780
13
enabled
Non-cluster
Small
No
170#3
700
320
--
1,020
14
Medium
No
1,900
2,800
4,700
15
Large
No
7,200
14,000
21,200
16
Cluster
Small
No
170#3, #4
700
320
40 x 2#5
1,100
17
Medium
No
1,900
2,800
4,780
18
Large
No
7,200
14,000
21,280
- Legend
-
--: The work area is not necessary
- #1
-
The system area is created on the disk on which JP1/AJS3 is installed or in the directory specified in the -i option of the ajsembdbinstl command. For details about the ajsembdbinstl command, see ajsembdbinstl in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
- #2
-
This value does not include the system area amount.
- #3
-
This value varies according to the OS.
OS
Size (MB)
Windows
170
HP-UX (IPF)
400
Solaris
260
AIX
200
Linux
210
- #4
-
In a cluster system, the embedded database must be installed on both the primary and secondary nodes.
- #5
-
In a cluster configuration, work areas must be created on both local disks, and must not be created on a shared disk. That is, you must create a work area on both the primary node and the secondary node.
(d) Operating environment
Take into consideration the following operating environment items related to the embedded database:
-
System definitions
The operands in the following system definitions are described below.
-
System common definition
-
Single server definition
■ System common definition
The following describes the operands in the system common definition, the values of which can be changed by the embedded database system administrator.
The path name of the system common definition file is as shown below. You (the embedded database system administrator) can change the values of operands specified in this file.
-
Windows: embedded-database-practical-directory\conf\pdsys
-
UNIX: embedded-database-practical-directory/conf/pdsys
Note that the operands in the following table that are enclosed in square brackets ([ ]) are not written when the embedded database is set up. Add the operands if necessary.
- Important
-
To ensure correct JP1/AJS3 operation, do not change the values of any operands that are not described here.
No. |
Format |
---|---|
1 |
set pd_max_users = maximum-number-of-concurrently-connectable-users |
2 |
[set pd_service_port = client-connection-port-number] |
3 |
set pd_mode_conf = embedded-database-start-method |
4 |
[set pd_utl_exec_time = execution-monitoring-time-of-a-command-for-operating-the-embedded-database] |
- (1) pd_max_users = maximum-number-of-concurrently-connectable-users
-
~ <unsigned integer> ((1 to 2000))
This operand specifies the maximum number of users who can connect to the embedded database. If you want to change the maximum number of users who can connect to the embedded database, change the value of this operand. If connection to the embedded database is requested when the number of users who have already been connected to the embedded database has reached the maximum, the embedded database does not accept the request (the request results in an error). Note that in JP1/AJS3, if the backup enhancement function is disabled, the default setting is 128, and if the backup enhancement function is enabled, the default setting is 256.
- Cautionary notes:
-
-
For embedded-database operation commands, each command is counted as a single connection to an embedded database.
The number of connections to the embedded database is counted as shown in the following table.
JP1/AJS3 behavior
Number of connections
Startup of JP1/AJS3 - Manager
2
Startup of a scheduler service
4#1, #2, #3
Execution of a command that performs an operation on a unit#4
1
Connection from JP1/AJS3 - View
The number of viewed scheduler services
Execution of a command that performs an operation on the embedded database
2
Execution of a remote jobnet (execution host)
1
Execution of a remote jobnet (target host)
1
Connection from JP1/AJS3 - Web Console
Number of connected scheduler services
- #1
-
If wait conditions are used, add 1 to this value. To determine whether wait conditions are used, check whether the procedure described in 6.1.8 Settings for using wait conditions has been performed.
- #2
-
If the manager functions for queueless job execution have been set up, add the value specified in the QUEUELESSMULTIREQ environment setting parameter to this value.
For details about the QUEUELESSMULTIREQ environment setting parameter, see 20.4.2(76) QUEUELESSMULTIREQ.
- #3
-
If the backup enhancement function is enabled, add 1. You can check the setting of the backup enhancement function by using the ajsembdbstatus command. For details about the ajsembdbstatus command, see ajsembdbstatus in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
- #4
-
Cases of linking to JP1/IM2 and referring to unit information are also applicable.
Note that, when a JP1/AJS3 command is executed from JP1/AJS3 - View, 1 connection is used from JP1/AJS3 - View to the embedded database, and 1 connection is used for executing the command.
-
If you set a value larger than 500 for pd_max_users, you need to expand the space for the sink point dump files. Execute the ajsembdbaddlog command three times with the -s 7 and -r spd options specified to expand the space for the sink point dump files.
The following shows an example of specifying the ajsembdbaddlog command:
ajsembdbaddlog -s 7 -r spd -id _JF0 -d directory-name
For details about the option of the ajsembdbaddlog command, see ajsembdbaddlog in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
-
In UNIX, if you increase the value of this operand, adjust system resources. For the system resources that require adjustment, see the Release Notes.
-
- (2) pd_service_port = client-connection-port-number
-
~ <unsigned integer> ((5001 to 65535))
If there is a firewall on the embedded database server side, specify the client connection port number. Note that the port number you specify must satisfy the following condition:
-
Port number that is unique on the host
- Explanation:
-
-
Specify this operand as necessary if you use a product that links to JP1/AJS3. You do not need to specify this operand in JP1/AJS3 - Manager because it is not available in JP1/AJS3 - Manager.
-
If you start multiple servers or units on the same computer, specify a separate port number for each embedded database.
-
- Cautionary note:
-
Make sure that the port number you specify is outside the range of port numbers assigned automatically by the OS. This differs depending on the OS. If another program is already using a port number in the range and you specify that port number, you will not be able to start the embedded database.
-
- (3) pd_mode_conf = starting-the-embedded-database
-
Specify how the embedded database starts. You can set the values below for pd_mode_conf. The default is MANUAL2. You usually do not need to change the default.
-
AUTO
When the OS starts, the embedded database is started automatically. If the embedded database terminates abnormally, it is restarted automatically.
-
MANUAL1
When the OS starts, the embedded database is not started automatically. The embedded database is restarted automatically only if it terminates abnormally.
-
MANUAL2
When the OS starts, the embedded database is not started automatically. Unlike MANUAL1, if the embedded database terminates abnormally, it is not restarted automatically.
-
- (4) pd_utl_exec_time = execution-monitoring-time-of-a-command-for-operating-the-embedded-database
-
~ <unsigned integer> ((0 to 35791394)) <<0>> (unit: second)
If you monitor the execution time of the following commands that operate the embedded database, specify the monitoring time in minutes.
-
ajsembdbreclaim command
-
ajsembdbrorg command
If the command does not complete execution within the time specified in this operand, a message (KAVS2117-E) is output to the standard error output and the command terminates abnormally.
- Advantage:
-
If the command does not send any response during execution in a nighttime batch job because of a problem such as a communication error or disk error, you can allow the command to terminate abnormally at the specified time.
- Guideline for specifying a value
-
The purpose of this operand is to handle a non-response error, not to monitor the maintenance processing time of the database. Therefore, specify a value for the operand that includes a margin for the maximum value of the actual performance value for the command execution time. For example, if the maximum execution time of the ajsembdbreclaim command is about 60 minutes and the maximum execution time of the ajsembdbrorg command is about 90 minutes, specify 120 for pd_utl_exec_time to provide the margin. The reason for this value is that a non-response error might occur if processing that always finishes in 90 minutes fails to send a response after an additional 30 minutes has elapsed. Note that the time of 30 minutes added to the maximum command execution time is based on the assumption that maintenance is being performed on a scheduler database and the agent management database. If a different type of database access is being performed (for example, access for execution of a job or unit operation command) during the maintenance processing, the maintenance processing waits one minute for the processing to be completed. Accordingly, as a guideline for the time to be added, specify a value that includes a margin obtained from the expression number-of-processing-target-tables x 2 x 1 (in minutes).
For details about the tables that are created in the embedded database, see 2.6.3 JP1/AJS3 database tables in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
-
■ Single server definition
The following describes the operands in the single server definition, the values of which can be changed by the embedded database system administrator. The path name of the single server definition file is as shown below. You (the embedded database system administrator) can change the values of operands specified in this file.
-
Windows: embedded-database-practical-directory\conf\ajs2
-
UNIX: embedded-database-practical-directory/conf/ajs2
- Important
-
To ensure correct JP1/AJS3 operation, do not change the values of any operands that are not described here.
No. |
Format |
---|---|
1 |
set pd_lck_pool_size = size-of-pool-used-for-locking |
- (1) pd_lck_pool_size = size-of-pool-used-for-locking
-
~ <unsigned integer> (unit: KB) ((1 to 2000000))
Specify, in kilobytes, the size of the shared memory area in the embedded database.
In JP1/AJS3, the default differs depending on the scale specified by the ajsembdbbuild, jajs_setup, or jajs_setup_cluster command.
Scale
Command option
Lock pool size
Large
-l
60,000
Medium
-m
37,500
Small
-s
15,000
- Operation method:
-
If units are to be operated by using commands or JP1/AJS3 - View, the size of memory area used for locking changes based on the number of units to be operated. For this reason, estimate and set the appropriate memory area size in advance.
If many units are operated at the same time, the memory area for locking might become insufficient, causing the following problems:
-
The message KAVS0902-E is output to the integrated log, syslog, or Windows event log, and the message KFPA11912-E is output as maintenance information for the message KAVS0902-E. The operations being performed end abnormally.
If insufficient memory area for locking prevents scheduler services from normally accessing the database, the following problems might occur:
-
The message KAVS0902-E is output, and jobs and jobnets cannot be executed normally.
-
The message KAVS0230-E is output to the integrated log, syslog, or Windows event log, and scheduler services end abnormally.
The unit operations#1 that use the memory area for locking are as follows:
-
The unit defined by using the ajsdefine command and all the units under control of the unit
-
The unit to be deleted by using the ajsdelete command or JP1/AJS3 - View and all the units under control of the unit#2
-
The unit specified as the copy source for the unit copy operation by using the ajscopy command or JP1/AJS3 - View and all the units under control of the unit
-
The unit to be restored by using the restoring operation via the ajsrestore command or JP1/AJS3 - View and all the units under control of the unit
-
The root jobnet specified as the release source for the release operation by using the ajsrelease command or JP1/AJS3 - View and all the units under control of the root jobnet#3
-
The root jobnet to be registered by using the execution registration operation via the ajsentry command or JP1/AJS3 - View and all the units under control of the root jobnet
-
The root jobnet to be re-executed by using the re-execution operation via the ajsrerun command or JP1/AJS3 - View and all the units under control of the root jobnet
-
The units that have been added to or deleted from the root jobnet to be released from suspended state by using the suspension cancellation operation via the ajssuspend command or JP1/AJS3 - View
-
The unit to be imported by using the ajsimport command or JP1/AJS3 - View and all the units under control of the unit
-
The units to be changed by using the ajsplan command or the temporary change operation in JP1/AJS3 - View
-
The root jobnet to which registered execution-schedule information is to be imported by using the ajsrgimport command and all the units under control of the root jobnet
-
The units to be checked by using the pre-check on definition contents via the ajschkdef command
-
Registration cancellation by using the ajsleave command or JP1/AJS3 - View#4
To prevent shortages in the memory area for locking, compare the value set for pd_lck_pool_size and the value calculated by using the following expression#5. If the value set for pd_lck_pool_size is smaller, change the value to the calculated value.
-
In cases 1, 2, 3, 4, 5, 8, or 9 above
(a + b + c + d + e) / 4 x 1.2
a: (total-number-of-job-groups x 2) + total-number-of-years-in-the-calendar-defined-for-job-groups
b: (total-number-of-jobnets x 2) + total-number-of-schedule-rules-defined-for-all-jobnets
c: total-number-of-jobs x 2
d: total-number-of-relations-defined-for-jobs-and-jobnets
e: total-number-of-jobs-and-jobnets-with-wait-condition-defined + total-number-of-defined-units-to-be-waited-for
If the UNITDEFDIVIDEUPDATE environment setting parameter is set to yes and the calculated value is 4,000 or greater, set 4,000.
-
In cases 6, 7, 10, or 11 above
(f + g) / 4 x 1.2
f: total-number-of-jobs-and-jobnets x 3
g: total-number-of-jobs-and-jobnets-with-wait-conditions-defined
-
In cases 12 above
h / 4 x 1.2
h: total-number-of-jobs-and-jobnets-and-jobgroups
If the jobnets used in the calculation use the jobnet release function, perform the calculation by using the jobnet definition as the target of operation. Also when an operation equivalent to the above operation is performed by a product related to or linked with JP1/AJS3, the memory area for exclusive control is used in a similar way.
If you change the value set for pd_lck_pool_size, see 3. Estimates in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide and the Release Notes, and then revise the memory requirements.
#1:
The memory area for locking is also used when operations equivalent to those described above are performed from products related to or linked with JP1/AJS3.
#2:
If the jobnet used for calculation uses the jobnet release function, definitions whose statuses are Release wait or Applied are subject to processing. Add the total number of units in those definitions. To estimate the number of units in a definition whose status is Applied, use the following expression: number-of-units-under-control-of-the-root-jobnet x number-of-release-registrations-performed-in-maximum-number-of-days-for-which-generations-are-retained
For details about the status of a jobnet definition, see 7.3.3 Jobnet status after registration of a jobnet-definition release in the JP1/Automatic Job Management System 3 Administration Guide.
#3:
If the jobnet used for calculation uses the jobnet release function, definitions of release-destination units whose statuses are Applied are subject to processing. Add the total number of units in those definitions. To estimate the number of units in a definition whose status is Applied, use the following expression: number-of-units-under-control-of-the-root-jobnet x number-of-release-registrations-performed-in-maximum-number-of-days-for-which-generations-are-retained
For details about the status of a jobnet definition, see 7.3.3 Jobnet status after registration of a jobnet-definition release in the JP1/Automatic Job Management System 3 Administration Guide.
#4:
It is necessary to estimate only when the backup enhancement function is enabled.
#5:
If multiple operations are performed at the same time, use the sum of the calculated values for comparison.
-
- Cautionary notes:
-
-
If you change the specified value of this operand to a larger value and then concurrently operate more units than the guideline for the database scale suggests, a message (KFPS01220-E) is output to the event log or to syslog and the embedded database might terminate abnormally. In such cases, reduce the number of units that are operated concurrently or consider configuring the embedded database on a larger scale.
For details about the guideline for the number of units, see 23.2 Estimating the database area.
-
If you increase the value of this operand, the amount of memory used by the embedded database also increases proportionally. Before you change the value, make sure that there is sufficient memory.
In addition, if you change the specified value of this operand to a larger value in UNIX, adjust the system resources accordingly. For details about the system resources that need to be adjusted, see the Release Notes.
If the value of this operand is too small, an attempt to access JP1/AJS3 might result in an error.
-
The maximum value that can be specified for this operand is 2,000,000. However, if OS memory management cannot secure a continuous area, startup of the embedded database fails. If a continuous area cannot be secured, adjust the value so that a continuous area can be secured.
-
■ Changing the system definition
To change the system definition:
-
Stop the JP1/AJS3 services.
-
Check the status of the target embedded database.
ajsembdbstatus -s ust -id _JF0#
-
If the target embedded database is running, stop it normally. If the target embedded database is not running, start it, and then stop it normally.
Example of the command used to start an embedded database:
ajsembdbstart -id _JF0#
Example of the command used to stop an embedded database normally:
ajsembdbstop -id _JF0#
-
Using a text editor, open the system common definition file or a single server definition file.
Before performing this operation, create a backup of the file in case a problem occurs.
-
Change the value of the operand.
-
Save the change made in step 5, and then close the file.
-
In a cluster configuration, copy the changed system common definition file or the single server definition file to the standby host.
-
Start the JP1/AJS3 services that you stopped.
The embedded database is also started at this time.
- #:
-
For the -id option, specify the setup identifier of the target embedded database. To start the embedded database in Windows, start the JP1/AJS3 Database _JFn (n: 0 to 9 or A to Z) service in advance.
- Important
-
If you use a multi-byte space or character, or add an unnecessary line-feed or space character in the system common definition or single server definition, startup of the JP1/AJS3 services fails.
(e) Environment required for installing an embedded database
This subsection describes how to determine the environmental requirements for the configuration of the embedded database that will be built.
■ Required disk space
For details about disk capacity, see the Release Notes.
Note that if you install an embedded database on an NTFS-formatted disk in Windows, you must not compress the files in the embedded database practical directory. If you do so, the embedded database will not operate normally.
■ Required memory
For the memory requirements, see the Release Notes.
In Windows, you must also check the virtual memory requirement. To do this, perform the following:
-
In Windows Control Panel, and then double-click System.
The System dialog box appears.
-
Click Advanced system settings.
The System Properties dialog box appears.
-
Click the Advanced tab.
-
Click the Settings button of Performance.
The Performance Options dialog box appears.
-
Click the Advanced tab.
-
Click the Change button of Virtual memory.
The virtual memory required for one instance of an embedded database is as follows:
Paging file size = 130 MB
To determine the size you actually specify, add the size required by Windows and other programs. If you change the size of the virtual memory, you must restart Windows.
- Cautionary note
-
The size may increase depending on the number of JP1/AJS3 - Views that are connected or the number of scheduler services that are set.
For the initial size, specify a quantity of virtual memory that can be allocated in a continuous area on one drive. If a contiguous area cannot be used for virtual memory, the embedded database might terminate abnormally because memory is insufficient.
■ Checking kernel parameters
In UNIX, you must change the kernel parameters as necessary. For details about estimating kernel parameters, see 3.2.5 Estimating the values for kernel parameters in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
(2) Database operations
Consider the following items related to embedded database operations:
-
Use of the system log data
-
Times at which the embedded database is backed up
-
Point up to which the embedded database is restored from the backup
-
Method for restoring the embedded database from the backup
(a) Use of the system log data
The following describes operation when the system log is used for restoration. You can ignore this item if you do not use the system log for restoration.
- Operation that uses unloading
-
In this method, the data output to a system log file is unloaded (that is, backed up) to another file. The contents of the system log files are unloaded automatically by the embedded database, at which time the system log file becomes available for reuse. However, since disk space is required to store the unloaded log files (called unload log files), available disk space must be monitored. In addition, when the system is restored, the unload log files must be specified in the correct order.
(b) Times at which the embedded database is backed up
The embedded database can be backed up at either of the following times:
- While the JP1/AJS3 service is stopped (while no jobs or jobnets are being executed)
-
In this case, you must stop JP1/AJS3 when you back up the embedded database. This is the basic backup method. With this method, you can restore the status of the embedded database at the time it was backed up by using the obtained backup data only.
- While the JP1/AJS3 service is running (when jobs and jobnets are being executed)
-
Two methods are available for creating a backup while the JP1/AJS3 service is running:
-
Use the backup enhancement function
-
Use an unload operation
You do not have to stop the operation of JP1/AJS3 when you back up an embedded database by using these methods. When you use an unload operation to recover data, however, you need the unload log files output by the embedded database in addition to the backup data.
You cannot use the backup enhancement function and unload log files at the same time.
-
(c) Point up to which the embedded database is restored from the backup
The embedded database can be restored from the backup up to the following times:
- Time when the embedded database was backed up
-
In this case, you can restore the embedded database to the state existing at the time the embedded database was backed up. However, any updates made after the backup was acquired will not be restored.
- Latest synchronization timepoint following backup of the embedded database
-
In this case, in addition to restoring the embedded database to the state existing at the time of the backup, you can also restore updates occurring after the backup, thereby restoring the database to the latest state.
(d) Methods for restoring the embedded database from a backup
The following describes how you can restore the embedded database from backup data.
- By using the backup data only
-
In this case, you use only the backup data to restore the embedded database. The embedded database is restored to the state existing at the time it was backed up.
- By using the backup data and the system log data
-
In this case, you use the backup data and the system log information output after the backup to restore the embedded database. This method also restores any updates made to the database after the backup. Use this method to restore the embedded database if you use backup data obtained while JP1/AJS3 was running.
The following table shows the methods of embedded database operation.
No. |
Method of operation |
||||
---|---|---|---|---|---|
System log |
Time that the embedded database is backed up |
Time up to which the embedded database is restored from the backup data |
Method for recovering the embedded database from the backup data |
||
A |
A-1 |
Not used |
While the JP1/AJS3 service is stopped |
Up to the time when the embedded database was backed up |
Backup data only |
A-2 |
Not used (The backup enhancement function is used.) |
While the JP1/AJS3 service is running |
Up to the time when the embedded database was backed up |
Backup data only |
|
B |
B-1 |
Unloading used |
When the JP1/AJS3 service is stopped |
Up to the time when the embedded database was backed up |
Backup data only |
B-2 |
Latest synchronization point |
Backup data and system log data |
|||
B-3 |
While the JP1/AJS3 service is running |
The following table shows the advantages and disadvantages of each method of operation. Study this table before you select a method from Table 23-3.
No.# |
Advantages and disadvantages |
||
---|---|---|---|
Advantages |
Disadvantages |
||
A |
Common |
Monitoring the status of the system log file is not required. |
The embedded database can be restored only up to the time when it was backed up. |
A-1 |
No setup is required before using this method. |
The JP1/AJS3 service must be stopped during the backup. |
|
A-2 |
A backup can be created while the JP1/AJS3 service is running. |
Configuration is required during setup of the embedded database. |
|
B |
Common |
Monitoring the status of the system log file is not required. |
|
B-1 |
If an error occurs in the system log file, the embedded database can be restored by using the backup data only. |
|
|
B-2 |
|
The JP1/AJS3 service must be stopped during the backup. |
|
B-3 |
|
If the unload log file is lost, the embedded database cannot be recovered by using the backup data only. |
- #
-
The numbers in this table correspond to the numbers in Table 23-3.
For details about the backup and how to restore the database from the backup data only, see the following:
-
5.2.5 Backing up and recovering an embedded database by using the backup enhancement function in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide
-
F.1(1) Restoring the scheduler database from unload log files in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide
-
F.1(2) Restoring the scheduler database without using the system log in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide
When using a method you have selected in Table 23-3, you need to use the following commands to set up the environment for the embedded database, back up the embedded database, and restore the embedded database from the backup data only:
-
ajsembdbbuild command (sets up the embedded database environment)
-
ajsembdbsetup command (set up the embedded database)
-
jajs_dbbackup command (backs up the embedded database in an environment in which the backup enhancement function is enabled)
-
jajs_dbrestore command (restores the embedded database from the backup in an environment in which the backup enhancement function is enabled)
-
ajsembdbbackup command (backs up the embedded database)
-
ajsembdbrstr command (restores the embedded database from the backup data only)
The jajs_dbbackup and jajs_dbrestore commands can be used only in an environment in which the backup enhancement function is enabled. The ajsembdbbackup and ajsembdbrstr commands are used in an environment in which the backup enhancement function is disabled.
The following table shows whether the each of the methods in Table 23-3 can be used with commands and their options.
No.# |
Duplicating system files |
Commands to be executed and options related to backup and recovery |
||||||
---|---|---|---|---|---|---|---|---|
ajsembdbbuild (-bs, -br, -bl, -b) |
ajsembdbsetup (-b) |
ajsembdbbackup (-s) |
ajsembdbrstr (-ld, -l) |
jajs_dbbackup |
jajs_dbrestore |
|||
A |
A-1 |
Not available |
Not available |
Not available |
Not available |
Not available |
-- |
-- |
A-2 |
-b |
-b |
-- |
-- |
Y |
Y |
||
B |
B-1 |
-bs -bl |
Not available |
Not available |
Not available |
-- |
-- |
|
B-2 |
-ld or -l |
-- |
-- |
|||||
B-3 |
-s |
-ld or -l |
-- |
-- |
||||
A |
A-1 |
Available |
-- |
-- |
-- |
-- |
-- |
-- |
A-2 |
||||||||
B |
B-1 |
-br -bl |
Not available |
Not available |
Not available |
-- |
-- |
|
B-2 |
-ld or -l |
-- |
-- |
|||||
B-3 |
-s |
-ld or -l |
-- |
-- |
- Legend
-
--: Cannot be used with the applicable method
Y: Can be used with the applicable method
- #:
-
The numbers in this table correspond to the numbers in Table 23-3.
For details about the ajsembdbbuild command, see 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.
For details about the ajsembdbbackup and ajsembdbrstr commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
(3) How to monitor the data area usage
If a database is not maintained for a long time, or if the number of units or the number of logs that must be retained exceeds that which is assumed for the scale of the database, the unused data capacity will become insufficient. If the unused data capacity is insufficient, the system might not be able to execute jobs. Check data area usage so that you can detect a shortage in data area capacity before that capacity becomes insufficient.
For details about how to check the data area usage, see 5.2.1 How to check the database usage in the JP1/Automatic Job Management System 3 Administration Guide.
(4) How to set up an embedded database
You can build an embedded database as an extension of a JP1/AJS3 installation or set up an embedded database by using the jajs_setup_cluster command. If you build an embedded database in this way, you do not need to perform advanced setup for the embedded database.
For details about the settings for an embedded database to be set up in JP1/AJS3, see 2.6.5 Database settings that are set up in JP1/AJS3 in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
To build an embedded database by specifying other settings, perform an advanced setup of an embedded database.
To change the settings for an existing embedded database, such as the _JF0 setup identifier specified during installation of JP1/AJS3, set up the embedded database again. For details about setting up the embedded database again, see 23.4.1(6) Setting up an embedded database again, 23.5.1(6) Setting up an embedded database again (in a cluster configuration (executing system)) , or 23.5.2(6) Setting up an embedded database again (in a cluster configuration (standby system)).