DFHPROG owns the following performance class data fields:
Note these points about remote transactions:
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).
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 |
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.
For detailed information on the CICS user-replaceable modules, see the CICS Customization Guide.
For more information, see Program load time.