Performance data in group DFHPROG

Descriptions of the performance data fields in the DFHPROG group, including the numeric identifer, type, and size of each field.

055 (TYPE-A, 'PCLINKCT', 4 BYTES)
Number of program LINK and INVOKE APPLICATION requests issued by the user task, including the link to the first program of the user task. This field does not include program LINK URM (user-replaceable module) requests.
056 (TYPE-A, 'PCXCTLCT', 4 BYTES)
Number of program XCTL requests issued by the user task.
057 (TYPE-A, 'PCLOADCT', 4 BYTES)
Number of program LOAD requests issued by the user task.
071 (TYPE-C, 'PGMNAME', 8 BYTES)
The name of the first program called at transaction attach-time.
Note these points about remote transactions:
  • If the CICS® definition of the remote transaction does not specify a program name, this field contains blanks.
  • If the CICS definition of the remote transaction specifies a program name, this field contains the name of the specified program. (This program is not necessarily the program that is run on the remote system.)

For a dynamically routed transaction, if the dynamic transaction routing program routes the transaction locally and specifies an alternative program name, this field contains the name of the alternative program.

For a dynamic program link (DPL) mirror transaction, this field contains the initial program name specified in the dynamic program LINK request. DPL mirror transactions can be identified using byte 1 of the transaction flags, TRANFLAG (164), field.

For web service applications, this field contains the target application program name.

For a web alias transaction, this field contains the initial application program name called by the alias transaction. Web alias transactions can be identified using byte 1 of the transaction flags, TRANFLAG (164), field.

For an ONC RPC transaction, this field contains the initial application program name called by the alias transaction. ONC RPC transactions can be identified using byte 1 of the transaction flags, TRANFLAG (164), field.

For an ECI over TCP/IP transaction, this field contains the name of the application program specified in the External Call Interface (ECI) request from the client application.

072 (TYPE-A, 'PCLURMCT', 4 BYTES)
Number of program LINK URM (user-replaceable module) requests issued by, or on behalf of, the user task.

A user-replaceable module (or user-replaceable program) is a CICS-supplied program that is always called at a particular point in CICS processing, as if it were part of the CICS code. You can modify the supplied program by including your own logic, or replace it with a version that you write yourself.

The user-replaceable programs are described in Customizing with user-replaceable programs.

073 (TYPE-A, 'PCDPLCT', 4 BYTES)
Number of distributed program link (DPL) requests issued by the user task.

For a breakdown by program name and system identifier (sysid) of the individual distributed program link (DPL) requests, you can request transaction resource monitoring. For more details, see Transaction resource class data: Listing of data fields.

113 (TYPE-C, 'ABCODEO', 4 BYTES)
Original abend code.
114 (TYPE-C, 'ABCODEC', 4 BYTES)
Current abend code.
115 (TYPE-S, 'PCLOADTM', 12 BYTES)
Elapsed time in which the user task waited for fetches from DFHRPL or dynamic LIBRARY concatenations. Only fetches for programs with installed program definitions or autoinstalled as a result of application requests are included in this figure. However, installed programs in the LPA are not included (because they do not incur a physical fetch from a library). For more information about program load time, see Clocks and time stamps, and Program load time.
286 (TYPE-A, 'PCDLCSDL', 4 BYTES)
The total length, in bytes, of the data in the containers of all the distributed program link (DPL) requests issued with the CHANNEL option by the user task. This total includes the length of any headers to the data.
287 (TYPE-A, 'PCDLCRDL', 4 BYTES)
The total length, in bytes, of the data in the containers of all DPL RETURN CHANNEL commands issued by the user task. This total includes the length of any headers to the data.
306 (TYPE-A, 'PCLNKCCT', 4 BYTES)
Number of local program LINK and INVOKE APPLICATION requests, with the CHANNEL option, issued by the user task.
This field is a subset of the program LINK and INVOKE APPLICATION requests field, PCLINKCT (055).
307 (TYPE-A, 'PCXCLCCT', 4 BYTES)
Number of program XCTL requests issued with the CHANNEL option by the user task.
This field is a subset of the program XCTL requests field, PCXCTLCT (056).
308 (TYPE-A, 'PCDPLCCT', 4 BYTES)
Number of program distributed program link (DPL) requests issued with the CHANNEL option by the user task.
This field is a subset of the distributed program link requests field, PCDPLCT (073).
309 (TYPE-A, 'PCRTNCCT', 4 BYTES)
Number of remote pseudoconversational RETURN requests, with the CHANNEL option, issued by the user task.
310 (TYPE-A, 'PCRTNCDL', 4 BYTES)
The total length, in bytes, of the data in the containers of all the remote pseudoconversational RETURN CHANNEL commands issued by the user task. This total includes the length of any headers to the data.

Abends that might not produce a transaction dump

Due to the circumstances under which transactions are called, a transaction dump might not be taken when the following abends occur:

  • ASPF
  • ASPN
  • ASPO
  • ASPP
  • ASPQ
  • ASPR
  • ASP1
  • ASP2
  • ASP3
  • ASP7
  • ASP8