DSNJ370I csect-name LOG DISPLAY CURRENT display-log-output

Explanation

This message marks the beginning of multiple lines of information in response to a DISPLAY LOG command. Some lines in the output have their own message numbers or alphanumeric identifiers to assist with identification.

Depending on other command options or system conditions, some additional detail lines are present within the report block:

DSNJ370I Output

The output from this command has the following general structure:

DSNJ370I csect-name LOG DISPLAY
CURRENT COPY1 LOG = dsname1 IS pct1% FULL 
KEY LABEL = keylabel-name1
CURRENT COPY2 LOG = dsname2 IS pct2% FULL 
KEY LABEL = keylabel-name2
          H/W RBA = hw-rba
          H/O RBA = ho-rba
          FULL LOGS TO OFFLOAD = full-count OF total-count
          OFFLOAD TASK IS status
          SOFTWARE ACCELERATION IS ENABLED
          ZHYPERLINK WRITE IS ENABLED
            LAST LOG WRITE FOR COPY1 USED ZHYPERLINK
            LAST LOG WRITE FOR COPY2 DID NOT USE ZHYPERLINK

          time-date-2
csect-name
The name of the control section that issued the message.
dsname1
The name of the current active log COPY 1 data set. This data set is used for the first copy of the active log. If the value for dsname1 is INACTIVE, this copy of the log is not currently active.
pct1
The percentage of log space in the active log COPY 1 data set that has been used for writing log records.
dsname2
The name of the current active log COPY 2 data set. This data set is used for the second copy of the active log. If the value for dsname2 is INACTIVE, this copy of the log is not currently active.
keylabel-name1
The key label name that was used to encrypt the active log COPY1 data set.
pct2
The percentage of log space in the active log COPY 2 data set that has been used for writing log records.
keylabel-name2
The key label name that was used to encrypt the active log COPY2 data set.
hw-rba
The RBA of the most recently written log record.
ho-rba
The highest log RBA that has been offloaded to an archive log data set.
full-count
The number of full active log data sets that have not been archived.
total-count
The total number of active log data sets.
status
The status of the offload task. status can be one of the following values:
BUSY,ALLC
The task is busy allocating an archive log data set. This status might indicate that a tape mount request is outstanding.
BUSY,BSDS
The task is busy copying the bootstrap data set (BSDS).
BUSY,ACTV
The task is busy copying an active log data set.
BUSY
The task is busy with other processing.
AVAILABLE
The task is available for work.
accel-status
The status of software-controlled mirroring, either ENABLED or DISABLED based on the setting of the REMOTE_COPY_SW_ACCEL subsystem parameter.
zhyperlink-status
The status of the ZHYPERLINK Db2 zparm, either ENABLED or DISABLED based on the setting of ZHYPERLINK Db2 parameter (shows enabled when the value is ZHYPERLINK=ENABLE or ZHYPERLINK=ACTIVELOG).

If the ZHYPERLINK Db2 system parameter is set to ENABLE or ACTIVELOG, DFSMS does a zhyperwrite implicitly, even if the REMOTE_COPY_SW_ACCEL Db2 system parameter is not enabled.

copy1 zhyperlink last IO status
LAST LOG WRITE status shows whether ZHYPERLINK was used successfully for the copy1 active log.

If the ZHYPERLINK Db2 zparm is enabled and all of the required prerequisites are in place for exploiting ZHYPERLINK write, the LAST LOG WRITE message should show successful ZHYPERLINK writes. If the message NOT USED is shown consistently, refer to this link for the required prerequisites for ZHYPERLINK write.

copy2 zhyperlink last IO status
LAST LOG WRITE status shows whether ZHYPERLINK was used successfully for the copy2 active log.

If the ZHYPERLINK Db2 zparm is enabled and all of the required prerequisites are in place for exploiting ZHYPERLINK write, the LAST LOG WRITE message should show successful ZHYPERLINK writes. If the message NOT USED is shown consistently, refer to this link for the required prerequisites for ZHYPERLINK write.

DSNJ371I Output

There are two possible outputs for DSNJ371I, depending on the CHKTYPE subsystem parameter values.

When the number of minutes and the number of log records are used to determine the checkpoint frequency, the output has the following structure:

 DSNJ371I  DB2 RESTARTED time-date-1
          RESTART RBA rstrt-rba
          CHECKPOINT FREQUENCY quantity-and-type
          LAST SYSTEM CHECKPOINT TAKEN

When both the number of minutes and the number of log records are used to determine the checkpoint frequency, the output includes the following alternative form of message DSNJ371I, which shows both values:

DSNJ371I  DB2 RESTARTED time-date-1
          RESTART RBA rstrt-rba
          CHECKPOINT FREQUENCY quantity-and-type OR quantity-and-type
          LAST SYSTEM CHECKPOINT TAKEN time-date-2
time-date-1
The time and date when Db2 started.
rstrt-rba
The RBA that Db2 began logging when it started.
quantity-and-type
The number of minutes or the number of log records that determine the current checkpoint frequency.
time-date-2
The time and date of the last system checkpoint.

DSNJ375I Output

Start of changeMessage DSNJ375I provides information about a compression dictionary data set that contains compression or expansion dictionaries for table space data in the log.End of change

Start of changeWhen the log is on a member of a data sharing group that is a component of a GDPS® Continuous Availability with zero data loss environment, or when the CDDS_MODE subsystem parameter value is SOURCE_ONLY, message DSNJ375I follows message DSNJ371I. End of change

DSNJ375I csect-name CDDS DSNAME=dsname3 IS cdds-status IN
          cdds-mode MODE.
csect-name
The name of the control section that issued the message.
dsname3
The name of the compression dictionary data set (CDDS) that interprets the log.
cdds-status
The status of the CDDS.
cdds-status can be one of the following values:
  • ACTIVE
  • INACTIVE
  • ACTIVE AND BROKEN
  • INACTIVE AND BROKEN
ACTIVE
When cdds-mode is SOURCE or PROXY, the CDDS is accessible for read/write access in the source data sharing group. The CDDS is accessible for read/only access in the proxy data sharing group.

When cdds-mode is SOURCE_ONLY, the CDDS is accessible for read/write access in the data sharing group or stand-alone Db2 subsystem.

INACTIVE
When cdds-mode is SOURCE or PROXY, the CDDS is not accessible for read/write access in the source data sharing group. The CDDS is not accessible for read/only access in the proxy data sharing group.

When cdds-mode is SOURCE_ONLY, the CDDS is not accessible for read/write access in the data sharing group or stand-alone Db2 subsystem.

Start of changeBROKENEnd of change
Start of changeThe CDDS is in an unusable state. The CDDS must be deleted and redefined to make it accessible for read/write access.End of change
cdds-mode
The purpose of the data sharing group or stand-alone Db2 subsystem to which the log belongs:
SOURCE
The data sharing group in a GDPS Continuous Availability with zero data loss environment supports replication of its log data sets by another data sharing group.
PROXY
The data sharing group in a GDPS Continuous Availability with zero data loss environment supports replication of log data sets for another data sharing group.
Start of changeSOURCE_ONLYEnd of change
Start of changeThe stand-alone Db2 subsystem or all members of the data sharing group that is not in a GDPS Continuous Availability with zero data loss environment can use the expansion dictionary that is in the compression dictionary data set to decompress table space data in log records.End of change

DSNJ384I Output

When the DETAIL option is specified for the DISPLAY LOG command, the output includes the message DSNJ384I. It provides information regarding the status of the active log data sets in the specified copy. If the removal-pending-count is greater than zero, it is followed by a list of active log data sets with a removal pending status, the date and time the -SET LOG REMOVELOG was first issued, and the number of active log readers.

Start of change
DSNJ384I -DB2A
 COPYlog-copy LOGS: TOTAL=total-cnt NOTREUSABLE=notreusable-cnt REUSABLE=reusable-cnt
                                    STOPPED=stopped-cnt REMOVAL PENDING=removal-pending-cnt
End of change

If there are any removal pending active log data sets for the specific COPYn, the following information is displayed after the active log status counts. This section includes the date and time the removal log pending was set, the number of readers, and the data set name: 

--------------------------------------------------------------------
LOG DATA SET NAME                           REMOVAL PENDING READERS
log-dsname                                  yy.ddd hh.mm.ss num-readers
log-copy
The active log copy for this message, either 1 or 2.
total-cnt
The total number of active log data sets in the specified log copy.
notreusable-cnt
The number of active log data set with a NOT REUSABLE status in the specified log copy.
reusable-cnt
The number of active log data set with a REUSABLE status in the specified log copy.
stopped-cnt
The number of active log data set with a STOPPED status in the specified log copy.
removal-pending-cnt
The number of active log data set with a REMOVAL PENDING status in the specified log copy.
log-dsname
The active log data set name with a status of REMOVAL PENDING.
yy.ddd hh.mm.ss
The year, day of year, hour, minutes, and seconds when the log was set to REMOVAL PENDING status.
num-readers
The number of readers using this active log data set for the current member. For data sharing, peer member usage counts are not included.