Dollar Universe – Maintenance – Purging in Area
This window displays the data maintenance configuration for the Dollar Universe Server. Technical data relating to a Job Run is purged on the fly by the Launch Engine. The purge uses a retention cycle which can be set for various Job statuses.
The dynamic on-line purge handled by the Launcher is supplemented by a cyclical purge handled by a sub-process of the I/O server. Both purges use the same parameters defined below.
During the dynamic online purge, if a record is purged from the launch file (u_fmsb), associated records will be removed from dynamic files (u_fmcx, u_fmhs, u_fmph, u_fmfu, u_fmev, u_fmtp, u_fmsp, u_fmer, u_fmeq). Therefore, retention criteria for dynamic files are the same as those of the launch file. The dynamic purge removes final job status.
The non dynamic (cyclical) purge removes records not purged by the dynamic purge. Retention criteria are:
- Those of the launch file (u_fmsb) for the files: u_fmtp, u_fmsp, u_fmcm.
- Those of the job monitor file (u_fmcx) for the files: u_fmer, u_fmeq, and management criteria.
- Those of the execution history file (u_fmhs) for the files: u_fmph, u_fmfu.
If the cyclical purge and loaded parameters must be restarted simultaneously, the purge will have priority.
<AREA> is A, I, S or X according to the Area.
<Area> is Application, Integration, Simulation or Production according to the Area.
|
Variable / Label
|
I/S/D
|
Description
|
|
<AREA>_O_DYN_PURGE
Dynamic online purge in <Area> Area
|
D
|
Turns the “dynamic purge” on or off.
This only concerns the dynamic purge done by the launcher, the cyclical purge done by the IO sever is not implicated.
|
|
<AREA>_O_PURGE_RGZ
Trigger online reorganization at the end of the non dynamic purge in <Area> Area
|
D
|
Enables or disables reorganization of the data files at the end of a non-dynamic purge.
|
|
<AREA>_O_PURGE_FREEZE
Freezes online purge in <Area> Area
|
D
|
Stops / Starts the online purge. If the purge is frozen, nothing is deleted.
|
|
<AREA>_O_PURGE_CYCLE
Online purge cycle in <Area> Area (DDD:HH:MM)
|
D
|
Purge cycle (non dynamic) done by the IO server.
Incompatible with X_O_PURGE_HHMM.
|
|
<AREA>_O_PURGE_HHMM
Online purge hour in <Area> Area (HH:MM)
|
D
|
Time of the non dynamic purge done by the IO server.
Incompatible with X_O_PURGE_CYCLE.
|
|
<AREA>_O_PURGE_HST_RET_DEF
History default retention delay in <Area> Area (DDD:HH:MM)
|
D
|
Default retention cycle for the history file.
|
|
<AREA>_O_PURGE_HST_RET_A
History retention delay of “pending” in <Area> Area (DDD:HH:MM)
|
D
|
Retention cycle specific to a particular status:
A: Pending
|
|
<AREA>_O_PURGE_HST_RET_D
History retention delay of “started” in <Area> Area (DDD:HH:MM)
|
D
|
D: Started
|
|
<AREA>_O_PURGE_HST_RET_E
History retention delay of “running” in <Area> Area (DDD:HH:MM)
|
D
|
E: Running
|
|
<AREA>_O_PURGE_HST_RET_F
History retention delay of “completion in progress” in <Area> Area (DDD:HH:MM)
|
D
|
F: Completion instructions
|
|
<AREA>_O_PURGE_HST_RET_I
History retention delay of “aborted” in <Area> Area (DDD:HH:MM)
|
D
|
I: Aborted
|
|
<AREA>_O_PURGE_HST_RET_O
History retention delay of “time overrun” in <Area> Area (DDD:HH:MM)
|
D
|
O: Time overrun
|
|
<AREA>_O_PURGE_HST_RET_R
History retention delay of “refused” in <Area> Area (DDD:HH:MM)
|
D
|
R: Refused
|
|
<AREA>_O_PURGE_HST_RET_T
History retention delay of “completed” in Production Area (DDD:HH:MM)
|
D
|
T: Completed
|
|
<AREA>_O_PURGE_CTL_RET_DEF
Control default retention delay in <Area> Area (DDD:HH:MM)
|
D
|
Default retention cycle for the job monitoring file.
|
|
<AREA>_O_PURGE_CTL_RET_A
Control retention delay of “pending” in <Area> Area (DDD:HH:MM)
|
D
|
Retention cycle specific to a particular status:
A: Pending
|
|
<AREA>_O_PURGE_CTL_RET_D
Control retention delay of “started” in <Area> Area (DDD:HH:MM)
|
D
|
D: Started
|
|
<AREA>_O_PURGE_CTL_RET_E
Control retention delay of “running” in <Area> Area (DDD:HH:MM)
|
D
|
E: Running
|
|
<AREA>_O_PURGE_CTL_RET_F
Control retention delay of “completion in progress” in <Area> Area (DDD:HH:MM)
|
D
|
F: Completion instructions
|
|
<AREA>_O_PURGE_CTL_RET_I
Control retention delay of “aborted” in <Area> Area (DDD:HH:MM)
|
D
|
I: Aborted
|
|
<AREA>_O_PURGE_CTL_RET_O
Control retention delay of “time overrun” in <Area> Area (DDD:HH:MM)
|
D
|
O: Time overrun
|
|
<AREA>_O_PURGE_CTL_RET_R
Control retention delay of “refused” in <Area> Area (DDD:HH:MM)
|
D
|
R: Refused
|
|
<AREA>_O_PURGE_CTL_RET_T
Control retention delay of “completed” in <Area> Area (DDD:HH:MM)
|
D
|
T: Completed
|
|
<AREA>_O_PURGE_LAN_RET_DEF
Launch default retention delay in <Area> Area (DDD:HH:MM)
|
D
|
Default retention cycle for the Launch file.
|
|
<AREA>_O_PURGE_LAN_RET_A
Launch retention delay of “pending” in <Area> Area (DDD:HH:MM)
|
D
|
Retention cycle specific to a particular status (states concerning the dynamic purge are shown in bold type):
A: Pending
|
|
<AREA>_O_PURGE_LAN_RET_D
Launch retention delay of “started ”in <Area> Area (DDD:HH:MM)
|
D
|
D: Started
|
|
<AREA>_O_PURGE_LAN_RET_E
Launch retention delay of “running” in <Area> Area (DDD:HH:MM)
|
D
|
E: Running
|
|
<AREA>_O_PURGE_LAN_RET_F
Launch retention delay of “completion in progress” in <Area> Area (DDD:HH:MM)
|
D
|
F: Completion instructions
|
|
<AREA>_O_PURGE_LAN_RET_I
Launch retention delay of “aborted” in <Area> Area (DDD:HH:MM)
|
D
|
I: Aborted
|
|
<AREA>_O_PURGE_LAN_RET_LO
Launch retention delay of “time overrun without any condition check” in <Area> Area (DDD:HH:MM)
|
D
|
LO: Time overrun in launch wait
|
|
<AREA>_O_PURGE_LAN_RET_WO
Launch retention delay of “time overrun after at least one condition check” in <Area> Area (DDD:HH:MM)
|
D
|
WO: Time overrun in event wait
|
|
<AREA>_O_PURGE_LAN_RET_H
Launch retention delay of “hold” in <Area> Area (DDD:HH:MM)
|
D
|
H: Held
|
|
<AREA>_O_PURGE_LAN_RET_R
Launch retention delay of “refused” in <Area> Area (DDD:HH:MM)
|
D
|
R: Refused
|
|
<AREA>_O_PURGE_LAN_RET_T
Launch retention delay of “completed” in <Area> Area (DDD:HH:MM)
|
D
|
T: Completed
|
|
<AREA>_O_PURGE_OEX_RET_DEF
Exceptions/outage default retention delay in <Area> Area (DDD:HH:MM)
|
D
|
Retention cycle for the Exceptions and Outage files.
|
Be careful, *PURGE_LAN_RET* settings values must not be greater than *<AREA>_O_PURGE_REPORTER* settings values.
No parameter is mandatory. If a parameter is not supplied, its default value will be used.
The default value will also be used if a parameter in the format DDD:HH:MM is set to ---:--:-- or if a HH:MM parameter is set to --:--.
A retention cycle set to 000:00:00 will be interpreted as infinity.
Specific characteristics:
- *PURGE_CYCLE and *PURGE_HHMM are incompatible; one of the two parameters must be left empty: ---:--:-- or --:--.
If *PURGE_HHMM is used, the purge cycle is set to one day.
If *PURGE_CYCLE is used, the first non dynamic purge takes place one minute after the loading of parameters, after which the purge cycle is applied.
- The purge is traced in the universe.log file in the level specified.
The purge cycle begins at the end of the last purge execution.
The settings below concern a file (u_fmhr*) shared by Reporter and Dollar Universe thus the file used by the watching tasks (u_fmfw *).
|
Variable / Label
|
I/S/D
|
Description
|
|
<AREA>_O_PURGE_REPORTER
Online purge for Reporter data in <Area> Area
|
S
|
Online purge of the Dollar Universe statistics, watching data and the Reporter data.
Yes by default. By default DUAS completes a file for Reporter. This file must be purged.
|
|
<AREA>_O_PURGE_REPORTER_RETENTION_GLOBAL
Retention delay for Reporter data (DDD:HH:MM) in <Area> Area
|
D
|
Retention duration of Dollar Universe statistics, watching data and Reporter data. Without extraction (or without Reporter) this file conserves n days of data. The default value is seven days.
The value 000:00:00 is strongly discouraged and will result in overloading the IO server.
|
|
<AREA>_O_PURGE_REPORTER_RETENTION
Retention delay for Reporter data after extraction (DDD:HH:MM) in <Area> Area
|
D
|
Retention duration of Dollar Universe statistics, watching data and Reporter data after extraction. If Reporter extracts the data, the file conserves n days of data. The default value is one day.
The value 000:00:00 is strongly discouraged and will result in overloading the IO server.
|
Be careful, *PURGE_REPORTER* settings values must not be lower than *<AREA>_O_PURGE_LAN_RET_DEF* settings values.
Dollar Universe (V6 and later) writes a copy of all job execution data in this file and uses it also when handling launches.
Reporter no longer extracts data from a permanent execution file but performs a direct extraction from this file. The goal of this change is to minimize the impact on Dollar Universe production and to avoid the extraction and the filtering of the entire production base.
Alerts are also based on this file.
Data in this file and in the launches file must therefore be consistent and the parameters of purge also. Under no circumstances should the retention delay of this file be less than the retention delay of the launches file.
|
Variable / Label
|
I/S/D
|
Description
|
|
<AREA>_O_PURGE_AUDIT_TRAIL
Online purge for Audit Trail data in <Area> Area
|
S
|
Purge the data from Audit Trail online. Yes by default. By default DUAS completes a temporary file for Audit Trail. This file must be purged.
|
|
<AREA>_O_PURGE_AUDIT_TRAIL_RETENTION
Retention delay for Audit Trail data after extraction (DDD:HH:MM) in <Area> Area
|
D
|
Retention duration of Audit Trail data. Without extraction (or without Reporter) this temporary file conserves n days of data. The default value is one day.
The value 000:00:00 is strongly discouraged and will result in overloading the IO server.
|
|
<AREA>_O_PURGE_AUDIT_TRAIL_RETENTION_GLOBAL
Retention delay for Audit Trail data (DDD:HH:MM) in <Area> Area
|
D
|
Retention duration of Audit Trail data after extraction. If Reporter extracts the data, the temporary file conserves n days of data. The default value is 90 day.
The value 000:00:00 is strongly discouraged and will result in overloading the IO server.
|
|
<AREA>_O_PURGE_TRIGGER_HISTORY
Retention delay for Audit Trail data (DDD:HH:MM) in <Area> Area
|
D
|
Retention duration of Trigger History data. The temporary file conserves n days of data. The default is seven days.
|