|
|
The Ascii/Commandline engine will check the directory you setup in the PG Admin program for files that have .asc as an extension (additional polling directories/filenames can be setup using the 'Advanced ascii polling' option. see the section above for more information). It will check for the files at the polling interval (in seconds) which is also setup in the PG Admin program. When the directory is polled, and a file is found, it is immediately moved to the 'process' subdirectory (underneath the polled directory) and given a unique filename (the .asc is replaced with a unique number). If in the same polling period, two or more files are put into the polled directory with the same filename, the first file will be overwritten by the second. The files are not given a unique name until the directory is actually polled. To avoid this, if the files are being written by an application, be sure to use unique filenames. If the sendpage program is being used, unique filenames are automatically generated. When the message is polled, if the format of the message or the recipient name is invalid, it will be immediately moved to the 'bad' subdirectory (under the polled directory). The file will have the same filename it was originally given, but the extension will be changed to a unique number. If the message is in a valid format and the recipient is also valid, the message will be moved to the 'process' subdirectory (under the polled directory) and then given to the paging engine for delivery. When the paging engine is done with the message, it will be moved from the 'process' subdirectory to either the 'good' or the 'bad' subdirectory depending on the ability of the engine to send the message to the carrier. Application programs can check the 'process', 'good' and 'bad' subdirectories for the original filename (with .* as an extension), to verify the status of the message. Messages are purged from the 'good' and 'bad' directories when they are older (in days) than the 'purge after' setting in the PG Admin program.
