Adding support for Debug Profile Service and APIs

Debug Profile Service is a REST API that uses the HTTP protocol to provide RESTful access to a set of resources related to debug profiles. It provides POST/GET/ PUT/DELETE methods to handle the creation, retrieval, updating, and deleting of debug profiles.

To enable all the features in the z/OS Debugger Profiles view with Eclipse, you need to install, configure and start z/OS Explorer V3.1.1.23 or later and Debug Profile Service.

For CICS, also see the instructions in Activating the TCP/IP Socket Interface for CICS and Adding support for the DTCN profiles APIs and views.

The Debug Profile Service API is similar to the DTCN API, except that it also handles batch, IMS, Db2® stored procedure profiles stored in EQAUOPTS data sets.

The Debug Profile Service API handles accessing profiles differently between CICS® and non-CICS.

For CICS, user debug profiles are stored in a repository that is owned by the region. The repository can either be a CICS temporary storage queue (TSQ), or a VSAM data set allocated to DD:EQADPFMB. In either case, the Debug Profile Service API acts as a client, relaying the HTTP request to the DTCN API to handle.

For non-CICS, debug profiles are stored in EQAUOPTS data sets. The Debug Profile Service API manipulates the data sets directly, and therefore needs to be running on the z/OS® host. Also, proper RACF® setup is required during the API installation to allow for authentication and data set authorization that use SAF/RACF.

For the API documentation, see z/OS Debug Profile Service API.