Functional entry to display system heap by token name

This is available with PJ44391 on z/TPF PUT13.

Using the Debugger in production is not a viable solution for us. We understand that a z command might not provide as much information/features as the Debugger option, but still require a z command.

The TPF Toolkit/Debugger has implemented a System Heap View feature in TPF Toolkit 4.2.5 and z/TPF APAR PJ42752. The system heap view allows you to enter a system heap token name with wild card and a list of matching entries is displayed. Upon selecting an entry, the memory contents are displayed with a memory rendering. The content can be rendered with various data renderings including XML as well as providing the other various features of the memory views. This solution provides substantially more features than a z command can. A screenshot can be viewed in the TPFUG presentation http://www-01.ibm.com/software/htp/tpf/tpfug/tgf16/TPFUG_2016_DEVP_TK_DBUG_UPDATES.pdf

If this solution is required for use in a production environment, risks of using the debugger in a production system can be mitigated. Generally speaking, you should not use the debugger in production since the application could be stopped while holding a lock and thereby significantly impact the system. However, the debugger can be used in an innocuous manner for using the system heap view. For example, the debugger could be used to debug CVZZ started by the ZTEST command resulting in no impact to the system. You can use ZDBUG access command to limit what actions are allowed by the debug server. And you can use the CDBPUX_ShouldProcessingOccurForThisTraceEntry user exit in cdbpux.c to limit debugger registration by workstation IP address, workstation name, program mask, a special/secret user token and/or etc. For example, you could use ZDBUG ACCESS to turn off all features except ZDBUG ACCESS DBUG. You could then modify the CDBPUX_ShouldProcessingOccurForThisTraceEntry user exit in cdbpux.c to limit debugger registration program mask CVZZ. If desired, you could insert further protections using the CP user exits UCCDBTS and UCCDBTA to prevent the debugger from starting the debugger for an ECB where the ZTEST command text in EBW000 contains any parameters. Some z/TPF customers are using the dump viewer in production environments today. In this way, the debugger system heap view can be safely used in a production environment if necessary.

Does the System Heap View feature satisfy this request?

Additional use case/business justification - PJ43375 addressed a problem mounting a tape because the previous device buffer (allocated in system heap using a unique token) had not been released. The initial problem would have been much easier to diagnose had we been able to display system heap by token name – we could have immediately seen that yes the system heap buffer was indeed there.
This is a ZDCOR using different criteria to identify what to display.

Additional use case/business justification - PJ43375 addressed a problem mounting a tape because the previous device buffer (allocated in system heap using a unique token) had not been released. The initial problem would have been much easier to diagnose had we been able to display system heap by token name – we could have immediately seen that yes the system heap buffer was indeed there.
This is a ZDCOR using different criteria to identify what to display.

IBM requires some additional information in order to evaluate this request.
Please provide an example of how this would be used (especially how it would help diagnose an SSL new error).