Using the Bundl DPMS967 - TSO Report Access Logging Exit

Products

• Bundl

Issue/Introduction

What is required to activate the TSO Report Logging Exit, DPMS967?

After assembling and binding the DPMS967 module into the Bundl load library, the exit is not being called.

Adding the DPMS967 module to a Bundl load library in the link list does not help either.

Environment

Release : 5.0

Cause

The DPMS967 exit was not installed correctly.

Resolution

The DPMS967 exit is NOT a stand alone load module that you put in the Bundl load library. It must be installed as a USERMOD via SMP/E, using the supplied CC50967 job, which can be found in the Bundl installed SAMPJCL library.

DPMS967 is just a CSECT and SMP/E will take care of linking it up with the appropriate load modules that will call the exit. As stated in the comment in the sample source (SAMPT967) that is provided for the exit:

*  The DPMS967 exit is called for all end user report access actions.

As to how/when the exit is called, a determination is made if a DPMS967 csect exists in the load module. If it does, then a call is made to it.

After installing the exit as ++USERMOD(CC50967) via SMP/E using the supplied SAMPJCL library CC50967 job, move the updated load module code into a LINKLIST library, and perform an LLA REFRESH.

It is also recommended to log off of Bundl and then log back on again before testing the changes.

And make sure that whatever the Bundl access method is, the updated load module code is being executed by your logon protocol, from the appropriate library.

Additional Information

For more information on the available Bundl exits, see Chapter 7 in The Bundl Getting Started Guide.

A PDF version of the documentation is available at Bundl Documentation.