Update Spool Group settings - assure_quick_edd

If needed, number of independent ASPs managed in this

environment (only one managed)

0= *SYSBAS, Objects from *SYSBAS (ASP 1 and 2 to 32 basics)

2/32= Basic, Objects from basic ASP

33/++= iASP, Objects from independent ASP

Using an independent ASP has some constraints:

• Only one independent ASP will be managed in one environment

• Independent ASP must be configured and active before starting EDH replication

To set a dedicated data server for this object. This option allows you

to define which server will manage this object, to separate files

with a high number of I/O.

0= Automatic management

Value 1 to 15 = Provide the server number which will manage this object. Any value greater than available servers will be omitted.

Date for next journal entry to be considered. All entries prior to this date will be ignored.

This date can be defined at the Object level, or Group level.

Date format is YYYYMMDD HHMMSS, MMMMMM or 0 (default) if not needed and entries are managed normally.

This date will be reset to 0 when reached.

This date is used to manage the synchro process and automatic restart after an abnormal end.

0: Spool file keeps the same status it has on source

1: Spool file will have HELD status on target

0: No tag

1: Tag spool file with the PMEDH program name that created it on the target.

Defines a number of seconds before running the synchro of an object for this group.

This delay gives time for the application to complete processing before EDH starts the synchro (create, resync, ...)

In the case of verification, for the objects of this group, this option allows you to edit detail of the objects:

0: Ignored objects, NOK objects, and OK objects whose data has been partially verified (% vfy).

1: All Objects, even OK objects fully verified.

To use this option, you first must activate object modification detection on the target system. Objects detected as modified will be tagged; then the Verify or Synchro will fix differences and remove the tag.

When an object is detected as modified, available options are:

0: Ignore

1: Message + Tag as "Not verified".

The Verify will control these tagged objects later.

2: Run Verify on the detected object

3: Force synchro

Caution: Synchro on large PF file should take a long time

Defines the frequency and option to run on the objects of the group.

The frequency is defined in hours with a decimal (0,1 = 6mn).

none: No automatic option.

C: Synchronization of group's objects.

Y: Verify on group's objects. Synchro if a difference is detected.

N: Check unverified objects

A: Verify objects.

R: Check unverified objects with active PF

V: Verify on group's objects. Synchro if a difference is detected

The two parameters must be defined allowing the function to run.

Defines when the exit program will be called (before or after the event):

0 = Exit program is not called

1 = Exit program is called before processing the operation

2 = Exit program is called after processing the operation

3 = Exit program is called before AND after processing the operation.

Defines when the exit program will be called (before or after the event):

0 = Exit program is not called

1 = Exit program is called before processing the operation

2 = Exit program is called after processing the operation

3 = Exit program is called before AND after processing the operation.

1 = Run exit program, including for Input/output operations (I/O)

I/O operations include WRITE and UPDATES for PF, DTAARAs, DTAQs, and STMF.

Caution: I/O operations on data can be very time consuming as calling a program from each one can make the replication very slow.

Defines a CALL of the exit program on target, before or

after a synchronization operation on an object of the group:
0 = Exit program is not called

1 = Exit program is called before processing the operation

2 = Exit program is called after processing the operation

3 = Exit program is called before AND after processing the operation.