SET LOG
Use SET LOG to dynamically change certain log system parameter values that were initially set by CSQ6LOGP.
Synonym: SET LOG
>>-SET LOG--+-DEFAULT-------------+-----------------------------> '-| parameter block |-' .-CMDSCOPE(' ')------------. >--+--------------------------+-------------------------------->< | (1) | +-CMDSCOPE(qmgr-name)------+ | (1) | '-CMDSCOPE(*)--------------' Parameter Block |--+------------------+--+--------------------+-----------------> +-DEALLCT(integer)-+ '-MAXARCH--(integer)-' '-DEALLCT(NOLIMIT)-' >--+-------------------+--+--------------------+----------------| '-MAXRTU--(integer)-' '-WRTHRSH--(integer)-'
Notes:
- Valid only on full function WebSphere MQ for z/OS when the queue manager is a member of a queue-sharing group.
Parameter descriptions
- CMDSCOPE
- This parameter applies to z/OS only and specifies how the command is executed when the queue manager is a member of a queue-sharing group.
- ' '
- The command is executed on the queue manager on which it was entered. This is the default value.
- qmgr-name
- The command is executed on the queue manager you specify, providing the queue manager is active within the queue-sharing group.
You can specify a queue manager name, other than the queue manager on which it was entered, only if you are using a queue-sharing group environment and if the command server is enabled.
- *
- The command is executed on the local queue manager and is also passed to every active queue manager in the queue-sharing group. The effect of this is the same as entering the command on every queue manager in the queue-sharing group.
- DEFAULT
- Resets the parameters to the values specified in the archive system parameters set by CSQ6LOGP.
- DEFAULT
- Resets the parameters to the values specified in the archive system parameters set by CSQ6LOGP.
Parameter block
For a full description of these parameters, see the WebSphere MQ for z/OS System Setup Guide.
Parameter block is any one or more of the following parameters that you want to change:
- DEALLCT
- Specifies the length of time that an allocated archive read tape unit is allowed to remain unused before it is deallocated. You are recommended to specify the maximum possible values, within system constraints, for both options to achieve the optimum performance for reading archive tapes.
This, together with the MAXRTU parameter, allows WebSphere MQ to optimize archive log reading from tape devices.
The possible values are:
- integer
- Specifies the maximum time in minutes, between zero and 1439. Zero means that a tape unit is deallocated immediately.
- NOLIMIT or 1440
- Indicates that the tape unit is never deallocated.
- MAXARCH
- Specifies the maximum number of archive log volumes that can be recorded in the BSDS. When this number is exceeded, recording begins again at the start of the BSDS.
Use a decimal number in the range 10 through 1000.
- MAXRTU(integer)
- Specifies the maximum number of dedicated tape units that can be allocated to read archive log tape volumes. This overrides the value for MAXRTU set by CSQ6LOGP in the archive system parameters.
This, together with the DEALLCT parameter, allows WebSphere MQ to optimize archive log reading from tape devices.
Notes:
- The integer value can range from 1 to 99.
- If the number specified is greater than the current specification, the maximum number of tape units allowable for reading archive logs increases.
- If the number specified is less than the current specification, tape units that are not being used are immediately deallocated to adjust to the new value. Active, or premounted, tape units remain allocated.
- A tape unit is a candidate for deallocation because of a lowered value only if there is no activity for the unit.
- When you are asked to mount an archive tape and you reply "CANCEL", the MAXRTU value is reset to the current number of tape units.
For example, if the current value is 10, but you reply "CANCEL" to the request for the seventh tape unit, the value is reset to six.
- WRTHRSH
- Specifies the number of 4 KB output buffers to be filled before they are written to the active log data sets.
The larger the number of buffers, the less often the write takes place, and this improves the performance of WebSphere MQ. The buffers might be written before this number is reached if significant events, such as a commit point, occur.
Specify the number of buffers in the range 1 through 256.
Usage notes
- Any changes to WRTHRSH take immediate effect.
- Any change to MAXARCH takes effect for the next scheduled off-load (that is, not for any off-load in progress at the time the command is issued).
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.