COMM (Communicate with MUF) › COMM EOJ (End MUF Processing) › Summary Reports Produced by the MUF During its EOJ Process › MUF EOJ Log Status Information

MUF EOJ Log Status Information

The following is an example of an EOJ Report that you get if the MUF opened the log.

                                            MUF EOJ LOG STATUS INFORMATION
 
MUF EOJ, LOG CLOSED, CLEAN EOJ                  
LOG CONTROL BYTES-229,376 ROLLBACK-3,963           
LOG RECORD BYTES-22,373,107 WRITTEN-24,891,580     
LOG RECORD SEQ-3 LOG BLOCK SEQ-243             

This page of the report provides the following information:

MUF EOJ, LOG CLOSED, CLEAN EOJ

This message indicates that there was a clean EOJ. If the EOJ had not been clean, other messages would have appeared here.

LOG CONTROL BYTES

This line gives LOG CONTROL BYTES information, that is, the number of bytes written when writing the control block. The control block is written as required. It is possible to use X_LOG_CONTROL_BLKS to control this writing, and if you are changing the defaults, the count shown in LOG CONTROL BYTES shows the variations. However, while changing the values are possible, we do not recommend your doing so. More writes allow a faster restart process. Fewer writes lengthen the restart process.

On the same line is ROLLBACK bytes written information. This refers to the rewritten blocks that have had one or more log records subject to rollback (transaction backout) and that therefore needed to be rewritten. This count indicates, therefore, the log records that have been undone. You have a certain amount of control over this process when your applications are designed to do frequent ROLBK or LOGTB commands.

LOG RECORD BYTES

This line gives LOG RECORD BYTES n, where n can be up to 31 digits, which is the total number of bytes in all the log records built by this MUF. The number is not affected by how CA Datacom/DB chooses to write the bytes to DASD. The number is not affected by spilling or transaction backout.

With LOG RECORD BYTES, there is also WRITTEN information displayed. WRITTEN n information, where n is up to 31 digits, indicates the total number of bytes written to local DASD.

With some logging options, WRITTEN n and LOG RECORD BYTES n match, but with other logging options they do not match. To maximize bytes written to a given track, CA Datacom/DB rewrites bytes.

LOG RECORD SEQ

This line gives the Log Record Sequence Number, that is, the count of log records added during this MUF execution, except that the count can be reset to 1 during QUIESCE processing. In a MUFplex environment, the MUF execution is defined as the enabling of a MUF in the MUFplex when no other MUFs are currently executing. The number is important. It should not be allowed to reach 4 billion, because at that number MUF terminates.

The line also gives the Log Block Sequence Number. This number starts at any number less than the number of tracks or blocks of the LXX when MUF is enabled. The same MUFplex rules as just previously given apply. The number is incremented for each log track or block with new log records. This number can only be reset by ending the MUF or all MUFplex MUFs and re-enabling it or them. The number is important. It should not be allowed to reach 4 billion, because at that number MUF terminates. This means that a busy MUF cannot remain enabled for years at a time.