A fix is available
APAR status
Closed as program error.
Error description
Improve DFHTRDUF description of DFHTRAP state at time of dump. There are two fields of interest in the TRA: TRA_TRAP_ACTIVE, which indicates the trap is active. TRA_TRAP_DISABLED, which indicates the trap is disabled. Sounds straightforward. However, once a trap fires, and sets TRAPDISA to disable it from being invoked on future trace calls, TRA_TRAP_DISABLED is set on but TRA_TRAP_ACTIVE remains on. Whether this is right or wrong, that's how things are. But, DFHTRDUF uses TRA_TRAP_ACTIVE (via dfhtrap_ind) for its message.
Local fix
Improve DFHTRDUF to issue a less misleading (more leading?) message depending on the combination of the two bits in the TR domain anchor block.
Problem summary
**************************************************************** * USERS AFFECTED: All CICS Users. * **************************************************************** * PROBLEM DESCRIPTION: When formatting a CICS dump using * * IPCS VERBX DFHPD720 'TR' there is no * * easy way to determine if DFHTRAP is * * enabled or disabled. * **************************************************************** When formatting a CICS dump using IPCS VERBX DFHPD720 'TR' text is displayed to show the Active/Inactive state of DFHTRAP, however there is no formatted text to indicate if the trap is enabled or disabled, or if it is unusable. If DFHTRAP is disabled or unusable then it is not in effect on the system regardless of the active state. It is useful to know the enabled/disabled and unusable state of the trap and the last time it was executed.
Problem conclusion
DFHTRDUF has been modified to display the time stamp indicating the last time that DFHTRAP was invoked. Text has also been added to display whether DFHTRAP has been marked 'usable' or 'unusable'. The ACTIVE state of the trap just tells us if there is a trap available to run. The DISABLED and UNUSABLE states of the trap are the parts that tell us if the trap will actually run or not. If either the DISABLED or UNUSABLE bits are on, then the TRAP will not run (even if the trap is ACTIVE). The CICS Transaction Server for z/OS V5.5 Data Areas manual will be updated to reflect the new 8 byte TRA_TRAP_LST_RUN field in the TRA at offset x'208'.
Temporary fix
Comments
APAR Information
APAR number
PH19847
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-12-03
Closed date
2020-03-31
Last modified date
2020-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI68711
Modules/Macros
DFHTRDUF DFHTRPT
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R200 PSY UI68711
UP20/04/02 P F004
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
04 May 2020