jajs_migrate

Format

jajs_migrate
     [-h logical-host-name]
     {-C|-convert
       [-T work-directory-name]
       [-r|-f]
       [-S | [[-s {l|m|s}]
            [-u number-of-scheduler-services-to-be-stored-in-one-database]]]}

jajs_migrate
     -convert
     [-T work-directory-name]
     [-s {l|m|s}]
     [-u number-of-scheduler-services-to-be-stored-in-one-database]

jajs_migrate
     -convert
     [-h logical-host-name]
     [-T work-directory-name]
     {-r|-f}
     -S

jajs_migrate
     -convert
     [-T work-directory-name]
     -S

jajs_migrate
     [-h logical-host-name]
     -C

To Page Top

Description

The jajs_migrate command sets up JP1/AJS3 in the standard configuration.

Perform setup after an upgrade installation from JP1/AJS2 to JP1/AJS3. You can execute this command only when the database for a JP1/AJS2 scheduler service can be accessed.

You can also use this command to output the current database configuration to the standard output file.

To Page Top

Execution privileges

In Windows: Administrators privileges

In UNIX: Superuser privileges

To Page Top

Storage directory

In Windows:

JP1/AJS3 - Manager-installation-folder\tools\

In UNIX:

/opt/jp1ajs2/tools/

To Page Top

Arguments

To Page Top

Notes

• If you are using the embedded database or HiRDB as the database for a JP1/AJS2 scheduler service, you must start the embedded database or HiRDB in advance. For details about how to start the embedded database or HiRDB, see the applicable JP1/AJS2 manual or the HiRDB manual.

• Take the following action before you execute this command with the -convert option specified:

  In Windows, stop the JP1/AJS3 service.

  In UNIX, stop the JP1/AJS3 service, and execute the ajsshmdel command. The ajsshmdel command is located in /opt/jp1ajs2/bin/ajsshmdel.

  The following shows an example of executing the ajsshmdel command.

  sh:

  /opt/jp1ajs2/bin/ajsshmdel >/dev/null 2>&1

  csh:

  /opt/jp1ajs2/bin/ajsshmdel >&/dev/null

  In UNIX, if you attempt to execute the jajs_migrate command without executing the ajsshmdel command after the JP1/AJS3 service has stopped, the KAVS0549-E message is output, and the jajs_migrate command terminates abnormally.

• Do not execute this command with the -convert option more than once in quick succession.

• Do not forcibly terminate this command when specifying the -convert option.

• Before you execute this command with the -convert option, register in the hosts file or DNS both the physical host name and logical host name of the JP1/AJS3 host you are migrating to the standard configuration.

  Even if you specify in the jp1hosts or jp1hosts2 definition file the names of the hosts to be migrated in the standard configuration, they are not used as the host names used for the embedded database.

  Do not use an alias as the name of a host you want to migrate in the standard configuration.

  The maximum length of the name of a host on which JP1/AJS3 can operate in the standard configuration is 32 bytes. Make sure that the names of the physical and logical hosts you want to migrate in the standard configuration are 1 to 32 bytes each.

• When you specify the -convert option, the command execution results are output to a log file. The location of the log file is as follows.

  For 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

  The default value of %ALLUSERSPROFILE% 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)

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

  JP1/AJS3 - Manager-installation-folder\log

  For UNIX:

  /var/opt/jp1ajs2/log

  The file name is jajs_migrate_logical-host-name_N.log, where N is a sequential number starting with 1.

• After you execute the jajs_migrate command with the -convert option, check the return value of the command and the log file to make sure that setup of the standard configuration has completed normally. If the command has terminated abnormally, correct the cause of the error, and then re-execute the command.

• To set up JP1/AJS3 in the standard configuration on a physical host, make sure that the JP1_HOSTNAME environment variable has not been set when you execute the jajs_migrate command specifying the -convert option. If the command is executed in an environment in which the JP1_HOSTNAME environment variable is set, JP1/AJS3 on the logical host specified in the JP1_HOSTNAME environment variable is set up in the standard configuration. If the JP1_HOSTNAME environment variable is set, delete it, and then execute the command.

• When you specify the -convert option, the command is executed on the embedded database existing before JP1/AJS3 migration. Therefore, if the embedded database is being used as the scheduler database prior to migration, add the following path to the appropriate environment variable, and then execute the command with the -convert option:

  In HP-UX:

  SHLIB_PATH=installation-directory-for-the-embedded-database-before-migration/client/lib

  In Solaris or Linux:

  LD_LIBRARY_PATH=installation-directory-for-the-embedded-database-before-migration/client/lib

  In AIX:

  LIBPATH=installation-directory-for-the-embedded-database-before-migration/client/lib

  If you execute the command without adding the above path, the command outputs the KAVS0990-E message, and terminates abnormally.

• Note the following if the jajs_migrate -convert command terminates abnormally and you need to re-execute the command:

  • If the DBBKUP directory has been created in the database directory of each scheduler service, and files have been contained in the DBBKUP directory, move these files to the database directory.

  • Use the ajsembdbstatus command with the -s ust option specified to check the status of the embedded database used in version 8. If the status is STOP, use the ajsembdbstart command to change the status to ONLINE.

• When you execute this command with the -convert option specified, a port number in the range 22220 to 22239 is allocated automatically when the system builds the embedded database. An error occurs if the selected port number is in use. Before you execute the command, make sure that ports 22220 to 22239 are available.

• If ISAM is being used as the scheduler service database in JP1/AJS3 version 8 or earlier, at successful execution of the jajs_migrate -convert command the ISAM files will be backed up to a DBBKUP directory created in the database directory of the scheduler service. You can delete the directory if deleting the directory causes no problem with operation.

• If the embedded database (HiRDB) is being used as the scheduler service database in JP1/AJS3 version 8 or earlier, use of HiRDB will cease at successful execution of the jajs_migrate -convert command. Delete the environment, if necessary.

• If you are using a Windows firewall, a pop-up message might appear during setup processing when you execute this command with the -convert option specified. If a pop-up message is displayed, registration in the Windows Firewall exceptions list is required. Take action by referring to the notes on the ajsembdbinstl command.

• When you execute this command with the -convert option specified, a default execution agent and an execution agent that has the same name as the local host are both defined as execution agents on the local host.^#

  #:

  If the execution agent that has the same name as the local host name has not been defined in version 8 or earlier, only the default execution agent is defined. The execution agent that has the same name as the local host name is not defined.

  Note that the execution agent that will be selected depends on how the execution agent is specified in the unit definition:

  • When specification of the execution agent is omitted in the unit definition:

    The default execution agent will execute jobs.

  • When the local host name is explicitly specified as the execution agent in the unit definition:

    The execution agent that has the same name as the local host name will execute jobs.

  Also note that the maximum number of concurrently executable jobs set for an execution agent applies only to that execution agent. If both execution agents have been defined, the maximum number of jobs that will be executed concurrently on the local host is the total of the maximum values for the two agents.

  For example, if the local host name host1 has already been defined as an agent in version 8 or earlier, executing the command will define two execution agents, @SYSTEM and host1. If the setting of the maximum number of concurrently executable jobs for host1 is 00:00-00:00=10 (maximum of 10 jobs at any time), a maximum of 15 jobs might be executed concurrently on the local host. This is because the setting of the maximum number of concurrently executable jobs for the default execution agent is 00:00-00:00=5 (maximum of five jobs at any time).

• You can execute this command specifying the -C option whether JP1/AJS3 services are active or not.

• When you execute this command with the -C option specified, JP1_DEFAULT is set as the logical host in the output items even if you specified the machine name of the physical host in the -h option.

• If you are using an embedded DB or HiRDB as the database for the scheduler service in a JP1/AJS2 V8 environment or earlier, disable the client environment definitions of the embedded DB and/or HiRDB specified in the environment where the command is executed.

To Page Top

Return values

To Page Top

Example 1

In the following example, the command sets up JP1/AJS3 in the standard configuration to create five scheduler services to be stored in one database on the physical host on which JP1/AJS3 is installed as an upgrade installation from JP1/AJS2.

jajs_migrate -convert -u 5

To Page Top

Example 2

The command in this example outputs the current database configuration on the logical host (lhost) to the standard output file.

jajs_migrate -h lhost -C

To Page Top

Output example

The following gives an example of file output when you specify the -C option, and explains what each item means.

Logical host  lhost
DB construction  standard

The output items are as follows:

Logical host

Indicates a logical host name.

If you specified the machine name of a physical host in the -h option, JP1_DEFAULT is set here.

DB construction

Indicates the current JP1/AJS3 database configuration as one of the following:

DB construction	Meaning
standard	The database has been migrated to the standard configuration.
compatible ISAM	The database has not yet been migrated to the standard configuration. The database is operating in a compatible ISAM configuration.
invalid (not yet shifted)	JP1/AJS3 cannot be used at present because the required migration to the standard configuration has not yet completed.

To Page Top