Customised Gen server TIRDATX for CICS system date not shown in client application

Products

• Gen
• Gen - Host Encyclopedia
• Gen - Run Time Distributed
• Gen - Workstation Toolset

Issue/Introduction

In our Gen 8.5 server we have a customised user exit TIRDATX to use the CICS system date and when we upgraded to Gen 8.6, we retrofitted the changes into the Gen 8.6 TIRDATX exit. 
We have tested modifying the system date in CICS using CECI i.e. WRITEQ TS QUEUE(DATE) FROM(YYYY/MM/DD)
Then we see the system date is getting changed. 
However, in the 8.6 client application, we are still seeing the current date instead of modified CICS system date. 

Environment

Release : 8.6

Component : Gen Run Time, Blockmode or Cooperative Server.

Resolution

The following changes are required to the 8.6 TIRDATX to resolve the problem:

1. Differences were found after comparing customised 8.5 & 8.6 versions and 8.6 version requires these changes:
a. PACKDATE and PUTDATE need to be uncommented.
b. Uncomment this line (after .TERM1 label under comments "START OF CICS SAMPLE 'DATE CARD' CODE"):
EXEC  CICS POP HANDLE 

2. Change the default 8.6 TIRDATX as follows:
CHANGE: CEETERM RC=R7
TO: CEETERM RC=(R7)
NOTE: This change will be incorporated into a future PTF.

See attached word document for full version.
NOTE: In the word document some areas of the code have been marked in blue to indicate what additional areas need to be uncommented in column 1.
Lines "BAL   R14,GETDATE", "BAL   R14,PACKDATE" and "BAL   R14,PUTDATE" cause GETDATE, PACKDATE and PUTDATE to be executed respectively.
However, PACKDATE and PUTDATE had not been uncommented and they need to be.
(There is no line to branch to PUTTIME so that code never gets executed.)

Additional Information

z/OS User Exits
TIRDATX - Date and Time Services Exit