A fix is available
APAR status
Closed as program error.
Error description
When processing a transient data deleteq, DFHTDA has to read in each CI used to hold records on the queue to be able to find out the number of the next CI used to hold the next range of records. A large queue can have a great many CIs and so the deleteq process can take a long time. It would help service to be able to see how big the queue had been and how many CIs it had used if they investigate a problem midway through a deleteq operation. DFHTDA could preserve some key DCT values into its lifo before beginning to read in and release the CIs used in the queue.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS Users. * **************************************************************** * PROBLEM DESCRIPTION: A number of the Transient Data Queue * * Entries (DCTE) are reset during deleteq * * processing. These fields would be * * useful during diagnosis of a problem. * **************************************************************** When a DELETEQ is issued against a Transient Data Queue the following fields from the DCTE are reset. * tddct_current_cis * tddct_committed_numelems * tddct_committed_start_rba * tddct_committed_read_rba * tddct_committed_write_rba However if a problem occurs during the processing of the delete, being able to refer to the previous values would be helpful. This serviceability APAR has been raised to resolve this.
Problem conclusion
DFHTDB and DFHTDRM have both been altered to save the five DCTE fields into LIFO before they are reset. The fields will be saved for DELETEQ processing and when processing a READQ request that will result in a QZERO for both non-recoverable and physically recoverable TDQueues. The fields will also be saved for all SYNCPOINT requests for logically recoverable TDQueues.
Temporary fix
Comments
APAR Information
APAR number
PI78313
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-03-16
Closed date
2018-06-27
Last modified date
2018-08-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI56884 UI56885 UI56886 UI56887
Modules/Macros
DFHTDB DFHTDRM
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R000 PSY UI56887
UP18/06/28 P F806
R100 PSY UI56886
UP18/06/28 P F806
R800 PSY UI56884
UP18/06/28 P F806
R900 PSY UI56885
UP18/07/06 P F807
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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 August 2018