| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | archive log #(+) | 0;1 | NUMERIC | B | The Log # number is used to identify a unique archive/purge operation for a single file. The number will be equal to the internal entry number of the Log entry. | |
| .02 | search template | 0;2 | FREE TEXT | C | This field contains the name of the Search Template used to contain the list of entries to be archived/purged. This name is the .01 field for the template entry in the SORT TEMPLATE file (#.401). The name of the template is stored instead of a hard pointer to the SORT TEMPLATE file because the template is deleted from the file after the entries have been purged. The name of the template is the string "IB ARCHIVE/PURGE #" concatenated with the Archive Log # (field .01). | |
| .03 | archive file | 0;3 | POINTER | 1 | D | This field points to the FILE file (#1) and represents the file to be archived/purged. The Billing data files subject to archiving/purging currently are: 350 INTEGRATED BILLING ACTION 351 CATEGORY C BILLING CLOCK 399 BILL/CLAIMS |
| .04 | # records archived | 0;4 | NUMERIC | This field will contain the number of entries which have been processed in each sequential archive/purge operation. The 'Search' option will update the field with the number of entries which have met the search criteria. The 'Archive' option will update this field with the number of entries archived. The 'Purge' option will update the field with the number of entries purged. Also, the 'Delete Entry From Search Template' option will update the field when entries from the template are deleted. | ||
| .05 | log status | 0;5 | SET OF CODES | 1:OPEN 2:CLOSED 3:CANCELLED | E | This field contains the current status of the archive/purge operation. The status will be OPEN when the log entry is created, and CLOSED after successfully purging archived entries. The entry will be CANCELLED if an error is detected during processing which invalidates the operation. |
| 1.01 | search begin date/time | 1;1 | DATE-TIME | The date/time at which the search was initiated is automatically stuffed into this field by the 'Search' option. | ||
| 1.02 | search end date/time | 1;2 | DATE-TIME | The date/time at which the search was completed is automatically stuffed into this field by the 'Search' option. The existence of this field in the log entry assures that the search on the file was successful, and thus the field is used as the flag to allow archiving. | ||
| 1.03 | search initiator | 1;3 | POINTER | 200 | This field conatins the individual who queued the search on the file. The field is updated by a trigger when the SEARCH BEGIN DATE/TIME field is updated. | |
| 2.01 | archive begin date/time | 2;1 | DATE-TIME | The date/time that the archiving of data is initiated is automatically stuffed into this field by the 'Archive' option. | ||
| 2.02 | archive end date/time | 2;2 | DATE-TIME | The date/time that the archiving of data was completed is automatically stuffed into this field by the 'Archive' option. The existence of this field in the log entry assures that archiving was successful, and thus the field is used as a flag to allow purging. | ||
| 2.03 | archive initiator | 2;3 | POINTER | 200 | This field contains the individual who archived the file. The field is updated by a trigger when the ARCHIVE BEGIN DATE/TIME field is updated. | |
| 3.01 | purge begin date/time | 3;1 | DATE-TIME | The date/time that purging is initiated is automatically stuffed into this field by the 'Purge' option. | ||
| 3.02 | purge end date/time | 3;2 | DATE-TIME | The date/time that the purging of data was completed is automatically stuffed into this field by the 'Purge' option. When this field is updated the status of the log entry is updated to CLOSED. | ||
| 3.03 | purge initiator | 3;3 | POINTER | 200 | This field contains the individual who purged the file. The field is updated by a trigger when the PURGE BEGIN DATE/TIME field is updated. |
Not Referenced