<PRE>\r
Usage:\r
pgAgent REMOVE <serviceName>\r
- pgAgent INSTALL <serviceName> [options] <connect-string>\r
+ pgAgent INSTALL <serviceName> [options] <connect-string>\r
+ pgAgent DEBUG [options] <connect-string>\r
\r
options:\r
-u <user or DOMAIN\user>\r
\r
<P>The service may then be started from the command line using <I>net start pgAgent</I>,\r
or from the <I>Services</I> control panel applet. Any logging output or errors will be\r
-reported in the Application event log.</P>\r
+reported in the Application event log. The DEBUG mode may be used to run pgAgent from a\r
+command prompt. When run this way, log messages will output to the command window.</P>\r
\r
<H3>Security concerns</H3>\r
<P>pgAgent is a very powerful tool, but does have some security considerations\r
<P>Each step consists of the details shown on the screenshot below, most of\r
which are self-explanatory. If <I>Kind</I> is set to SQL, then it goes without\r
saying that a database against which to run the script must be selected. If \r
-set to <I>Batch</I>, the database should be left blank. The <I>On Error</I> option \r
-controls how failure of this step will affect the\r
+set to <I>Batch</I>, the database/connection string should be left blank. \r
+The <I>On Error</I> option controls how failure of this step will affect the\r
status of the overall job.</P>\r
\r
<P><center><img src="images/pgagent-stepdetails.png" alt="Step details"></center></P>\r