Changes between Version 233 and Version 234 of ippToPsps

Timestamp:

Apr 2, 2012, 3:14:43 PM (14 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -170 +170 @@
 
 This will produce an IN batch, publish it, then stop (the IN-batch MySQL tables will also be updated in the local scratch database).
-== pollodm.py ==
-
-{{{pollodm.py}}}'s job is to poll the PSPS ODM webservice to establish the status of each batch as it passes through the PSPS system. Gathering this information allows {{{cleanup.py}}} to know when it can delete existing copies of batches.
-
+== pollOdm.py ==
+
+{{{pollOdm.py}}}'s job is to poll the PSPS ODM webservice to establish the status of each batch as it passes through the PSPS system. Gathering this information allows {{{cleanup.py}}} to know when it can delete existing copies of batches.
+
+{{{pollOdm.py}}} takes a few extra args, as shown here:
+
+{{{
+Usage: pollOdm.py <configPath> <P2|ST|OB|all> <unloaded|unmergeworthy|unmerged|all> [hours]
+}}}
+
+Where the first argument sets batch type and the second which PSPS stage to check. So, example usage might be:
+
+{{{
+./run.sh pollOdm.py someConfig all all 1
+}}}
 == cleanup.py ==