AUTOINFO (Collect Environmental MUF Information)

The AUTOINFO function collects information from memory and certain selected Dynamic System Tables and records that information into a sequential file. The collected information is also output in printed form.
datacom
The AUTOINFO function collects information from memory and certain selected Dynamic System Tables and records that information into a sequential file. The collected information is also output in printed form.
The main purpose of the AUTOINFO function is to allow you to choose a given MUF and quickly generate information about that environment. This information can be helpful for you and for your communications to Support about a MUF problem.
AUTOINFO should be executed while the MUF is experiencing the problem. However, AUTOINFO can be executed after the MUF has come down or has been cycled. While it will not furnish as much information about a particular situation that occurred in the previous MUF execution, it still provides valuable environmental information.
If AUTOINFO is executed after a MUF has ended but has not been restarted, the function ends with a U0004 condition code. This notifies you that while the report has executed, certain data was not available.
Using AUTOINFO in DBUTLTY
The AUTOINFO function is unique in DBUTLTY because it can communicate to the MUF and its memory at the same time. When the AUTOINFO executes, it uses an internal communication path to query the memory of the MUF and uses the standard DBSIDPR connection path to gather additional data.
The AUTOINFO function communicates with one MUF. Be aware of the following:
  • Run the DBUTLTY on the same LPAR as the targeted MUF
  • 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
  • Ensure proper load library concatenation by keeping the System Identifier modules (DBSIDPR) in separate load libraries.
When to Use
Use the AUTOINFO function when you want to record information about a MUF execution, build a report, and write it as a sequential output file. Support may request the output file if you contact them for support.
How to Use
Use the following syntax to write the AUTOINFO command:
►►─ AUTOINFO DDNAME=
ddname
─┬─────────────────────────────┬───────────────────► └─ ,DECIMAL= ─┬─ . ◄ ───────┬─┘ └─
character
─┘ ►─┬─────────────────────────────┬────────────────────────────────────────────►◄ └─ ,DELIMIT= ─┬─ ; ◄ ───────┬─┘ └─
character
─┘
Command
  • AUTOINFO
    The AUTOINFO command invokes the AUTOINFO function.
Required Keyword
  • DDNAME=
    DDNAME= specifies the name for the diagnostic output from this execution. Support may request this file for analysis or help in solving an open contact.
    A DDNAME is not acceptable
    for sequential input or output files if it is a name reserved for a
    Datacom
    area. Names with the following patterns are therefore not acceptable for DDNAME=:
  • 3-byte names that end with XX, meaning they are reserved as either current or future
    Datacom
    control areas.
  • 6-byte names that end with what could be a database ID from 001 through 999.
  • 7-byte names that end with what could be a database ID from 1000 through 9999.
    The DDNAME= value is verified for acceptability to protect you from unintentionally causing data corruption. The DDNAME check is the default but optional. You can prevent the DDNAME check by using a DBSIDPR parameter (DBUTLTY_EDIT_DATA_SET=) for individual MUF environments. However, we recommend that you allow the DDNAME check.
    The data corruption risk involves not the DDNAME itself but the content of the data set. For example, suppose that you used the CXX DDNAME as the output of a backup. You then copied the CXX DD statement and changed the DDNAME of the copy to be acceptable, avoiding the DDNAME= error. The backup would, however, then overlay the CXX data set, which is not the intent of a backup.
    If you specify an unacceptable name for DDNAME=, message DB10059E is generated.
    We recommend that you allow DDNAME= check protection. You can, however, disable DDNAME= protection. To disable protection, assemble the DBSIDPR module used for this
    Datacom
    environment and specify NONE for the DBUTLTY_EDIT_DATA_SET= parameter. The default is DBUTLTY_EDIT_DATA_SET=FULL_1, which allows DDNAME= protection.
Optional Keywords
  • DECIMAL=
    DECIMAL= specifies the character to use for the decimal point, such as a period (.) or a comma (,).
    • Valid Entries:
      One character enclosed in single quotes
    • Default Value:
      period (.)
  • DELIMIT=
    DELIMIT= specifies the character to use as the delimiter between values in the DSV output. Do not use a period (.) or a comma (,) as these special characters occur normally throughout the AutoCollect data and would cause the DSV output to be unusable.
    • Valid Entries:
      One character
    • Default Value:
      semicolon (;)
Example JCL
Following is an example of the JCL for the AUTOINFO function.
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 and JCL Requirements
.
// EXEC PGM=DBUTLTY,REGION=2M //STEPLIB See the previous note
and JCL Requirements
.
//AUTOINFO EXEC PGM=DBUTLTY,REGION=0M //TABLES DD DSN=TEMP.AUTOINFO.TABLES.SUPPORT,DISP=(NEW,CATLG,CATLG), // UNIT=SYSDA,SPACE=(TRK,(3,1),RLSE) //SYSPRINT DD SYSOUT=* //SYSIN DD * AUTOINFO DDNAME=TABLES /* //
Sample Reports
The reports produced by the AUTOINFO function look similar to the following samples. For examples of the report headers, see Sample Report Headers.
Report - MUF Available and Operational
When the MUF is available and operational, you receive a report similar to the following:
CONTROL CARD(S) .........1.........2.........3.........4.........5.........6.........7.........8 AUTOINFO DDNAME=TABLES FUNCTION=AUTOINFO DDNAME=TABLES
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.
MUF IS AVAILABLE, INFORMATION IS PROVIDED BY THE MUF. MUFNAME: MUF4 VERSION: 14.0 JOB/STC NAME: QA12MUF4 CXXNAME: QAMUF4 JOBID: JOB11528 SYSTEM: CA31 ENABLED TIME: 2008/11/11 13:12:17 CURRENT MUF TIME: 2008/11/11 13:14:59 MUF IS SHADOW: N MUF HAS SHADOW: N DB SUBSYS PRESENT: Y SQL: Y EXTERNAL SECURITY: N ACCOUNTING ON: N DBIDS: DST: 1000 HISTORY: 1007 CBS TEMP: 0006 CBS HEUR: 1006 TASKS: TOTAL: 00250 XCF: 00250 CCI: 00050 SIZE: 46080
TABLE MUF_OPTIONS: MFO ACCTPRM_PRM_DBID 0 ACCTPRM_ANN_DBID 0 ACCTPRM_CPU_TIME Y ...etc.
TABLE MUF_COVEREDVIRTUAL: MFC DBID AREA V/C F/A DS MEM_SIZE BLKS_MAX BLKS_CURR TOTAL_READS MRDF_READS VIRT_WRITES ACTV_READS NONF_READS 6 IXX V N X 262144000 64000 64000 2 2 0 NULL NULL 17 IXX V N N 32768 NULL NULL NULL NULL NULL NULL NULL 17 TTM V N N 33554432 NULL NULL NULL NULL NULL NULL NULL TOT V N N 295731200 64000 64000 2 2 0 0 0 TOT C N N 0 0 0 0 0 0 0 0
TABLE MUF_ACCOUNTING: MFY DBID TABLE BUF_SIZE S THRESHOLD SPILLING TOTAL_REQU PHYSIC_IOS LOCATES TOTAL_ADDS TOTAL_UPDT UNAVAILABL CONFLICTS SKIPPED ENTRIES RECLAIMED LOCATES_ST SPIL_THRES SPIL_INTER TOT 0 T 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
TABLE MUF_INTERNAL_STATS: MFV TIMES_RD_1 TIM_RD_2_8 TIM_RD_9_32 TIM_RD_33_99 TIM_WRITE_1 TIM_WRT_2_12 TIM_WRT_13_24 TIM_WRT_25_48 BRKS_DONE IO_MEM_ST 0 0 0 0 0 0 0 0 0 0
TABLE MUF_SMP_STATS: MFW POSTED_0 10
TABLE MUF_RETURN_CODES: MFU EXTERNAL_CODE INTERNAL_CODE COUNT_CODES TOT 0
TABLE MUF_SQLCODES: SQQ SQL_CODE CODE_COUNT TOTAL 0
TABLE MUF_MISC_STATS: SQM PROC_CACHE_REUSE PROC_FROM_CALL PROC_FROM_TRIGGER PROC_QUEUED PROC_SQL_STMTS PROC_FAILURES PROC_NESTS 0 0 0 0 0 0 0
TABLE MUF_SYSTEM_STATS: MFS BEGIN_TIME 20081111 13.12.17.000000 CURRENT_DATETIME 20081111 13.14.59.633053 CURRENT_CPU 1 RQ_PENDING_1_10 8 RQ_PENDING_11_20 0 RQ_PENDING_21_30 0 ... etc. DATA2_USED_4 0 DATA2_USED_5 0
TABLE MUF_AREA_STATS: MFA DBID AREA_NAME PHYSICAL_READS PHYSICAL_WRITES LOGICAL_READS LOGICAL_WRITES 0 CXX 83 6 502 8 0 FXX 15 14 15 0 0 LXX 4 6 4 1 6 IXX 0 0 4 0 1000 IXX 0 0 0 0 1000 SYS 0 0 0 0 ... etc.. 1006 CBS 2 0 2 0 1006 IXX 2 0 2 0 TOT 106 26 529 9
TABLE MUF_TABLE_STATS: MFT DBID TABLE_NAME AREA_NAME TOTAL_REQUEST TOTAL_READS TOTAL_ADDS TOTAL_DELETES TOTAL_UPDATES 1000 DRA SYS 0 0 0 0 0 1000 DRB SYS 0 0 0 0 0 1000 DRC SYS 0 0 0 0 0 1000 DRD SYS 0 0 0 0 0 1000 DRE SYS 0 0 0 0 0 1000 DRF SYS 0 0 0 0 0 1000 DRI SYS 0 0 0 0 0 ... etc. 1006 CBS CBS 0 0 0 0 0 TOT TOT 72 56 0 0 0
TABLE MUF_CBS: MCB BUF_CUR_PERC_FULL 0 BUF_MAX_PERC_FULL 0 CUR_USED_SET_MEM 311 MAX_USED_SET_MEM 0 SETS_DEL_MAX_AGE 16 SETS_FETCHED 0 SETS_PROCESSED 0 SETS_SPILLED 0 SETS_TEMP_INDEX 0 TEMP_INDEX_ENTRIES 0 SPILLED_JOB_NAME NULL SPILLED_UIB NULL DURATION_AT_SPILL NULL
TABLE MUF_CONFIG: MCF CONFIG_COMMAND CONFIG_PARAMETERS DIAGOPTION 000800000000000000000000000000000000000000000000 HISTORY 1007....
TABLE MUF_SRB_ZIIP: MZI SEQ.NO ENCLAVE_SEC ZIIP_ON_CP_SEC ZIIP_QUAL_SEC ZIIP_SECONDS ZIIP_PERCENT TOTAL 0 0 0 0
TABLE MUF_TCB_OR_SRB: MTC TASK PROGRAM SEQ.NO CPU_SECONDS TIMES_USED TIMES_POSTED PHYSICAL_IO MAIN DBMUFPR 1 0 249 248 132 SMP DBSMPPR 1 0 0 0 0 SMP DBSMPPR 2 0 0 0 0 SMP DBSMPPR 3 0 0 0 0 SUB DBCONPR 1 0 0 0 0 SUB DBDUSPR 1 0 0 0 0 SUB DBENQPR 1 0 13 13 0 SUB DBMSBPR 1 0 3 0 0 SUB DBOCSPR 1 0 5 10 0 SUB DBOCSPR 2 0 0 0 0 SUB DBOC2PR 1 0 5 5 0 TOT 9999 0 275 276 132
TABLE BUSINESS_VALUE_METRICS: BVM Elapsed Seconds 162 CPU Seconds Used 1 Physical I/O 132 Database Requests 27 Data Area Requests 538 Table Requests 56 Table Reads 56 Table Adds 0 Table Deletes 0 Table Updates 0 Calculated Business Value Metrics Requests per elapsed second 0.16 Requests per CPU second 27.00 Requests per Physical IO 0.20
TABLE BUSINESS_VALUE_METRICS: BVD Elapsed Seconds 162 CPU Seconds Used 1 Request Processing % Database Requests 27 ** Data Manager Requests 30 111.1 SQL Requests 0 0.0 Physical I/O Processing % Total Physical I/O 132 ** Physical I/O - Read 106 80.3 Physical I/O - Write 26 19.6 Sequential Read Ahead I/Os 0 0.0 Accounting I/O 0 0.0 Logging I/O 6 4.5 Buffer Processing 5 to 1 Ratios IXX Buffer Use 5+ 0 0.0 DXX Buffer Use 5+ 0 0.0 DATA Buffer Use 5+ 0 0.0 DATA2 Buffer Use 5+ 0 0.0 No IXX Buffer Available 0 No DXX Buffer Available 0 No DATA Buffer Available 0 No EXPAND Buffer Available 0 No TXB Buffer Available 0 MRDF Processing % Saved I/O MRDF Memory (bytes) 295731200 ** MRDF Virtual Reads 2 1.5 MRDF Virtual Writes 0 0.0 MRDF Covered Memory (bytes) 0 ** ... etc. Request Pending 31-40 0 Request Pending 41-50 0 Request Pending 50+ 0
DB30073I - TOTAL RECORDS SELECTED: 101
Report - MUF Previously Active
When the MUF is not currently available but was previously active on the system, you receive a report similar to the following:
CONTROL CARD(S) .........1.........2.........3.........4.........5.........6.........7.........8 AUTOINFO DDNAME=TABLES FUNCTION=AUTOINFO DDNAME=TABLES
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.
MUF NOT AVAILABLE, INFORMATION PROVIDED FROM PRIOR EXECUTION THIS SYSTEM. MUFNAME: MUF4 RELEASE: 12 SP: JOB/STC NAME: QA12MUF4 CXXNAME: QAMUF4 JOBID: JOB51596 SYSTEM: CA31 ENABLED TIME: 2008/11/10 10:53:01 MUF IS SHADOW: Y MUF HAS SHADOW: N DB SUBSYS PRESENT: N SQL: Y EXTERNAL SECURITY: N ACCOUNTING ON: N DBIDS: DST: 1000 HISTORY: 1007 CBS TEMP: 0006 CBS HEUR: 1006 TASKS: TOTAL: 00250 XCF: 00250 CCI: 00050 SIZE: 46080 DB30073I - TOTAL RECORDS SELECTED: 0 DB10045E - ABNORMAL TERMINATION DUE TO ERROR(S)
Report - MUF Not Available
When the MUF has not been started since this LPAR was last IPLed, you receive a report similar to the following:
CONTROL CARD(S) .........1.........2.........3.........4.........5.........6.........7.........8 AUTOINFO DDNAME=TABLES FUNCTION=AUTOINFO DDNAME=TABLES
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.
MUF NOT AVAILABLE, NO INFORMATION BECAUSE NO PRIOR EXECUTION THIS SYSTEM. DB30073I - TOTAL RECORDS SELECTED: 0 DB10045E - ABNORMAL TERMINATION DUE TO ERROR(S)