Help

 

IMS Tab

The Strobe Advisor IMS report displays the Activity by DL/I Request report identified by the CPU time and run time spent in wait by the transaction, module, section, and PSB name that initiated a request for IMS DL/I services. It also provides detailed information for each DL/I call and its parameter list within a transaction, module, section, and PSB.

Strobe advisor only produces the advisor reports for IMS MPRs because they are the only ones that have transactions. Note that DLBs and BMPs do not have transactions.

You can create a note for this particular report and profile by simply clicking at the top of the page. The note created is exclusive to this report and can only be accessed from this report and profile. Other users can edit the note.

The report provides a total DL/I execution count.

Click on a Transaction ribbon to view the Activity by DL/I Request report.

Report details

  • Transaction identifies the CICS or IMS transaction responsible for activity within a particular module, section, and Program Specification Block.

  • Module shows the name of the DL/I application used by the transaction responsible for the DL/I requests showing CPU activity.

  • Section identifies the control section within the module responsible for DL/I requests showing CPU activity.

Note: For all module or section names that exceed eight characters, Strobe generates a token, which is an eight-byte identifier. The token comprises the first four characters of the module or section name followed by a hyphen (-) and then the last three characters of the name. Refer to the Token Long Name Cross Reference report to reconcile all tokens with their long names.

  • PSB identifies the Program Specification Block that the active module used.

  • DL/I Execution Count identifies the execution count.

  • DL/I Avg Service Time (sec) identifies the average service time.

  • Total CPU % shows the percentage of CPU time used by a module or DL/I request in a transaction as a percentage of all CPU time used by programs executed in the measured job step.

  • Wait % shows the percentage of wait time used by a module or DL/I request in a transaction as a percentage of all wait time used by programs executed in the measured job step.

Click  next to the Transaction to view additional detail about it:

  • Line Number shows the application line number associated with the DL/I request, if the module was indexed. Otherwise, the field is blank.

  • Procedure Name shows the procedure name associated with the DL/I request, if the module was indexed. Otherwise, the field is blank.

  • Request Location shows the location of the DL/I request within the application program, in hexadecimal notation.

  • DL/I Function identifies the DL/I function being requested. [MORE]

  • SSA ( Segment Search Argument) shows:

    • for Segment Search Arguments, the segment name, optionally followed by a command code, field name specification, relational operator, and a question mark to represent the remainder of the expression

    • for Field Search Arguments, the key or search field name, optionally followed by a command code, field name specification, relational operator, and a question mark to represent the remainder of the expression.

  • PCB Type shows the type of Program Control Block (PCB) referenced by the current DL/I request. Values are as follows:

    • I/O for IOPCB I/O Program Control Blocks

    • DB for DBPCB Database Program Control Blocks

    • ALT for Alternate Program Control Blocks

  • PCB Name/Label shows the name or Label of the Program Communication Block referenced in the DL/I request.

  • Resource Name shows the IMS resource used to execute the DL/I request. The type of resource depends on the PCB type, as follows:

    • for Database PCBs, the resource is the Database Descriptor (DBD) name

    • for I/O PCBs, the resource is blank

    • for ALTERNATE PCBs, the resource is MODIFY for modifiable alternate PCBs, or the name of the fixed destination for non-modifiable alternate PCBs

    • Execution Count shows how many times the DL/I call executed.

    • Avg Service Time (sec) identifies the average service time, in seconds, for the transaction. Service time represents the time the transaction is being processed or awaiting processing within the region.

    • Total CPU % shows the percentage of CPU time used by a module or DL/I request in a transaction as a percentage of all CPU time used by programs executed in the measured job step.

    • Wait % Page shows the percentage of wait time used by a module or DL/I request in a transaction without concurrent CPU execution or other I/O activity.

    • Wait % Total shows the percentage of wait time used by a module or DL/I request in a transaction as a percentage of all wait time used by programs executed in the measured job step.

Analysis Tips

Examine the values in the Segment Search Argument column for the following considerations:

  • Does the application use the database design appropriately? For example, does it take advantage of existing secondary index fields, instead of using search fields?

  • Do the command codes take advantage of any pointers provided in the database design?

  • Are the relational operators appropriate? For example, using NOT EQUAL instead of a less resource-consumptive syntax can cause an extensive search of the database.