Use CSQ6SYSP

Using CSQ6SYSP

Use CSQ6SYSP to set system parameters.
The default parameters for CSQ6SYSP, and whether we can alter each parameter using the SET SYSTEM command, are shown in Table 8. If you want to change any of these values, refer to the detailed descriptions of the parameters.
Table 8. Default values of CSQ6SYSP parameters

Parameter Description Default value SET command

CLCACHE Specifies the type of cluster cache to use. STATIC -
CMDUSER The default user ID for command security checks. CSQOPR -
CTHREAD Maximum number of connections from batch, CICS, IMS, TSO, and other tasks to a single queue manager. 300 X
EXITLIM Time (in seconds) for which queue-manager exits can execute during each invocation. 30 -
EXITTCB How many started server tasks to use to run queue manager exits. 8 -
IDBACK Maximum number of background connections to a single queue manager using batch connections. 20 X
IDFORE Maximum number of foreground connections to a single queue manager using batch connections. 100 X
LOGLOAD Number of log records written by WebSphere MQ between the start of one checkpoint and the next. 500 000 X
OTMACON OTMA connection parameters. See below -
QINDXBLD Determines whether queue manager restart waits until all indexes are rebuilt, or completes before all indexes are rebuilt. WAIT -
QMCCSID Coded character set identifier for the queue manager. zero -
QSGDATA Queue-sharing group parameters. See below -
RESAUDIT RESLEVEL auditing parameter. YES -
ROUTCDE Message routing code assigned to messages not solicited from a specific console. 1 -
SERVICE Reserved for use by IBM. 0 X
SMFACCT Specifies whether SMF accounting data is to be collected when the queue manager is started. NO -
SMFSTAT Specifies whether SMF statistics are to be collected when the queue manager is started. NO -
STATIME Default time, in minutes, between each gathering of statistics. 30 X
TRACSTR Specifies whether tracing is to be started automatically. NO -
TRACTBL Size of trace table, in 4 KB blocks, to be used by the global trace facility. 99 (396 KB) X
WLMTIME Time between scanning the queue index for WLM-managed queues. 30 -
WLMTIMU Units (minutes or seconds) for WLMTIME MINS -

CLCACHE

Specifies the type of cluster cache to use. See WebSphere MQ Queue Manager Clusters for more information.

STATIC

When the cluster cache is static, its size is fixed at queue manager start-up, enough for the current amount of cluster information plus some space for expansion. The size cannot increase while the queue manager is active. This is the default.

DYNAMIC

When the cluster cache is dynamic, the initial size allocated at queue manager startup can be increased automatically if required while the queue manager is active.

CMDUSER

Specifies the default user ID used for command security checks. This user ID must be defined to the ESM (for example, RACF). Specify a name of 1 through 8 alphanumeric characters. The first character must be alphabetic.
The default is CSQOPR.

CTHREAD

Specifies the maximum number of connections (of any type, such as batch, CICS, IMS, and the channel initiator) to the queue manager.
CICS connections are not limited in the same way as batch connections. During the connection of the main CICS TCB to WebSphere MQ, the adapter attaches up to eight z/OS subtasks (TCBs) to be used by this CICS system. This means each CICS system connected takes up nine of the connections specified on CTHREAD, so increase CTHREAD by nine for each CICS system connected. You must also increase the value of CTHREAD by one for each instance of the task initiator CKTI.
For IMS connections, the number of connections required is one for the control region, and one for each dependent region connected to WebSphere MQ. For each IMS MPP or IFP region that is defined to permit WebSphere MQ connections through either a specific SSM= EXEC parameter or through the control region default, a thread is created when the first application is scheduled in that region, regardless of whether that application invokes any WebSphere MQ calls. The value you set for CTHREAD should take account of this.
For distributed queuing, the number of connections required by the channel initiator address space depends on the number of adapter subtasks and dispatchers there are. The number of connections is up to eight plus the sum of the queue manager parameters CHIADAPS and CHIDISPS. See the description of the ALTER QMGR command in WebSphere MQ Script (MQSC) Command Reference.
When the number of connections reaches the limit set by CTHREAD, any further requests for a connection are suspended until a spare slot becomes available. For example, an MQDISC call releases that connection. For planning purposes, the value of CTHREAD must be greater than the maximum of IDBACK, IDFORE, and the number of potential connections from the CICS, IMS, and channel initiator address spaces.
Specify a number in the range 1 through 32 767.
The default is 300.
Note that this controls the number of connections; a connection might involve more than one thread. Connections and threads are discussed in the WebSphere MQ for z/OS Concepts and Planning Guide.

EXITLIM

Specifies the time, in seconds, allowed for each invocation of the queue manager exits. (This parameter has no effect on channel exits.)
Specify a value in the range 5 through 9999.
The default is 30. The queue manager polls exits that are running every 30 seconds. On each poll, any that have been running for more than the time specified by EXITLIM are forcibly terminated.

EXITTCB

Specifies the number of started server tasks to use to run exits in the queue manager. (This parameter has no effect on channel exits.)
Specify a value in the range zero through 99. A value of zero means that no exits can be run.
The default is 8.

IDBACK

Specifies the maximum number of background batch connections to the queue manager. The value of IDBACK is related to those of IDFORE and CTHREAD. See the description of the CTHREAD parameter for more information.
Specify a number in the range 1 through 32 767.
The default is 20.

IDFORE

Specifies the maximum number of foreground batch connections to the queue manager.
The value of IDFORE is related to those of IDBACK and CTHREAD. See the description of the CTHREAD parameter for more information.
The number of TSO connections might be greater than the number of concurrent TSO users if, for example, users split their ISPF screens.
Specify a number in the range zero through 32 767.
The default is 100.

LOGLOAD

Specifies the number of log records that WebSphere MQ writes between the start of one checkpoint and the next. WebSphere MQ starts a new checkpoint after the number of records that you specify has been written.
Specify a value in the range 200 through 16 000 000.
The default is 500 000.
The greater the value, the better the performance of WebSphere MQ; however, restart takes longer if the parameter is set to a large value.
Suggested settings:

Test system 10 000
Production system 500 000
In a production system, the supplied default value might result in a checkpoint frequency that is too high.

The value of LOGLOAD determines the frequency of queue manager checkpoints. Too large a value means that a large amount of data is written to the log between checkpoints, resulting in an increased queue manager forward recovery restart time following a failure. Too small a value causes checkpoints to occur too frequently during peak load, adversely affecting response times and CPU usage.
An initial value of 500 000 is suggested for LOGLOAD. (For example, this adds approximately 90 seconds to the restart time after a failure if using RAMAC Virtual Array 2 Turbo 82 (RVA2-T82) DASD.) For a 1 KB persistent message rate of 100 messages a second (that is, 100 MQPUTs with commit and 100 MQGETs with commit) the interval between checkpoints is approximately 5 minutes.
Note:
This is intended as a guideline only and the optimum value for this parameter is dependent on the characteristics of the individual system.

OTMACON

OTMA parameters. This keyword takes five positional parameters, as shown below:

OTMACON = (
Group,Member,Druexit,Age,Tpipepfx)

Group

This is the name of the XCF group to which this particular instance of WebSphere MQ belongs.
It can be 1 through 8 characters long and must be entered in uppercase characters.
The default is blanks, which indicates that WebSphere MQ should not attempt to join an XCF group.

Member

This is the member name of this particular instance of WebSphere MQ within the XCF group.
It can be 1 through 16 characters long and must be entered in uppercase characters.
The default is the 4-character queue manager name.

Druexit

This specifies the name of the OTMA destination resolution user exit to be run by IMS.
It can be 1 through 8 characters long.
The default is DFSYDRU0.
This parameter is optional; it is required if WebSphere MQ is to receive messages from an IMS application that was not started by WebSphere MQ. The name should correspond to the destination resolution user exit coded in the IMS system. For more information see Appendix C. Using OTMA exits in IMS.

Age

This represents the length of time, in seconds, that a user ID from WebSphere MQ is considered previously verified by IMS.
It can be in the range zero through 2 147 483 647.
The default is 2 147 483 647.
You are recommended to set this parameter in conjunction with the
interval parameter of the ALTER SECURITY command to maintain consistency of security cache settings across the mainframe.

Tpipepfx

This represents the prefix to be used for Tpipe names.
It comprises three characters; the first character is in the range A through Z, subsequent characters are A through Z or 0 through 9. The default is CSQ.
This is used each time WebSphere MQ creates a Tpipe; the rest of the name is assigned by WebSphere MQ. We cannot set the full Tpipe name for any Tpipe created by WebSphere MQ.

QINDXBLD

Determines whether queue manager restart waits until all queue indexes are rebuilt, or completes before all indexes are rebuilt.

WAIT

Queue manager restart waits for all queue index build to complete. This means that no applications are delayed during normal WebSphere MQ API processing while the index is created, as all indexes are created before any applications can connect to the queue manager.
This is the default.

NOWAIT

Queue manager restart can complete before all queue index building is completed.

QMCCSID

Specifies the default coded character set identifier that the queue manager (and therefore distributed queuing) is to use.
Specify a value in the range zero through 65 535. Zero means use the CCSID currently set or, if none is set, use CCSID 500.
The default is zero.

QSGDATA

Queue-sharing group data. This keyword takes four positional parameters, as shown below:

QSGDATA=(
Qsgname,Dsgname,Db2name,Db2serv)

Qsgname

This is the name of the queue-sharing group to which the queue manager belongs.
It can be 1 through 4 characters long. Acceptable characters are uppercase A-Z, 0-9, $, #, and @. It must not start with a numeric. For implementation reasons, names of less than four characters are padded internally with @ symbols, so do not use a name ending in @.
The default is blanks, which indicates that the queue manager is not a member of any queue-sharing group.

Dsgname

This is the name of the DB2 data-sharing group to which the queue manager is to connect.
It can be 1 through 8 characters long and must be entered in uppercase characters.
The default is blanks, which indicates that you are not using queue-sharing groups.

Db2name

This is the name of the DB2 subsystem or group attachment to which the queue manager is to connect.
It can be 1 through 4 characters long and must be entered in uppercase characters.
The default is blanks, which indicates that you are not using queue-sharing groups.
Note:
The DB2 subsystem (or group attachment) must be in the DB2 data-sharing group specified in the
Dsgname, and all queue managers must specify the same DB2 data-sharing group.

Db2serv

This is the number of server tasks used for accessing DB2.
It can be in the range 4 through 10.
The default is 4.

If you specify one of the name parameters (that is, not the Db2serv parameter), enter values for the other names, otherwise WebSphere MQ fails.

RESAUDIT

Specifies whether RACF audit records are written for RESLEVEL security checks performed during connection processing.
Specify one of:

NO

RESLEVEL auditing is not performed.

YES

RESLEVEL auditing is performed.

The default is YES.

ROUTCDE

Specifies the default z/OS message routing code assigned to messages that are not sent in direct response to an MQSC command.
Specify one of:

A value in the range 1 through 16, inclusive.
A list of values, separated by a comma and enclosed in parentheses. Each value must be in the range 1 through 16, inclusive.

The default is 1.
For more information about z/OS routing codes, see the MVS Routing and Descriptor Codes manual.

SERVICE

This field is reserved for use by IBM.

SMFACCT

Specifies whether WebSphere MQ sends accounting data to SMF automatically when the queue manager starts.
Specify one of:

NO

Do not start gathering accounting data automatically.

YES

Start gathering accounting data automatically for the default class 1.

The default is NO.

SMFSTAT

Specifies whether to gather SMF statistics automatically when the queue manager starts.
Specify one of:

NO

Do not start gathering statistics automatically.

YES

Start gathering statistics automatically for the default class 1.

The default is NO.

STATIME

Specifies the default time, in minutes, between consecutive gatherings of statistics.
Specify a number in the range zero through 1440.
If you specify a value of zero, both statistics data and accounting data is collected at the SMF data collection broadcast. See Using System Management Facility for information about setting this.
The default is 30.

TRACSTR

Specifies whether global tracing is to start automatically.
Specify one of:

NO Do not start global tracing automatically.
YES Start global tracing automatically for the default class, class 1.
integers A list of classes for which global tracing is to be started automatically in the range 1 through 4.
* Start global trace automatically for all classes.

The default is NO if you do not specify the keyword in the macro.
Note:
The supplied default system parameter load module (CSQZPARM) has TRACSTR=YES (set in the assembler module CSQFSYSP). If you do not want to start tracing automatically, either create your own system parameter module, or issue the STOP TRACE command after the queue manager has started.
For details about the STOP TRACE command, see the WebSphere MQ Script (MQSC) Command Reference manual.

TRACTBL

Specifies the default size, in 4 KB blocks, of trace table where the global trace facility stores WebSphere MQ trace records.
Specify a value in the range 1 through 999.
The default is 99. This is equivalent to 396 KB.
Note:
Storage for the trace table is allocated in the ECSA. Therefore, select this value with care.

WLMTIME

Specifies the time (in minutes or seconds depending on the value of WLMTIMU) between each scan of the indexes for WLM-managed queues.
Specify a value in the range 1 through 9999.
The default is 30.

WLMTIMU

Time units used with the WLMTIME parameter.
Specify one of :

MINS

WLMTIME represents a number of minutes.

SECS

WLMTIME represents a number of seconds.

The default is MINS.

Parameter	Description	Default value	SET command
CLCACHE	Specifies the type of cluster cache to use.	STATIC	-
CMDUSER	The default user ID for command security checks.	CSQOPR	-
CTHREAD	Maximum number of connections from batch, CICS, IMS, TSO, and other tasks to a single queue manager.	300	X
EXITLIM	Time (in seconds) for which queue-manager exits can execute during each invocation.	30	-
EXITTCB	How many started server tasks to use to run queue manager exits.	8	-
IDBACK	Maximum number of background connections to a single queue manager using batch connections.	20	X
IDFORE	Maximum number of foreground connections to a single queue manager using batch connections.	100	X
LOGLOAD	Number of log records written by WebSphere MQ between the start of one checkpoint and the next.	500 000	X
OTMACON	OTMA connection parameters.	See below	-
QINDXBLD	Determines whether queue manager restart waits until all indexes are rebuilt, or completes before all indexes are rebuilt.	WAIT	-
QMCCSID	Coded character set identifier for the queue manager.	zero	-
QSGDATA	Queue-sharing group parameters.	See below	-
RESAUDIT	RESLEVEL auditing parameter.	YES	-
ROUTCDE	Message routing code assigned to messages not solicited from a specific console.	1	-
SERVICE	Reserved for use by IBM.	0	X
SMFACCT	Specifies whether SMF accounting data is to be collected when the queue manager is started.	NO	-
SMFSTAT	Specifies whether SMF statistics are to be collected when the queue manager is started.	NO	-
STATIME	Default time, in minutes, between each gathering of statistics.	30	X
TRACSTR	Specifies whether tracing is to be started automatically.	NO	-
TRACTBL	Size of trace table, in 4 KB blocks, to be used by the global trace facility.	99 (396 KB)	X
WLMTIME	Time between scanning the queue index for WLM-managed queues.	30	-
WLMTIMU	Units (minutes or seconds) for WLMTIME	MINS	-

Test system	10 000
Production system	500 000 In a production system, the supplied default value might result in a checkpoint frequency that is too high.

NO	Do not start global tracing automatically.
YES	Start global tracing automatically for the default class, class 1.
integers	A list of classes for which global tracing is to be started automatically in the range 1 through 4.
*	Start global trace automatically for all classes.