This section describes the system parameters that you can use to identify
or alter CICSPlex® SM attributes.
These parameters are specified by means of an extrapartition transient
data queue. The transient data queue name is COPR. The parameters may be assigned
to a DD * file, sequential data set or a partitioned data set member.
The DD name for the extrapartition transient data queue is EYUPARM.
The system parameters are coded as 80-byte records. Multiple system parameters
may be specified on a single record as long as they are separated by commas
and do not exceed a total of 71 characters in length. The format of the system
parameters is:
For CMASs and CICS®/ESA, CICS Transaction Server for OS/390®, and CICS Transaction Server for z/OS® MASs, members of the CICSTS31.CPSM.SEYUPARM
library containing samples of these parameters are:
- ALERTRCVR(NETVALRT | name)
- Identifies the 1-8 character name of the NetView® Alert Receiver to be used by the CMAS
if NetView Generic Alerts are to be sent by the CMAS to NetView.
- ALERTVER( 0 | 1 )
- Identifies the version of the CPSM generic alert record that the CMAS
will send to NetView. See Appendix B of the
CICSPlex System Manager Managing Resource Usage manual for details on the generic alert Records CPSM may
send to NetView.
ALERTVER is only relevant for
a CMAS which is named in an ACTNDEF as sending generic alerts to NetView.
- APISIGNMSG(YES | NO)
- Indicate whether the successful signon / signoff message, EYUXD0807I,
is to be issued when a CICSPlex SM API user CONNECTs to, or DISCONNECTs
(TERMINATEs) from, the CICSPlex SM API.
BASASSOCBLK(value | 14301)
Specify the number of BAS association blocks that can be acquired from
a single association element. The default EYUPARM value creates an association
segment size requiring approximately 1.2 mB of storage. If the maximum value
of 114597 blocks-per-segment is specified, then the resultant segment size
will be just over 8 mB.
- BASLOGMSG(YES | NO)
- Indicate whether CICS resources defined using BAS should have their definitions
logged to the CSDL Transient Data Queue of the MAS when they are installed.
If the CICS version used by the MAS does not support the LOGMESSAGE option of
the EXEC CICS CREATE command, BASLOGMSG will have no effect.
- CASNAME(name)
Identify the 4-character
name of the CAS subsystem with which the CMAS is
to be associated.
This name must match the CAS subsystem ID identified
in the CAS startup JCL and also specified with the SSID parameter of the
START command.
If this parameter is omitted, the CMAS does not attempt
to connect with a CAS. It is not necessary to start a CAS on the MVS system
on which the CMAS runs.
Note:
You should ensure that every CMAS
connects to a CAS. The connection allows a TSO user signed on to any MVS
image to access the CPSM EUI. It also provides Single System Image (SSI)
function for requests directed at resources accessed under a CMAS context.
If you start a CMAS without a CASNAME, you need not start a CAS on that MVS
image. However, if it later becomes necessary to connect to the EUI with the
context set to that CMAS, you must bring down the CMAS and restart it with
the CASNAME parameter identifying the SSID of a CAS running on the same MVS
image.
- CICSPLEX(name)
Identify the 1- to 8-character name of the CICSplex to which the local MAS is to be associated.
The name
of a CICSplex should not be the same as the name of a CMAS, a CICS system, or
a CICS system group.
- CMASSYSID(name)
Identify the 1- to 4-character name of the CMAS to which a MAS is to be attached.
You can also use this
parameter when a local MAS is to attach to a specific CMAS in the same MVS™ image.
CMTCMLNKACQ( ALWAYS | RECONN)
Specify whether you want the CMAS to attempt to reacquire LU6.2 CMAS-to-CMAS
links (CMTCMLNKs) if the initial acquire attempt made by CICS fails. The initial
acquire attempt is made by CICS at CMAS startup, VTAM ACB open, or CMTCMDEF
(CMAS-to-CMAS definition) install.
If the initial acquire
attempts fail, CICSPlex SM network surveillance may attempt to reacquire the
LU6.2 CMAS-to-CMAS links, depending on the value of CMTCMLNKACQ:
- ALWAYS
- The CMAS will attempt to acquire CMTCMLINKs even if they have never
been established in the current CMAS run.
- RECONN
- The CMAS will attempt to reacquire only those CMTCMLNKs that were previously
established in the current CMAS run. Note that if the CMTCMLNKs were not previously
used in the current CMAS run and the initial acquire attempts fail, you must
acquire the CMTCLNK manually, using one of the following methods:
- using the ACQUIRE action in the EYUSTARTCMTCMLINK Web User Interface view.
- using the ACQUIRE action of the CMTCMLNK resource table in a user-written
CICSPlex SM API program.
- using CEMT to manually acquire the CICS connection used by the CMTCMLNK.
Note:
Depending on the CMTCMLNKACQ option in use, the repeated
acquire attempts may cause multiple error messages from CICS (DFHZC3437, DFHZC3462
and DFHZC2405) and VTAM (IST663, and IST664) logging the connection ACQUIRE
attempt if the requests continue to fail.
CMTCMLNKACQ can
be dynamically changed in a CMAS via the COD0 SET command. See the Problem Determination Guide for details.
- COHTTASKPRI( value | 200)
- Specify the CICS task priority for the MAS COHT task. COHT is invoked
in a MAS when an API or web user interface query for completed task history
records (HTASK records) is directed to the MAS. Use this parameter to tune
the priority of HTASK requests so that a resource intensive query does not
impact the performance of other tasks in the MAS.
- COIRTASKPRI(value | 200)
- Specify the task priority of COIR, in the range 0 to 255. COIR
is a CICSPlex SM task that can be used to process evaluation definitions
(EVALDEFs) independent of the MAS.
For each EVALDEF that requests a separate
task, an instance of COIR is started at the specified priority. If you specify
a priority of 0, no separate COIR tasks are started; all EVALDEFs are processed
by the MAS long running task (LRT).
Note:
This
parameter does not apply to CICS for Windows.
- COMMTSBLOCKS((value | 512/128)
- This is the number of sets of control blocks allocated at CMAS or MAS
startup for CPSM Communications Transport Services. These control blocks
are used when data must be shipped between a CMAS or MAS and other CMASs or
MASs.
The default and minimum values for this parm are 512 in a CMAS and
128 in a MAS. The maximum value is 8192 in either a CMAS or MAS.
Each
set requires 1204 bytes of storage allocated in ESDSA in the CMAS or MAS.
If the defaults are used, the following total storage is allocated:
CMAS - 512 * 1204 = 616,448 bytes
MAS - 128 * 1204 = 154,112 bytes
If the maximum value is specified,
the following total storage is allocated:
CMAS - 8192 * 1204 = 9,863,168 bytes
MAS - 8192 * 1204 = 9,863,168 bytes
If a shortage occurs during the
execution of a CMAS or MAS, message EYUCT0105E is issued. At termination
of the CMAS or MAS, message EYUCT0106W is issued. The later message will
include a value equal to the highest concurrent shortage of sets (High water
mark). It is recommended that the COMMTSBLOCKS parm for the CMAS or MAS be
increased by at least the amount specified by the EYUCT0106W message before
restarting the CMAS or MAS.
- HISTORYONLY( YES | NO)
- Specify whether history data should be collected without collecting
normal CICSPlex SM monitoring data as well. For example, if MLOCTRAN and MREMTRAN
data is not required set HISTORYONLY(YES) to prevent this data from being
collected.
- HISTRECSMSG( value | 0)
- Specify that message EYUNL0179I 'Task History Recorder dataset EYUHISTx
has accrued nnnn records' should be output each time 'value' thousand records
are written to the history data sets. The maximum allowed value is 1000 which
means output a message every time 1 million records are written to the history
data sets.
The message can be used as an aid to determining the optimum
size of the history data sets. A value of 0 means no EYUNL0179I messages are
to be produced.
- HISTSECS( value | 30)
- Specify the number of seconds to use as the default when API or web
user interface users specify a parameter of RECENT(HISTSECS) when requesting
completed task (HTASK) resource table records. The maximum allowed value is
86400 seconds (24 hours).
- JRNLDEFCH(YES | NO)
- Causes a journal record to be written for each data repository
add, delete, and update operation.
- JRNLOPACT(YES | NO)
- Causes a journal record to be written for each successful action
command issued against a MAS or CMAS.
- JRNLRTAEV(YES | NO)
- Causes a journal record to be written each time an real-time analysis (RTA) event
is generated.
MASALTLRTCNT(0 - 5 | 0)
The number of alternate long running tasks (CONA) started in the MAS
during MAS agent initialization. These tasks remain active until the MAS
agent terminates or goes into restart mode, and handles all EUI/API/WUI/RTA
normally handled by the CONL task, allowing the CONL task to perform other
processing in the MAS. At any time, only one of the CONA tasks processes
requests. If the CONA task that is currently processing requests becomes
busy (as determined by the value of the MASALTLRTTIM EYUPARM), subsequent
requests are directed to another CONA task.
If zero (0) is specified, no
CONA tasks are started and the CONL task services the EUI/API/WUI/RTA requests
that are normally directed to the long running task.
Note:
Specifying
different values for MASALTLRTCNT for multiple WLM target regions might result
in an uneven distribution of transactions to those regions because of differing
long running task counts.
MASALTLRTPRI(0 - 255 | 255)
The priority given to the CONA transaction for the current execution
of the MAS.
Note:
Specifying this value less than 255 can adversely
affect the response time of EUI, API, and WUI users, and might result in RTA
EVENTs not being created or resolved in a timely manner
MASALTLRTTIM(1 - 3600 | 10)
The amount of time in seconds for which a CONA task can be busy before
subsequent requests are directed to another active CONA task.
- MASINITTIME(value | 10)
Specifies the number of minutes, from 5 to 59, that CICSPlex SM
should wait for the MAS to initialize.
- If you specify MASPLTWAIT(YES), the MASINITTIME value is the maximum length
of time that PLT processing can be suspended for MAS initialization. (By
suspending PLT processing the chance of completing MAS initialization within
a specified time is increased, because you are asking for less work to be
done in a given time interval, and reducing the scope for contention, during
that time).
- If you specify MASPLTWAIT(NO), the MASINITTIME value is the maximum length
of time that can elapse before MAS initialization is aborted if it does
not complete.
- MASPLTWAIT(YES | NO)
-
Indicates whether CICSPlex SM should suspend all PLT processing until
the MAS is fully initialized and connected to the CMAS.
- When you specify MASPLTWAIT(YES), no CICS applications can be started and no users
can sign on to the system until CICSPlex SM completes the installation
of resources and resumes PLT processing. If CICSPlex SM does complete the installation
of resources and resume PLT processing within the time interval specified
by MASINITTIME, message EYUTS0003I is issued. If it does not complete within
the time interval specified by MASINITTIME, message EYUNL0090W is issued,
the MAS initialization is aborted and the PLT processing resumes to allow
the region to function as a CICS region without CICSPlex SM
control. MAS Initialization can be retried by entering the COLM transaction
manually.
- When you specify MASPLTWAIT(NO), CICSPlex SM still observes the MASINITTIME
value waiting for the MAS agent to complete the topology connect. If CICSPlex SM
does not complete the topology connect within the time interval specified
by MASINITTIME (or its default value), message EYUNL0090W is issued, the MAS
initialization is aborted and the PLT processing resumes to allow the region
to function as a CICS region without CICSPlex SM control. MAS Initialization
can be retried by entering the COLM transaction manually.

If you are using Business Application Services (BAS) to automatically install resources at CICS system initialization, you
should specify MASPLTWAIT(YES) for that system.
Note:
If you
are using Business Application Services (BAS) to automatically install a DB2® connection, and you want the connection
to be activated during CICS startup, see the information in topic
Activating DB2 connections during CICS startup
- MAXAUXCPSM(value | 50)
- Specify the percent of total auxiliary storage which may be committed
to each CMAS, in the range of 1 to 99. Note that each CMAS will require 24,160
4kB pages (94 mB) of cache storage at initialization. If a request for additional
cache storage would cause the CMAS to exceed this threshold, an SDUMP is taken
and the CMAS is terminated. If this occurs during CMAS initialization, it
means that the CMAS was unable to acquire the initial allocations for all
required component data cache areas. Either the value of MAXAUXCPSM must
be increased, or the total amount of auxiliary storage must be increased by
adding or expanding external page data sets. If this threshold is reached
during an attempt to create or extend a data cache after CMAS initialization
has completed, ARM is invoked to attempt to restart the CMAS.
- MAXAUXTOTL(value | 70)
- This value is the maximum total auxiliary storage usage at which the
CMAS allows a request for additional cache storage to be made, in the range
of 1 to 99. This prevents the CMAS from requesting an amount of cache storage
which would cause the MVS system to enter a state of auxiliary storage shortage.
If a request for additional cache storage would cause the CMAS to exceed this
threshold, an SDUMP is taken and the CMAS is terminated. This parameter can
cause a CMAS to shut down even though the CMAS is not the largest user of
auxiliary storage. If this occurs during CMAS initialization, it means that
the CMAS was unable to acquire the initial allocations for all required component
data cache areas. The total amount of auxiliary storage available must be
increased by adding or expanding external page data sets. If this threshold
is reached during an attempt to create or extend a data cache after CMAS initialization
has completed, ARM is invoked to attempt to restart the CMAS.
- MAXHISTRECS( value | 1)
- Specify a limit, in the range 1 to 50, on the number of records returned
on a completed task query from the MAS to 'value' thousand records. This can
be used to limit the amount of data in a request for completed task (HTASK)
resource table records. When this limit is reached, the CICSPlex SM API
GET request will receive a WARNING response and MAXRECORDS reason.
MSGBUCKETS(value | 1024)
Specify a value in the range 1 to 32768. This value specifies the number
of buffers to be allocated for Topology data collection in the MAS. Each
buffer is 64 bytes long. The buffer pool, allocated in the MAS cache data
space, is used by CPSM's XMEOUT and XRSINDI Global User Exits and by the MAS
Heartbeat task. The number of buffers must equal or exceed the total number
of connections, DSNAMEs, GLUEs, TRUEs, and FEPI connections defined in the
MAS. If the number of buffers is not sufficient for the Topology mapped resources
in the MAS, a trace record with debug text XDATLOST is written at every other
heartbeat interval when MAS Topology resource data is collected. If this occurs,
resources will be missing from Topology Resource Maps for the MAS in all CMASes
in the CICSplex, and query or action requests entered from the EUI or API
for specific resources may fail because the target resources are not known
to Topology.
- MSGCASE(MIXED | UPPER)
- Indicate whether the following types of output should
be displayed in mixed case or upper case:
- Messages issued by Message Services to the console, joblog, and EYULOG
- Batched repository-update facility output
- Diagnostic output from the CODB, COD0, and COLU transactions.
You can specify:
- MIXED
- Mixed case text is displayed as is.
If you specify MIXED, output
may be displayed incorrectly on Katakana display terminals, where lower case
characters are displayed as Katakana symbols.
- UPPER
- Mixed case text is displayed in upper case only.
- NAME(name)
Identify the 1- to 8-character name of the CMAS or local MAS that is to be started. If you do not specify
this parameter, the default is the VTAM® application ID.
- RESSTATUS(NOTIFY | MSG |
CONMSG)
- Indicate how the CMAS is to respond when a CICS resource that is being reported to the resource status facility has a change in operational
state:
- NOTIFY
- Issues event notifications in the form of ERESSTAT resource table records.
These event notifications can be monitored by using the LISTEN command of
the CICSPlex SM API. For more information, see the CICSPlex System Manager Application Programming Guide.
- MSG
- Writes external messages to EYULOG.
If you specify MSG, event notifications
are produced in addition to the messages.
- CONMSG
- Writes external messages to the job log, console, and EYULOG.
If
you specify CONMSG, event notifications are produced in addition to the messages.
Note:
Use this option with care. It could cause a large number
of messages to be sent to the console.
- SEC(YES | NO)
- For a CMAS, indicate whether the CMAS is to perform security
checking of CICSPlex SM requests directed to the CICS systems it manages.
When
NO all security-related parameters are ignored.
If a CMAS manages any CICS regions that are running with security active (SEC=YES specified as
a system initialization parameter), the CMAS must include SEC(YES) in EYUPARM.
If you do not activate CICSPlex SM security in the CMAS, a
connection cannot be established to a CICS system that specifies SEC=YES. If a connection
is attempted, the following message is issued to the console, the CMAS job
log, and the CMAS EYULOG:
EYUCR0007E Security mismatch between CMAS cmasname and
MAS masname. Connection terminating.
Note:
If a CMAS started with SEC(NO) connects directly or indirectly to
a CMAS started with SEC(YES), any request sent to the SEC(YES) CMAS will fail.
- If the request originates from the TSO EUI, the TSO user will receive
message: EYUEI0586E
- If the request originates from the CICSPlex SM API connected to the SEC(NO) CMAS,
the API request will receive: RESPONSE 1031 NOTPERMIT REASON 1345 USRID
- If the request originates from the CICSPlex SM Web User Interface server connected
to a SEC(NO) CMAS, the browser will receive message: EYUVC1220E
SECLOGMSG(NO | YES | ALL)
Controls whether CICSPlex SM should issue message EYUCR0009I
to the CMAS EYULOG, to record security failures.
When NO is specified, the
default, message EYUCR0009I is not issued.
Specify YES, or ALL, to cause
message EYUCR0009I to be issued.
SECLOGMSG(YES) can be useful if the
External Security Manager (ESM) does not issue messages when it cannot make
a decision, or when a failure occurs.
Note:
When SECLOGMSG(YES) is
specified, EYUCR0009I will be issued only for requests which are to be logged
to the ESM.
SECLOGMSG(ALL) causes EYUCR0009I to be
issued even when the ESM permits access to the resource. The ALL operand can
produce a large number of EYUCR0009I messages and should normally be used
only under the direction of IBM Support.
SECLOGMSG can be dynamically
changed in a CMAS with the COD0 SET command. See the CICS Problem Determination Guide for details.
SECPRFX(YES6 |prefix
userid
- Indicate whether the user ID is used as the prefix
that is added to the beginning of all resource names to distinguish this CICS system from other CICS systems.

SECTIMEOUT(value|30)
Specifies the time in minutes, in the range of 1 through 1440 (1 day),
that idle userids are to remain signed on within the CMAS before being considered
for timeout.
The value is also used to control how often the CMAS checks
for idle users to timeout. For example, with the default value of 30, the
CMAS will check every 30 minutes for users who have not used the CMAS for
30 minutes. However, as the times are not synchronized it may mean that the
userid will not be timed out for up to double the SECTIMEOUT value. Setting
this value low will increase the number of calls to the External Security
Manager (ESM). Setting this value high means that users may have to wait a
long time before automatically picking up security changes that affect the
userid (for example, adding the user to a new group).
The CMAS or CMASLIST
PURGE request (available from the EUI, API and WUI) can be used to force a
CMAS to check for users to timeout immediately.
The CMAS or CMASLIST
RESET USERID request (available from the API and WUI) can be used to force
the CMAS to rebuild the user's security information the next time it is used.
This request would typically be used after adding or removing a userid to,
or from, a group, and the user does not want to wait to be timed out to pick
up the change.
- SPOOLCLASS(class | P)
- Specify a SYSOUT class value, from A to Z, that identifies where CICSPlex SM spool output is to be sent.
Spool output can be generated
by these CICSPlex SM functions:
- The online utility transaction (COLU)
- The PRINT and CAPTURE commands of the interactive debugging transaction
(COD0).
- STALLxxxTSK
- Where xxx represents a CICSPlex SM suspend class. The
values for xxx are shown in Table 42.
Identify the
minimum number of concurrent tasks required to enter the suspend class. The
value may be between 0 and 999. The default value for each task is shown in Table 41. Use 0 to indicate STALL detection for the xxx suspend class
is not active.
- STALLxxxCNT
- Where xxx represents a CICSPlex SM suspend class. The values
for xxx are shown in Table 42.
Identify the number
of consecutive occurrences of an entry in the suspend class required for CICSPlex SM to report a STALL. The value may be between 0 and 999.
The default value for each task is shown in Table 41. Use 0
to indicate STALL detection for the xxx suspend class is not active.
- SUPPRESSCMF(YES | NO)
- For a local MAS, indicates whether
the records collected by the CICS Monitor Facility are written to SMF.
The parameter only suppresses CICS type 3 performance
class records. Type 4 exception records and type 5 transaction resource records
are not suppressed. The type 3 performance records are only suppressed if
the CICS region has an active CICSPlex SM monitor definition installed for
the MTRAN monitoring class. You can verify which CICS regions have active monitoring for the
MTRAN class by issuing the MONACTV view from the TSO End User Interface.
TOBATCHREQ(value | 0)
APAR
PK05183 added TOBATCHREQ, TOONLINEREQ, and TOPOLLINT
The time in seconds before a batch request directed to a MAS is timed
out. This includes RTA requests and API requests initiated from non-CICS
programs. Specify zero, or a value in the range 10 to 1800.
- If you specify zero, the default value of 240 seconds (4 minutes) is applied.
This value is then doubled when the request is transmitted to the MAS.
- If you specify a non-zero value in the range 10 to 1800, that value is
used.
- If you specify a non-zero value less than 10, TOBATCHREQ is set to 10.
Depending upon the value specified for TOBATCHREQ more time outs may
be received. This may be noticed in the following ways:
- RTA requests
- No data will be processed for any MAS that times out and no external
message will be displayed. This may cause an event to not be created, or
lead to premature termination of existing events.
- API requests initiated from non-CICS programs
- All API requests initiated from non-CICS programs will receive a REPSONSE
of ENVIRONERROR (1030) and REASON of REQTIMEOUT (1342) and no data records
will be returned, regardless of the CONTEXT and SCOPE of the request.
TOONLINEREQ(value | 0)
The time in seconds before an online request directed to a MAS is timed
out. This includes EUI and WUI requests and API requests initiated from
CICS programs. Specify zero, or a value in the range 10 to 1800.
- If you specify zero, the default value of 240 seconds (4 minutes) is applied.
This value is then doubled when the request is transmitted to the MAS.
- If you specify a non-zero value in the range 10 to 1800, that value is
used.
- If you specify a non-zero value less than 10, TOONLINEREQ is set to 10.
Depending upon the value specified for TOONLINEREQ more time outs
may be received. This may be noticed in the following ways:
- EUI requests
- If all systems that are part of the CONTEXT and SCOPE time out, the
following messages are returned to the EUI display:
- EYUEI0591E
- Communications to <masname> timed out
- BBMXBD15I
- There is no data that satisfies your request
- BBMXBD23I
- 0 records presented by the product
If at least one of the systems that are part of the CONTEXT and SCOPE
do not time out, the records for that system (or those systems) will
be displayed and no error messages will be displayed.
- WUI requests
- All WUI requests will receive the following message and no data records
will be displayed, regardless of the CONTEXT and SCOPE of the request.
- EYUVC1220E
- CICSPlex SM API command (GET) failed. (Environerror, Reqtimeout)
- API requests initiated from CICS programs
- All API requests initiated from CICS programs will receive a REPSONSE
of ENVIRONERROR (1030) and REASON of REQTIMEOUT (1342) and no data records
will be returned, regardless of the CONTEXT and SCOPE of the request.
TOPOLLINT(value | 300)
The time in seconds that a CMAS delays between checking all requests
to determine if they exceed their time out time. Since polling is used to
determine when to time out a request, more reliable time outs will occur if
this value is set less than or equal to both TOBATCHREQ and TOONLINEREQ.
When a request is directed to a MAS that is not connected to the originating
CMAS, it is transmitted from the originating CMAS to the remote CMAS to which
the MAS is connected. When this occurs, the remote CMAS performs the time
out processing, based upon the TOBATCHREQ and TOONLINEREQ values specified
in the originating CMAS and the TOPOLLINT value specified in the remote CMAS.
For this reason, time out processing will be more consistent if all CMASes
in the network have the same TOPOLLINT value.
WLMLOADCOUNT(ALLQUEUED | MXTQUEUED)
For a local MAS, indicates which queued tasks should be included in
the WLM task load count for the MAS.
Specify ALLQUEUED to include tasks
queued for both maxtask and tranclass.
Specify MXTQUEUED to include
tasks queued only for maxtask.
WLMLOADTHRSH(65 | 1 - 100)
For a local MAS that is defined as a CPSM WLM routing region, indicates
what task load percentage ((active tasks/maxtask) *100) should be used as
part of the determination as to when the routing region should route to target
regions on other CECs.
For example, if the default value of 65 is used,
then all target regions on the CEC where this routing region resides must
have a task load of 65% or higher before the routing region routes to target
regions on other CECs, if all other health factors (for example, short-on-storage)
for the routing regions are similar. As soon as all target regions on other
CECs achieve a task load of 65% or higher, the routing region resumes routing
to the target regions on the local CEC again. When a local target region's
task load drops below 65%, the routing region resumes routing to that target
region regardless of the task load in target regions on remote CECs.
Specifying this value lower than the default probably decreases the delay
in routing to target regions on remote CECs. Take care not to set this value
so low that the threshold is met by long-running tasks in the target regions.
Specifying this value higher than the default probably increases the
delay in routing to target regions on remote CECs.
Note that the effectiveness
of this parameter is increased as the characteristics (for example, maxtask
value or number of long-running tasks) of the target regions become
similar.