Data contained in relevant IMS monitor reports

This topic shows you what data you can find in the IMS monitor reports that apply to DBCTL.

General wait time events

All threads built for a CICS® system have the same job name as that CICS system. They are shown in the jobnames for regions in the General reports.

General reports

The general reports include the Regions and jobname report and the Region summary report.

Regions and jobname report

Within a trace interval, a thread can be assigned to multiple CICS systems but it can only be assigned to one CICS at any one time.

Depending on the number of CICS systems connected to DBCTL, the regions and jobname report can show:
  • One region with only one jobname.
  • One region with multiple jobnames.
  • Multiple regions with multiple jobnames where some regions have the same jobname, and some have multiple jobnames.
  • Multiple regions with only one jobname.

Any monitor report for a region is a summary for all connected CICS systems that a thread has served during the trace interval. For example, the elapsed time of schedule end to first call means the sum of this elapsed time for all CICS systems that a thread has been assigned to during the trace interval.

Depending on the workload of a CICS system, a trace interval may be a relatively short period of time, and thread switching between depending regions may not occur very often. However, the more the workload fluctuates, the more frequently threads are likely to be assigned among connected CICS systems.

Region summary report

A region summary report can include the following information about DBCTL:
  • Scheduling and termination, including:
    • The time from PSB schedule request being received by DBCTL to when the request is completed by DBCTL. This includes the time spent by DBCTL allocating IMS resources and does not include any schedule time spent in CICS or being processed by the DRA.
    • The time from when a PSB unschedule request is received by DBCTL to when the request is completed by DBCTL. This request could be an unschedule PSB request, or a request embedded in any synchronization type terminate request, or a terminate thread request.
  • Schedule to first call is the time from when DBCTL completed the PSB schedule to when DBCTL received the first DL/I request. This time includes all time spent processing in CICS, including application program, CICS itself, and DRA processing. (Because CICS is the transaction manager, how and when its own applications are loaded or scheduled cannot be interpreted by DBCTL in the IMS monitor reports.)
  • Elapsed execution is the time between the completion of the DBCTL PSB schedule request and when DBCTL receives the PSB unschedule request. It indicates the amount of time IMS resources were allocated to a CICS thread.
  • Region occupancy is the ratio of the elapsed time when a thread is active (that is, with IMS resources allocated) to the trace interval.
  • DL/I calls is the time between DBCTL receiving the DL/I request and the request being completed in DBCTL.

Program summary

DBCTL does not process any messages. For the purpose of using the DC monitor report, it counts each PSB schedule as one message dequeued. Because DBCTL is not the transaction manager, it must assume a one-to-one relation between a CICS transaction and a PSB schedule. This relationship is shown in program summary, where the number of transactions dequeued is the same as the number of scheduled requests. Per transaction means requests per schedule, and elapsed time per transaction means elapsed time per schedule.

Run profile

In run profile, the number of messages dequeued means the number of scheduled PSBs and transactions per second means PSB schedules per second.

Transaction queuing report

The transaction queuing report can include a list of transactions for DBCTL. Each transaction name is an 8-byte transaction ID specified by CICS on the schedule request. A transaction ID from CICS consists of a 4 byte CICS transaction name, plus a 4 byte CICS identifier. If CICS does not specify a transaction ID, DBCTL takes the CICS region ID, obtained at connection time. In this report, for DBCTL, the transaction number dequeued means number of PSB schedules. The on queue when scheduled in this report is always zero because the IMS message queues do not apply to DBCTL.

For examples of IMS monitor reports and detailed guidance on interpreting their contents, see Database utilities in IMS product documentation.