DC/UCF System Statistics Reports

Record Systemwide Data
idms19
Record Systemwide Data
System statistics record systemwide data. DC/UCF always collects system statistics (they are not optional) because they require minimal overhead and provide valuable information for tuning and maintaining the DC/UCF system.
When Statistics Are Logged
System statistics are logged to the DC/UCF log file at the following times:
  • At normal system shutdown
  • At the statistics interval established at system generation by the STATISTICS parameter of the SYSTEM statement. The statistics interval can be varied at run time by means of the DCMT VARY STATISTICS command.
  • Upon explicit request by means of a DCMT WRITE STATISTICS command.
Summary of System Statistics Reports
System statistics are collected and written for six categories:
General systemwide statistics
SREPORT 003
Systemwide task statistics
SREPORT 012
Systemwide program statistics
SREPORT 013
Systemwide queue statistics
SREPORT 014
Systemwide line statistics
SREPORT 015
Systemwide physical terminal (including UCF PTERMs) statistics
SREPORT 016
This article contains the following information:
SREPORT 003 - IDMS DC System Statistics
SREPORT 003, the IDMS DC System Statistics report, summarizes all systemwide statistics and thus provides an overview of system performance.
Sample SREPORT 003
:
REPORT NO. 03 IDMS-DC SYSTEM STATISTICS Rnn.n mm/dd/yy PAGE 1 SELECTED FROM: yyddd hh:mm TO: yyddd hh:mm CV SYSTEM START: yyddd hh:mm TO: yyddd hh:mm CV JOB NAME: jobname CV NUMBER: nnn SYSTEM STATISTICS 116 TOTAL TASKS 0 STD PGMPOOL LOADS 72 TOTAL SYSTEM TASKS 0 STD PGMPOOL WAITS 0 TASKS ABENDED 0 STD PGM PAGES LOADED 0 RUNAWAY TASKS ABORTED 29 RENTPOOL LOADS 0 TIMES AT MAX TASK 0 RENTPOOL WAITS 0 SHORT ON STORAGE 842 RENT PGM PGS LOADED 0 OVER RLE THRESH 0 XA PGMPOOL LOADS 0 OVER RCE THRESH 0 XA PGMPOOL WAITS 0 OVER DPE THRESH 0 XA PGM PGS LOADED 0 OVER ILE THRESH 169 XA RENTPOOL LOADS 0 STORAGE POOL WAITS 0 XA RENTPOOL WAITS 1,624 STG REQS - PASS 1 24,987 XA RENT PGS LOADED 1,103 STG REQS - PASS 2 0 PAGE RELEASE RQSTS 0 PUT JOURNALS 0 PAGES RELEASED 0 SET TIME WAITS 0 PAGE FIX RQSTS 236 SET TIME POSTS 0 PAGES PFIXED 1 SET TIME STRTTASKS 0 PAGE FREE RQSTS 234 SET TIME CANCELS 0 PAGES PGFREED 0 AUTOSTART TASKS DC STATISTICS 19.8805 USER MODE CPU TIME 3.8358 SYSTEM MODE CPU TIME 659,356 DC SERVICE REQUESTS 64 GET SCRATCHES 659,928 DB SERVICE REQUESTS 106 PUT SCRATCHES 245 PROGRAMS CALLED 64 DELETE SCRATCHES 375 MAX # RLE'S USED 10 GET QUEUES 329 MAX # RCE'S USED 0 PUT QUEUES 308 MAX # DPE'S USED 0 DELETE QUEUES 1,337 STACK HI WATERMARK 8 GET TIMES 2,727 GET STORAGES 0 SET TIMES 2,494 FREE STORAGES DC EXTENDED STATISTICS 40.806072 SYSTEM MODE CPU .000000 ZIIP ON CP CPU .000000 ZIIP ON ZIIP CPU 22.013726 USER MODE CPU 62.819799 TOTAL TCB CPU .000000 ENCLAVE CPU DB STATISTICS 2,336,618 PAGES REQUESTED 0 CALC RECS NO OFLOW 1,041,703 PAGES READ 0 CALC RECS OFLOW 0 PAGES WRITTEN 0 VIA RECS NO OFLOW 1,319,871 CALLS TO DBMS 0 VIA RECS OFLOW 1,296,108 RECORDS REQUESTED 0 FRAGMENTS STORED 1,294,797 RECORDS CURRENT OF RU 0 RECORDS RELOCATED 330 TOTAL LOCKS 0 RECORDS UPDATED 0 PAGES FOUND IN CACHE 0 PAGES IN PREFETCH BUFF INDEX STATISTICS 0 SR8 SPLITS 0 SR8 STORES 0 SR8 SPAWNS 0 SR8 ERASES 0 ORPHANS ADOPTED 0 SR7 STORES 0 BTREE SEARCHES 0 SR7 ERASES 0 MIN LEVELS SEARCHED 0 TOTAL LEVELS SEARCHED 0 MAX LEVELS SEARCHED SQL STATISTICS 0 SQL COMMANDS 0 TUPLES FETCHED 0 SORTS 0 ROWS INSERTED 0 TUPLES SORTED 0 ROWS UPDATED 0 MIN SORT 0 ROWS DELETED 0 MAX SORT 0 AM RECOMPILES
Field Descriptions
A description of the fields in the IDMS DC System Statistics report follows:
  • SELECTED FROM/TO
    Specifies the time period specified on the USE 'SREPORT 000' parameter where SELECTED FROM specifies the beginning date and time and SELECTED TO specifies the ending date and time. The date is in Julian form, yyddd, where yy is the last two digits of the year and ddd is the day. The time is in hh:mm form, where hh is hours based on a 24-hour clock and mm is minutes.
  • CV SYSTEM START/INTERVAL START/TO
    Specifies the actual time period for the report generated. If the USE 'SREPORT 000' parameter does not specify a time range, CV SYSTEM START/INTERVAL START and TO represent the time range for the entire input archive file or input file created by SREPORT 099. When the input file contains cumulative statistics, the CV SYSTEM START date and time will be displayed. When the input file contains interval based statistics, the INTERVAL START date and time will be displayed.
  • CV JOB NAME
    Specifies the starting job name of Central Version which collected the statistics.
  • CV NUMBER
    Specifies the number of Central Version which collected the statistics.
  • TOTAL TASKS
    Indicates the total number of system and user tasks, including external request units, executed for this session.
  • TOTAL SYSTEM TASKS
    Indicates the number of system tasks active at the conclusion of this session. System-initiated tasks include FACTOTUM, MASTER, DBRC, print, and line drivers.
  • TASKS ABENDED
    Indicates the number of tasks that abended during this session.
  • RUNAWAY TASKS ABORTED
    Indicates the number of tasks that terminated abnormally because their execution time exceeded the maximum amount of time defined in the RUNAWAY INTERVAL clause of the SYSTEM statement.
  • TIMES AT MAX TASK
    Indicates the number of times a new task could not start because the system was processing the maximum number of tasks specified at system generation in the MAXIMUM ERUS and MAXIMUM TASK clauses of the SYSTEM statement.
    Interpretation: Generally, this value should be close to 0. Values equal to 0 may indicate that the overall system size is larger than necessary; values greater than 0 may represent peaks in system loads or chronic system overload.
    To reduce the number of times at maximum tasks, make one or more of the following system adjustments:
    • Increase the MAX ERUS and MAX TASKS thresholds
    • Decrease the limit specified for the MAXIMUM CONCURRENT THREADS clause of the TASK statement at system generation
  • SHORT ON STORAGE
    Indicates the number of times program storage requests were not satisfied. Generally, the value should be close to zero; values greater than zero should represent peaks in storage utilization, rather than chronic shortages.
    Interpretation: Values consistently greater than zero indicate the size of the storage pool or storage cushion is too small. The size of the storage pool is defined at system generation with the STORAGE POOL and XA STORAGE POOL clauses of the SYSTEM system generation statement; the size of the cushion is defined with the CUSHION clause of the same statement.
  • OVER RLE THRESH
    Indicates how many times the number of resource link elements (RLEs) exceeded the value allocated in the SYSTEM statement at system generation. When the threshold is reached, the task that is executing abends; if the task is a system task, the system abends. Ideally, this value should be 0.
  • OVER RCE THRESH
    Indicates how many times the number of resource control elements (RCEs) exceeded the value allocated in the SYSTEM statement at system generation. When the threshold is reached, the task that is executing abends; if the task is a system task, the system abends. Ideally, this value should be 0.
  • OVER DPE THRESH
    Indicates how many times the number of deadlock prevention elements (DPEs) exceeded the value allocated in the SYSTEM statement at system generation. When the threshold is reached, the task that is executing abends; if the task is a system task, the system abends. Ideally, this value should be 0.
  • OVER ILE THRESH
    Indicates the number of time the internal lock elements (ILEs) exceeded their allocated value. When the threshold is reached, the task that is executing abends. If the task is a system task, the system abends. Ideally, this value should be zero (0).
  • STORAGE POOL WAITS
    Indicates the number of times tasks had to wait for a sufficient amount of contiguous storage. This value should be as low as possible; if the value is large or increasing, increase the size of the storage cushion in the CUSHION clause of the STORAGE POOL statement at system generation.
  • STG REQS - PASS 1
    Indicates the number of storage requests that allocated space on a previously allocated page.
  • STG REQS - PASS 2
    Indicates the number of storage requests that allocated space on a previously allocated page and on a contiguous new page.
  • SET TIME WAITS
    Indicates the number of program requests to place a task in a wait state. The program issues the request with a SET TIMER WAIT DML statement.
  • SET TIME POSTS
    Indicates the number of program requests to post a user-specified event control block (ECB) after the specified time interval elapses. The program issues the request with a SET TIMER POST DML statement.
  • SET TIME STRTTASKS
    Indicates the number of program requests to initiate a user-specified task after the specified time interval elapses. The program issues the request with a SET TIMER START DML statement.
  • SET TIME CANCELS
    Indicates the number of program requests to cancel the effect of a previously issued SET TIMER request. The program issues the request with a SET TIMER CANCEL DML statement.
  • AUTOSTART TASKS
    (DC/UCF only) Indicates the number of times the associated task of each queue was invoked to process queue records. The task is invoked each time the queue threshold is exceeded. The threshold is defined with the THRESHOLD clause of the QUEUE system generation statement; the task is identified by the INVOKES TASK clause of the same statement.
  • STD PGMPOOL LOADS
    Indicates the number of nonresident modules loaded into the 24-bit program pool; nonresident modules include programs, CA ADS and CA ADS batch dialogs, maps (DC/UCF only), and tables.
  • STD PGMPOOL WAITS
    Indicates the number of times program loads were delayed due to insufficient space in the 24-bit program pool. Ideally, this value should be zero; a value greater than zero indicates insufficient space in the program pool for the volume of program load activity in the system.
    Interpretation: If this value is high, the size of the 24-bit program pool should be increased or nonresident programs should be redefined as either resident or reentrant. Program pool usage can be observed dynamically by means of the OPER WATCH PR command. For more information on program pools, see the
    Administrating section
    .
  • STD PGM PAGES LOADED
    Indicates the number of pages used by programs loaded into the 24-bit program pool. The size of a page equals 4K. Only one program can occupy a program pool page; that is, a 4.5K program uses two pages of program pool.
  • RENTPOOL LOADS
    Indicates the number of reentrant programs loaded into the 24-bit reentrant pool; reentrant programs include CA ADS dialogs and subschemas.
  • RENTPOOL WAITS
    Indicates the number of times reentrant program loads were delayed due to insufficient space in the 24-bit reentrant pool. Ideally, this value should be zero; a value greater than zero indicates the size of the reentrant pool should be increased.
  • RENT PGM PGS LOADED
    Indicates the number of pages used by reentrant programs loaded into the 24-bit reentrant pool. A page is 512 bytes (0.5K).
  • XA PGMPOOL LOADS
    (Extended addressing only) Indicates the number of nonresident modules loaded into the 31-bit XA program pool; nonresident modules include programs, subschemas, maps, database procedures, and tables that have been assigned an RMODE of ANY.
  • XA PGMPOOL WAITS
    (Extended addressing only) Indicates the number of times program loads were delayed due to insufficient space in the 31-bit XA program pool. Ideally, this value should be zero; a value greater than zero indicates insufficient space in the XA program pool for the volume of program load activity in the system.
  • XA PGM PGS LOADED
    (Extended addressing only) Indicates the number of pages used by nonresident modules loaded into the 31-bit XA program pool. The size of a page equals 4K. Only one program can occupy a program pool page; that is, a 4.5K program uses two pages of program pool.
  • XA RENTPOOL LOADS
    (Extended addressing only) Indicates the number of reentrant modules loaded into the 31-bit XA reentrant pool; reentrant modules include reentrant programs, subschemas, CA ADS dialogs, and DC/UCF maps that have been assigned an RMODE of ANY.
  • XA RENTPOOL WAITS
    (Extended addressing only) Indicates the number of times program loads were delayed due to insufficient space in the 31-bit XA reentrant pool. Ideally, this value should be zero; a value greater than zero indicates insufficient space in the XA reentrant pool for the volume of program load activity in the system.
  • XA RENT PGS LOADED
    (Extended addressing only) Indicates the number of pages used by reentrant modules loaded into the 31-bit XA reentrant pool. The size of a page equals 512 bytes (0.5K).
  • PAGE RELEASE RQSTS
    Indicates the number of requests to release 4K virtual pages.
  • PAGES RELEASED
    Indicates the number of 4K byte pages actually released.
  • PAGE FIX RQSTS
    (VS systems only) Indicates the number of requests to fix 4K virtual pages allocated to storage pools defined to the system.
  • PAGES PFIXED
    (VS systems only) Indicates the number of 4K virtual pages fixed in storage pools defined to the system.
  • PAGE FREE RQSTS
    Indicates the number of requests to release 4K fixed virtual pages allocated to storage pools defined to the system, thereby making storage eligible for paging out.
  • PAGES PGFREED
    Indicates the number released of 4K fixed virtual pages allocated to system storage pools.
  • PUT JOURNALS
    Indicates the number of program requests to write statistics to the journal file with the WRITE JOURNAL DML statement.
  • USER MODE CPU TIME
    Indicates the amount of CPU time (in ten-thousandths seconds) spent in executing user code.
  • DC SERVICE REQUESTS
    Indicates the number of times user programs requested DC/UCF services (for example, GET STORAGE requests). This value also includes both explicit and implicit requests for database services. For example, OBTAIN
    record-name
    is an explicit program request. PUT QUEUE is an implicit request for database services because the DC/UCF system must store the queue record.
  • DB SERVICE REQUESTS
    Indicates the number of times a user or system program requests database services (for example, OBTAIN
    record-name
    ).
    For LRF and SQL programs, DB SERVICE REQUESTS should be less than or equal to the number of CALLS TO DBMS. You can use these values to evaluate how efficiently the LRF or SQL path extracts data. For example, a program OBTAIN
    logical-record
    command increments DB SERVICE REQUESTS by one, but may greatly increment the CALLS TO DBMS value, especially if an area sweep occurs due to the NULL SELECT clause.
  • PROGRAMS CALLED
    Indicates the number of programs called (for example, the number of #LOAD PGM requests issued).
  • MAX # RLE'S USED
    Indicates the highest number of resource link elements (RLEs) used during this session. If this value approximates the threshold established at system generation, increase the threshold.
  • MAX # RCE'S USED
    Indicates the highest number of resource control elements (RCEs) used during this session. If this value approximates the threshold established at system generation, increase the threshold.
  • MAX # DPE'S USED
    Indicates the highest number of deadlock prevention elements (DPEs) used during this session. If this value approximates the threshold established at system generation, increase the threshold.
  • STACK HI WATERMARK
    Indicates the largest amount of the task control element (TCE) stack area used by any task. The stack size is defined at system generation with the STACKSIZE clause of the SYSTEM statement.
  • GET STORAGES
    Indicates the number of program requests to acquire variable storage dynamically from a DC/UCF storage pool or obtain the address of a previously acquired storage area. The program issues the request with the GET STORAGE DML statement.
  • FREE STORAGES
    Indicates the number of program requests to free all or part of a DC/UCF storage area. The program issues the request with the FREE STORAGE DML statement.
  • SYSTEM MODE CPU TIME
    Indicates the amount of CPU time (in ten-thousandths seconds) spent in executing system code.
  • GET SCRATCHES
    Indicates the number of program requests for scratch records from the DDLDCSCR area. The program issues the request with the GET SCRATCH DML statement.
  • PUT SCRATCHES
    Indicates the number of program requests to store or replace a scratch record in the DDLDCSCR area. The program issues the request with the PUT SCRATCH DML statement.
  • DELETE SCRATCHES
    Indicates the number of program requests to delete scratch records from the DDLDCSCR area. The program issues the request with the DELETE SCRATCH DML statement.
  • GET QUEUES
    Indicates the number of program requests to retrieve a queue record from the DDLDCRUN area and place it in a storage area associated with the issuing program. The program issues the request with the GET QUEUE DML statement.
  • PUT QUEUES
    Indicates the number of program requests to store a queue record in the DDLDCRUN area. The program issues the request with the PUT QUEUE DML statement.
  • DELETE QUEUES
    Indicates the number of program requests to delete queue records from the DDLDCRUN area. The program issues the request with the DELETE QUEUE DML statement.
  • GET TIMES
    Indicates the number of program requests for the system date and time. The program issues the request with the GET TIME DML statement.
  • SET TIMES
    Indicates the number of SETTIME requests to define an event that is to occur after a specified time interval.
  • SYSTEM MODE CPU
    Indicates the amount of CPU time (in microseconds) spent in executing system code.
  • USER MODE CPU
    Indicates the amount of CPU time (in microseconds) spent in executing user code.
  • ZIIP on ZIIP CPU
    Indicates the amount of CPU time (in microseconds) spent on zIIP.
  • ZIIP on CP CPU
    Indicates the amount of CPU time (in microseconds) spent on CP, while qualified for zIIP.
  • TOTAL TCB CPU TIME
    Indicates the amount of CPU time (in microseconds) spent on CP in either system mode or user mode.
  • ENCLAVE CPU
    Indicates the amount of CPU time (in microseconds) spent on CP or zIIP, while qualified for zIIP.
  • PAGES REQUESTED
    Indicates the number of pages requested by IDMSDBMS (including pages found in a buffer). A page request does not result in a page read if the page is in the buffer pool.
    Interpretation: The ratio of PAGES REQUESTED/PAGES READ is the
    buffer utilization ratio
    . It measures the effectiveness of the buffer-pool size and design of the database (for example, CALC and VIA clustering). The higher the ratio the better. Ratios consistently below 2.0 indicate that processing is random or that the buffer-pool size is too small.
    The buffer utilization ratio may be artificially high for transactions that keep locks, due to the nature of the internal locking mechanism. IDMSDBMS cannot hold a buffer while requesting a lock; therefore, when locks are kept, IDMSDBMS must free and request a page each time a record is requested.
  • PAGES READ
    Indicates the number of database pages read from disk.
  • PAGES WRITTEN
    Indicates the number of database pages physically written to disk. A page can be updated several times before it is actually written back to the database.
  • CALLS TO DBMS
    Indicates the number of calls to the database management system.
    Execution of each navigational DML request involves one call; execution of each logical record facility (LRF) and SQL request typically involves multiple calls.
  • RECORDS REQUESTED
    Indicates the number of database records requested by IDMSDBMS.
    Interpretation: The ratio of RECORDS REQUESTED to PAGES READ is the
    space management ratio
    . The space management ratio measures how well space is allocated (for example, VIA options, CALC distribution, and buffering). The higher the ratio the better. Ratios less than 4 or less than the norm indicate that the size of the buffer should be increased and database tuning should be performed.
    The space management ratio may be artificially high for transactions that keep locks, due to the nature of the internal locking mechanism. IDMSDBMS cannot hold a buffer while requesting a lock; therefore, when locks are kept, IDMSDBMS must free and request a page each time a record is requested.
  • RECORDS CURRENT OF RU
    Indicates the number of records made current of transaction.
    Interpretation: The ratio of RECORDS REQUESTED to RECORDS CURRENT is the
    effectiveness ratio
    . The effectiveness ratio measures the amount of work CA IDMS/DB is doing for the programmer (that is, how many records the DBMS has to examine to find the one requested). The lower the ratio the better. If the ratio is high, examine set options (for example, sorted order or next pointers only) for appropriateness. If the options are correct, examine the program logic for accurate use of currency.
  • TOTAL LOCKS
    Indicates the number of all locks acquired and released by all completed transactions. This is NOT a count of locks currently held.
  • PAGES FOUND IN CACHE
    Indicates the number of requested database pages that have been found in a shared cache or an ESA dataspace.
  • CALCRECS NO OFLOW
    Indicates the number of CALC records stored on the target page.
  • CALC RECS OFLOW
    Indicates the number of CALC records not stored on the target page.
    Interpretation: The ratio of CALC records stored on their target page to the total number stored (that is, hits plus overflows) is the
    CALC cluster ratio
    . The ratio reflects the efficiency of the CALC algorithm.
    The CALC cluster ratio is especially important when the database is loaded or restructured. Ideally, the ratio should be 1, which indicates no overflow. Ratios consistently less than 1 or less than the norm indicate that space utilization is getting high and the database should be tuned.
  • VIA RECS NO OFLOW
    Indicates the number of VIA and/or DIRECT records stored on the target page.
  • VIA RECS OFLOW
    Indicates the number of VIA and/or DIRECT records not stored on the target page.
    Interpretation: The ratio of VIA records stored on their target page to the total number of VIA records stored (that is, hits plus overflows) is the
    VIA cluster ratio
    . The ratio reflects how well VIA records cluster around their owner.
    Ideally, the ratio should be 1, which indicates no overflow. Ratios less than 1 or less than the norm indicate very large data clusters, high utilization of space, or small page size.
  • FRAGMENTS STORED
    Indicates the number of noncontiguous segments (fragments) stored for variable-length records.
  • RECORDS RELOCATED
    Indicates the number of records relocated from their home page.
  • PAGES IN PREFETCH BUFF
    Indicates the number of database pages that have been directly found in a prefetch buffer.
  • SR8 SPLITS
    Indicates the number of SR8 splits.
  • SR8 SPAWNS
    Indicates the number of SR8 spawns.
  • ORPHANS ADOPTED
    Indicates count of Index members or SR8s whose up-level pointers were corrected to point to the actual SR8 in which they appear.
  • BTREE SEARCHES
    Indicates number of Btree index probes.
  • MIN LEVELS SEARCHED
    Indicates least number of levels descended.
  • MAX LEVELS SEARCHED
    Indicates highest number of levels descended.
  • SR8 STORES
    Indicates count of SR8s created.
  • SR8 ERASES
    Indicates count of SR8s erased.
  • SR7 STORES
    Indicates count of SR7s created.
  • SR7 ERASES
    Indicates count of SR7s erased.
  • TOTAL LEVELS SEARCHED
    Indicates total number of levels descended.
  • SQL COMMANDS
    Indicates the number of SQL commands executed.
  • SORTS
    Indicates the number of SQL sorts performed.
  • TUPLES SORTED
    Indicates the number of rows participating in all sorts.
  • MIN SORT
    Indicates the least number of rows sorted.
  • MAX SORT
    Indicates the largest number of rows sorted.
  • TUPLES FETCHED
    Indicates number of tuples FETCHed.
  • ROWS INSERTED
    Indicates the number of rows INSERTed.
  • ROWS UPDATED
    Indicates the number of rows UPDATed.
  • ROWS DELETED
    Indicates the number of rows DELETEd.
  • AM RECOMPILES
    Indicates the number of automatic access module recompilations.
For a detailed explanation of DML commands, see the
CA IDMS Navigational DML Administrating section
. For more information on system generation statements, see the
CA IDMS Administrating section
.
SREPORT 012 - IDMS DC Task Summary
SREPORT 012, the IDMS DC Task Summary report, summarizes systemwide task statistics, indicating the number of times each task was invoked. Systems administrators can use SREPORT 012 to monitor trends in task usage; for example, watching for peaks in task usage over a set time period.
The following figure shows one page of a sample IDMS DC Task Summary report:
Sample SREPORT 012
:
REPORT NO. 12 IDMS-DC TASK SUMMARY Rnn.n mm/dd/yy PAGE 3 SELECTED FROM: yyddd hh:mm TO: yyddd hh:mm CV SYSTEM START: yyddd hh:mm TO: yyddd hh:mm CV JOB NAME: jobname CV NUMBER: nnn TASK TIMES INVOKED S 0 SCHEMA 0 SCHEMAT 0 SEND 0 SHOWMAP 0 SIGNOFF 0 SIGNON 0 SSC 0 SSCT 0 SUSPEND 0 SYSGEN 0 SYSGENT 0 TCF 0 TOTAL 4
Field Descriptions
A description of the fields in the IDMS DC Task Summary report follows:
  • SELECTED FROM/TO
    Specifies the time period specified on the USE 'SREPORT 000' parameter where SELECTED FROM specifies the beginning date and time and SELECTED TO specifies the ending date and time. The date is in Julian form,
    yyddd
    , where
    yy
    is the last two digits of the year and
    ddd
    is the day. The time is in
    hh:mm
    form, where
    hh
    is hours based on a 24-hour clock and
    mm
    is minutes.
  • CV SYSTEM START/INTERVAL START/TO
    Specifies the actual time period for the report generated. If the USE 'SREPORT 000' parameter does not specify a time range, CV SYSTEM START/INTERVAL START and TO represent the time range for the entire input archive file or input file created by SREPORT 099. When the input file contains cumulative statistics, the CV SYSTEM START date and time will be displayed. When the input file contains interval based statistics, the INTERVAL START date and time will be displayed.
  • CV JOB NAME
    Specifies the starting job name of Central Version which collected the statistics.
  • CV NUMBER
    Specifies the number of Central Version which collected the statistics.
  • TASK
    Specifies the task identifier that is used at run time by a terminal operator or program to invoke the task. A task is the basic unit of work under DC/UCF. It consists of a main program and one or more additional programs. A task is identified to the system by a unique name (such as OLM) that is usually identical to the task code used by the teleprocessing system.
  • TIMES INVOKED
    Specifies the number of times the task was invoked for the session.
SREPORT 013 - IDMS DC Program Summary
SREPORT 013, the IDMS DC Program Summary report, summarizes systemwide program statistics. System administrators can use SREPORT 013 to monitor program activity relative to available storage.
Available Program Pools
A program can be assigned to any one of the following pools:
  • 24-bit program pool
  • 24-bit reentrant pool
  • 31-bit program pool (Extended addressing only)
  • 31-bit reentrant pool (Extended addressing only)
A program can be put into both a 24-bit pool and a 31-bit pool depending on the LOC= parameter used to invoke the task.
The following figure shows one page of a sample IDMS DC Program Summary report:
Sample SREPORT 013
:
REPORT NO. 13 IDMS-DC PROGRAM SUMMARY Rnn.n mm/dd/yy PAGE 40 SELECTED FROM: yyddd hh:mm TO: yyddd hh:mm CV SYSTEM START: yyddd hh:mm TO: yyddd hh:mm CV JOB NAME: jobname CV NUMBER: nnn PROGRAM PGM TIMES TIMES RATIO OF TIMES TIMES NAME VER DICTNAME DICTNODE CALLED LOADED CALLED/LOADED WAITED CHECKED RHDCWAIT 1 0 1 0.0000 RHDCWTL 1 0 1 0.0000 RM000121 1 ASFDICT 1 1 1.0000 RM000122 1 ASFDICT 1 1 1.0000 RM000123 1 ASFDICT 1 1 1.0000 RM000124 1 ASFDICT 18 4 4.5000 RU000121 1 ASFDICT 3 3 1.0000 RU000122 1 ASFDICT 3 3 1.0000 RU000123 1 ASFDICT 3 3 1.0000 RU000124 1 ASFDICT 20 8 2.5000 TSTDNWKA 1 42 1 42.0000 TSTDNWKS 1 2 1 2.0000 UMBRMAP 1 0 0 0.0000 UMBRMAPE 1 0 0 0.0000 XASFNWKS 1 1 1 1.0000 TOTALS 1,458 181 8.0552 0 0
Field Descriptions
A description of the fields in the IDMS DC Program Summary report follows:
  • SELECTED FROM/TO
    Specifies the time period specified on the USE 'SREPORT 000' parameter where SELECTED FROM specifies the beginning date and time and SELECTED TO specifies the ending date and time. The date is in Julian form,
    yyddd
    , where
    yy
    is the last two digits of the year and
    ddd
    is the day. The time is in
    hh:mm
    form, where
    hh
    is hours based on a 24-hour clock and
    mm
    is minutes.
  • CV SYSTEM START/INTERVAL START/TO
    Specifies the actual time period for the report generated. If the USE 'SREPORT 000' parameter does not specify a time range, CV SYSTEM START/INTERVAL START and TO represent the time range for the entire input archive file or input file created by SREPORT 099. When the input file contains cumulative statistics, the CV SYSTEM START date and time will be displayed. When the input file contains interval based statistics, the INTERVAL START date and time will be displayed.
  • CV JOB NAME
    Specifies the starting job name of Central Version which collected the statistics.
  • CV NUMBER
    Specifies the number of Central Version which collected the statistics.
  • PROGRAM NAME
    Specifies the name of the program load module.
  • PGM VER
    Indicates the version number associated with the named program.
  • DICTNAME
    Names the dictionary in which the program resides.
  • DICTNODE
    Names the DC/UCF system that controls the dictionary in which the program resides.
  • TIMES CALLED
    Indicates the number of times the program was called.
  • TIMES LOADED
    Indicates the number of times the program was loaded from disk to a pool.
    Interpretation: The ratio of TIMES CALLED to TIMES LOADED measures the effectiveness of the program pool size. The higher the ratio the better. A low ratio for a frequently called program indicates that the size of the program pool should be enlarged or that the program should be made resident, reentrant, or reusable.
  • RATIO OF CALLED/LOADED
    Measures the effectiveness of the program pool size. The higher the ratio the better. A low ratio for a frequently called program indicates that the size of the program pool should be enlarged or that the program should be made resident, reentrant, or reusable.
  • TIMES WAITED
    Indicates the number of times the program waited to be loaded.
  • TIMES CHECKED
    Indicates the number of program check errors that occurred.
SREPORT 014 - IDMS DC Queue Summary
SREPORT 014, the IDMS DC Queue Summary report, summarizes systemwide queue statistics. System administrators can use SREPORT 014 to monitor queue activity.
Sample SREPORT 014
:
REPORT NO. 14 IDMS-DC QUEUE SUMMARY Rnn.n mm/dd/yy PAGE 1 SELECTED FROM: yyddd hh:mm TO: yyddd hh:mm CV SYSTEM START: yyddd hh:mm TO: yyddd hh:mm CV JOB NAME: jobname CV NUMBER: nnn QUEUE NAME TIMES AUTOTASK STARTED OLQQNOTE 0 TOTAL 0
Field Descriptions
A description of the fields in the IDMS DC Queue Summary report follows:
  • SELECTED FROM/TO
    Specifies the time period specified on the USE 'SREPORT 000' parameter where SELECTED FROM specifies the beginning date and time and SELECTED TO specifies the ending date and time. The date is in Julian form,
    yyddd
    , where
    yy
    is the last two digits of the year and
    ddd
    is the day. The time is in
    hh:mm
    form, where
    hh
    is hours based on a 24-hour clock and
    mm
    is minutes.
  • CV SYSTEM START/INTERVAL START/TO
    Specifies the actual time period for the report generated. If the USE 'SREPORT 000' parameter does not specify a time range, CV SYSTEM START/INTERVAL START and TO represent the time range for the entire input archive file or input file created by SREPORT 099. When the input file contains cumulative statistics, the CV SYSTEM START date and time will be displayed. When the input file contains interval based statistics, the INTERVAL START date and time will be displayed.
  • CV JOB NAME
    Specifies the starting job name of Central Version which collected the statistics.
  • CV NUMBER
    Specifies the number of Central Version which collected the statistics.
  • QUEUE NAME
    Specifies the queue identifier. A queue is a database work area shared by tasks on all DC/UCF terminals and by batch programs. Queue records can be transferred between tasks or applications or from one terminal to another.
  • TIMES AUTOTASK STARTED
    Indicates the number of times each queue's associated task was invoked to process queue records. If the value is consistently zero, review the threshold level assigned in the THRESHOLD IS clause of the QUEUE system generation statement; For more information, see the
    CA IDMS Administrating section
    .
SREPORT 015 - IDMS DC Line Summary
SREPORT 015, the IDMS DC Line Summary report, summarizes systemwide line statistics. Systems administrators can use SREPORT 015 to monitor the quality of lines in the system.
Sample SREPORT 015
:
REPORT NO. 15 IDMS-DC LINE SUMMARY Rnn.n mm/dd/yy PAGE 1 SELECTED FROM: yyddd hh:mm TO: yyddd hh:mm CV SYSTEM START: yyddd hh:mm TO: yyddd hh:mm CV JOB NAME: jobname CV NUMBER: nnn LINE READ WRITE NAME READS WRITES ERRORS ERRORS CONSOLE 0 0 CTCQA10 0 0 CTCQA21 0 0 CTCQA35 0 0 JESRDR 0 0 S3270Q1 0 0 UCFLINE 0 0 VTAM91 0 0 TOTALS 0 0 0 0
Field Descriptions
A description of the fields in the IDMS DC Line Summary report follows:
  • SELECTED FROM/TO
    Specifies the time period specified on the USE 'SREPORT 000' parameter where SELECTED FROM specifies the beginning date and time and SELECTED TO specifies the ending date and time. The date is in Julian form,
    yyddd
    , where
    yy
    is the last two digits of the year and
    ddd
    is the day. The time is in
    hh:mm
    form, where
    hh
    is hours based on a 24-hour clock and
    mm
    is minutes.
  • CV SYSTEM START/INTERVAL START/TO
    Specifies the actual time period for the report generated. If the USE 'SREPORT 000' parameter does not specify a time range, CV SYSTEM START/INTERVAL START and TO represent the time range for the entire input archive file or input file created by SREPORT 099. When the input file contains cumulative statistics, the CV SYSTEM START date and time will be displayed. When the input file contains interval based statistics, the INTERVAL START date and time will be displayed.
  • CV JOB NAME
    Specifies the starting job name of Central Version which collected the statistics.
  • CV NUMBER
    Specifies the number of Central Version which collected the statistics.
  • LINE NAME
    Specifies the line identifier. A line is a system component that defines the method of communication for physical terminals that use the same access method.
  • READS
    Indicates the number of reads performed for each line.
  • WRITES
    Indicates the number of writes performed for each line.
  • READ ERRORS
    Indicates the number of read errors that occurred for each line. A large value indicates problems in the line.
  • WRITE ERRORS
    Indicates the number of write errors that occurred for each line. A large value indicates problems in the line.
SREPORT 016 - IDMS DC Physical Terminal Summary
SREPORT 016, the IDMS DC Physical Terminal Summary report, summarizes system wide line statistics.
Sample SREPORT 016
:
REPORT NO. 16 IDMS-DC PHYSICAL TERMINAL SUMMARY Rnn.n mm/dd/yy PAGE 2 SELECTED FROM: yyddd hh:mm TO: yyddd hh:mm CV SYSTEM START: yyddd hh:mm TO: yyddd hh:mm CV JOB NAME: jobname CV NUMBER: nnn CUMULATIVE AVERAGE PHYSICAL READ WRITE RESPONSE RESPONSE CUMULATIVE TERMINAL READS WRITES ERRORS ERRORS RESPONSES TIME TIME I/O TIME VP91007 0 0 0 0.0000 0.0000 0.0000 VP91008 0 0 0 0.0000 0.0000 0.0000 VP91009 0 0 0 0.0000 0.0000 0.0000 VP91010 0 0 0 0.0000 0.0000 0.0000 VP91011 0 0 0 0.0000 0.0000 0.0000 VP91012 0 0 0 0.0000 0.0000 0.0000 VP91013 0 0 0 0.0000 0.0000 0.0000 VP91014 0 0 0 0.0000 0.0000 0.0000 VP91015 0 0 0 0.0000 0.0000 0.0000 TOTALS 312 238 0 0 0
Field Descriptions
A description of the fields in the IDMS DC Physical Terminal Summary report follows:
  • SELECTED FROM/TO
    Specifies the time period specified on the USE 'SREPORT 000' parameter where SELECTED FROM specifies the beginning date and time and SELECTED TO specifies the ending date and time. The date is in Julian form,
    yyddd
    , where
    yy
    is the last two digits of the year and
    ddd
    is the day. The time is in
    hh:mm
    form, where
    hh
    is hours based on a 24-hour clock and
    mm
    is minutes.
  • CV SYSTEM START/INTERVAL START/TO
    Specifies the actual time period for the report generated. If the USE 'SREPORT 000' parameter does not specify a time range, CV SYSTEM START/INTERVAL START and TO represent the time range for the entire input archive file or input file created by SREPORT 099. When the input file contains cumulative statistics, the CV SYSTEM START date and time will be displayed. When the input file contains interval based statistics, the INTERVAL START date and time will be displayed.
  • CV JOB NAME
    Specifies the starting job name of Central Version which collected the statistics.
  • CV NUMBER
    Specifies the number of Central Version which collected the statistics.
  • PHYSICAL TERMINAL
    Specifies the physical terminal identifier. A physical terminal is a physical device such as a CRT (3270-type device), TTY, or printer that exists within a teleprocessing system.
  • READS
    Indicates the number of reads performed for each physical terminal.
  • WRITES
    Indicates the number of writes performed for each physical terminal.
  • READ ERRORS
    Indicates the number of read errors that occurred for each physical terminal.
  • WRITE ERRORS
    Indicates the number of write errors that occurred for each physical terminal.
  • RESPONSES
    Indicates the number of physical terminal responses. A response begins when a physical terminal issues a read request and ends when the next read request is issued.
  • CUMULATIVE RESPONSE TIME
    Indicates the cumulative response time, in hundredths of a second, for the physical terminal. Response time is the total non-I/O time measured from the one read request to the next.
  • AVERAGE RESPONSE TIME
    Specifies the ratio of CUMULATIVE RESPONSE TIME to RESPONSES. Systems administrators can monitor this value to determine the impact of system configuration changes upon response time.
  • CUMULATIVE I/O TIME
    Specifies the cumulative I/O time, in hundredths of a second, for the physical terminal.