DEFINE LOG on z/OS
Use the MQSC command DEFINE LOG to add a new active log data set in the ring of active logs.
Use MQSC commands
For information on how we use MQSC commands, see Performing local administration tasks using MQSC commands.
We can issue this command from sources CR. For an explanation of the source symbols, see Sources from which we can issue MQSC commands on z/OS .
The named data set is dynamically allocated to the running queue manager, added to either the COPY1 or COPY2 active log and the BSDS updated with the information so it is retained over a queue manager restart. The data set is added to the active log ring in a position such that it will be the next active log used when the current active log fills and an active log switch occurs.
Synonym: DEF LOG
DEFINE LOG
Notes:- 1 Valid only when the queue manager is a member of a queue sharing group.
Usage note for DEFINE LOG
If a log data set has to be added because there is no more log space and the queue manager is waiting, we must issue the command from the z/OS console, and not through the command server.Parameter descriptions for DEFINE LOG
- (name)
-
The name of the new log data
set. This is required and is the name of a VSAM linear data set which will have already been defined
by Access Method Services (and, optionally, formatted by utility CSQJUFMT). This is allocated
dynamically to the queue manager.
The maximum length of the string is 44 characters. The string must conform to z/OS data set naming conventions.
- COPY
-
Specifies the number of an active log ring to which to add the new log data set. This is either 1 or 2 and is required.
- CMDSCOPE
-
This parameter specifies
how the command runs when the queue manager is a member of a queue sharing group.
- ' '
- The command runs on the queue manager on which it was entered. This is the default value.
- qmgr-name
- The command runs on the queue manager you specify, providing the queue manager is active within
the queue sharing group.
We can specify a queue manager name other than the queue manager on which it was entered, only if we are using a shared queue environment and if the command server is enabled.
Parent topic: MQSC commands