Job Management Partner 1/Automatic Job Management System 3 Command Reference 2

jajs_migrate

Format

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

Format 1 (standard setup on a physical host)

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

Format 2 (for setting up a logical host)

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

Format 3 (for manually setting up the embedded database on the physical host)

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

Description

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

This command is executed after JP1/AJS3 is installed as an upgrade installation from JP1/AJS2.

Execution privileges

In Windows: Administrators privileges

In UNIX: Superuser privileges

Storage directory

In Windows:

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

In UNIX:

/opt/jp1ajs2/tools/

Arguments

-convert

Always specify this option.

-h logical-host-name

Specify this option if you want to specify a logical host name, instead of using the JP1_HOSTNAME environment variable. You can specify a character string of 1 to 32 bytes.

The value of this option overrides the value of the JP1_HOSTNAME environment variable. By specifying JP1_DEFAULT as the value of this option, you can explicitly specify the physical host. You can also specify the computer name of the physical host.

Note, if a logical host is set up with the same name as the physical host name, the logical host is still treated as a logical host rather than the physical host.

-T work-directory-name

Specify the name of the work directory use for migration.

You need to specify this option if free space required for the default work directory cannot be secured. The default work directory is as follows.

For Windows Server 2008

%ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\backup

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

For Windows Server 2003

JP1/AJS3 - Manager-installation-folder\backup

In UNIX:

/var/opt/jp1ajs2/backup/

If the specified directory does not exist, the command terminates abnormally.

If the command terminates abnormally, files might remain. If files remain, delete them and then re-execute the command.

-S

Specify this option if you want to skip setup of the embedded database during migration. If you execute the command when the embedded database has already been set up, specify this option.

However, if you execute the command with this option specified when the embedded database has not been set up, the KAVS0177-E message (Database type is invalid) is output.

-s {l|m|s}

Use this option to specify one of the following database models:

• l
  Specifies a large-scale system model such as shown below:
  
  • Total number of units: About 48,000 to 240,000
  • Total number of jobs and jobnets executed per day: 30,000 to 120,000
  • Required disk space: About 20,700 MB
• m
  Specifies a medium-scale system model such as shown below:
  
  • Total number of units: About 5,000 to 48,000
  • Total number of jobs and jobnets executed per day: 5,000 to 30,000
  • Required disk space: About 4,200 MB
• s
  Specifies a small-scale system model such as shown below:
  
  • Total number of units: A maximum of about 5,000
  • Total number of jobs and jobnets executed per day: A maximum of about 5,000
  • Required disk space: About 520 MB

The default value for this option is s (small-scale model).

-u number-of-scheduler-services-to-be-stored-in-one-database

If you do not want to inherit the configuration existing before migration, using a decimal number specify the number of scheduler services to be stored in one database.

You can specify a value from 1 to 20. If you omit this option, the system assumes 4.

Note that if the embedded database set up in version 8 was used as the scheduler database before migration, the configuration existing before migration is inherited regardless of the specification of this option.

-r

Specify this option to set up the primary host environment in a cluster configuration. If you specify this option, you must also specify the logical host name (-h option).

The shared disk must be mounted on the primary host. In addition, the logical host must be accessible.

-f

Specify this option to set up the secondary host environment in a cluster configuration. If you specify this option, you must also specify the logical host name (-h option).

If this option is specified, the command performs only setup of the embedded database, and does not create data areas or start the embedded database. Note, however, that the specification of the data and system areas for the embedded database (-d option) on the secondary host must be the same as the specification in the primary host environment.

Notes

• Before you execute the command, perform the following operation:
  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 more than once in quick succession.
• Do not terminate the command forcibly.
• Before you migrate the host in the standard configuration, make sure that the physical and logical host names are registered in the hosts file or the DNS.
  Even if you specify in the jp1hosts 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.
  
• The command execution results are output to a log file. The location of the log file is as follows.
  

  For Windows Server 2008

  %ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\log

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

  For Windows Server 2003

  JP1/AJS3 - Manager-installation-folder\log

  In 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 command execution, use the return value and the log file to confirm that JP1/AJS3 has been set up in the standard configuration successfully. 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 the physical host, make sure that you execute the jajs_migrate command in an environment in which the JP1_HOSTNAME environment variable is not set. 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.
• This command performs operations on the embedded database existing before migration. Therefore, if the embedded database is used as the scheduler database before migration, add the following path to the appropriate environment variable, and then execute the command.
  

  In HP-UX:

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

  In Solaris:

  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.
  
• Keep the following points in mind when you 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.
  • The jajs_migrate command might terminate abnormally, causing the following message to be output to the standard error output: KAVS0550-E An error occurred in the shift processing of JP1/AJS3 to the standardized configuration. : jpoman_convert_to_multi 8. If this message is output, delete the following directories or files, and then re-execute the jajs_migrate command:
    - In Windows:
    JP1/AJS2 - Manager-installation-folder\log\EV_Convert_Log.log
    JP1/AJS2 - Manager-installation-folder\tmp\EVaction_backup
    shared-folder\jp1ajs2\log\EV_Convert_Log.log
    shared-folder\jp1ajs2\tmp\EVaction_backup
    - In UNIX:
    /var/opt/jp1ajs2/log/EV_Convert_Log.log
    /var/opt/jp1ajs2/tmp/EVaction_backup
    shared-disk/jp1ajs2/log/EV_Convert_Log.log
    shared-disk/jp1ajs2/tmp/EVaction_backup
    
• When this command sets up an embedded database, the command automatically selects a port number from the 22220-22239 range. Therefore, if the port number selected by the command is already being used, the command results in an error. Before you execute the command, make sure that ports 22220 to 22239 are available.
• If ISAM is used as the scheduler service database in an environment whose version is 8 or earlier, the DBBKUP directory is created in the database directory of the scheduler service when the command terminates normally. In this directory, ISAM files are backed up. You can delete the directory if deleting the directory causes no problem with operation.
• If the embedded database (HiRDB) is used as the scheduler service database in an environment whose version is 8 or earlier, then, after the command terminates normally, the database can no longer be used as the JP1/AJS3 scheduler service database. Delete the environment, if necessary.
• If Windows Firewall is used, a pop-up message might be displayed during setup processing. 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 this command is executed, the default execution agent and the execution agent that has the same name as the local host name are defined in the agent definition 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).
  

Return values

0	Normal end
Values other than 0	Abnormal end

Example

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

[Contents][Back][Next]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.