The SAFE X3 software is able to manage, by means of the archiving / purging functions, the transfer to archives or the purging of entries that no longer change, and are considered sufficiently old that they are not frequently consulted.

It is important to note that the archiving function is used to transfer data to an archive database considered as closed (i.e. no longer likely to evolve). Inquiries can only be carried out separately on the data (the data cannot be viewed simultaneously with the non archived data: the choice is made either to view archived data or the live data). On the other hand, if an archive table makes reference to the data in the live database (not available to be archived by definition, such as customers, accounts) or for data for which no archive table has been defined, the inquiry can zoom to the non-archived data.

The Purging rule setup is used to define the 'shelf life' from which the movements can be purged or archived, following coherence rules by table group defined elsewhere.

The archiving is carried out by transfer of data from a folder table to a table with the same structure (with two additional fields, CREHISDAT and CREHISUSR, which make it possible to know the dates and operators that archived the data). This table is defined in a dedicated folder, which uses the current folder as a 'mother' folder, and whose creation is carried out by this function.

The interest in this method of operations resides in the fact that the inquiry functions for the archived data function by simple connection to this folder, in the same way that they work for the current folder.

Note that the archived folder is managed with one limit: the customized portal cannot be accessed from an archived folder.

Screen management

Entry screen

If the archive folder already exists, this function is not usable and an error message is displayed. If this is not the case, the setup entry screen for the archive folder is displayed for entry.

Once these setups are entered, the confirmation of the choice causes the creation of the folder.

Block number 1

Folder (field DOSSIER)

Define the name of the folder to be created (by default, the name of the current folder, prefixed by H is proposed).
Data size (field SIZDAT)

These values are used to size the data files and the index in the database. The size is expressed in Mega-bytes.

These values are only interesting from the point of view of folder creation, and they are generally entered at the end of the definition of the folder parameters, just before the actual folder creation. In fact, to have available a correct estimate for the value, it is important to have previously sized the database tables by means of the sizing values ( Tables tab), and to have more importantly defined the table structure of the database by means of the activity codes (Options, Screens, Specifics).
Index size (field SIZIDX)
Use file groups (field GRPFIL)

When the database is Oracle, it is necessary to give an identifier of 4 characters maximum, used notably to name the datafile associated with the database user. When the database is SQLServer, it is only necessary if file groups (Yes / No). are to be managed.
Coefficient of augmentation tables (field COEFF)

The increase coefficient for the tables makes it possible to define the size used to dimension the archive table, by reference to the size used to dimension the table in the live folder. This coefficient can be less than or greater that 1. If for example, at a given moment of time there is a year of live data on line, and 5 years of archived data should be maintained, the coefficient should be equal to 5.

Block number 2

Inquiry menu profile (field HISMEN)

Define the menu profile used for access to the archive folder. All the functions of the inquiry type can be referenced in this profile, however it is also the case that object functions can only function in inquiry mode when connected to the archive folder.

Notes

The creation of an archive folder creates the folder and the minimum number of tables necessary for its operation. The archived tables are created at the moment of the archive operation.

Once created, the archive folder name, the increase coefficient and the menu code are stored in the live folder setups. These setups, defined in the SUP group, are called respectively HISDOS, HISCOE, HISMEN and they are not modifiable.

Batch task

This function can be run in batch mode, but no dedicated standard task is delivered to run it.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Folder already exists

A folder that already exists has been proposed as an archive folder name.

Tables used

See also Refer to documentation Implementation