Synopsis
stemsetdbpath {-p | dbpath [-n] [-r] [-sys subsystem number]}
Description
The stemsetdbpath command changes a database directory of the Master Schedule Management function. Use this command when you relocate the database directory of the Master Schedule Management function on a shared disk in a cluster environment.
When executing the command on the active node, change the registration information of the database directory of the Master Schedule Management function, and then copy it, without using the -n option. For the standby node, use the -n option to change the registration information only.
Options
-p
Displays a present database directory.
dbpath
Specify a full path to the database directory to which you want to move. To move the database directory of the Master Schedule Management function, append "stemDBn (n: subsystem number) to the desired directory.
-n
Specify this option when changing only the registration information of the database directory. If omitted, the database is relocated to the destination directory.
-r
Backs up the database before the database directory is changed. Create a stemDBn.local (n: subsystem number) in the same directory as the previous one to save the database. If omitted, the database is not saved.
-sys subsystem number
Specify the subsystem number whose database directory is changed, using a range of 0 to 9. If omitted, the default is subsystem 0.
Return Values
Completed
Abended
Command Location
Windows | Systemwalker Operation Manager Installation Directory\mpwalker.jm\bin |
Privilege Required
System administrator (user belonging to the Administrator group or superuser) privileges are required.
Cautions
This command must be executed in an environment where the Jobscheduler service is inactive.
Example
When you deploy a database directory on a shared disk on the active node while creating a cluster environment in a 1:1 active/standby configuration:
stemsetdbpath.exe y:\disk -sys 0
The database directory information of the subsystem 0 is changed into "y:\disk\stemDB0" to which the database will be moved.
When you deploy a database directory on a shared disk on the standby node while creating a cluster environment in a 1:1 active/standby configuration:
stemsetdbpath.exe y:\disk -n -sys 0
The database directory information of the subsystem 0 is changed into "y:\disk\stemDB0". The database is not moved.
When you deploy the database directory of the subsystem 1 on a shared disk on the active node while creating a cluster environment in a 2-node standby configuration:
stemsetdbpath.exe y:\disk -sys 1
The database directory information of the subsystem 1 is changed into "y:\disk\stemDB1" to which the database to be moved.
When you display the current database directory:
stemsetdbpath.exe -p
The database directory currently configured is displayed.
Execution Results/Output Format
When the database directory is changed:
MpStem: INFO: stemsetdbpath.exe exited normally.
When the database is displayed:
No. path -------------------------------------------------- 1 z:\omgr1\mpstemsv\stemDB1 2 y:\omgr2\mpstemsv\stemDB2
Error contents are output to the standard output.