MAXWRITERTHREADS

Description

The Classic data server uses the value of the MAXWRITERTHREADS configuration parameter to determine the maximum number of CICS writer tasks that can be started.

When you define MAXWRITERTHREADS, you also need to consider the following associated parameters:

• If you increase the value beyond 255, you must restart the target server. If you do not restart, attempts to start writers beyond 255 return errors with specific return code 0066000B because the session table is created at startup by using this value or a minimum of 255.
• Ensure that your system's MAXPROCUSER value is high enough to avoid EC6 abends in the CICS replication region in program EZACIC01. You change the MAXPROCUSER either in BPXPRMxx or dynamically with z/OS® command SETOMVS MAXPROCUSER=. You can use z/OS command DISPLAY OMVS,O to see your current value.

When the target server is configured for journal replication, the MAXWRITERTHREADS configuration parameter identifies the maximum number of writer services the applied service can start. The applied service starts an initial pool of writer services based on the value that is specified on the WRITERTRHEADS configuration parameter.

The applied service only starts a new writer thread when all existing threads are in-use, and a log buffer is received from the capture service for a subscription that is not currently being serviced by a writer thread. Once a writer is started, it cannot be stopped. While specifying a MAXWRITERTHREADS value larger than 255 should not be necessary, the target severs needs to be stopped and restarted if a MAXWRITERTHREADS value greater than 255 is provided on a SET, CONFIG command.

See WRITERTHREADS for specific guidelines about defining each of these parameters.

Specifications

Use: Configuration parameter for the applied service.

Service class: APLY

Service task: CECAPLY

Data type: INT

Default: 10

Valid values: 1 - 2147483647