4 replies to this topic

[fuldo]

Hello,

we've recently replaced uxpurge by officially recommended continuous (online) purge (UNIX), with retentions set generally to 10 days.


I'd like to ask you for help regarding following questions:

1)
It seems, that the online purge doesn't perform cleanup of entries in execution history for aborted uprocs, which were relaunched - I assumed, that these are covered by U_RETENTION_DELAY_ABORTED variable.
Or will the entry be purged automatically later together with the cleanup of newer record created as result of job relaunch ( once the retention period for the new entry is reached)?

Purge of other entries in execution history/launch is behaving correctly.


2)
The intervention and distribution history is not being considered - is the way to make them considered by continuous purge?

3)
There is no visible evidence, that the continuous purge is active and dta files are being processed by it.
Is there any configuration variable, which could be applied in order to be able trace the continuous purge process/progress?



Thanks for your help and advices in advance.


Kind regards,


Peter

[men]

Hello Peter,

Just to make sure: What is your Dollar Universe release and patch level (file uxversion*)?

If you are running the V533, are you using the latest flavour of the purge?

Michel

[fuldo]

Hi Michel,

$U on UNIX is in 5.3/24697 (on Windows in 5.4/FX24585).

The intension was to use classic continuous purge as it is officially described in documentation.


In case, the "old" online purge "won't work", we will have to consider to use the newer IO online purge.


Thanks for help

Regads,

Peter

[men]

Hello Peter,

I would indeed recommend that you use the newer IO online purge. It should solve point 2 and will bring enhanced purges for other files.

Michel

[fuldo]

Hi Michel,

then it willl be better to use the IO online purge...

Thanks

Regards,

Peter