DFHPROG fields

DFHPROG owns the following performance class data fields:

055 (Type-A, PCLINKCT, 4 bytes)
The number of program LINK requests issued by the user task.
056 (Type-A, PCXCTLCT, 4 bytes)
The number of program XCTL requests issued by the user task.
057 (Type-A, PCLOADCT, 4 bytes)
The number of program LOAD requests issued by the user task.
071 (Type-C, PGMNAME, 8 bytes)
The name of the initial application program invoked at transaction attach.

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.

Byte 4 of the transaction flags field, TRANFLAG (owner: DFHTASK, field ID: 164) can also be used to provide additional detail on the transaction's origin. See DFHTASK fields for more details on the transaction origin type.

Table 1 shows the transaction type values from byte 1 of the transaction flags field, TRANFLAG (owner: DFHTASK, field ID: 164) and its relationship with the transaction routing sysid field, RSYSID (owner: DFHCICS, field ID: 130) and the initial program name field, PGMNAME (owner: DFHPROG, field ID: 071).

Table 1. Transaction routing sysid and initial program name relationships
TRANFLAG (Byte 1) RSYSID Program Name
X'00' - User transaction 'xxxx' N/A
X'00' - User transaction null Initial application program
X'80' - System transaction N/A Initial application program
X'40' - Mirror transaction N/A Mirror program
X'20' - DPL mirror transaction N/A Initial application program
X'10' - ONC RPC alias transaction N/A Initial application program
X'08' - WEB alias transaction N/A Initial application program
X'04' - 3270 bridge transaction N/A Initial application program
X'01' - CICS BTS run transaction N/A Initial application program
072 (Type-A, PCLURMCT, 4 bytes)
The number of program LINK URM (user-replaceable module) requests issued by the user task.

A user-replaceable module is a CICS-supplied program that is always invoked 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 you can replace it with a version that you write yourself.

The CICS-supplied user-replaceable modules are:
  • bridge exit program - DFH0CBRE, DFH0CBAE, DFHWBLT, or user specified
  • CICS JVM interface program - DFHJVMAT
  • distributed dynamic routing program - DFHDSRP (or user specified)
  • document template exit program - user specified on the DOCTEMPLATE resource definition
  • dynamic routing program - DFHDYP (or user specified)
  • Internet Inter-ORB Protocol (IIOP) inbound request security exit program - DFHXOPUS
  • Java hot-pooling pre-call program - DFHJHPAT
  • node error program - DFHNEP
  • program autoinstall program - DFHPGAxX (or user specified)
  • program error program - DFHPEP
  • terminal autoinstall programs - DFHZATDX/DFHZATDY
  • terminal error program - DFHTEP
  • transaction restart program - DFHRTY
  • CICS-DBCTL interface status program - DFHDBUEX
  • CICS-DB2 dynamic plan exit program - DSNCUEXT
  • Enterprise JavaBeans (EJB) Distinguished Name program - DFHEJDNx
  • Enterprise JavaBeans (EJB) event program - DFHEJEP

For detailed information on the CICS user-replaceable modules, see the CICS Customization Guide.

073 (Type-A, PCDPLCT, 4 bytes)
The number of distributed program link (DPL) requests issued by the user task.
113 (Type-C, ABCODEO, 4 bytes)
If the transaction abends, this field contains the 4 character abend code of the original abend.
114 (Type-C, ABCODEC, 4 bytes)
If the transaction abends, this field contains the 4 character abend code of the current abend.
115 (Type-S, PCLOADTM, 8 bytes)
The total elapsed time in which the user task waited for program fetches from the DFHRPL program library. Only fetches for programs with installed program definitions or autoinstalled as a result of application program requests are included in this figure. Installed programs residing in the LPA are not included because they do not incur a physical fetch from a program library.

For more information, see 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, with the CHANNEL option, issued 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 the distributed program link (DPL) RETURN requests, with the CHANNEL option, 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 requests, with the CHANNEL option, issued by the user task. Note: This field is a subset of the program LINK requests field, PCLINKCT (055).
307 (Type-A, PCXCLCCT, 4 bytes)
Number of program XCTL requests, with the CHANNEL option, issued by the user task. Note: 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, with the CHANNEL option, issued by the user task. Note: 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.