jp1ajs2_setup_cluster (UNIX only)
- Organization of this page
Format
jp1ajs2_setup_cluster
-h logical-host-name
[-d shared-directory-name]
[-n value]
[-m {cold|warm|hot}]
[-v]
Description
The jp1ajs2_setup_cluster command sets up the operating environment of the logical host for compatibility with JP1/AJS2 whose version is 8 or earlier.
- JP1/AJS3 - Manager
-
When the JP1/AJS3 database is to be operated in a compatible ISAM configuration, the jp1ajs2_setup_cluster command is used to set up the operating environment of the logical host in a compatible ISAM configuration.
- JP1/AJS3 - Agent
-
Use the jajs_setup_cluster command to set up the operating environment of the logical host. For details about the jajs_setup_cluster command, see jajs_setup_cluster in 2. Commands Used during Setup.
In a cluster environment, set up the operating environment for both the primary node and secondary node.
To use this command to set up a primary node, you must first set up both the JP1/Base physical host environment and logical host environment.
Before executing this command, make sure that you stop all JP1/AJS3 services.
If you use this command to set up the JP1/AJS3 - Manager environment on the primary node, make sure that you execute the command when only one scheduler service is running on the physical host.
This command sets up the following:
-
JP1/AJS3 - Manager
- Primary node setup
-
Sets up definition information for the logical host as JP1 common definition information.
Creates a definition file and execution environment for a logical host on a shared disk. The definition file is copied from the physical host environment (actually, not all the files are copied).
Sets the write mode for the ISAM database to sync.
Set sync for the event-start file writing mode.
Sets JP1/AJS3 startup mode.
Changes the communication method for the logical and physical hosts to the IP bind method.
Set Y for the event-start option used at the end of the detail process.
- Secondary node setup
-
Changes the communication method for the logical and physical hosts to the IP bind method.
-
JP1/AJS3 - Agent
- Primary node setup
-
Sets the definition information for the logical host as JP1 common definition information.
Creates a definition file and execution environment for the logical host in the shared disk. The definition file is copied from the physical host environment (actually, not all the files are copied).
Set sync for the event-start file writing mode.
Changes the communication method used by the logical and physical hosts to the IP bind method.
Set Y for the event-start option used at the end of the detail process.
- Secondary node setup
-
Changes the communication method used by the logical and physical hosts to the IP bind method.
Execution privileges
Superuser privilege
Arguments
-h logical-host-name
Specify the name of the logical host to be set up (logical host name set up in JP1/Base).
You can specify 1 to 63 characters (bytes).
The system creates an environment under the logical host name specified by this option.
-d shared-directory-name
Specify the name of the directory on which you have mounted the shared disk used to store the information passed from the primary node to the secondary node.
You can specify 1 to 165 characters (bytes).
Specify this option when setting up the primary node.
If you omit this option, the system sets up the secondary node.
The system creates specified-shared-directory-name/jp1ajs2 as the shared directory and creates the environment definition file and execution environment for the logical host in the shared directory. Mount the shared disk before executing this command.
-n value
Specify the identification number of the desired scheduler service. A scheduler service named AJSROOTn will be created.
You can specify a value from 1 to 20.
If you omit this option, the system assumes 2 (creates AJSROOT2). AJSROOT1 is used in the physical host environment.
Specify a scheduler service identification number that is not used by the physical host or any logical host. When setting up a logical host, if you specify a scheduler service identification number that is already used by the physical host or another logical host, the command terminates normally, but the same scheduler service is created on multiple hosts. JP1/AJS3 does not operate correctly in such an environment, so you should delete the unnecessary logical host.
For details about deleting a logical host, see 17.2.8 Deleting logical hosts in the JP1/Automatic Job Management System 3 Configuration Guide.
You can specify this option only when setting up the primary node.
-m {cold|warm|hot}
Specify how the scheduler service is to be started.
-
cold
Cold-starts the scheduler service.
-
warm
Warm-starts the scheduler service.
-
hot
Hot-starts the scheduler service.
You can specify this option only when setting up the primary node.
If this option is omitted, the value specified in the STARTMODE environment setting parameter is assumed.
-v
Displays the processing status.
Notes
-
This command can be used in a compatible ISAM configuration only. In the standard configuration, use the jajs_setup_cluster command.
-
You cannot use this command if a system block has been placed on a physical host or logical host on the target machine.
-
This command can be executed in UNIX only. It cannot be executed in Windows.
-
ISAM sets up the scheduler database for a scheduler service created when this command is executed.
The embedded database cannot be used as a scheduler database.
-
This command copies the jp1ajs_spmd.conf file from the physical host to a logical host. Therefore, processes not necessary for the logical host might be started on the logical host. If the file was edited on the physical host, edit the file on the logical host so that only necessary processes are started.
Return values
|
0 |
Normal end |
|
1 |
Abnormal end |
Examples
The jp1ajs2_setup_cluster commands in the following examples set up the JP1/AJS3 operating environment.
The table below lists the setup conditions.
|
Logical host name |
lnode0 |
|
Shared directory name |
/shdsk/lnode0 |
|
Scheduler service name |
AJSROOT2 |
|
How to start the scheduler service |
Hot start (The states of a jobnet and job are taken over when a failover occurs.) |
- Example of specifying the jp1ajs2_setup_cluster command that sets up a primary node:
# jp1ajs2_setup_cluster -h lnode0 -d /shdsk/lnode0 -n 2 -m hot
- Example of specifying the jp1ajs2_setup_cluster command that sets up a secondary node:
# jp1ajs2_setup_cluster -h lnode0