Skip to main content
Skip table of contents

STREFREORG, reorganize i-effect

Usage

With the command STREFREORG you can reorganize all logbook files, archive directories and internal logs created by i-effect. After some time it will be necessary to clean up documents and logs created by i-effect, so that infinitely large log files and old archive files do not accumulate.

Parameters and their meaning

The command has the following parameters


Parameter

Value


Description

End i-effect

LOG



Selection of the data to be archived


*SELECT


Entries in log book files, IFS files in archive directories and internal logs that are older than the number of days specified in the DAY parameter are deleted.                                

No


*ALL


The contents of all logbook files, all files in the archive directories and all internal logs are deleted.

Yes

DAY



Entries in logbook files, IFS files in archive directories and internal logs that are not older than the number of days defined in this parameter are not removed. All other entries or files are removed from the logbook. With the value 0, all are removed.

0 => Yes

>0 => No

MODULES



Specifies the module name for which the reorganization is performed

No


*ALL


Logbook/transaction entries, IFS files are reorganized for all i-effect modules.

No

ARCHIV



Defines whether archived data should be saved in a ZIP archive.


*YES


Logbook files, archive directories, and internal logs are archived in an i-effect archive before the reorganization. To preserve the DDS data, the logbook files are first automatically backed up in a backup file before archiving.

No


*NO


The data is not saved before the reorganization.

No

ARCPATH



Absolute path to the archive file.

(Warnung) Only valid when using ARCHIVE(*YES) 

No


*PROMPT


The file name and path as well as the settings of the archive are queried with another prompt.

No

LOGBOOK



Determines whether the logbook should be reorganized


*YES


Files of the logbook are reorganized. These include the files SESSION, ACTION, DOCUMENT, DOCUMENTADE.

No


*NO


The tables are not reorganized.

No

FWDLOGBOOK



Determines whether the forwarding log should be reorganized


*YES


The forwarding log is reorganized

No


*NO


The forwarding log is not reorganized

No

WCNOTICES



Determines whether Webcontrol averaging is reorganized


*YES


Webcontrol averaging is reorganized

No


*NO


Webcontrol averages are not reorganized

No

VORGANG



Determines whether data from transaction tracking is reorganized.


*YES


The operation files VORGANG, VORADDINF are reorganized.

No


*NO


The operation files are not reorganized.

No

RGZPFM



Partial files of the database are reorganized using RGZPFM. Data records marked as deleted are removed.


*YES


Deleted records of a physical sub-file in the database are removed and the sub-file is reorganized.

Yes


*NO


Deleted records of a physical partial file in the database are removed, partial file is reorganized.

No

DLTJRNRCV



Determines whether old journal receivers (*JRNRCV) are removed


*YES


The detached journal receiver files are not removed.

Yes


*NO


The detached journal receiver files are removed.

No

DLTSQLPKG



Determines whether old SQL packages (*SQLPKG) are removed


*YES


The *SQLPKG files are removed.

Yes


*NO


The *SQLPKG files are not removed.

No

CRTSQLIND



Determines whether SQL access paths are recreated.


*YES


The new creation of the SQL access paths is carried out

Yes


*NO


SQL access paths are not recreated.

No

PRCEFFIFS



Determines whether content from the IFS directories should be reorganised.


Element 1


Determines whether files from archive directories are reorganized. 

The directories include all directories that have been stored as archives in the i-effect module configuration or in the config.xml of the modules (Zugferd, Mapper).

In the standard these are:

/home/ieffect/archive/email/receive/*.eml
/home/ieffect/archive/email/send/*.eml

/home/ieffect/archive/ftp/receive/*
/home/ieffect/archive/ftp/send/*

/home/ieffect/archive/as2/receive/*
/home/ieffect/archive/as2/send/*

/home/ieffect/archive/http/receive/*
/home/ieffect/archive/http/send/*

/home/ieffect/oftp2/archive/receive/*
/home/ieffect/oftp2/archive/send/*


/home/ieffect/zugferd/archiv/*

/home/ieffect/archive/mapper/*



*YES

Yes, the files in the internal archive directories of i-effect are reorganized.

No



*NO

No, the files in the internal archive directories of i-effect are excluded from the reorganization.

No


Element 2


Determines whether files from internal working directories are reorganized. 



*YES

Yes, the files in the internal working directories of i-effect are reorganized.

No



*NO

No, the files in the internal working directories of i-effect are excluded from the reorganization.

No


Element 3


Determines whether files from internal error directories are reorganized

The directories include all directories that have been stored as archives in the i-effect module configuration or in the config.xml of the modules (Zugferd, Mapper).

In the standard these are:

/home/ieffect/email/error/*
/home/ieffect/as2/error/*

/home/ieffect/http/error/*

/home/ieffect/oftp2/send/error/*

/home/ieffect/zugferd/error/*

/home/ieffect/oftp2/send/error/*



*YES

Yes, the files in the internal error directories of i-effect are reorganized.

/home/ieffect/internal/*

No



*NO

No, the files in the internal error directories of i-effect are excluded from the reorganization.
With the command STREFREORG (menu item 83) you can reorganize all logbook files, archive directories and internal logs created by i-effect. After some time it will be necessary to clean up documents and logs created by i-effect, so that large log files and old archive files do not accumulate.

No

Application example

Description

Command Parameters

Store all data older than 30 days in a ZIP archive

IEFFECT/STREFREORG ARCHIV(*YES)  ARCPATH('/home/ieffect/2mebeff_reorg.zip' )  WCNOTICES(*YES)  FWDLOGBOOK(*YES)

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.