SET,REPL command

You can use the SET,REPL command to modify existing subscriptions.

Modifying subscription information

You can use the following SET command to modify the attributes of an existing subscription or of all subscriptions on a source server.

Read syntax diagramSkip visual syntax diagram SET , REPL , SUBSCR=subscription-nameALL , 'CAPTURECACHE=n''PERSISTENT=YES'NO''SETLOGPOS,GMTTIME=time'SERVERTIME=time''STATUS=ACTIVEPARK,OBJECT=object',NOWTHRESHOLDS1THRESHOLDS2THRESHOLDS3THRESHOLDS,DISCRETETIMEMAXTIMERESETTIME=thresholdTHRESHOLDS1THRESHOLDS,HEARTBEATMEANTIME=timevalTHRESHOLDS2THRESHOLDS3,WORKLOAD=workload-name

You can use the following SET command to modify the attributes of an existing subscription or of all subscriptions on a target server.

Read syntax diagramSkip visual syntax diagram SET , REPL , SUBSCR=subscription-nameALL , 'APPLYCACHE=n'

Parameters

subscription name
The name of the subscription to modify. You can specify the subscription name as an identifier with or without quotation marks. If the subscription name is mixed case you must use quotation marks.
ALL
Modifies the specified attributes for all subscriptions. The ALL parameter does not apply to setting thresholds or workload names. Therefore you cannot specify both the ALL parameter and the THRESHOLDSn or THRESHOLDS parameter, or both the ALL parameter and WORKLOAD names.
APPLYCACHE
The size of the apply cache. A value of 64 to 2048 MB is allowed.
CAPTURECACHE
The size of the capture cache. A value of 64 to 2048 MB is allowed.
PERSISTENT
Automatically restarts replication for the specified subscription. Specify this keyword only for subscriptions that use continuous replication. Valid values are YES or NO.
SETLOGPOS
Updates the bookmark information stored at the target server.
Specify the time in the format YYYY-MM-DD-hh.mm.ss.thmiju:
  • YYYY-MM-DD is a calendar date
  • hh.mm.ss.thmiju is a time of day
Valid values: You can specify a value to get the current time or specify GMTTIME or SERVERTIME.
GMTTIME
The Greenwich Mean Time (GMT) time. You must specify this value up to the ss (seconds). For example: 
SET,REPL,SUBSCR=subscription name,'SETLOGPOS,
GMTTIME=2011-04-14-18.01.00.123456'
SERVERTIME
The server time. Specify the local time of the server time zone. You must specify this value up to the ss (seconds) value. For example: 
SET,REPL,SUBSCR=subscription name,'SETLOGPOS,
SERVERTIME=2011-04-14-18.01.00.123456'
Important: If you use the SETLOGPOS keyword and either the GMTTIME or SERVERTIME keywords, the entire phrase must be in quotes and the keywords must be upper case. If you modify a bookmark, you might need to refresh the entire subscription and restart replication for the subscription to recreate a valid bookmark. You should only change a bookmark under the direction of IBM® Software Support.

Ensure that all data sets that are part of the subscription are closed in all CICS® regions and in CICS VR at the specified time. This ensures that CICS and CICS VR will generate a tie-up record when the data sets are be opened after the specified time.

“STATUS= <status>,OBJECT=<object>”
The status of the subscription. Valid values:
ACTIVE
For any subscription, you can set mappings as active for replication. If a mapping is not set as active, it will not replicate when replication is started for the subscription.

You can use the optional NOW modifier to set the mapping as active and set its log position time to the current time when the command is processed. With this optional modifier, the command syntax looks as follows: “STATUS=ACTIVE,OBJECT=object,NOW”

PARK
For any subscription, you can park replication mappings. If a mapping is set as parked, it will not replicate when replication is started for the subscription.
The STATUS and OBJECT keywords must be enclosed in quotation marks.
THRESHOLDSn|THRESHOLDS,<keyword>=<value>
Sets the apply latency threshold values and workload names of the threshold sets for a subscription. The Classic data server uses these values to determine when to emit Event Integration Facility (EIF) events to an event server.
You can define up to three threshold sets for a subscription in the format THRESHOLDSn,keyword=value.
THRESHOLDSn
The threshold set identifier for the subscription:
  • THRESHOLDS1
  • THRESHOLDS2
  • THRESHOLDS3
  • THRESHOLDS
The suffix n designates 1, 2, or 3 to correspond to the three sets of apply latency thresholds for a subscription. If you do not specify a threshold set identifier, the command is issued against threshold set 1.
keyword
The threshold keyword:
  • DISCRETETIME
  • MAXTIME
  • RESETTIME
  • HEARTBEAT
  • MEANTIME
  • WORKLOAD
value
The threshold value (threshold) or time value (timeval) in milliseconds. Valid values are 0 - 600000. You must name workloads for threshold sets 2 and 3 before setting any values for these thresholds.
The following guideline applies to setting threshold values:
  • The RESETTIME value must be less than 80% of the MAXTIME value.
  • The MAXTIME value must be less than the DISCRETETIME value.
DISCRETETIME=threshold
The discrete level of latency in milliseconds. This threshold defines the discrete threshold at which you want an event to notify you about the latency of a subscription. You can define this value to alert you to take a particular action when the event occurs.
The value of DISCRETETIME controls when the Classic data server sends the EIF event AA_replication_discrete_latency_exceeded.
  • The event is sent when the apply latency of an individual unit of work for a subscription exceeds the DISCRETETIME threshold
  • The event is suppressed to one per mean time interval to prevent overloading the event server that receives this event.
The DISCRETETIME threshold is independent of other threshold values. You must configure this threshold to a value higher than the value of the MAXTIME threshold time.
MAXTIME=threshold
The maximum level of latency in milliseconds. The value of MAXTIME controls when the Classic data server sends the EIF event AA_replication_max_latency_exceeded. The minimum non-zero configurable value of MAXTIME is 250 milliseconds.
  • The event is sent when the averaged or non-averaged apply latency for a subscription exceeds the MAXTIME threshold.
  • The event is not sent if MAXTIME <= RESETTIME .
RESETTIME=threshold
The reset level of latency in milliseconds. This threshold defines a reset point after a maximum threshold is reached. The RESETTIME threshold must be less than 80% of the MAXTIME threshold. The minimum non-zero configurable value of RESETTIME is 100 milliseconds.
The value of RESETTIME controls when the Classic data server sends the EIF event AA_replication_reset_latency_met.
  • The event is sent when the averaged or non-averaged apply latency for a subscription is less than the RESETTIME threshold after the CONSTRAINEDTIME, CRITICALTIME, or MAXTIME threshold is exceeded.
HEARTBEAT=timeval
The latency heartbeat time in milliseconds. The heartbeat defines the heartbeat interval at which a heartbeat event reports the average latency and subscription state for a subscription.

You can only define this threshold time value in the THRESHOLDS1 threshold set. The THRESHOLDS2 and THRESHOLDS3 threshold sets use the same value when their MAXTIME or RESETTIME threshold value are not zero. The minimum non-zero configurable value of HEARTBEAT is 10000 milliseconds (10 seconds).

The value of HEARTBEAT controls when the Classic data server sends the EIF event AA_replication_averaged_latency_heartbeat.
  • If the value of HEARTBEAT is greater than 0 and the subscription state is REPLICATION CONTINUOUS, this event is issued on the specified interval.
  • If the value of HEARTBEAT is greater than 0, that value is used as the heartbeat interval for all threshold sets.
MEANTIME=timeval
The latency mean time in milliseconds. The minimum non-zero value of MEANTIME is 3000 milliseconds (3 seconds).

You can only define this threshold time value in the THRESHOLDS1 threshold set. The THRESHOLDS2 and THRESHOLDS3 threshold sets use the same value when their MAXTIME or RESETTIME threshold value are not zero.

The mean time defines the time period during which end-to-end apply latency values are collected and averaged. Based on that averaging, EIF events are emitted when the averaged apply latency value transitions to the specified MAXTIME and RESETTIME thresholds. Averaging occurs when the value of MEANTIME is greater than 0.

If the MEANTTIME value is set to 0, apply latencies are not averaged. Events will be emitted for each instance when an apply latency threshold is breached. If the value of MEANTIME is greater than 0, that value is used as the latency mean time for all threshold sets.

WORKLOAD=workload-name
The workload name for the threshold set.
Each threshold set must have a workload name.
  • The workload name of the first threshold set is the same as the subscription name. This workload is named when any of its threshold values are greater than zero. The workload name will be cleared when all its threshold values are zeros.
  • You must define the workload name for the second and third threshold sets in the format THRESHOLDSn,WORKLOAD=workload-name, where n designates the threshold set (2 or 3).

When the Classic data server participates in GDPS® AA, threshold set 1 corresponds with the active/standby workload, threshold set 2 corresponds with the first active/query workload, and threshold set 3 corresponds with the second active/query workload.

The following rules apply to threshold sets:
  • The length of the names is from 1 to 63 characters.
  • The first character must be alphabetic.
  • Characters 2 through 63 can be any alpha-numeric character and can contain the underscore character.
  • Imbedded blanks are not allowed.
  • Workload names are saved in upper case.

The configuration of workload names is performed against both the Classic source server and the Classic target server.

Use the DISPLAY,REPL,SUBSCR=subscription_name,THRESHOLDS MTO command to verify the state of the workload name.