DISPLAY LOG (display log information) on z/OS

Using MQSC commands

For information on how you use MQSC commands, see Performing local administration tasks using MQSC commands.

Usage notes for DISPLAY LOG

1. DISPLAY LOG returns a report that shows the initial log parameters, and the current values as changed by the SET LOG command:
   • Whether log compression is active (COMPLOG).
   • Whether writes to the active logs are made with zHyperWrite being enabled (ZHYWRITE)
   • Length of time that an allowed archive read tape unit remains unused before it is deallocated (DEALLCT).
   • Size of input buffer storage for active and archive log data sets (INBUFF).
   • Size of output buffer storage for active and archive log data sets (OUTBUFF).
   • Maximum number of dedicated tape units that can be set to read archive log tape volumes (MAXRTU).
   • Maximum number of archive log volumes that can be recorded (MAXARCH).
   • Maximum number of concurrent log offload tasks (MAXCNOFF)
   • Whether archiving is on or off (OFFLOAD).
   • Whether single or dual active logging is being used (TWOACTV).
   • Whether single or dual archive logging is being used (TWOARCH).
   • Whether single or dual BSDS is being used (TWOBSDS).
   • Number of output buffers to be filled before they are written to the active log data sets (WRTHRSH).

   It also returns a report about the status of the logs.

2. This command is issued internally by IBM® MQ at the end of queue manager startup.

Parameter descriptions for DISPLAY LOG

CMDSCOPE

This parameter specifies how the command runs when the queue manager is a member of a queue sharing group.

CMDSCOPE cannot be used for commands issued from the first initialization input data set CSQINP1.

' '

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.

You can specify a queue manager name, other than the queue manager on which the command was entered, only if you are using a queue sharing group environment and if the command server is enabled.

*

The command runs 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.