Purge Processes

The system enables you to purge the historical records from certain objects that generate a large number of entries and may become unwieldy over time.

The following table lists the various background processes that are used to purge the historical data:
Batch Control ID	Program Name	Description	Multiple Threads	Extra Parameters	Records Between Commits / Minutes Between Cursor Re-Initiation
BCUP-PRG	CIPCDBSB	Purges `completed` billable charge upload objects.	Yes	NO-OF-DAYS = number of days after the creation date that a `completed` billable charge upload object should be purged MAX-ERRORS = Used to override the maximum number of errors after which the batch must be terminated.	200/15
PYUP-PRG	CIPPDUSB	Purges `completed` tender upload objects.	Yes	NO-OF-DAYS = number of days after the related tender's payment event's creation date that a `completed` tender upload object should be purged MAX-ERRORS = Used to override the maximum number of errors after which the batch must be terminated.	200/15
TD-PURGE	CIPQDTDB	Purges `completed` To Do entries.	Yes	NO-OF-DAYS = number of days after the completion date that a `completed` To Do entry should be purged DEL-ALL-TD-SW = Y or N. If this switch is Y, all `completed` To Do entries that are old enough will be deleted. If N, the next parameter defines the specific type of To Do entry that will be deleted. DEL-TD-TYPE-CD. This parameter is only used if DEL-ALL-TD-SW is N. It contains the To Do type code whose `completed` entries will be deleted. MAX-ERRORS = Used to override the maximum number of errors after which the batch must be terminated.	200/15
XMLUP-PR	CIPXDXUB	Purges `completed` XML upload objects.	Yes	NO-OF-DAYS = number of days after the completion date that a `completed` XML upload object should be purged MAX-ERRORS = Used to override the maximum number of errors after which the batch must be terminated.	200/15

Please refer to Column Descriptions for more information on the columns used in the table above.