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
      [-M {s|m|l}]
      [-E {byte | sjis}]
      [-B] |
       -S} |
      [-S | -C embedded-database-settings-file-name]}
     [-R]

For JP1/AJS3 - Agent:

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

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 |
      [-M {s|m|l}]
      [-E {byte | sjis}]
      [-B] |
      [-S]}

jajs_setup_cluster
     [-h logical-host-name]
     -F scheduler-service-name
     [-S | -C embedded-database-settings-file-name]

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

jajs_setup_cluster
     [-h logical-host-name]

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

To Page Top

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.

This command creates a logical host environment by copying the environment of the physical hosts. Scheduler services are created by copying the settings of the default scheduler service on the physical hosts. If no scheduler service has been defined as the default, the command creates the scheduler service on the logical host by copying the setup of the scheduler service that has the smallest identifier number (set in the AJSSERVICEID environment setting parameter) among all the existing scheduler services on the physical host.

With the -R option specified, a scheduler service is added to the JP1/AJS3 logical host when setup of JP1/AJS3 - Manager on the primary and secondary nodes at the remote site has finished.

To Page Top

Execution privileges

In Windows: Administrators privileges

In UNIX: Superuser privileges

To Page Top

Arguments

To Page Top

Notes

• Before you execute this command, stop all JP1/AJS3 services.

• Do not execute this command more than once in quick succession.

• Do not terminate this command forcibly.

• This command copies the jp1ajs_spmd.conf file from the physical host to a logical host. For this reason, if you edit the jp1ajs_spmd.conf file on the physical host to set the startup of a process or to set the suppression of the startup process, the settings are passed to the logical host. In such cases, a process unnecessary for the logical host might start, or a process required for the logical host might not start. If the file was edited on the physical host, edit the file on the logical host so that only necessary processes are started.

  For details about suppressing the startup process, see 13.1.6 Limiting JP1/AJS3 - Manager resources to those used for job operation in the JP1/Automatic Job Management System 3 Administration Guide.

• 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.

• The command might terminate abnormally, outputting the following message: Database maintenance failed (func code=xx, error code=yy). If this message is output, take appropriate action according to the following table.

  Value of xx	Action
  1	Correct the error indicated in the message output before this message according to the action to be taken if an error occurs in the ajsembdbbuild command. Then re-execute the command.
  2	Correct the error indicated in the message output before this message according to the action to be taken if an error occurs in the ajsembdbsetup command. Then re-execute the command.
  3	Correct the error indicated in the message output before this message according to the action to be taken if an error occurs in the ajsembdbunset command. Then re-execute the command.
  4	Correct the problem according to the error message output before this message, and then re-execute the command.
  5	Check 2.7.8(1) Action to be taken if an error occurs during embedded database maintenance in the manual JP1/Automatic Job Management System 3 Troubleshooting for error code yy in the output message, and correct the problem.
  6	Check 2.7.8(2) Action to be taken if an error occurs during installation of the embedded database in the manual JP1/Automatic Job Management System 3 Troubleshooting for error code yy in the output message, and correct the problem.
  7	Check 2.7.8(3) Action to be taken if an error occurs during uninstallation of the embedded database in the manual JP1/Automatic Job Management System 3 Troubleshooting for error code yy in the output message, and correct the problem.

• If an error occurs during command execution on the primary node, correct the cause of the error, and then delete the logical host information as described in Action to be taken if an error occurs on the primary node below. Then re-execute the command.

• If an error occurs during command execution on the secondary node, correct the cause of the error, and then re-execute the command (without deleting logical host information).

• Do not delete the scheduler service specified in the -F option when you set up JP1/AJS3 - Manager on the primary node. If you delete that scheduler service, setup on the secondary node will fail. If you need to delete the scheduler service, delete the information on the primary node as described in Action to be taken if an error occurs on the primary node below. Then perform the setup again, starting from the primary node.

• If the scheduler service on the physical host has an operation profile, the operation profile will be copied to the logical host when you execute this command. Delete the copied operation profile as needed.

• This command copies the executable-command settings file from the physical host to the logical host. After the file is copied, the logical host inherits the settings for commands that can be executed from the physical host. If commands can be executed on the physical host from JP1/AJS3 - View, edit the executable-command settings file on the logical host to allow the execution of necessary commands only. For details about how to specify settings in the executable-command settings file, see 11.3.18 Allowing execution of JP1/AJS3 commands in the JP1/Automatic Job Management System 3 Operator's Guide.

• To change the directory used by the scheduler service, perform the following.

  • To change the database directory, change the value of the AJSDBDIRECTORY environment setting parameter.

  • To change the temporary directory, change the value of the AJSTMPDIR environment setting parameter.

  • To change the job information directory, change the value of the JOBINFDIR environment setting parameter.

  • To change the backup information directory, change the value of the AJSBKUROOT environment setting parameter.

  For details about these parameters, see 20.4.2 Details of the environment setting parameters for scheduler services in the JP1/Automatic Job Management System 3 Configuration Guide.

To Page Top

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 setup of the logical host fails and the jajs_setup_cluster command outputs error message KAVS1126-E, you must delete the embedded database on the logical host. You do not need to do so, however, if you specified the -S option to skip setup of the embedded database, and logical host setup fails without error message KAVS1126-E appearing.

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 JP1/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 JP1QLAGENT

   #

   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.

To Page Top

Permissions for sub-directories in the shared directory created at setup of the primary node

For Windows

Full Control is set for the Everyone group for all folders created in the shared-folder\jp1ajs2 path and listed in the table below. For all other folders, the permissions of the upper-level folder apply.

For folders above shared-folder\jp1ajs2, set Full Control for users who have SYSTEM and Administrators privileges, and set Read & Execute or a higher privilege for all other users who perform settings to pass these settings to the files and folders under the folder.

Important

Do not change the permission for folders for which Everyone has Full Control. If you do so, the logical host will not start.

Table 2‒3: Folders for which Everyone has Full Control

No.	Folder path	JP1/AJS3 - Manager	JP1/AJS3 - Agent
1	shared-folder\jp1ajs2\backup	Y	--
2	shared-folder\jp1ajs2\database	Y	--
3	shared-folder\jp1ajs2\jobinf	Y	--
4	shared-folder\jp1ajs2\log	Y	Y
5	shared-folder\jp1ajs2\sys	Y	Y
6	shared-folder\jp1ajs2\tmp	Y	Y

Legend:

Y: Supported

--: Not supported

For UNIX

Directories are created in the shared-directory/jp1ajs2 path and 777 permission is set for all directories listed in the table below. For all sub-directories not listed in the table, 755 permission is set.

When the AJS administrator sets up a primary node, read and write permissions of the JP1 administrator group are required for the upper-level directory of shared-directory/jp1ajs2.

Important

Do not change the permission for directories for which 777 permission is set. If you do so, the logical host will not start.

Table 2‒4: Directories for which 777 permission is set

No.	Directory path	JP1/AJS3 - Manager	JP1/AJS3 - Agent
1	shared-directory/jp1ajs2/backup/schedule	Y	--
2	shared-directory/jp1ajs2/database/schedule/scheduler-service-name	Y	--
3	shared-directory/jp1ajs2/jobinf	Y	--
4	shared-directory/jp1ajs2/jobinf/schedule/scheduler-service-name	Y	--
5	shared-directory/jp1ajs2/jobinf/delete	Y	--
6	shared-directory/jp1ajs2/log	Y	Y
7	shared-directory/jp1ajs2/log/JAJS_SETUP	Y	Y
8	shared-directory/jp1ajs2/log/jpqagent	Y	Y
9	shared-directory/jp1ajs2/log/jpqclient	Y	Y
10	shared-directory/jp1ajs2/log/jpqmanager	Y	--
11	shared-directory/jp1ajs2/log/jpqnotify	Y	Y
12	shared-directory/jp1ajs2/log/schedule	Y	--
13	shared-directory/jp1ajs2/log/schedule/scheduler-service-name	Y	--
14	shared-directory/jp1ajs2/tmp	Y	Y
15	shared-directory/jp1ajs2/tmp/schedule	Y	--
16	shared-directory/jp1ajs2/tmp/schedule/scheduler-service-name	Y	--

Legend:

Y: Supported

--: Not supported

To Page Top

Return values

To Page Top

Additional information

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

• Database mode: small scale

• System log: Not used

• Duplex of system file: Disabled

• Unload log file: Not used

• Data area directory:

  For Windows

  shared-folder\jp1ajs2\embdb\value-specified-in-the-I-option\dbarea

  For UNIX

  shared-directory/jp1ajs2/embdb/value-specified-in-the-I-option/dbarea

• Work area directory:

  For Windows

  JP1/AJS3-installation-folder\embdb\value-specified-in-the-I-option\dbarea

  For UNIX

  /opt/jp1ajs2/embdb/value-specified-in-the-I-option/dbarea

• Embedded database practical directory:

  For Windows

  JP1/AJS3-installation-folder\embdb\value-specified-in-the-I-option

  For UNIX

  /opt/jp1ajs2/embdb/value-specified-in-the-I-option

• Database area auto-increment function: Enabled

• System log auto-increment function: Enabled

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

To Page Top

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:

• logical host: lhost1

• scheduler service: AJS3SCHEDULE001

• shared directory name: F:\shdsk\lhost1

• embedded database port number: 22201

• embedded database setup ID: _JF1

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

To Page Top

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:

• logical host: lhost2

• scheduler service: AJS3SCHEDULE002

• shared directory name: F:\shdsk\lhost2

• scheduler service ID number: 3

• scheduler service startup mode: hot start

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

To Page Top

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:

• logical host: lhost1

• scheduler service: AJS3SCHEDULE001

jajs_setup_cluster -h lhost1 -F AJS3SCHEDULE001

To Page Top

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:

• logical host: lhost2

• scheduler service: AJS3SCHEDULE002

jajs_setup_cluster -h lhost2 -F AJS3SCHEDULE002 -S

To Page Top

Example 5

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

• logical host: lhosta1

• shared directory name: F:\shdsk\lhosta1

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

To Page Top

Example 6

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

• logical host: lhosta1

jajs_setup_cluster -h lhosta1

To Page Top