hvrsuspend – Suspend (or un–suspend) jobs
hvrsuspend [–options] hubdb jobs...
In the first form hvrsuspend will force jobs in the HVR Scheduler into SUSPEND state. The second form (with option –u) will un–suspend jobs, which means that they will go into PENDING or RUNNING state.
Jobs can either be specified explicitly (e.g. chn–cap–locx) or they can be partially specified (e.g. chn–cap which matches all capture jobs). If only a channel name is specified, then hvrsuspend suspends all jobs in the channel.
The first argument hubdb specifies the connection to the hub database. This can be an Oracle, Ingres, SQL Server, DB2, DB2 for I, PostgreSQL, or Teradata database depending on its form. See further section Calling HVR on the Command Line.
This command connects to the HVR Scheduler so the scheduler must be already running.
|–Cpub_cert||Public certificate for encrypted connection to hub machine. This must be used with option –R.|
|–Enm=val||Set environment variable nm to value val.|
|–Kpair||SSL public certificate and private key of local machine. If pair is relative, then it is found in directory $HVR_HOME/lib/cert. Value pair specifies two files; the names of these files are calculated by removing any extension from pair and then adding extensions .pub_cert and .priv_key. For example, option –Khvr refers to files $HVR_HOME/lib/cert/hvr.pub_cert and $HVR_HOME/lib/cert/hvr.priv_key.|
|–Llogin/pwd||Login/password for remote hub machine. Must be used with option –Rnode:port.|
|–Rnode:port||Remote hub machine node name and TCP/IP port number. Must be used with option –Llogin/pwd.|
A change has been made to the HVR catalogs for location d01 but for the change to take effect the job's script must be regenerated.
$ hvrsuspend hubdb chn # Halt all replication jobs $ hvrinit –oj –ld01 hubdb chn # Regenerate script for location d01 $ hvrsuspend –u hubdb chn # Reactivate replication