Skip to content
CA Datacom Core - 15.1
Documentation powered by DocOps

COMM EOJ - EOJ_OK (End MUF Processing)

Last update March 1, 2019

The Comm EOJ (EOJ_OK) function communicates with one MUF. Be aware of the following:

  • Ensure that DBUTLTY is communicating with the desired MUF by executing DBUTLTY with the same System Identifier module (DBSIDPR) that is being used by the MUF, and
  • Ensure proper load library concatenation by keeping the System Identifier modules (DBSIDPR) in separate load libraries.

If the z/OS Cross-System Coupling Facility (XCF) is being used, ensure that the TOGROUP DBSIDPR parameter is correctly defined. For more information about XCF, see Administrating.

When using a console command, these steps are unnecessary.

The following topics are discussed on this page:

When to Use

Use the COMM EOJ option to end the MUF in an orderly fashion. This is the recommended way to terminate the MUF. The MUF supports being terminated as an orderly EOJ by supporting the z/OS command STOP ‘P’.

Processing of EOJ Requests

The COMM EOJ option informs the MUF that processing is to end. After receiving an EOJ request, it is acknowledged with message DB00247I - EOJ REQUESTED, NO NEW CONNECTIONS, EOJOFF AVAILABLE, and the MUF does not allow any new jobs to start processing. MUF allows jobs in progress to continue. The MUF goes to EOJ when the last job completes. A job is considered complete when all open User Requirements Tables have been closed.

There are exceptions to the closing of User Requirements Tables (URT) to support special situations. There is a URT option on the DBURSTR Macro named EOJ_OK that can be set to YES for a Job connected to MUF having a single task area. The details of the keyword are documented with the URT description. If the requirements are met, as part of EOJ detection the Job can be set as missing and the task area be set to close its URT, thereby moving the EOJ to closer execution. A second ability exists for Job connections that use multiple task areas known as EOJ_OK_S, (see the information about Extended Options Entry Processing in Administrating).

It is at the point of the URT closings that the EOJ is committed, noted with message: DB00243I - EOJ COMMITTED, EOJOFF DISABLED.

When the MUF is terminated an EOJ report is written to the SYSPRINT file. The report contains information about the following:

  • An echo of MUF startup options
  • A set summary information as shown in EOJ Reports.

No other COMM function, except the COMM EOJOFF console command, is accepted by the MUF after this option is initiated. Once an EOJ request is accepted by the MUF, the request can only be canceled with the COMM EOJOFF command. Unless EOJOFF is used, the MUF must be allowed to complete termination processing. See Administrating for details about using EOJOFF. After the MUF is started again, new jobs can be executed.

Online systems must initiate a close request for each User Requirements Table opened.

MVS STOP

The MVS STOP console command is honored by the MUF as equal to the COMM EOJ command.

How to Use the Console Command

The MUF must be active when you execute this command.

Use the following in your command to initiate this function from the system console. Consult your site operating system documentation for additional syntax information.

►►─┬────────┬ EOJ ────────────────────────────────────────────────────►◄
   └─ COMM ─┘

Command

  • COMM
    You can omit the COMM function name when submitting this console command.
  • EOJ

Specifies the COMM EOJ option is the desired action.

How to Use the DBUTLTY Command

The MUF must be active when you execute this command. Execute the COMM function with the following command format.

►►─ COMM OPTION= ─ EOJ ─┬──────────────────────┬──────────────────────►◄
                        └─ ,IGN68= ─┬─ NO ◄ ─┬─┘
                                    └─ YES ──┘

Command

  • COMM
    Invokes the function to pass communication to the MUF.

Required Keyword

  • OPTION=EOJ
    Requests normal termination of the MUF.

Optional Keyword

  • IGN68=
    Specify IGN68=YES to ignore a return code 68. IGN68= is allowed for every ACCESS and COMM function. By ignoring return code 68, you can set up and run JCL that incorporates a stack of DBUTLTY functions without requiring that the MUF be enabled. IGN68= would therefore be useful, for example, if you wanted to load a database without first enabling the MUF, perhaps to allow restart to properly occur. Following is an example showing a stack of DBUTLTY functions that use IGN68=.

     ACCESS STATUS=UTLTY,DBID=997,USERS=WAIT,IGN68=YES
     COMM   OPTION=CLOSE,DBID=997,IGN68=YES
     INIT   AREA=IXX,DBID=997
     INIT   AREA=A01,DBID=997
     LOAD   AREA=A01,DBID=997,FORMAT=NONE,KBYTES=9999,SORT=1
     ACCESS STATUS=WRITE,DBID=997,IGN68=YES

    Note: If the CXX is externally secured, the INIT and LOAD functions do not execute without the MUF being available, and IGN68=YES is therefore not recommended.

    A function or functions specified with IGN68=YES generates message DB13001E to note that the function did not occur. Because no error was recognized, however, other functions in the stack continue to execute, and the DBUTLTY step ends without a recognizable error. Message DB13001E signals that the MUF was not enabled For details, see DB13001E.
    The DBSYSID macro parameter DELAY68= can be used to specify the number of minutes that the MUF connection can wait if the MUF is not currently available. But if IGN68=YES is specified, DELAY68= is ignored and the function continues. If the delay is desired, however, either do not specify IGN68=, in which case it defaults to NO, or specify IGN68=NO.

    • Valid Entries:
      NO or YES
    • Default Value:
      NO

Example JCL

The following shows the command to issue the EOJ option.

Note: Use the following as a guide to prepare your JCL. The JCL statements are for example only. Lowercase letters in a statement indicate a value you must supply. Code all statements to your site and installation standards.

 //jobname    See the previous note
 //       EXEC PGM=DBUTLTY,REGION=2M
 //STEPLIB    See the previous note
 //SYSIN    DD *                                   Command input
           COMM     OPTION=EOJ
 /*

Sample Report

Following is a sample report page. For an example report header, see Sample Report Headers.

Sample Report COMM EOJ 

                    CONTROL CARD(S)
                    .........1.........2.........3.........4.........5.........6.........7.........8
                    COMM OPTION=EOJ
 
                    FUNCTION=COMM
                       OPTION=EOJ

This page of the report shows the following:

  • The command exactly as entered.
  • An analysis of keywords encountered and expected. Any errors found are flagged with a note in the left margin.
  • Any messages related to syntax processing.

DB13105I - COMM     EOJ      REQUEST ACCEPTED   

This page of the report shows a message indicating that DBUTLTY successfully placed the request on the MUF communication queue.

MUF Startup Options Echoed

When the MUF is terminated, a list of the MUF startup options specified is written to SYSPRINT.

For information about the MUF startup options, see Administrating.

DB01900I - *ACCT   0,4K,OPEN,4K               ACCT'ING - TABLE, BUFFER, STS, THRH  
DB01900I - *ACCT   1,8K,CLOSED,2K             ACCT'ING - TABLE, BUFFER, STS, THRH  
DB01900I - *ACCT   2,16K,OPEN,6K              ACCT'ING - TABLE, BUFFER, STS, THRH  
DB01900I - *ACCT   3,32K,CLOSED,1K            ACCT'ING - TABLE, BUFFER, STS, THRH  
DB01900I - *ACCT   4,64K,OPEN,32K             ACCT'ING - TABLE, BUFFER, STS, THRH  
DB01900I - *ACCT   5,128K,CLOSED              ACCT'ING - TABLE, BUFFER, STS, THRH  
DB01900I - *ACCTPRM 4                         ACCT'ING - DBID OF PRM TABLE         
DB01900I - BREAK   10                         ALLOW TASK SWITCHING                 
DB01900I - CBS     6,32K,0,0                  CBS - DBID, BUFFER, STEN, STIO       
DB01900I - COVERED 1                          ALL OF BASE 1 (FIRST)                
DB01900I - COVERED IXX999,80K,ACTIVE          PART OF INDEX                        
DB01900I - COVERED DEM999,40K,ACTIVE          PART OF DATA                         
DB01900I - DATACOM DB,SQL,DTCMSRVR                                                 
DB01900I - DATAPOOL 8192,40                   DATALN,DATANO                        
DB01900I - DICTIONARY 2,15                    DATA-DICT DBID,DDD DBID              
DB01900I - EXCTLNO 16                         EXCLUSIVE CONTROL MAX (IGN IF SQL)   
DB01900I - *FLEXPOOL 2,2,2                                                         
DB01900I - *IOTASK  2                         IOTASK MAX/CURR,CURR,DSP             
DB01900I - LOGPEND 100                        LOGGING PEND NUMBER                  
DB01900I - LOGPOOL 3                          LOG TXB BUFFERS                      
DB01900I - LOGRCV  NEVER                      LOGGING RECOVERY                     
DB01900I - LOGSPILL 99                        SPL2,SPL3,SPL1                       
DB01900I - MAXELRQ 255                        MAXIMUM ELEMENT PER REQUEST          
DB01900I - MUF DBDVMUF                        MUF NAME FOR DYNAMIC TABLES          
DB01900I - NONSWAP YES                        MAKE IS NON-SWAPPABLE IF AUTHORIZED  
DB01900I - PXXSTATS EOJ                       PXX STATS (DETAIL,EOJ,EOJPRT,NONE)   
DB01900I - *SMPTASK  1                                                             
DB01900I - *SMPTASK  1                         IOTASK MAX/CURR,CURR,DSP            
DB01900I - *SQLDEFAULT 16,CASQLDEFAULT         AREABASE,AREANAME                   
DB01900I - *SQLOPTION YES,17,DATACOM,120       SQL,TTMID,SQLMODE,LUWTOUT           
DB01900I - SUBTASK NONE                       NO SUBTASK                           
DB01900I - SYSPOOL 4,10,20                    CXXNO,IXXNO,DXXNO
DB01900I - TASKS   6,8K                       USER TASKS,SIZE,VMTASK,VAECOM
DB01900I - VIRTUAL 6,2M                       CBS VIRTUAL

This page of the report shows an echo of the MUF startup options.

Summary Reports Produced by the MUF During its EOJ Process

This section shows examples of the following:

  • MUF Startup Options Echoed
  • Memory Resident Data Facility Summary Information
  • XCF Summary Information
  • MUFplex Summary Information
  • Accounting Facility Summary Information
  • TCB Use Summary Information
  • SMP Informational Report
  • Miscellaneous Diagnostic Information Report

See EOJ Reports for these additional summary reports:

  • Procedure TCB Use Summary Information
  • Procedure Summary Information
  • Return Code Summary Information
  • SQL Code Summary Information
  • Memory Use Summary Information
  • MUF EOJ Log Status Information
  • Other Information
  • Task Information

Memory Resident Data Facility Summary Information

When the MUF is terminated, summary Memory Resident Data Facility (MRDF) information is written to the SYSPRINT file after the MUF startup options.

Note: The spacing in this example is expanded for clarity.

                                            M R D F     SUMMARY INFORMATION
               
 
                                                               VIRTUAL        COVERED        COVERED
AREA      USE      SIZE      BLOCKS  SPACE      MRDF READS   MRDF WRITES  1ST/ACT READS  NON-1ST READS     PERCENT
 
IXX00001  COVERED   83K          22  ADDRESS             1                            4              0  WITHIN 100
DEM00001  COVERED   62K          62  ADDRESS             1                            2              0  WITHIN 100
PAY00001  COVERED   62K          62  ADDRESS             1                            2              0  WITHIN 100
IXX00006  VIRTUAL    2M         510  ADDRESS             6             3                                  USED   0
IXX00999  COVERED   80K          21  ADDRESS             1                            3                 REUSED  25
DEM00999  COVERED   40K          40  ADDRESS             1                            2                 REUSED  33

This page of the report shows the following information:

  • AREA
    Area DATACOM-NAME and database DATACOM-ID in the format aaannnnn.
  • USE
    Indicates whether the resident area is COVERED or VIRTUAL.
  • SIZE
    Amount of memory allocated for this area that contains the data, Index, or Log Area blocks. This is the amount used, not the size specified in the MUF startup options. SIZE values are printed as follows:
    • Numbers 1 through 9999 are printed with a blank terminator, for example, 9999 is printed as 9999 followed by a blank.
    • Numbers 10000 through 9999K are printed as n through nnnnK, rounded up.
    • Numbers 9999K plus one through 9999M are printed as n through nnnnM, rounded up.
    • Numbers above 9999M are printed with a G as the terminating character, rounded up.
  • BLOCKS
    The number of data, Index, or Log Area blocks allocated to memory. COVERED is allocated in blocks and VIRTUAL is allocated in tracks.
  • SPACE
    ADDRESS indicates no use of a data space and the data is allocated in normal memory (above the 24-bit line). DATA indicates use of a data space to contain the blocks provided. 64-BIT indicates that the data is allocated in z/OS 64-bit.
  • MRDF READS
    Provides the number of blocks that were read from the MRDF space instead of from disk.
  • VIRTUAL MRDF WRITES
    Provides the number of blocks that were written to the MRDF VIRTUAL space.
  • COVERED 1ST/ACT READS
    Provides the number of blocks read from disk for either a FIRST or ACTIVE COVERED area.
  • COVERED NON-1ST READS
    For a COVERED FIRST area only, provides the number of blocks read from disk which do not reside in the MRDF buffers.
  • PERCENT
    Indicates the amount of use based on the following:
    • REUSED
      (COVERED ACTIVE areas only.) Provides the percent of MRDF reads out of the total reads.
    • USED
      (Virtual Areas Only.) Provides the percent of the space allocated which was actually used to service program requests.
    • WITHIN
      (COVERED FIRST areas only.) Provides the percent of the total reads which occurred within the COVERED FIRST buffers.

Accounting Facility Summary Information

If the Accounting Facility is generated in this MUF and not disabled, an Accounting report follows the MRDF report.

                                            ACCOUNTING SUMMARY INFORMATION
 
 
TABLE NAME:  A04                       DATABASE:  5
REQUESTS PROCESSED:  7                 EXCPS:  14
LOCATES:  6                            ADDS:  0                                 UPDATES:  3
ENTRY UNAVAILABLE:  0                  EXCLUSIVE CONTROL CONFLICTS:  0          SKIPPED DUE TO EXCLUSIVE:  0
CORE SIZE:  65,536                     NUMBER OF ENTRIES:  613                  ENTRIES RECLAIMED:  0
LOCATES INITIATED:  1                  SPILLS INITIATED TO AXXTHLD:  0          INTERNALLY INITIATED SPILLS:  0

This page of the report shows the following information:

  • ADDS
    Displays the number of new records added to the Accounting table.
    Tuning Information:
    To decrease this number, decrease the complexity of the key.
  • CORE SIZE
    Displays the buffer parameter specified for this table.
  • DATABASE
    Displays Database ID containing the Accounting table.
  • ENTRIES RECLAIMED
    Displays Number of in-memory table entries reused after a spill, that is, the number of entries for which a LOCATE was not required.
    Tuning Information:
    To increase this number, increase the buffer parameter, decrease the complexity of the key, or both.
  • ENTRY UNAVAILABLE
    Displays the number of user application requests that had to wait due to insufficient memory allocated by the buffer parameter.
    Tuning Information:
    To decrease this critical value, decrease the complexity of the key, increase the value of the buffer parameter, or both.
  • EXCLUSIVE CONTROL CONFLICTS
    Displays the number of entries in the Accounting table that had exclusive control held by a user application when a spill was initiated.
  • EXCPS
    Displays the number of execute channel programs (EXCPs) issued for this Accounting table.
    Tuning Information:
    This value is adversely affected by:
    • The number of records processed.
    • The number of spills initiated due to the threshold parameter of the MUF startup option ACCT being exceeded.
    • The value of the buffer parameter of the ACCT option being too small.
  • INTERNALLY INITIATED SPILLS
    Displays the number of spills initiated to decrease the number of entries unavailable.
    Tuning Information:
    To decrease this value, increase the buffer parameter value, decrease the complexity of the key, or both.
  • LOCATES
    Displays the number of entries retrieved into the accounting buffers including existing entries in the Accounting table with reclaimed internal space.
    Tuning Information:
    To minimize this number, decrease the complexity of the key, if the number of adds is high, or increase the size of the buffer parameter, if the number of updates is high (see UPDATES).
  • LOCATES INITIATED
    Displays the number of times that a group of locates were performed for the Accounting table. This parameter is not applicable to tuning and is for use by CA Support.
  • NUMBER OF ENTRIES
    Displays the number of entries in the in-memory accounting buffer (always odd).
  • REQUESTS PROCESSED
    Displays the number of times this Accounting table was used. This value is determined by the conditional expression, if there is one.
  • SKIPPED DUE TO EXCLUSIVE
    Displays the number of entries that were not immediately processed due to exclusive control conflicts.
  • SPILLS INITIATED TO AXXTHLD
    Displays the number of times that the threshold parameter value of the MUF startup option ACCT was exceeded. (This value is reset after each internally initiated spill.)
    Tuning Information:
    To decrease this value, increase the threshold parameter value.
  • TABLE NAME
    Displays the name of the Accounting table.
  • UPDATES
    Displays the number of times that records in the Accounting table were updated.
    Tuning Information:
    To decrease this value, increase the buffer and threshold parameters, decrease the complexity of the key or perform all of these.

XCF Summary Information

If any XCF requests are processed by the MUF, in the EOJ Report following the Memory Resident Data Facility Summary Information Report, the XCF Summary Information Report is generated. Following is an example of a XCF Summary Information Report:

                                             XCF SUMMARY INFORMATION
 
 JOB/SYS NAME    GROUP         TOTAL JOBS   TOTAL REQUESTS
 
 *               DCMDEV                2           12,014
 *               DCMD2                 4           37,363
 
 BUFFER SIZE    IB-REQUESTS     OB-REQUESTS
 
      1K             43,268          12,014
      2K              6,107          18,209
      8K                  0           9,925
     16K                  0           9,227

This page of the report shows the following information:

  • JOB/SYS NAME
    Is based on the XCFFROM startup parameter.
  • GROUP
    Is based on the XCFFROM startup parameter.
  • TOTAL JOBS
    Displays the count of jobs associated with this XCFFROM origin.
  • TOTAL REQUESTS
    Displays the total requests processed for this XCFFROM origin.
  • BUFFER SIZE
    Displays the XCF message size. This includes standard CA Datacom® request fields, plus CA Datacom® XCF overhead (variable), plus IBM XCF overhead (68 bytes). You can use this distribution to allocate XCF buffer sizes.
  • IB-REQUESTS
    Displays the count of application requests for the specified buffer size.
  • OB-REQUESTS
    Displays the count of results returned for the specified buffer size.

MUFplex Summary Information

If the MUF was an active MUFplex member, the MUFplex Summary Information Report follows the XCF Summary Information Report. Following is an example of a MUFplex Summary Information Report:

                                             MUFPLEX SUMMARY INFORMATION

       EVENT                              COUNT
 
       ALL CALLS                            167
       LIST CALLS                           126
       LOCK CALLS                            14
       SRB USES                             205
       MESSAGES OUT                           5
       MESSAGES IN                            8
       LIST SETS                             38
       LIST RESETS                           15
       LIST READS                            33
       LIST WRITES                           98
       LOCK OBTAINS                           7
       LOCK RELEASES                          7
       MAX STR SIZE                       4,096
       REQ STR SIZE                       4,096
       STR NBR ENTRIES                    1,714
       STR NBR ELEMENT                   26,476
       MAX NBR ENTRIES                       16
       MAX NBR ELEMENT                      211
       MAX NBR BUFF                           3

This page of the report shows the EVENT column that lists the following statistics:

  • ALL CALLS
    Displays the number of times DBXESPR was called.
  • LIST CALLS
    Displays the number of times an explicit LIST request (read/write/lock set/lock reset) was made.
  • LOCK CALLS
    Displays the number of LOCK requests that were made (obtain/release/alter).
  • SRB USES
    Displays the number of invocations of MUFplex service SRBs by system.
  • MESSAGES OUT
    Displays the number of MUFplex messages sent to other members of the MUFplex.
  • MESSAGES IN
    Displays gives the number of MUFplex messages received from other members of the MUFplex.
  • LIST SETS
    Displays the number of LIST LOCK SET requests.
  • LIST RESETS
    Displays the number of LIST LOCK RESET requests.
  • LIST READS
    Displays the number of LIST READ requests, explicit or implicit, using SRB.
  • LIST WRITES
    Displays the number of LIST WRITE requests, explicit or implicit, using SRB.
  • LOCK OBTAINS
    Displays the number of LOCK OBTAIN explicit requests.
  • LOCK RELEASE
    Displays the number of LOCK RELEASE explicit requests.
  • MAX STR SIZE
    Displays the maximum possible size of the Coupling Facility structure for this MUFplex (4K blocks).
  • REQ STR SIZE
    Displays the requested size of the Coupling Facility structure for this MUFplex (4K blocks).
  • STR NBR ENTRIES
    Displays the approximate capacity in number of LIST entries for this structure.
  • STR NBR ELEMENTS
    Displays the approximate capacity in number of 256-byte elements for this structure.
  • MAX NBR ENTRIES
    Displays the high-water mark for number of LIST entries simultaneously in the Coupling Facility for the MUFplex.
  • MAX NBR ELEMENT
    Displays the high-water mark for number of 256-byte elements simultaneously in the Coupling Facility for the MUFplex.
  • MAX NBR BUFF
    Displays the high-waiter mark for number of buffer LIST entries simultaneously in the Coupling Facility for the MUFplex.

TCB/SRB Use Summary Information

If the MUF startup option SMPTASK was specified and TCB mode was specified, this report on CPU time used by each Task Control Block (TCB) can be useful.

If the MUF startup option SMPTASK was specified and SRB mode was specified, an ENCLAVE SRB USE SUMMARY INFORMATION section occurs (see Enclave SRB Use Summary Information).

In TCB mode, the SMP subtask has a program name of DBSMPPR in the report, as it did in prior releases.

In SRB mode, the SMP task has a program name of *SRB-SMP in the report.

DBSMAPR subtasks are listed in the report with a program name of DBSMAPR.

                                         TCB/SRB USE SUMMARY INFORMATION


ITEM PROGRAM          USED COUNT             CPU TIME          POSTED COUNT            I/O COUNT       POSTED, NO WORK


  1  DBMUFPR                 185         000:00:14.72               187,433                  175               187,251
  2  *SRB-SMP        195,262,512         000:29:21.72            70,941,827                    0               884,803
  3  *SRB-SMP         33,708,874         000:07:21.89            19,652,702                    0            12,301,160

  4  DBMSBPR              22,291         000:00:00.00                     0                    0
  5  DBOCSPR               2,255         000:00:12.32                 1,721                    0
  6  DBOCSPR               2,013         000:00:10.80                 1,761                    0
  7  DBOCSPR               2,686         000:00:15.24                 1,615                    0
  8  DBOCSPR               1,921         000:00:10.48                 1,666                    0
  9 DBDUSPR               62,965         000:00:00.61                62,965                    0
 10 DBENQPR               23,589         000:00:00.79                23,589                    0
 11 DBSATPR                1,360         000:00:00.00                     0                    0
 12 DBCONPR                1,365         000:00:28.78                     0                    0
 13 DBMFSPR                    0         000:00:00.00                     0                    0
 14 DBCPMPR               16,874         000:00:10.19                     0                    0
 15 DBIOSP            22,030,367         000:04:34.10            11,688,821           22,030,367
 16 DBIOSPR            1,445,050         000:00:17.63               407,342            1,445,050
 17 DBSMAPR            8,005,261         000:05:12.51             8,005,261                    0
 18 DBSMAPR            4,821,889         000:02:08.78             4,821,889                    0

............... TOTALS OF ABOVE VALUES ................    ... Z/OS ASCB VALUES (INCLUDES OTHER TCB-SRB-RB WORK) ....

         TCB      *SRB-SMP     OTHER SRB       COMBINED             TCB       *SRB-SMP       OTHER SRB       COMBINED

000:14:21.75  000:36:43.61  000:00:00.00   000:51:05.36    000:14:21.75   000:36:44.06    000:07:15.67   000:58:21.49    

This page of the report provides the following information:

  • ITEM
    The first item represents the MUF main task. The second and any following items represent either TCBs for subtasks or SRBs used as SMP tasks.
  • PROGRAM
    Displays the name of the program.
    • SRB-SMP
      SMP subtask (See the MUF startup option SUBTASK). The name is *SRB-SMP when you are using an SRB option.
    • DBCONPR
      Console driven subtask (MVS Modify command /F)
    • DBCPMPR
      The Change Data Capture Monitor subtask in the source MUF (see Change Data Capture in Administrating.)
    • DBDQMPR
      Part of a removed feature.
    • DBDUSPR
      DBDUSPR exists, if needed, for PXX and (or) SYSOUT processing.
    • DBENQPR
      Enqueue locking subtask
    • DBIOSPR
      Asynchronous I/O functions subtask (See MUF startup option IOTASK in Administrating.)
    • DBMFSPR
      MUF restart processing during startup and before MUF is enabled.
    • DBMUFPR
      Main task
    • DBMSBPR
      Timer control subtask
    • DBOCSPR
      Open/close subtask. By default, there are 4 but you can control the number with MUF startup option 'X_OPEN_CLOSE_SUBTASKS 20'.  The number 20 can be set as 0-20. Zero is the default.
    • DBSATPR
      Subtask optional, present to support optional MUF startup option 'SUBTASK_AUTO'.
    • DBSMAPR
      DBSMAPR exists for each SMPTASK, if the SRB option was specified.
    • DBSMPPR
      SMP subtask. See the MUF startup option SUBTASK in Administrating. Name DBSMPPR when you are not using the SRB option.
    • DBSPSPR
      Active recovery spilling subtask
  • USED COUNT
    Lists the number of times an internal unit of work was performed. The count of internal units of work cannot be compared to any other CA Datacom®/DB counter.
  • CPU TIME
    Displays the total CPU time for the TCB or SRB used in hours, minutes, seconds, and hundredths of a second.
  • TIMES POSTED
    Displays the number of times individual TCBs or SRBs went into a wait (no work to do) and were posted to start processing. Once any of the TCBs are posted, they run (and take new work) until no work exists to be done. For the items DBMUFPR, DBSMPPR, and *SRB-SMP, the information provided in this field could be useful in tuning the ready-to-run option on the SMPTASK MUF startup option.
  • I/O COUNT
    Displays the I/O count.
  • POSTED, NO WORK 
    Displays the count of times the TCB or SRB was posted but did no work counted as ‘used’. This field has values only for items DBMUFPR, DBSMPPR, and *SRB-SMP. The count does not reflect an error of any kind, just multiple CPU processing timing cases where another processor performed needed work because it was already running and before it was posted for new work. Starting and stopping a TCB or SRB has substantial overhead. This count is provided to allow more accurate tuning of the ready-to-run option on the SMPTASK MUF startup option. It defaults to 4 but can be set lower or higher. Lower numbers will cause more postings and occurrences of ‘POSTED, NO WORK’ and so additional CPU usage but reduce the elapsed times for user processing. Higher numbers will cause less postings and so less CPU usage but longer elapsed times. CPU time is less with fewer SMPTASK tasks but elapsed times are longer; a tradeoff that the DBA controlling the MUF startup options must choose.

    Following the items 1-n are totals. The left set of columns are totals of the numbers provided in the detailed items. The right set of columns are numbers extracted from MVS z/OS control blocks and so reflect any work not provided as items or work MUF does not track. Within the left and right set of columns the following fields are provided:

    For TCB and *SRB-SMP the MVS times will be a little higher as some work will occur after the last time MUF requested the CPU time for each TCB and SRB.

    • TCB
      Provides the CPU time total for the TCBs which is always billable CPU time.

    • *SRB-SMP 

      Provides the CPU time total for all the SRB processing that is executed on a zIIP processor and so not billable.

    • OTHER SRB 
      Provides the CPU time total for SRB processing that is executed on a CP processor and so is billable. MUF does not normally track this time.
    • COMBINED 
      Provides the CPU time totals for the above 3 items

Procedure TCB Use Summary Information

Following is an example of a new report on Task Control Block (TCB) use.

                                             PROCEDURE TCB USE SUMMARY INFORMATION

         LAST         PROCEDURE                              SQL
 TCB  PROGRAM            STARTS     TCB CPU TIME      STATEMENTS
 
   1  B580PA01                5     000:00:00.03               5
    2 B580PA02                5     000:00:00.73               0
    3 ?                       0     000:00:00.00               0
   4  B580PA01                1     000:00:00.00               1
    5 B580PA02                1     000:00:00.14               0
    6 ?                       0     000:00:00.00               0
      7-9                     0     000:00:00.00               0

This page of the report provides the following information:

  • TCB
    Displays the number of TCBs assigned for procedures are indicated. Those that have been used at least once have a detail line. Those never used have only a range reflected under the LAST PROGRAM heading. Nested TCBs are indented by one position to note that they are different from the non-nested TCBs. Nested TCBs are only used when an SQL request is issued by the previous TCB in that nest group.
  • LAST PROGRAM
    Displays the name of the last program to be processed in this TCB. A question mark (?) in a nested TCB is used to reflect it has never been used.
  • PROCEDURE STARTS
    Displays the number of times this particular TCB was selected to process a user procedure (caused by a call procedure or a trigger).
  • TCB CPU TIME
    Displays the hours, minutes, seconds, and sub-seconds of execution time.
  • SQL STATEMENTS
    Displays the number of SQL statements executed from any program that executed in this TCB. This is zero in the last TCB of each nest group.

Procedure Summary Information

                                             PROCEDURE SUMMARY INFORMATION

                      PROCEDURE                              SQL            TCB
      PROGRAM            STARTS     TCB CPU TIME      STATEMENTS        FAILURES
 
      B580PA01                6     000:00:00.03               6               0
      B580PA02                6     000:00:00.87               0               0

This page of the report provides the following information:

  • PROGRAM
    Displays the name of the program that was executed.
  • PROCEDURE STARTS
    Displays the number of times this program was started for execution.
  • TCB CPU TIME
    Displays the time this procedure spent executing.
  • SQL STATEMENTS
    Displays the number of SQL statements executed by all occurrences of this program.
  • TCB FAILURES
    Displays either 'LE' was unable to fetch the module or the module abended.

Enclave SRB Use Summary Information

When the SMPTASK MUF startup option has been used to specify SRB mode, the TCB/SRB USE SUMMARY INFORMATION report has a section that gives summary information about enclave SRB use.

Note: The appearance of a MUF EOJ report you receive in actual practice cannot necessarily be expected to conform exactly to the following sample.

                                         ENCLAVE SRB USE SUMMARY INFORMATION
 
                      USER LIMIT  ZIIP QUALIFIED         ZIIP     ZIIP ON CP
 ITEM                   PERCENT         CPU TIME     CPU TIME       CPU TIME
 
   1                        100    000:00:19.30   000:00:18.71   000:00:00.63
   2                        100    000:00:02.48   000:00:02.38   000:00:00.09
   3                         50    000:00:00.65   000:00:00.63   000:00:00.02
   4                         50    000:00:00.00   000:00:00.00   000:00:00.00
   5                          0    000:00:00.00   000:00:00.00   000:00:00.00

This page of the report provides the following information:

  • ITEM
    Corresponds to the SMPTASK number for this SRB.
  • USER LIMIT PERCENT
    Displays the value set at startup for this SRB either by allowing it to default to 100 percent, or by using the optional tuning MUF startup option ZIIP_USER_LIMIT (see the information about MUF startup options in Administrating).
  • ZIIP QUALIFIED CPU TIME
    Displays the CPU time that has executed as qualified to run on a zIIP engine.
  • ZIIP CPU TIME
    Displays the time work executed on the zIIP engine.
  • ZIIP ON CP CPU TIME
    Displays the time that work was executed on CP engine because a zIIP was not available at that instant.
Note: Even when there is no user limit, not all SRB execution is qualified to run on a zIIP engine.

The times reported are provided by the operating system and might not always appear to be in sync with each other.

SMP Informational Report

If the MUF startup option SMPTASK was specified, the following report can be useful for some tuning and in dealing with CA Support. Similar to the SMP dynamic system table, it provides information about statistics for the entire MUF run. This report is available to SQL and non-SQL sites. Most of the information reported reflects counts of SMP waiting conditions, and these fields cannot be changed by tuning.

Each POSTED ENTRY item reflects the depth counts of a POSTED LIST that provides information about how many tasks were ready to run at various times. Periodically, the posted list is scanned and the counter at the appropriate depth is incremented by one. This is not done often and the counts are not comparable to other counts. As a group, the counts provide a clue as to whether running in SMP mode would help or hurt, the number of SMPTASKs that might be selected, and the ready-to-run count. This information can be used to tune the ready-to-run option of the SMPTASK MUF startup option.

Note: Items in the report which have a zero count are skipped.

                                            SMP INFORMATIONAL REPORT
      EVENT                    COUNT
 
      DXX BUFFER                 266
      DATA BUFFER                 17
      LOG BUFFER                  15
      LOG LRU                      3
      LOCK LIST                  111
      OPEN TABLE                   1
      TASK AREA                  126
      WAIT LIST                  863
      MEMORY MANAGER              23
      PXX CONSOLE                  1
      POSTED ENTRY  0          8,029
      POSTED ENTRY  1          7,243
      POSTED ENTRY  2          3,368
      POSTED ENTRY  3          3,649
      POSTED ENTRY  4          4,048
      POSTED ENTRY  5          4,348
      POSTED ENTRY  6          4,811
      POSTED ENTRY  7          5,299
      POSTED ENTRY  8          5,735
      POSTED ENTRY  9          6,448
      POSTED ENTRY 10          7,594
      POSTED ENTRY 11          9,368
      POSTED ENTRY 12         10,870
      POSTED ENTRY 13         10,815
      POSTED ENTRY 14         10,013
      POSTED ENTRY 15          9,230
      POSTED ENTRY 16          8,559
      POSTED ENTRY 17          7,829
      POSTED ENTRY 18          7,184
      POSTED ENTRY 19          6,427
      POSTED ENTRY 20          5,803
      POSTED ENTRY 21          5,636
      POSTED ENTRY 22          5,482
      POSTED ENTRY 23         36,928

This page of the report shows the following:

Each count represents two tasks conflicting on the resource. All of these SMP locks are of short duration. Two tasks searching a particular index or data buffer for a read request get share locks and have no contention. If one task might need to update the block, it must run alone. This is true of all the locks as appropriate. All locks are global in nature, that is, only one exists except as follows:

  • Data space locks exist for each data area.
  • An Accounting table (ACCT TABLE) lock exists for each Accounting table.
  • A TASK AREA lock exists for each RWTSA (task).
  • Covered/Virtual control (MRDF CNTRL) exists for each covered or virtual area.

The following explain the event names that can appear in the report:

  • ACCOUNTING ENT
    Incrementing counters in a particular entry in the Accounting buffer.
  • ACCOUNTING STS
    Accounting system changes across all Accounting tables.
  • ACCOUNTING TBL
    Accounting changes to each specific Accounting table.
  • ADD DELETE FLEX
    Control during add or delete of a sequential or flexpool buffer.
  • CBS BUF SPILL
    CBS buffer spill to IXX.
  • CBS BUFFER
    Control during get/free memory in the CBS buffer.
  • CHECK INTERLOCK
    Control during interlock detection.
  • COMIT WAIT BAD
    Occurs when using the X_LOG_DELAY MUF startup option which enables the log COMIT delay enhancement. This is a count of times a task doing a transaction-ending command delayed for another task to write the LXX block, but none did within the one second time limit.
  • COMIT WAIT GOOD
    Occurs when using the X_LOG_DELAY MUF startup option which enables the log COMIT delay enhancement. This is a count of times a task doing a transaction ending command delayed for another task to write the LXX block and another did, thus saving a possible LXX I/O.
  • COVERED VIRTUAL
    Control of a covered or virtual area during block fetch/store.
  • DATA BUFFER
    A specific data block in memory.
  • DATA HASH
    Hash list of data blocks in memory.
  • DATA LRU
    The Least Recently Used data chain to read a block not in memory.
  • DATA SPACE BUFF
    Blocks in data area with free space in memory.
  • DATA SPACE MGMT
    Data area space management.
  • DATA WRITE PEND
    Write pending chain (pipeline) for data.
  • DEFRAG
    A DEFRAG SMP lock is used to interact with backwards processing (for example, the LOCBR command). DEFRAG obtains an exclusive SMP lock at the start of each key ID processing. If there are no backward requests for this key ID during the life of the DEFRAG, the lock is simply maintained. If there is a backward request during the process, DEFRAG notes where it is in the DXX (the "lowest" level of the IXX that contains key values and pointers to actual rows) and frees the SMP lock to allow the backward process to run. DEFRAG then reestablishes the lock and rereads its blocks and continues as before. Backwards processing obtains a shared SMP lock.
  • DXX BUFFER
    A specific DXX index block in memory.
  • DXX HASH
    Hash list of DXX index blocks in memory.
  • DXX LRU
    The Least Recently Used DXX index chain to read a block not in memory.
  • DXX WRITE PEND
    Write pending chain (pipeline) for index.
  • EXPAND BUFFER
    Control to get or free an expand buffer.
  • INDEX QUEUE
    Control during get/free of entry in index queue.
  • IXX BUFFER
    A specific IXX index block in memory.
  • IXX HASH
    Hash list of IXX index blocks in memory.
  • IXX LRU
    The Least Recently Used IXX index chain to read a block not in memory.
  • LOCK LIST
    Control to add, delete, or search the primary exclusive control table.
  • LOG BUFFER
    A specific log block in memory.
  • LOG LRU
    The Least Recently Used data chain to read a log block not in memory (by transaction backout).
  • LOG VAR WAITSMP
    A task is waiting on access to the Log Area (LXX) control information. This particular condition can occur with all LXX formats, but it occurs more frequently with variable logging. The counts are not within control of the user and should not be a concern, regardless of the count, that is to say, the count is for informational purposes only.
  • MEMORY MANAGER
    Memory manager control.
  • MISCELLANEOUS
    Non-SQL miscellaneous other locking.
  • OPEN TABLE
    Share lock to search open table list or additions, exclusive lock to delete entries.
  • POSTED ENTRY
    Depth count of a POSTED LIST.
  • POSTED LIST
    Control of the posted list as required.
  • PXX CONSOLE
    Print file (PXX) and console control.
  • SECURITY
    Waits for SMP synchronization with external security.
  • SQL ATTACH
    SQL control of attached tasks.
  • SQL GLOBAL
    SQL global locking requirements.
  • SQL MISC
    SQL miscellaneous control requirements.
  • SQL PLAN
    SQL control during starting/stopping a plan.
  • SQL STATUS
    SQL locking of a task status change.
  • SQL TTM
    Control requirements to get/free a TTM block.
  • SQL URT
    SQL control during URT open/close.
  • STAR
    STAR storage control.
  • STAR TASK
    STAR control task usage.
  • TASK AREA
    Control during change in status of task area.
  • TSN
    Control to start or stop a new transaction, or to see if a transaction is active.
  • USER COMPRESS
    Lock during user compression routine(s).
  • WAIT LIST
    Control of the wait list of tasks.

Five of the locks allow a diagnostic startup option (DIAGOPTION) to accumulate the time the task waited. If this has been selected (because of a request by CA Support), the following counts can print. The count reflects the total number of seconds of waiting that occurred.

  • WTIM MEM-MGR
    Time spent waiting for the memory manager lock.
  • WTIM PXX
    Time spent waiting for the print file (PXX) lock.
  • WTIM TASK AREA
    Time spent waiting for the RWTSA (task) lock.
  • WTIM TIMER
    Time spent waiting for the timer lock.
  • WTIM WAIT LIST
    Time spent waiting for the wait list lock.

Miscellaneous Diagnostic Information Report

The Miscellaneous Diagnostic Information Report can be useful in dealing with CA Support and in some tuning. Similar to the Internal Statistics dynamic system table, it provides statistics for the entire MUF run. This report is available to SQL and non-SQL sites. The first section of the report provides multi-block read information. Multi-block reads can be done during sequential commands GETIT and GETPS based upon the User Requirements Table option SEQBUFS= and the contents of the actual table(s) being read. It is also done during some ADDITs when using the next overflow blocks. Multi-block read is also done (under some conditions) during Compound Boolean Selection processing. This section of the report provides the number of times various numbers of DASD blocks were read with a single EXCP. Some control exists for GETIT and GETPS, and this information is provided for information and possible tuning.

The next section of the report provides multi-block write information. With pipelining, it is possible to have multiple blocks in an area that needs to be written. When possible, CA Datacom®/DB writes them together with one EXCP. This usually speeds I/O processing. These counts are provided for information and cannot be tuned.

The last section reflects miscellaneous information about the MUF execution. The sample shows one counter in this last section, BREAKS DONE. For an explanation of BREAKS DONE and other counters that could appear (if they are non-zero), see the descriptions that follow the sample.

Note: Items in the report which have a zero count are skipped.

                                            MISCELLANEOUS DIAGNOSTIC INFORMATION
      EVENT                    COUNT
 
      WRITE BLOCKS  1              6
      WRITE BLOCKS  2             11
      WRITE BLOCKS  3              2
      WRITE BLOCKS  4              9
      WRITE BLOCKS  5              3
      WRITE BLOCKS  6             10
      WRITE BLOCKS 13              1
      WRITE BLOCKS 14              1
      WRITE BLOCKS 15              1
      WRITE BLOCKS 17              4
      WRITE BLOCKS 18              1
      WRITE BLOCKS 19              5
      WRITE BLOCKS 20              5
      WRITE BLOCKS 21              2
      WRITE BLOCKS 32              1
      WRITE BLOCKS 36              1
      WRITE BLOCKS 39              5
      WRITE BLOCKS 41              1
      WRITE BLOCKS 44              1
      WRITE BLOCKS 46              5
      WRITE BLOCKS 48             28
      BREAKS DONE              1,189

This page of the report shows the following:

The following explains the possible counters that could appear in the last section of the previously shown report, if those counters are not zero. Counters with a value of zero are not shown in the report. The only counter displayed in the previously shown report is BREAKS DONE.

  • BREAKS DONE
    If any break was done (in support of the BREAK MUF startup option), it is noted here. A break represents a time when a lower priority task which is looking at many index and or data buffers can release control and allow any waiting higher (or equal) priority task to run.
  • IXX QUEUE DBIDS
    The maximum number of DBIDs in the index queue.
  • IXX QUEUE DEPTH
    The maximum depth (that is, maximum number of blocks) of the index queue.
  • LOG VAR MAX GT8
    This count is printed if you have allocated more than 8 buffers. It tells you the maximum number of buffers that have actually been used. If printed, it cannot be less than 9 nor more than the number of log-ahead buffers. It represents a high-water mark to buffer usage because the detail used counts stop at 8.
  • LOG VAR NO AVL
    This is the count of times all log-ahead buffers are full and a wait needs to occur for a current block to free one or more buffers. If this count is large, you might want to increase the number of log-ahead buffers.
  • LOG VAR USED 1
    This count is the number of times the first log-ahead buffer is activated. It occurs only when the single current buffer is full and no log-ahead buffers are in use. If activated, the buffer may contain only one record or a full block of records before it is written. A similar count is provided for blocks 2-7. A special count is provided for block 8, which is printed as 8+ because users can define more than 8 log-ahead buffers. The 8 count is the number of times the 8th or 9th to the end are used (similar to the 5+ buffer reuse counters).
  • LOG VAR WRITE 2
    This count is the number of times the current log block was written with a chain of multiple blocks. These statistics are printed in the MUF EOJ report if they are not zero. The first counter provides for the times that two log current blocks are written with a single I/O, reported as LOG VAR WRITE 2. Additional counts are provided for writing three blocks, four blocks, five blocks or six blocks. In general, two blocks per track exist and so this represents 3 tracks of log data.
  • IO WAIT CXX BFR
    Count of number of times a task waited on a CXX I/O that was already in process.
  • IO WAIT IXX BFR
    Count of number of times a task waited on an IXX I/O that was already in process.
  • IO WAIT DXX BFR
    Count of number of times a task waited on a DXX I/O that was already in process.
  • IO WAIT DATA BFR
    Count of number of times a task waited on a Data I/O that was already in process.
  • IO WAIT LXX BFR
    Count of number of times a task waited on an LXX I/O that was already in process.
  • LOCK LXX CUR RC
    A task is waiting on access to current log buffer.
  • LOCK WAIT CXX B
    A task is waiting on a specific Directory (CXX) block to become available.
  • LOCK WAIT LRU C
    A task is waiting on the least recently used chain for a Directory (CXX) buffer.
  • MRDF IXX DIRECT
    Count of times the MRDF facility could reference an IXX block directly without moving it to an IXX buffer.
  • OPEN EXIT WAITS
    A task is waiting on open exit.
  • REBINDS DONE
    Count of number of automatic plan rebinds that SQL has successfully completed.
  • WAIT_DBIO_24BIT
    Count of number of times MUF did not start an I/O because its 24-bit memory was over the size limit specified with the MUF startup option X_IO_24BIT_SIZE.
  • X_IO_LOW_THRESHOLD
    The count of times CA Datacom®/DB constrained and started no I/O because the available memory was below the low threshold. This can occur once per 4/100th of a second in the MUF main task and any I/O subtask attempting to start an I/O.

    Note: For information about the MUF startup option X_IO_LOW_THRESHOLD, see Administrating.
  • X_IO_HIGH_THRESHOLD
    The count of times CA Datacom®/DB constrained and started no I/O because the available memory was both below the high threshold and above the low threshold, and also because 30 or more I/Os were currently outstanding.

    Note: For information about the MUF startup options X_IO_HIGH_THRESHOLD and X_IO_LOW_THRESHOLD, see Administrating.
  • X_IO_OS_THRESHOLD
    The count of times CA Datacom®/DB constrained and started no I/O because the outstanding I/O was 480 or more.

Return Code Summary Information

The following example of an EOJ Report provides Return Code Summary Information:

                                            RETURN CODE SUMMARY INFORMATION
            
          RETURN CODE    OCCURRENCES    SHORT TEXT     
 
           01 (032)        3    INVALID DB COMMAND
           03 (027)        1    KEY NAME NOT IN CXX
           05 (034)        5    TABLE HAS NOT BEEN OPENED

This page of the report provides the following information:

  • RETURN CODE
    Note that these are CA Datacom®/DB return codes. Not all return codes, however, are listed in these counts. Several return codes that occur frequently in non-error situations are not counted. These include (but are not restricted to) return codes: 14, 19, and 04(170). Also not counted are certain return codes that occur outside the MUF. These include (but are not restricted to) return codes: 36, 37, 57, 68, 85, and 86.
    CA Datacom®/DB, in its internal processing, sometimes generates return code situations that are not errors and are not externalized other than in this report or in a Master List dump, if enabled by a user using the RCERROR option. These counts cannot be clearly identified, but must be ignored as normal. They include occurrences of 12(045), 61(061), and possibly others.
  • SHORT TEXT
    Displays text for the return code provided to speed the review of errors and save time that could be spent looking up message meanings.

SQL Code Summary Information

                                             SQL CODE SUMMARY INFORMATION
             SQL CODE    OCCURRENCES
                  -14              2
                  -20              1
                  -56              1
                 -124              2

This page of the report provides the following information:

  • SQL CODE
    Note that these are SQL error codes. Also note that SQL code 100 (that is, +100, not -100) is not listed in these counts because it indicates a non-error situation. Specifically, SQL code 100 indicates NO ROW FOUND and can occur during a DELETE or UPDATE, if no rows are found to delete or update. It is a normal, non-error condition for which no action is required, and therefore it is not counted in the SQL Code Summary Information report.

Memory Use Summary Information

Following is an example of an EOJ Report that provides Memory Use Summary Information. The memory usage reported is that which exists at MUF termination. It does not include memory allocated by the operating system. It does, however, include most memory allocated by CA Datacom®/DB, but not all memory.

                                            MEMORY USE SUMMARY INFORMATION

          DESC  LONG DESCRIPTION        24BIT-----ANY---64BIT (M=MEG,K=1024,ELSE BYTES) / OCCURRENCES
 
                PROGRAM MEMORY (AT EOJ)-   58-K   408-K

                UNALLOCATED  (AT EOJ)-   7712-K  1054-M    
                DBMEMPR CALLS-----------   61       0     
                ERROR, NON-SQL----------    1       0     
 
          MAIN  DBMEMPR OWNED MEMORY, 24  128-K     0     
          MA31  DBMEMPR OWNED MEMORY,ANY    0       2--M
          PC31  COMMON, POOL 0, ANY ----    0       8-K   
          MLB4  MUF STARTUP, 24 BIT ----   29-K     0
          MLB1  MUF STARTUP, ANY -------    0     304-K
          DCB   DCB/DTF, 24 BIT --------   32-K     0
          DBIO  I/O CONTROL BLOCKS -----   32-K     0
          4K31  MISC. 4K POOL, ANY -----    0      24-K
          BDES  IXX/DXX/DATA/LXX BDES --    0      32-K
          BUFS  IXX/DXX/DATA/EXP.BFRS --    0     564-K
          DMP   PXX PRINT CACHE --------    0      33-K
          MRDF  COVERED/VIRTUAL NOT DTSP    0      47-K
          LOGB  LOG BUFFERS ------------    0     112-K
          LOGT  LOG TRACE TABLE --------    0      32-K
          DSM   DSM TRACE TABLE --------    0      32-K
          MA64  DBMEMPR OWNED MEMORY, 64    0       0        6--M
          BF64  IXX/DXX/DATA BFRS ------    0       0       81-K
          MRDF  COVERED/VIRTUAL 64BIT       0       0      200-K

This page of the report provides the following information:

  • DESC
    Displays a short description that can be blanks and can be duplicated, if appropriate.
  • LONG DESCRIPTION
    Displays a long description that can be blanks and can be duplicated, if appropriate.
  • 24BIT
    Displays the amount of 24-bit requested memory, except for one case where it is a count.
  • ANY
    Displays the amount of any requested (usually 31-bit) memory, except for one case where it is a count.
  • 64BIT
    Displays the amount of any requested 64-bit memory. The amount is presented as follows:
    • Numbers 1 through 9999 are printed with a blank terminator, for example, 9999 is printed as 9999 followed by a blank.
    • Numbers 10000 through 9999K are printed as n through nnnnK, rounded up.
    • Numbers 9999K plus one through 9999M are printed as n through nnnnM, rounded up.
    • Numbers above 9999M are printed with a G as the terminating character, rounded up.
  • OCCURRENCES
    Displays the number of occurrences of LUW, STME, STMR, and XCL (see the descriptions in the following table).
  • PROGRAM MEMORY (AT EOJ)
    In z/OS, this line shows the amount of memory for most (but not all) programs.
  • UNALLOCATED
    Displays the amount of storage still available from the operating system when MUF terminated.
  • DBMEMPR CALLS
    This line, the second line in z/OS but the first line in z/VSE, is a count of the number of memory manager requests in the 24-bit column and zero in the ANY column.
  • ERROR, NON-SQL
    There are three possible counters which can be printed here. Each can be printed if they are non-zero counts. The three possible counters are as follows:
    • OUT OF STORAGE indicates the number of times a request to get memory could not be performed because no memory was available to satisfy the request.
    • ERROR, NON-SQL is a parameter error on a memory manager request. This counter is used only by CA Support. Users have no control over it.
    • ERROR, SQL is a parameter error on a memory manager request. This counter is used only by CA Support. Users have no control over it.
  • MAIN and MA31
    The MAIN and MA31 lines represent the amount of memory obtained from the operating system for use as dynamic memory. MAIN contains only 24-bit memory, while MA31 is ANY requested memory, generally 31-bit. This size is never reduced, that is, once obtained from the operating system this memory is used and reused as necessary.
  • Remaining lines
    The lines following the MAIN and MA31 lines represent a current breakdown of where the MAIN and MA31 memory is specifically allocated. Each line represents one or more pools. Some pools can occur more than once and some of those are collapsed for reporting purposes. General descriptions of the possible pools are as follows:
DESC LONG DESCRIPTION Explanation
DCB DCB/DTF, 24 BIT -------- 24-bit memory used for operating system control blocks.
DBIO I/O CONTROL BLOCKS ----- 24-bit memory used during I/O.
4K31 MISC. 4K POOL, ANY ----- Dynamic 4K pool of memory used for many items such as open areas, open tables, open data sets, open extents, open CXX base/area/table information.
ACCT ACCOUNTING BFRS -------- Accounting tables buffers.
BDES IXX/DXX/DATA/LXX BDES -- Index, data, and log buffer directory entries.
BF64 IXX/DXX/DATA BFRS ------- Index and data buffers in 64-bit memory.
BUFS IXX/DXX/DATA/EXP.BFRS -- Index, data, and expand buffers.
CAP CXX CATALOG, DDL ------- Work areas during a CXX catalog or during SQL DDL statements.
CBSS CBS SET CBS set buffer
CBSW CBS Work Working storage for CBS
CDC Change Data Capture Working storage for Change Data Capture
CNSB CONSTRAINT BUILD OBJECT SQL constraint processing memory, build object.
CNSC CONSTRAINT CHECK ADD -- SQL constraint processing memory, check during add.
CNSR CONSTRAINT READ TO EXEC SQL constraint processing memory, read to execute.
CNST CONSTRAINT TEMP. STORAGE SQL constraint processing memory, temporary storage.
DBLG SAVED LOG RECORD --- Transaction backout saved log record.
DMP PXX PRINT CACHE -------- Buffer to cache SQL and CBS trace and debugging information.
DSM DSM TRACE TABLE --- Space management trace table.
KYEL CXX KEY/ELEMENT -------- CXX key and element memory for open tables.
LOGB LOG BUFFERS ------------ Log buffers.
LOGT LOG TRACE TABLE -------- Log trace/debugging table.
LUW LOG.UNIT.WORK STORAGE -- SQL memory for logical unit of work control. Number of occurrences listed in OCCURRENCES column.
MA64 DBMEMPR OWNED MEMORY, 64 If 64-bit memory has been used by MUF, the report contains a MA64 line showing the total memory acquired in 64-bit.
MFR RESTART WORK TABLE --- Restart work tables and User Requirements Tables.
MLB1 MUF STARTUP, ANY ------- Done during MUF enable. Contains static control blocks allowed to be in 31-bit memory.
MLB4 MUF STARTUP, 24-BIT ---- Done during MUF enable. Contains static control blocks required to be in 24-bit memory.
MPZ MPZ TRACE TABLE --- (z/OS only) Data Sharing, MUFplex, trace table.
MRDF COVERED/VIRTUAL NOT DTSP Control information for Covered/Virtual usage required in the MUF address space. Also contains buffers when running z/OS and not running Authorized.
MRDF COVERED/VIRTUAL 64BIT MRDF in 64-bit memory
MSC MISCELLANEOUS SQL ------ SQL miscellaneous memory.
PC31 COMMON, POOL 0, ANY ---- Miscellaneous small uses of 31-bit memory.
PCOM COMMON, POOL 0, 24-BIT - Miscellaneous small uses of 24-bit memory.
PLN PLAN STORAGE ----------- SQL plan memory.
PRCD PROCEDURE RELATED ------ SQL procedure-related storage.
PRS PARSER TEMP. STORAGE ---- SQL parser memory.
REQ REQUEST SQL STORAGE ---- SQL request memory.
SASV STXIT WORK AREAS ------- z/VSE program failure work areas.
SCF1 SECURITY FAST PATH-USER Security fast path for users.
SCF2 SECURITY FAST PATH-TABLE Security fast path for tables.
SPILL LOG SPILL BUFFERS Buffers used for spilling the log to the RXX.
STMC STMT PREPARE: CURSOR UPDSQL SQL statement prepare - cursor update.
STMD STMT EXECUTE: DYN-CURSOR SQL statement execution - dynamic cursor.
STME STMT EXECUTE: STMT COPY SQL statement execution cache. Number of occurrences listed in OCCURRENCES column.
STMN STMT EXECUTE: NON-STATIC SQL statement execution - non-static.
STMP STMT PREPARE: GENERAL -- SQL statement prepare - general use.
STMR STMT READ PROCESSING --- SQL statement read processing. Number of occurrences listed in OCCURRENCES column.
STMS STMT SEARCH: DB2 MODE -- (z/OS only) SQL statement search - DB2 mode statements.
TSKW TASK (RWTSA) WORK AREAS Work areas associated with each task area being used.
VEW VIEW RESOLUTION -------- SQL view resolution.
VPEP DD VPE GLOBAL ----------
CA Datacom® Datadictionary™ global work area.
WORK GENERAL WORK AREAS----- General non task related working storage.
XCF MVS XCF USAGE ---------- Contains the work areas required for XCF communication in z/OS. This occurs when using XCF to run jobs on an image other than the one on which the MUF is executing or during Data Sharing.
XCL SQL C STACK, TASK WORK - Work areas for SQL task processing. Number of occurrences listed in OCCURRENCES column.
XES1 DATASHARING (MUFPLEX) (z/OS only) Data Sharing, MUFplex, trace/debugging table.

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.

MUF EOJ Report Logging Section Changes

The MUF LXX format options feature is a performance enhancement that allows MUF to process more maintenance requests per second while reducing the total cost of ownership. For details, see Administrating.

In support of the LXX format options feature, the logging section of the MUF EOJ provides new headings and six new detail lines as follows:

  • One detail information line was added for each of the following: ADDIT, DELET, and UPDAT.
  • One detail information line was added for TSN records, that is, transaction-related information such as for the following (some of which are internally used and nowhere externally described):
    • COMIT
    • ROLBK
    • CLOSE
    • LOGCP
    • LOGCR
    • DEQUE
    • LOGPR
    • LOGPN
    • LOGRP
    • LOGBA
    • LOGBU
    • LOGBD
    • YYC??
    • DELAL
  • One detail information line was added for moved records in support of compressed tables or the DBUTLTY OLREORG function.
  • One detail information line was added for Data Access Capture (*DAC*) which are accesses to data captures into the log area LXX.
  • One detail information line was added for OTHER records, including LOGIT, LOGDW, OPEN, and a CLOSE that was not done as a commit.
Note: Many of the fields in the report are provided to show that features are working and their results, largely for use by CA Support, CA Datacom® development, and QA debugging.

All lines show the total record count as follows:

  • Counts of 0-99999 are printed as specific numbers
  • Counts of 100,000-9,999,999 are printed as rounded to 4 digits with the letter k
  • Counts of less than 9 gigabytes (<9g) are rounded to 4 digits and printed with the letter m
  • Numbers greater than 9 gigabytes (>9g) are rounded to 4 digits and printed with the letter g

Other lines in the report are as follows:

  • PRCT OF LXX
    provides the byte count of the records as a percent of all log bytes during this MUF execution, with one decimal place if it amounts to one percent or higher. If the size is less than one percent, however, it is printed as a number similar to the total record count field previously described.

    Note: Other lines in the report are formatted as appropriate to their descriptions, similarly to the PRCT OF LXX format.
  • OLD RCD EXP
    provides the bytes of the log records that contained the before image record in fully expanded format. Includes encrypted tables written as encrypted.
  • OLD RCD CMP
    provides the bytes where CA Datacom®/DB compression was used.
  • OLD RCD USER
    provides the bytes where user compression was used and the option allowed them to be written as compressed (includes 16 bytes of compression name and data).
  • NEW WA ORIG
    provides the bytes during a DELET or UPDAT that were the original user Work Area that was logged as smaller than the other options.
  • NEW WA DELTA
    provides the bytes during an UPDAT that were logged as a Work Area with only changes based upon the LOG_RECORD_UPDAT_SIZE option.
  • NEW RCD EXP
    provides the bytes that were logged as the expanded after record. Includes encrypted tables written as encrypted.
  • NEW RCD CMP
    provides the bytes that were logged as the compressed after record.
  • NEW RCD USER
    provides the bytes that were logged as the user compressed after record.
  • ELEM LIST
    provides the bytes that were logged as the element list (FORMAT 0 external style or FORMAT 1 internal style) for records logged with a Work Area.
  • FORMAT 1 SAVED
    provides the bytes that were saved by records logged over how they would have been saved with FORMAT 0.

In the following example, the number of log bytes was 337 million, which makes each percent 3m. The numbers in the form nn.n are percentages, and the others are less than one percent, which means they are printed as a number of bytes.

             PRCT --   OLD   OLD   OLD   NEW   NEW   NEW   NEW   NEW      FORMAT 
      TOTAL    OF --   RCD   RCD   RCD    WA    WA   RCD   RCD   RCD  ELEM     1 
GROUP  RCDS   LXX --   EXP   CMP  USER  ORIG DELTA   EXP   CMP  USER  LIST SAVED 
ADDIT  352K  30.7                      1262K         6.6 3289K  727K  165K   1.6 
DELET  352K  32.1      8.0   1.2 1705K                                     1453K 
UPDAT  352K  36.2      8.0   1.1  844K 1262K   2.2  1008   146     0   1.7   6.1 
TSN    7781 1685K                                                                
MOVER  3340 1042K 

*DAC*   11K   8.3                                                      
OTHER   304 84805                                                                

Note: If any data access capture log records were written, an additional line (*DAC*) occurs. This line provides the total number of records and percent of the log.

Buffer Pool Information

                     BUFFER POOL INFORMATION  
NAME    NUMBER    SIZE  USED 1  USED 2  USED 3  USED 4  USED 5+      
                                                                     
                                                                     
IXX         12      4K       7       5       5       4     199-K     
DXX        210      4K    2543    1707    1539    1453     269-K     
DATA       210      8K       2       0       0       0       0       
DATA2       20  32,767       0       0       0       0       0       
                                                                     
IXX01       10      8K       0       0       0       0       0       
DXX01       20      8K       0       0       0       0       0       
DATA01      40     32K    6479    6182    6088    6005     293-K     
IXX02       10      8K       0       0       0       0       0       
IXX03        9      4K       0       0       0       0       0       
DXX03        9      4K       0       0       0       0       0       
DATA03       9      4K       0       0       0       0       0       
DATA99      40      4K       0       0       0       0       0

This page of the report provides details about what buffer pools exist and their 1-5 usage. This report includes both the standard buffer pools and the alternate buffers pools, if defined to the current MUF.

Note the following:

  • DATA2
    The DATA2 line only appears if the current MUF has a standard large data pool defined.
  • SIZE
    The numbers in the buffer SIZE column are not rounded, that is, the numbers represent the actual buffer size.
  • USED
    The buffer USED totals are rounded numbers that follow standard CA Datacom® rules regarding when to round numbers to K, M, or G.

Compound Boolean Selection (CBS) Information Example

The following Compound Boolean Selection (CBS) information section of the EOJ report contains information that compliments the already existing CBS statistics at EOJ.

                                                  CBS INFORMATION
 
                            SETS PROCESSED               561        SETS DELETED MAX AGE          0    
                            SETS SPILLED                   0        SETS FETCHED                  0 
                            CBSBFR CURRENT PERCENT FULL    0        CBSBFR MAX PERCENT FULL       0

This page of the report shows an example of the additional CBS information in the EOJ report:

  • SETS PROCESSED
    Displays the total number of sets processed by the MUF.
  • SETS DELETED MAX AGE
    Displays the number of sets which were deleted from the CBS buffer due to the CBS MAX AGE setting.
  • SETS SPILLED
    Displays the number of sets which had to be paged to the CBS index. This is an interaction between the specified CBS buffer size and the number and size of open CBS sets. If Sets Spilled is non-zero, you might want to either increase the CBS buffer size or examine your applications for missing SELPR statements.
  • SETS FETCHED
    Displays the number of times a spilled set was referenced to retrieve more rows. The ratio between Sets Spilled and Sets Fetched can be used to understand if sets that are truly in use are being spilled to the CBS index, or if it is an absence of SELPR in user programs which is causing sets, that are no longer in use, to be paged out.
  • CBSBFR CURRENT PERCENT FULL
    Displays the percent of CBS buffer max size that is being used by open sets.
  • CBSBFR MAX PERCENT FULL
    Displays the high water mark for concurrent open sets.

Index Queue Task Information

                                           INDEX QUEUE TASK INFORMATION


QUEUE TASK               REQUESTS        I/O COUNT

         1                  2,584            1,724

         2                     68               45

This page of the report shows the following information:

  • Queue Task
    One of the RWTSAs dedicated to Index Queue Processing
  • Requests
    Displays the number of index queue entries processed by this Queue RWTSA.
  • I/O Count
    Displays the number of I/O requests performed by this Queue RWTSA to service the Queue Requests.

CDC Report Example

                                            CHANGE DATA CAPTURE
 
 
 
DB03161I - CDCL MUFP1 CLOSED LASTCDC-20070827100407 LASTLXX-20070827100709
DB03162I - CDCL MUFP1 POLL-15 GAPWAIT-  MODE-REMOTE(DS)
DB03163I - CDCL MUFP1 CDCLXXIO-73,682 MNT-785,000 WRAP-0

This page of the MUF EOJ report shows an example of CHANGE DATA CAPTURE (CDC. For more information about the CDC feature, see Administrating.

DATA ACCESS CAPTURE - DAC_TABLE

If Data Access Capture tables were defined, a page is printed with the DBID, table name, status, content, total log records, total log record bytes, and optionally an error.

Log records are printed up to one less than 10 billion. A number larger than this is printed as all plus (+) signs.

Log bytes are currently printed up to 1,000 billion. A larger number than this is printed as all plus (+) signs.

Example

                                            DATA ACCESS CAPTURE - DAC_TABLE                                             
                                                                                                                        
 DBID TABLE STS  CONTENT        RCDS            BYTES                                            ERRORS
                                                                                                                        
  897  C01  YES  NONE              0                0                                                                   
  897  F01  YES  NONE             20            6,000                                                                   
  897  F02  YES  NONE              4            1,200                                                                   
  897  F03  YES  NONE             20            5,500                                                                   
TOTAL                             44           12,700                                                                  

 In the above report columns provided are described below.

  • DBID and TABLE defined with DAC_TABLE 
  • STS (Status) is:
    • YES specifies the entry is in the active list and is currently being used in selection for each data access request. There will be a maximum of one YES entry (except possibly fleetingly as a one is added to replace an existing one that will then transition to OLD).   
    • NO specifies the entry is in the active list and, with its current NO status, is not available for selection. 
    • *NO specifies the entry is in the active list and would be available for selection except that global DATA_ACCESS_CAPTURE is set to NO blocking any selection.
    • NEW specifies the entry is in the new list and not available for selection. The new item is intended to exist only a short time to set proper detail selection before being added to the active list. 
    • OLD specifies the entry is in the active list but not available for selection. It has been available for selection in this MUF execution and has what counts (below) as occurred. There will be as many old entries as the particular table has been replaced by a newer table definition. Each old entry has its statistics available for reporting and auditing.
  • CONTENT is always set to "NONE" as the only current setting.
  • RCDS is the number of log records written to the Log Area (LXX) for this MUF instance for this DBID and table name for the current definition.

  • BYTES are log record bytes for those records.

  • Blanks are normally under the ERRORS heading. However, it is possible to have an "LG" if an error occurred when writing one or more  log records. An "LG" also occurs for a table with a row length of 25,001 or more as those tables are not currently supported for DAC.

For detailed information about the other uses of the DAC feature, see Data Access Capture.

DATA ACCESS CAPTURE - DAC_TABLE PATH COUNTS - SQL

                                            DATA ACCESS CAPTURE - DAC_TABLE PATH COUNTS - SQL
 DBID TABLE STS             SCQ            SQQ            SCI            SSR            SQL  
                        DQ CICS       DQ BATCH           CICS         SERVER          OTHER  
                                                                                             
  897  C01  YES             N/A            N/A            *NO            *NO            *NO  
  897  F01  YES             N/A            N/A            *NO            *NO            *NO  
  897  F02  YES             N/A            N/A              0              0              0  
  897  F03  YES             N/A            N/A              0              0              0  
  897  F04  NO              N/A            N/A              0              0              0  
  897  RNA  YES             N/A            N/A              0              0              0  
 1000  DRB  YES             N/A            N/A              0              0              0  
TOTALS                        0              0              0              0              0                               

DATA ACCESS CAPTURE - DAC_TABLE PATH COUNTS - NOT SQL

                                            DATA ACCESS CAPTURE - DAC_TABLE PATH COUNTS - NOT SQL

 DBID TABLE STS             RCQ            RAQ            RCI            RSR            RAT       
                        DQ CICS       DQ BATCH           CICS         SERVER          OTHER       
                                                                                                  
  897  C01  YES             N/A            N/A            *NO            *NO            *NO       
  897  F01  YES             N/A            N/A            *NO            *NO              0       
  897  F02  YES             N/A            N/A              0              0              0       
  897  F03  YES             N/A            N/A              0              0              0       
  897  F04  NO              N/A            N/A              0              0              0       
  897  RNA  YES             N/A            N/A              0              0              0       
 1000  DRB  YES             N/A            N/A              0              0              0       
TOTALS                        0              0              0              0              0  


 If there are DAC_TABLE statements, the two PATH reports above are provided. The first page is for the SQL paths; the second page is for the non-SQL paths.

  • DBID and table defined with DAC_TABLE
  • Status is:
    • YES if the table at the time of the report is set to YES for active selection.
    • NO if the table is set to NO for active selection.
    • NO if it is set to YES but the current DATA_ACCESS_CAPTURE option is set to NO.
    • NEW if the table has been added after the MUF enabled using DAC_TABLE as NEW,ADD.
    • OLD if the table has been in the active list but was replaced with a new definition. There will be as many OLD entries as NEW DAC_TABLE commands after MUF enabled that were moved to the active list. 
  • The columns are for the DAC_PATH settings for the table. The 4 DQ columns are all set as N/A if Dataquery is not externally secured. The DQ columns are a planned future item.
  • Paths that are set to NO have a count value of *NO to note that the current setting has them not selected.
  • Path counts provide the number of log records logged for DAC for that table that were made through that path.
  • Columns are selected as left to right with the most accurate column that in force for the particular request. For example, a SQL request made through a user program in CICS will be excluded from the first two columns for DQ and will appear in the third colum.

Other Information

Other information that does not fit into one of the previously discussed categories is printed in another summary information report. For example, the following shows information that is printed if, in a z/OS environment, one or more of the high/low threshold options is used.

                                            OTHER INFORMATION
 
 
I/O THRESHOLDS - HIGH-260K LOW-132K MIN-1036K

Task Information

If the MUF fails with an abnormal EOJ, a page showing task information follows the previously shown other information report. The task information contains status information similar to other status displays, but the task information report is specifically targeted at helping to debug the abnormal failure. Fields unique to the task information report are described after the report example that follows.

                                            TASK INFORMATION
 
JOBNAME  RUNIT TASK   TIME  I/O B-RF CMD-DBID-TBL STATUS          TSN    LOGR OWNR/Y VALUE/RID
 
JOB0040  79588    1    :04           UPDAT 997C02 PENDING
JOB0040  79588    2    :04         1 RDUNX 997F01 WAIT BFR LOCK D DBDB0771 83
JOB0040  79588    3    :04    1    2 RDUKG 997F02 WAIT BFR LOCK D DBDB076C101
JOB0040           4    :04           RDUNX 997F03 PENDING

This page of the report provides the following information:

  • B-RF
    Displays the current buffer references.
  • LOGR
    Displays the number of log records executed by the task since the last close or commit occurred.
Was this helpful?

Please log in to post comments.