Document how to figure out the hostname used to target job steps to a server.

git-svn-id: svn://svn.pgadmin.org/trunk/pgadmin3@7538 a7884b65-44f6-0310-8a51-81a127f17b15

diff --git a/docs/en_US/pgagent-jobs.html b/docs/en_US/pgagent-jobs.html
index 3d76e6b8b5564396005e3e621dfa1eda71806f2a..0495f104b04786d67204a947ade9e52e51db47a9 100644 (file)
--- a/docs/en_US/pgagent-jobs.html
+++ b/docs/en_US/pgagent-jobs.html
@@ -29,10 +29,20 @@ details of each run of the job.</P>
 schedules. When configuring a job, we specify the job name, whether or\r
 not it is enabled, a job class or category, and optionally the hostname\r
 of a specific machine running pgAgent, if this job should only run on\r
-that specific server. If left empty, any server may run the job. This\r
-is not normally an issue for SQL-only jobs, however any jobs with\r
-batch/shell steps may need to be targetted to a specific server. A\r
-comment may also be included.</P>\r
+that specific server. If left empty (which is normally the case), any \r
+server may run the job. This is not normally needed for SQL-only jobs, \r
+however any jobs with batch/shell steps may need to be targetted to a \r
+specific server. A comment may also be included.</P>\r
+\r
+<p><b>Note:</b> It is not always obvious what value to specify for the\r
+Host Agent in order to target a job step to a specific machine. With pgAgent\r
+running on the required machines and connected to the scheduler database, \r
+the following query may be run to view the hostnames as reported by each\r
+agent:</p>\r
+\r
+<p><i>SELECT jagstation FROM pgagent.pga_jobagent</i></p>\r
+\r
+<p>Use the hostname exactly as reported by the query in the Host Agent field.</p>\r
 \r
 <P><center><img src="images/pgagent-jobproperties.png" alt="Job properties"></center></P>\r
 \r