8.5.1 How to set up JP1/AJS3 - Manager after upgrading from JP1/AJS2 - Manager

Migration tasks must be performed first on the physical host, and then on the logical host.

Organization of this subsection

(1) Estimates when migrating data
(2) Standard data migration procedure
(3) Data migration procedure when using advanced settings
(4) The notice which is at the time of re-execution of the jajs_migrate command
(5) The procedure to delete environment before a shift
(6) Database before a shift and after a shift
(7) Estimating the disk space requirements after migration from a version 8 embedded database

(1) Estimates when migrating data

Because data migration involves the creation of temporary files, disk space equivalent to the area used by the existing scheduler services is required. After performing the migration, make sure there are no issues with the new JP1/AJS3 - Manager before you delete these temporary files. For the directory in which the temporary files are created, see jajs_migrate in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

You must also estimate the requirements of the new host environment in advance. For details about making estimates, see 3.2 Estimating system performance.

To Page Top

(2) Standard data migration procedure

The following figure shows the standard workflow when migrating data.

Figure 8‒2: Data migration workflow (standard)

To migrate data using the standard procedure:

Cautionary note: The logical host environment cannot shift in this procedure. the shift procedure of logical host environment, see (3) Data migration procedure when using advanced settings and 2.2.2 Installing a JP1/AJS3 series program in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (in Windows) or 12.2.1 Notes on installation in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (in UNIX).

Stop the JP1/AJS3 service.

In the case of the UNIX environment, please execute the ajsshmdel command after a service stop. The path of the ajsshmdel command is /opt/jp1ajs2/bin/ajsshmdel. The example of execution is shown below.

In the case of sh
```
/opt/jp1ajs2/bin/ajsshmdel >/dev/null 2>&1
```
In the case of csh
```
/opt/jp1ajs2/bin/ajsshmdel >&/dev/null
```
In UNIX, if you execute the jajs_migrate command without executing the ajsshmdel command after the service stops, the KAVS0549-E message is output and the command terminates abnormally.
Execute the jajs_migrate command.

If an embedded database is used for the scheduler database before migration, activate the embedded database, and then execute the jajs_migrate command.

An execution example is as follows:
```
jajs_migrate -convert -u 5
```
For the command syntax, see jajs_migrate in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

Cautionary notes

- When using JP1/AJS3 - Manager in a cluster configuration, execute the jajs_migrate command for each logical host.

- In the case of the UNIX version, when it uses an embedded database in the scheduler database before shift, a setup of an environment variable is required. For details, see jajs_migrate in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

- When the jajs_migrate command ends normally, check if a warning message has been output. If a warning message has been output, take the action indicated in the message.
Restart the JP1/AJS3 service.

To Page Top

(3) Data migration procedure when using advanced settings

The following figure shows the data migration workflow when using advanced settings.

Figure 8‒3: Data migration workflow (advanced settings)

To migrate data with advanced settings:

Stop the JP1/AJS3 service.

In the case of the UNIX environment, please execute the ajsshmdel command after a service stop. The path of the ajsshmdel command is /opt/jp1ajs2/bin/ajsshmdel. The example of execution is shown below.

In the case of sh
```
/opt/jp1ajs2/bin/ajsshmdel >/dev/null 2>&1
```
In the case of csh
```
/opt/jp1ajs2/bin/ajsshmdel >&/dev/null
```
In UNIX, if you execute the jajs_migrate command without executing the ajsshmdel command after the service stops, the KAVS0549-E message is output and the command terminates abnormally.
Execute the ajscnvdbexport command to save the database information.

An execution example is as follows:
```
ajscnvdbexport -F AJSROOT1 -b D:\workdir
```
This command operates on the pre-migration embedded database. If the embedded database is used for the scheduler database before migration, activate the embedded database and set the following environment variable before you execute the ajscnvdbexport command:

In HP-UX:

SHLIB_PATH=installation-directory-of-pre-migration-embedded-database/client/lib

In Solaris or Linux:

LD_LIBRARY_PATH=installation-directory-of-pre-migration-embedded-database/client/lib

In AIX:

LIBPATH=installation-directory-of-pre-migration-embedded-database/client/lib

For the syntax of the ajscnvdbexport command, see ajscnvdbexport in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
Execute the ajsembdbinstl command to install the JP1/AJS3 database.

An execution example is as follows:
```
ajsembdbinstl -s "C:\Program Files\HITACHI\JP1AJS2\tools\AJS3DB" -id _JF0
```
For the command syntax, see ajsembdbinstl in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

Cautionary note

To install an embedded database on the logical host, specify a value that is _JF1 or greater for the -id option of the ajsembdbinstl command.
Execute the ajsembdbbuild command to build the database environment.

An execution example is as follows:
```
ajsembdbbuild -s -d "D:\database\RDArea_JF0,D:\database\SYSArea_JF0" -p 22220 -i "C:\Program Files\HITACHI\JP1AJS2\embdb\_JF0" -id _JF0
```
For the command syntax, see ajsembdbbuild in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

Cautionary note

In the case of the UNIX version, build the first database environment on the relevant host (-i option specification value of the ajsembdbbuild command) built on an applicable host to /opt/jp1ajs2/embdb/_JF0.
Execute the ajsembdbsetup command to set up the database environment.

An execution example is as follows:
```
ajsembdbsetup -F AJSROOT1 -p 22220 -id _JF0 -ru s -convert
```
For the command syntax, see ajsembdbsetup in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
Execute the ajscnvdbimport command to migrate the database information.

An execution example is as follows:
```
ajscnvdbimport -F AJSROOT1 -b D:\workdir
```
For the command syntax, see ajscnvdbimport in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
Execute the jajs_migrate command.

An execution example is as follows:
```
jajs_migrate -convert -S
```
For the command syntax, see jajs_migrate in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

Cautionary note

When using JP1/AJS3 - Manager in a cluster configuration, execute the jajs_migrate command for each logical host.
Restart the JP1/AJS3 service.

To Page Top

(4) The notice which is at the time of re-execution of the jajs_migrate command

When re-executing the jajs_migrate command, attention is needed about the next.

A DBBKUP directory is created in the database directory of each scheduler service. When the file is stored in the directory, arrange the contents of the DBBKUP directory to a database directory.
To the ajsembdbstatus command, specify -s ust, check the state of the embedded database, which was being used by the version 8, and, in the case of a STOP state, change the database into an ONLINE state by using the ajsembdbstart command.
If the KAVS0550-E message (the following message) is output to the standard error output and the jajs_migrate command terminates abnormally, delete the directories or files below, and then re-execute the jajs_migrate command: An error occurred in the shift processing of JP1/AJS3 to the standardized configuration: jpoman_convert_to_multi 8

In Windows:

JP1/AJS2-Manager-installation-folder\log\EV_Convert_Log.log

JP1/AJS2-Manager-installation-folder\tmp\EVaction_backup

shared-folder-name\jp1ajs2\log\EV_Convert_Log.log

shared-folder-name\jp1ajs2\tmp\EVaction_backup

In UNIX:

/var/opt/jp1ajs2/log/EV_Convert_Log.log

/var/opt/jp1ajs2/tmp/EVaction_backup

shared-disk-name/jp1ajs2/log/EV_Convert_Log.log

shared-disk-name/jp1ajs2/tmp/EVaction_backup

To Page Top

(5) The procedure to delete environment before a shift

It you use an embedded database or HiRDB as a database of scheduler service before shift, it is necessary to delete if needed after the completion of shift. Uninstall a database according to the procedure of the manual of each version.

In addition, in the case of UNIX, execute the following command after ajsembdbunset command execution.

/opt/HiRDB_J/bin/pdesetup -u embedded database practical directory

To Page Top

(6) Database before a shift and after a shift

When JP1/AJS3 - Manager is a standard configuration, the database of scheduler service is stored in an embedded database.

Before shift, as a database of scheduler service of JP1/AJS2 - Manager ISAM, HiRDB, or an embedded database built by JP1/AJS2 - manager version 7 is being used, if it shifts to the database of scheduler service of JP1/AJS3 - Manager, jajs_migrate command stores the data of four scheduler services to one embedded database automatically.

When the embedded database built by JP1/AJS2 - Manager is being used before shift, if it shifts to the database of scheduler service of JP1/AJS3 - Manager, the state where it is stored as a database of two or more scheduler services to one embedded database.

To change the embedded database in which the database of the scheduler service is stored after shift, perform the procedure of (3) Data migration procedure when using advanced settings, or specify -u option to jajs_migrate command to shift.

The example of composition of the database before shift and after shift is shown below.

(Example 1) When operating with single scheduler service before shift.

Before migration		After migration
Scheduler service name	Database type	Scheduler service name	Setup identifier
AJSROOT1	ISAM	AJSROOT1	_JF0

(Example 2) When operating with two or more scheduler services before shift.

Before migration		After migration
Scheduler service name	Database type	Scheduler service name	Setup identifier
AJSROOT1	ISAM	AJSROOT1	_JF0
AJSROOT2	ISAM	AJSROOT2
AJSROOT3	ISAM	AJSROOT3
AJSROOT4	ISAM	AJSROOT4
AJSROOT5	ISAM	AJSROOT5	_JF1
AJSROOT6	ISAM	AJSROOT6
AJSROOT7	ISAM	AJSROOT7

(Example 3) When operating with two or more scheduler services before shift (ISAM, HiRDB, embedded database (Version 7) mixture environment).

Before migration		After migration
Scheduler service name	Database type	Scheduler service name	Setup identifier
AJSROOT1	ISAM	AJSROOT1	_JF0
AJSROOT2	HiRDB	AJSROOT2
AJSROOT3	HiRDB	AJSROOT3
AJSROOT4	Embedded database (Version 7)	AJSROOT4
AJSROOT5	Embedded database (Version 7)	AJSROOT5	_JF1
AJSROOT6	ISAM	AJSROOT6
AJSROOT7	ISAM	AJSROOT7

(Example 4) When operating with two or more scheduler services before shift (ISAM, embedded database (Version 8) mixture environment).

Before migration		After migration
Scheduler service name	Database type	Scheduler service name	Setup identifier
AJSROOT1	ISAM	AJSROOT1	_JF1
AJSROOT2	Embedded database (Version 8) _JAA	AJSROOT2	_JF0

(Example 5) When operating with two or more scheduler services before shift (ISAM, HiRDB, embedded database (Version 7), embedded database (Version 8) mixture environment).

Before migration		After migration
Scheduler service name	Database type	Scheduler service name	Setup identifier
AJSROOT1	ISAM	AJSROOT1	_JF2
AJSROOT2	Embedded database (Version 8) _JA0	AJSROOT2	_JF0
AJSROOT3	HiRDB	AJSROOT3	_JF2
AJSROOT4	Embedded database (Version 8) _JA0	AJSROOT4	_JF0
AJSROOT5	Embedded database (Version 7)	AJSROOT5	_JF2
AJSROOT6	Embedded database (Version 8) _JA1	AJSROOT6	_JF1
AJSROOT7	ISAM	AJSROOT7	_JF2
AJSROOT8	Embedded database (Version 7)	AJSROOT8	_JF3
AJSROOT9	Embedded database (Version 8) _JA1	AJSROOT9	_JF1
AJSROOTA	ISAM	AJSROOTA	_JF3

To Page Top

(7) Estimating the disk space requirements after migration from a version 8 embedded database

After migration from a version 8 embedded database, the disk space requirements depend on the migration method as described below.

(a) Standard migration

The following disk space is required for migration:

(50 + (490 + a)) x [Figure] b/c + d (units: megabytes)

a: Variable that depends on the scale specified in the -s option of the jajs_migrate command

Substitute one of the following values according to the scale of the database:

l: 20,700

m: 4,200

s: 520 (default value)

b: Number of scheduler services

c: Value specified in the -u option of the jajs_migrate command (default is 4)

d: Database size for all scheduler services before migration

For ISAM: Total size of the ISAM files
For an embedded database: Variable that depends on the scale specified in the ajsembdbbuild command

Substitute one of the following values according to the scale of the database:

-l: 1,600 (default value)

-m: 800

-s: 300

If the database area has been expanded, add the amount of the increase to the value.
For HiRDB: The size created by using the HiRDB simple setup script

ajshirdbsetupl: 288

ajshirdbsetupm: 72

ajshirdbsetups: 18

ajshirdbsetupsfm1: 288

If the database area has been expanded, add the amount of the increase to the value.

Note that the space specified by the value that replaces d occupies the disk that contains the directory specified in the -T option of the jajs_migrate command. When the migration is complete, delete this information because it is no longer necessary.

(b) Migration with advanced setup

For a migration that uses advanced setup, before executing the ajsembdbbuild command, you need to determine the scale based on the database capacity and operational requirements before migration.

For the capacity required for setting up one embedded database environment, see C. Advanced Setup of an Embedded Database in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

To Page Top