Installing Job Scheduler for the Cluster Edition

All instances in the cluster share a single Job Scheduler. You can set up Job Scheduler so that, in the event the instance on which it is running fails, Job Scheduler can fail over to another node.

1. �Create a device called sybmgmtdev with a size of at least 90MB on a shared raw device that is accessible to all instances in the cluster.

2. Run the installjsdb script:

   isql –Usa –Psa_password –Sservername 
   –i $SYBASE/$SYBASE_ASE/scripts/installjsdb
   

   You must have the directory with the location of the isql executable ($SYBASE/$SYBASE_OCS/bin) in your path.

   The installjsdb script looks for the sybmgmtdb database. If it exists, the script creates Job Scheduler tables and stored procedures. If it does not exist, the script looks for a sybmgmtdev device on which to create the sybmgmtdb database, tables, and stored procedures.

   If the installjsdb script finds neither a sybmgmtdev device nor a sybmgmtdb database, it creates a sybmgmtdb database on the master device. Sybase strongly recommends that you remove the sybmgmtdb database from the master device to make recovery easier in the case of a disk failure.

3. Create a directory services entry for the JS Agent in the interfaces file using either dscp, dsedit, or a text editor as appropriate. Sybase suggests that you name the entry “clustername_JSAGENT”.

   To enable HA failover, the JS Agent entry must contain master and query rows for each node in the cluster. For example, to add a JSAGENT entry for the cluster “mycluster” with two nodes, the syntax might be:

   mycluster_JSAGENT
       master tcp /dev/tcp node_name1 17780
       query tcp /dev/tcp node_name1 17780
       master tcp /dev/tcp node_name2 16780
       query tcp /dev/tcp node_name2 16780
   
   

   The node name must match the name returned by the uname -n command executed at the UNIX prompt. For example, on host “myxml1,” uname -n returns the value “myxml1.sybase.com,” and on host “myxml2”, uname -n returns the value “myxml2.sybase.com”. The correct entry for JS Agent is:

   mycluster_JSAGENT
       master tcp /dev/tcp myxmll.sybase.com 17780
       query tcp /dev/tcp myxmll.sybase.com 17780
       master tcp /dev/tcp myxml2.sybase.com 16780
       query tcp /dev/tcp myxml2.sybase.com 16780
   
   

   You must specify a port not currently in use.

   See the System Administration Guide, Volume 1 for more information on directory services.

4. Using sp_addserver, create an entry in the sysservers table for the cluster. For example:

   sp_addserver SYB_JSAGENT, null, mycluster_JSAGENT
   

   See the Reference Manual: Commands for more information on sp_addserver.

5. Enable Job Scheduler:

   sp_configure "enable job scheduler," 1
   

6. To start Job Scheduler, you can either restart the server, or execute:

   use sybmgmtdb�
   go�
   sp_js_wakeup "start_js", 1
   go�
   

7. To determine the instance on which Job Scheduler is running, query the global variable @@jsinstanceid.

   select @@jsinstanceid
   go