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

[Contents][Glossary][Index][Back][Next]

jajs_setup_cluster

Format

For JP1/AJS3 - Manager:
jajs_setup_cluster
     [-h logical-host-name]
     -F scheduler-service-name
     {-d shared-directory-name
      [-n scheduler-service-ID-number]
      [-m {cold|warm|hot}]
      {-P embedded-database-port-number
       -I embedded-database-setup-ID
       -S} |
      [-S]}

For JP1/AJS3 - Agent:
jajs_setup_cluster
     [-h logical-host-name]
     [-d shared-directory-name]

Format 1 (for setting up JP1/AJS3 - Manager on the primary node)

jajs_setup_cluster
     [-h logical-host-name]
     -F scheduler-service-name
     -d shared-directory-name
     [-n scheduler-service-ID-number]
     [-m {cold|warm|hot}]
     {-P embedded-database-port-number
      -I embedded-database-setup-ID |
      -S}

Format 2 (for setting up JP1/AJS3 - Manager on the secondary node)

jajs_setup_cluster
     [-h logical-host-name]
     -F scheduler-service-name
     [-S]

Format 3 (for setting up JP1/AJS3 - Agent on the primary node)

jajs_setup_cluster
     [-h logical-host-name]
     -d shared-directory-name

Format 4 (for setting up JP1/AJS3 - Agent on the secondary node)

jajs_setup_cluster
     [-h logical-host-name]

Description

The jajs_setup_cluster command sets up a JP1/AJS3 operating environment appropriate for the logical host. The command must be executed on both the primary and secondary nodes during setup of a cluster system environment.

Before you execute the jajs_setup_cluster command, make sure that the JP1/Base physical and logical environments have been set up.

The jajs_setup_cluster command creates a scheduler service on a logical host by copying the scheduler service environment from the physical host.

Execution privileges

In Windows: Administrators privileges

In UNIX: Superuser privileges

Arguments

-h logical-host-name

Specify the name of the logical host to be set up (a logical host name set in JP1/Base).

You can specify a character string of 1 to 32 bytes.

A logical host environment is created under the name specified for this option.

If this option is omitted, the value of the JP1_HOSTNAME environment variable is assumed. You can omit this option only when the JP1_HOSTNAME environment variable has been set.

Note that the primary node can be set up only when the specified logical host name can be resolved into an IP address.

-F scheduler-service-name

When setting up the primary node for JP1/AJS3 - Manager:
Specify the name of the scheduler service you want to create.
If you specify the name of an existing scheduler service or if a scheduler service has already been created on the logical host, the command terminates abnormally.

When setting up the secondary node for JP1/AJS3 - Manager:
Specify the scheduler service name that you specified on the primary node.
If no scheduler service is found on the specified logical host, the command terminates abnormally.

You can specify a character string of 1 to 30 bytes.

You cannot omit this option when you perform setup for JP1/AJS3 - Manager.

-d shared-directory-name

Specify the full path name of the mount-point directory for the shared disk used to contain information that the secondary node can inherit from the primary node. You must specify an existing directory. If you specify a non-existent directory, the command terminates abnormally. Do not specify a disk on a network drive.

You can specify a character string of 1 to 122 bytes.

You must specify this option when setting up the primary node. If you omit this option, the node is set up as the secondary node.

In the specified directory, the command creates the JP1AJS2 (in Windows) or jp1ajs2 (in UNIX) subdirectory, in which the environment definition files and execution environment for the logical host are created. However, if the subdirectory already exists, the command terminates abnormally. Before you use the jajs_setup_cluster command to set up the primary node, always mount the shared disk, and confirm that the subdirectory does not exist.

-n scheduler-service-ID-number

Use a decimal number to specify the number that identifies the scheduler service.

You can specify a value from 1 to 20.

You can specify this option only when you perform setup of the primary node for JP1/AJS3 - Manager.

Make sure that the ID number you specify is not used by the physical host or any logical host of the local host. If you specify an ID number that has already been used, the command terminates abnormally.

If you omit this option, the smallest available ID number is assumed.

-m {cold|warm|hot}

Specify the scheduler service startup mode.

You can specify this option only when you perform setup of the primary node for JP1/AJS3 - Manager.

If this option is omitted, the command assumes the value of the STARTMODE environment setting parameter for the scheduler service specified in the DEFAULTSERVICENAME environment setting parameter on the physical host.

-P embedded-database-port-number

Specify the port number of the embedded database used on the logical host if you also want to set up the embedded database during setup of the logical host.

You can specify a value from 5001 to 65535.

You cannot specify a port number that has already been used by another program. Make sure that the port number you specify is not used by another program. If the port number specified in this option is also used by another application, a problem with either the application or the embedded database occurs. If a problem occurs, change the port number of either the application or the embedded database.

You cannot omit this option if you also set up the embedded database during setup of the primary node for JP1/AJS3 - Manager.

You cannot specify this option with the -S option.

-I embedded-database-setup-ID

Specify _JFn (n: 0 to 9 or A to Z) as a four-character setup ID of the embedded database to be used on the logical host if you also set up the embedded database during setup of the logical host. Make sure that the setup ID you specify has not yet been registered in the system. If you specify a setup ID that has already been registered, the command terminates abnormally. You can use the ajsembdbidlist command to check the setup IDs that have already been registered. For details on the ajsembdbidlist command, see ajsembdbidlist in 2. Commands Used during Setup.

You cannot omit this option if you also set up the embedded database during setup of the primary node for JP1/AJS3 - Manager.

You cannot specify this option with the -S option.

-S

Specify this option if you want to skip setting up the embedded database during setup for the logical host, and perform advanced setup for the embedded database after the logical host has been set up.

For details about advanced setup for the embedded database, see D. Advanced Setup for the Embedded Database (in a Cluster Configuration) in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

You can specify this option only when you perform setup for JP1/AJS3 - Manager.

You cannot specify this option with the -P and -I option.

Notes

Action to be taken if an error occurs on the primary node

If an error occurs during execution of the jajs_setup_cluster command on the primary node, remove the cause of the error, and then delete logical host information. Then re-execute the command.

If an error occurs or a command is terminated forcibly during setup of the embedded database, the embedded database must be deleted from the logical host. Use the ajsembdbuninstl command to delete the embedded database on the logical host. For details on the ajsembdbuninstl command, see ajsembdbuninstl in 2. Commands Used during Setup. Note that you must delete the embedded database from the logical host before deleting the logical host.

The procedure for deleting logical host information is described below.

To delete logical host information:
  1. Delete the shared files and directories on the shared disk.
    Delete the JP1/AJS3 shared disk information.
    In Windows: shared-disk\JP1AJS2
    In UNIX: shared-disk/jp1ajs2
  2. Delete the JP1/AJS3 common definition information on the logical host.
    To do this, execute the commands shown below. For details on the jbsunsetcnf command, see the Job Management Partner 1/Base User's Guide.
    jbsunsetcnf -i -h logical-host-name -c JP1AJS2
    jbsunsetcnf -i -h logical-host-name -c JP1AJS2COMMON
    jbsunsetcnf -i -h logical-host-name -c JP1NBQAGENT
    jbsunsetcnf -i -h logical-host-name -c JP1NBQMANAGER#
    jbsunsetcnf -i -h logical-host-name -c JP1NBQCLIENT
    jbsunsetcnf -i -h logical-host-name -c JP1NBQNOTIFY
    jbsunsetcnf -i -h logical-host-name -c JP1AOMMANAGER#
    jbsunsetcnf -i -h logical-host-name -c JP1AOMAGENT
    jbsunsetcnf -i -h logical-host-name -c JP1AJSMANAGER#
    jbsunsetcnf -i -h logical-host-name -c JP1AJS2COMMON
    jbsunsetcnf -i -h logical-host-name -c JP1QLAGENT
    jbsunsetcnf -i -h logical-host-name -c JP1AJS2CONSOLEMANAGER#

    #
    Execute this command only when you delete logical host information from JP1/AJS3 - Manager.
    If the data to be deleted does not exist during execution of the command, the following message might be output: KAVA0405-I The specified character-string-specified-for-the-c-option does not exist (logical-host-name). Processing stops.. If this message is output, ignore it.

Return values

0 to 9 Normal end
10 to 49 End with warning. The command terminated but requires manual operations.
50 or greater Abnormal end

Additional information

When setup is performed by specifying the -P and -I options, the embedded database is set up with the following settings:

For the settings other than the above, the default settings are used.

Example 1

In this example, the command also sets up the embedded database under the following conditions during setup of the primary host for JP1/AJS3 - Manager:

 
jajs_setup_cluster -h lhost1 -F AJS3SCHEDULE001 -d "F:\shdsk\lhost1" -P 22201 -I _JF1

Example 2

In this example, the command sets up the primary host for JP1/AJS3 - Manager under the following conditions, but does not set up the embedded database:

 
jajs_setup_cluster -h lhost2 -F AJS3SCHEDULE002 -d "F:\shdsk\lhost2" -n 3 -m hot -S

Example 3

In this example, the command also sets up the embedded database under the following conditions during setup of the secondary host for JP1/AJS3 - Manager:

 
jajs_setup_cluster -h lhost1 -F AJS3SCHEDULE001

Example 4

In this example, the command sets up the secondary host for JP1/AJS3 - Manager under the following conditions, but does not set up the embedded database:

 
jajs_setup_cluster -h lhost2 -F AJS3SCHEDULE002 -S

Example 5

In this example, the command sets up the primary host for JP1/AJS3 - Agent under the following conditions:

 
jajs_setup_cluster -h lhosta1 -d "F:\shdsk\lhosta1"

Example 6

In this example, the command sets up the secondary host for JP1/AJS3 - Agent under the following conditions:

 
jajs_setup_cluster -h lhosta1

[Contents][Back][Next]

[Trademarks]

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