The DNPScanner should have an entry in the environment table file, RtapEnvTable, for every environment requiring the DNPScanner.
For a detailed description of the columns in the RtapEnvTable
refer to RtapEnvTable(5) in the RTAP Reference Manual.
Create an entry in the RtapEnvTable for the DNPScanner as follows; where `#' represents any number selected from the allowed range for the field:
| Field: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| Entry: | 0 | 0 | see below | N | Y | A | N | # | # | DNPScanner |
Specifically, for DNPScanner:
| Field 1: | Process Number - enter a 0 (zero) to allow multiple copies (one per comm-port). |
| Field 2: | Autostart Phase - should be 0 (zero) since the DNPScanner should not start automatically. It is started by the scan manager based on an entry in the scan config point. |
| Field 3: | Autostart as user "rtap" - since DNPScanner; is not autostarted, this field is irrelevant. |
| Field 4: | Restart on Termination - specify `N' (no) for this field, since the scan manager restarts the scan task when required. |
| Field 5: | Multiple Copies Allowed - specify `Y' (yes) for this field, since multiple comm-ports can use the same scan task. The scan manager will start one copy for each comm-port. |
| Field 6: | Cleanup on Termination - since abnormal shutdowns should be logged, specify `A' for this field. |
| Field 7: | Care About Process Terminations - use `N' (no), since the DNPScanner is not directly associated with any other system process, and therefore, not concerned with their termination. |
| Field 8: | Shutdown Order - the DNPScanner should be shutdown after the scan manager since the scan manager tries to stop the scan task cleanly with a message request. If this fails, the process scheduler will shut down the scan task. |
| Field 9: | Priority - see RtapEnvTable(5) for more detail. |
| Field 10: | Command Line - see DNPScanner man page for possible command line arguments. |