General Tab - assure_quick_edd

Assure QuickEDD GUI Guide

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure QuickEDD
ft:locale
en-US
ft:title
Assure QuickEDD GUI Guide
Copyright
2025
First publish date
1997
ft:lastEdition
2025-08-06
ft:lastPublication
2025-12-11T07:02:50.081000
L1_Product_Gateway
Integrate
L2_Product_Segment
IBM Infrastructure
L3_Product_Brand
Precisely Assure
L4_Investment_Segment
IBM i HA
IBM i Security
L5_Product_Group
IBM i HA
IBM i Security - Base
L6_Product_Name
Assure QuickEDD for PowerHA
Assure QuickEDD Promoter
Assure QuickEDD HA
Legacy Security
Options Description
Environment description Short description of the environment.
Definition of server jobs
Read journals

Number of servers available on the source for journal tracking.

The job names should look like: EDH_xx_Jnn

Apply I/O on target

Number of servers available on the target for synchronous operations (execution of I/O’s)

The job names should look like: EDH_xx_Xnn

Synchronization Mini/Maxi

Minimum and maximum number of servers available for asynchronous operations (synchronizations)

The job names should look like: EDH_xx_Snn on source and EDH_xx_Rnn on target

Accelerated PF execution/Verify

Maximum number of servers available for large PFile data verification operations.

When checking all the data of a large PFile, these servers are used promptly to accelerate reading.

0: No use of these acceleration servers

2/15: Number of servers that can be used

The job names should look like: EDH_xx_Snn on source and EDH_xx_Rnn on target

Environment options
DATA replication mode

Limitations of backup mode.

0: All - No limitations

1: Data - Data Limitation (*FILE, *DTAARA, *DTAQ et *USRPRF)

3: MapDrop - Data Limitation with PF drawing conversion (MAPDROP)

Note: In MAPDROP mode, the exit point 11 can be used to intervene on the target record of the files before its use to update it (SND) or copy it (Snn).

Verify mode only

Check box to activate Verify mode only.

In this mode, EDH only checks the suitability of objects on the target and edits the list of differences.

No modifications to the target, does not trigger journalization or auditing on source, or read journal entries.

Anonymize defined fields

Check box to enable anonymization on file fields.

Anonymization mode consists of writing some files on the target with scrambled or masked fields in order to make it impossible to recognize these fields.

For environment XX, the object XX_ANONYME (* USRSPC) containing the list of libraries, files and fields concerned, must be present on the source at the start of EDH.

A field can be anonymized by scrambling (changing characters) or masking (replacing characters by another (*)) for all or part of the characters in the field (see the documentation).

Variance: An index from 0 to 63, which allows to completely modify the result of the anonymization.

Mb compared by IOA

This parameter specifies the maximum size (in MB) of controlled data from a PF member or * STMF object.

If 0, there is no control of the data. This option is faster but does not detect gaps in the data. If the value is large, all data is read and controlled, but the verification will take longer.

Time option auto (hh, h)

Frequency (in hours) of object security checks.

If 0, no checks will be started automatically.

This security check makes it possible to check the correlation between the source objects and targets to detect anomalies. Objects that are not being updated or synchronized will be checked and resynchronized if necessary.

C: Synchronization of group objects.

Y: Verification of group objects and synchronization if needed.

N: Check unverified objects

A: Verification of objects

A: Checking unverified objects even if active PF

V: Group objects verification and synchronization if necessary.

Both parameters must be populated.

Ignore upd PF < (sec) During the check, this delay (in seconds) ignores PF whose members have been updated recently. This avoids declaring these PFs in error.
Auto restart delay (hh)

Number of hours since the last start before triggering an automatic restart of EDH.

The restart function cleans the system spaces used by EDH. It will be put on hold until EDH reaches the end of the journals. If 0, no automatic restart is performed.

Manage Commit/Rollback

In the case of applications managing commit / rollback transactions, possibility to store the commit cycles (on the target) in the event of a FAIL-OVER

0: No storing of the validation cycles COMMIT

1: Stores validation cycles COMMIT (if appropriate application). No effect if the application does not use commit

Supervision
Source / Remote Check the box to always start EDH monitoring for this environment at startup.
End/Read This is the time (in minutes) before sending a message that the environment is stopped, or journals are not being read.
Process This is the time (in minutes) before sending a message indicating a delay in processing journal entries.
Backlog The time (in minutes) before sending a message indicating a delay of processing journals. This is different from the Process field, as the backlog is the difference between the current time and the time of the last applied entry on the target.
Resent This is the time (in minutes) before sending message, reminder or new message.
iASPS
Source N° / Device Name

Optional number and group name of an independent ASP managed in this environment.

The use of an independent ASP imposes the following constraints:

  • EDH supports only one independent ASP per environment

  • When starting EDH, the ASP must be configured and active on the source machines and target