Mainframe Release Notes

Monthly PTF's have been made available for Dynatrace AppMon 7.0 mainframe components thru the cumulative monthly maintenance. Recommended for all users!

To download the cumulative PTF’s, JCL exists in the sample library created during the initial install (hilevel.LZDT70.SZDTSAMP). FTPMAINT and RFNMAINT facilitate downloads from a Dynatrace FTP server with RFNMAINT taking advantage of Receive from Network technology. Additional information can also be found at Download and SMP/E install of the z/OS Agent Components. If using RFNMAINT, please update your JCL with the hash contained in the RFNINSTL job in the aforementioned link.

Resolved and known issues

Date PTF What's Impacted Description
2017 May DTR010A DTAX JLT-188327 ‐ SOC4 in ZDTPLT when shutting down a system
  • Impact: Low, should only happen if VTAM is recycled.
  • Cause: When VTAM comes down, ZDTPLT is trying to refer to storage that is not available.
  • Solution: Added a condition to check if the pointer is null before using it.
2017 Jul DTR011A zDC JLT-190041 ‐ zLocal command line loses usetransactionsbuffers=true on restart
  • Impact: Medium, If transaction buffers and no zIIP option is used, a zLocal agent restart would stop using transaction buffers. Also, a USS file i/o error could cause excessive messages in the ZDC Joblog.
  • Cause: Programming error.
  • Solution: Correct code.
2017 Jul DTR012A zDC JLT-193261 - zIIP SRB is not released on zRemoteAgent bounce
  • Impact: Medium, in a zIIP enabled environment, the zLocal would have to be restarted after restarting the zRemote.
  • Cause: Programming error.
  • Solution: Correct code.
2017 Jul DTR013A ADK JLT-193348 ‐ Added new ADK functions for CICS and IMS to provide API’s to start and end program nodes in any transaction that is being traced.
  • Impact: None, PTF is an enhancement, not a fix.
  • Cause: NA
  • Solution: NA
2017 Jul DTR014A IMS Agent JLT-191517 ‐ IMS DB2 nodes not generated when the zDC is stopped prior to any DB2 activity and restarted subsequent to DB2 activity.
  • Impact: Medium, uncommon sequence of events that causes missing DB2 nodes.
  • Cause: The sensor install process failed if driven while the zDC was not available, and was only allowed to be driven once.
  • Solution: The sensor install process was modified to be re-driven until successful.
2017 Jul DTR016A zDC JLT-194199 ‐ DTR003A Old version of PTF released to customers.
  • Impact: Low, no customers have reported any issues.
  • Cause: Programming error.
  • Solution: Improved support from DTR003A and DTR012A by adding ZDC parms to control dispatch delay warning. This PTF supersedes DTR003A and DTR012A.
2017 Aug DTR018A zDC JLT-177280 ‐ Log message missing: zDC output and syslog should contain zLocalAgent connect messages.
  • Impact: NA
  • Cause: Customer requested zLocalAgent connect/disconnect/reconnect messages written to the zDC output and SYSLOG. Currently, this information is only written to the zLA logs.
  • Solution: Coding change.
2017 Aug DTR019A CICS Agent JLT-190112 ‐ SOAP program defined as remote causing possible issues.
  • Impact: Medium, Purepath timeouts if the initial program of a SOAP transaction is defined as REMOTE.
  • Cause: Non-local initial program.
  • Solution: Detect and correctly handle remote program definition.
2017 Aug DTR020A CICS Agent JLT-184501 ‐ Message spam in z/OS console.
  • Impact: Low, CICS is reporting an error when ZDTSOAPH tries to retrieve the HTTP headers from what CICS believes to be a non-Web application.
  • Cause: Requests for HTTP headers from pipeline messages that arrived over MQ transport returning response code INVREQ(16) with a RESP2 value of 1.
  • Solution: ZDTSOAPH was changed to ignore this combination instead of issuing an error message for each failing request.
2017 Aug DTR021A IMS Agent JLT-197047 ‐ IMS – MPR loop calling D2sensor after MQ start is done in region.
  • Impact: High, May cause a CPU limit reached in the IMS region.
  • Cause: The DB2 sensor code gets into a loop generating the same node repeatedly.
  • Solution: ZDTIDB00 changed to only enable the 2nd LIIB of the pair when enabling the DB2 sensor.
2017 Sep DTR022A IMS Agent JLT-196903 – IMS – Add optional Include/Exclude Transaction name lists to CTL region MQ sensor configuration.
  • Impact: None, PTF is an enhancement, not a fix.
  • Cause: NA
  • Solution: NA
2017 Sep DTR024A IMS Agent JLT-197853 – IMS – Agent ABEND retry needs to free internal process locks.
  • Impact: High, IMS agent may loop or become unusable if an ABEND occurs while holding a resource lock.
  • Cause: IMS agent ABEND retry does not free resource locks.
  • Solution: IMS agent ABEND retry routine was changed to free all locks.
2017 Sep DTR025A IMS Agent JLT-198821 – IMS – Agent S0C4 ABEND when issuing path table full message if called in AR mode.
  • Impact: Medium, results in a S0C4 ABEND and the IMS agent is disabled.
  • Cause: The code that issues the diagnostic message indicating that the path is full is not coded correctly for the AR mode caller.
  • Solution: Corrected code to handle AR mode caller.
2017 Oct DTR015A CICS Agent JLT-189671 – Abend ASRA when LE sensor is activated.
  • Impact: Medium, could cause an abend in the described situation.
  • Cause: When a PL1 program issues a FETCH/CALL to a COBOL program and passes the called program a parameter, an 0c4 may occur.
  • Solution: Improved interlanguage LE support.
2017 Oct DTR023A CICS Agent JLT-198319 – CICS ADK routine DTILA: extra byte is copied to the tag buffer
  • Impact: Low, may cause applications to send more data than required when using standard tags because they would send the entire buffer, not the actual length.
  • Cause: The DTILA and DTIALA ADK API’s left the tag buffer length in the second argument instead of changing it to the 30 byte length of the binary tag. Also, some API’s returned an additional byte beyond the tag.
  • Solution: Code changed to correct issues.
2017 Oct DTR026A IMS Agent JLT-198797 – IMS – DB2 sensor enabled by ZDCPCRT3 even if CONFIG wants it disabled
  • Impact: Low, will only occur if the DB2 sensor is disabled at the time that the first transaction to access DB2 is run in the MPR.
  • Cause: No check was being made to determine if the sensor should actually be enabled.
  • Solution: Changed the DB2 and MQ sensor install to not initially set the IBM code address in the LIIB to the DT code address; instead it will be zero until the hook is actually set.