Project Level Auto Purge
Moderators: chulett, rschirm, roy
Project Level Auto Purge
Hi,
We have enable the auto purge at the project level on our 8.1 FP1 DS server.
I am unable to find the PURGE.SETTINGS control record in our RT_LOGnnn files to reflect the project level purge setting. Inerestingly log entries are cleared as per the project level auto purge settings.
The question I have is how should I verify any given job if it has active project level auto purge settings? The reason I ask is we have some jobs which are imported before the project level auto purge setting was enabled.
Please note that I have no issue of this kind on our 7.5 server.
We have enable the auto purge at the project level on our 8.1 FP1 DS server.
I am unable to find the PURGE.SETTINGS control record in our RT_LOGnnn files to reflect the project level purge setting. Inerestingly log entries are cleared as per the project level auto purge settings.
The question I have is how should I verify any given job if it has active project level auto purge settings? The reason I ask is we have some jobs which are imported before the project level auto purge setting was enabled.
Please note that I have no issue of this kind on our 7.5 server.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The //PURGE.SETTINGS record is created by someone manually overriding the default purge settings. Obviously this has not been done to this job in the new environment.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
There is no difference between versions. Newly created jobs don't get a //PURGE.SETTINGS record in either version. The only thing that creates the //PURGE.SETTINGS record is someone manually overriding the default settings in Director client.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Ray,
In my case no one is overriding the default setting. Just curious to know how it got into RT_LOG in 7.5 and not on 8.1?
If I stick to your observations then how can I verify that a given job is enforced for project level purging? So, that I can scan through all the jobs with corresponding purge settings.
In my case no one is overriding the default setting. Just curious to know how it got into RT_LOG in 7.5 and not on 8.1?
If I stick to your observations then how can I verify that a given job is enforced for project level purging? So, that I can scan through all the jobs with corresponding purge settings.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Someone did, in 7.5.
To verify, check that the values in //PURGE.SETTINGS match those of the project default. Yes, in each log hashed file. Or you could simply delete the //PURGE.SETTINGS record. (Or \\PURGE.SETTINGS if that's what it happens to be.)
To verify, check that the values in //PURGE.SETTINGS match those of the project default. Yes, in each log hashed file. Or you could simply delete the //PURGE.SETTINGS record. (Or \\PURGE.SETTINGS if that's what it happens to be.)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
If there's no \\PURGE.SETTINGS entry it's enabled as per the project default. If there is a \\PURGE.SETTINGS entry then you have to review that entry to establish whether auto-purge is enabled for that particular job.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The project default is always set, even if the setting is "not enabled".
If it's changed, the changes only affect jobs created/imported after the change has been wrought.
If it's changed, the changes only affect jobs created/imported after the change has been wrought.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Thank you very much for patiently answering all my questions Ray!!!ray.wurlod wrote:The project default is always set, even if the setting is "not enabled".
If it's changed, the changes only affect jobs created/imported after the change has been wrought.
I have another one, what is the purging project default which is always set even if the purge setting is not enabled? I am under impression that if the purge setting is not enabled the log files will accumulate forever.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I believe that is the default default.
Best practice is to remedy that immediately the project is created, since you have the Administrator client open anyway.
Best practice is to remedy that immediately the project is created, since you have the Administrator client open anyway.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.