In the ISPF configuration
table keyword file, this exit is set with keyword ACTIVITY_MONITORING_PROGRAM_EXIT.
The
activity monitoring exits provide monitoring information for these
PDF functions:
- Primary commands invoked from BROWSE
- Primary commands invoked from EDIT
- Primary commands invoked from VIEW
- Edit macros invoked from EDIT
- Line commands invoked from EDIT
- Line commands invoked from VIEW
- Library/Data Set utility sub-functions
- Data Set List utility built-in line commands.
The activity monitoring exit
routine is given control at the start and end of each command or function.
Exit parameters
PDF uses these parameters
to communicate with the monitoring exit.
Table 1. Details of the parameters used to communicate
with the monitoring exitParameter |
Type |
Len |
Description |
Modifiable |
---|
EXIT ID |
FIXED |
4 |
Numeric code for the exit point. |
No |
COMMAND/ SUB-FUNCTION ADDRESS |
PTR |
4 |
Storage location containing the command name or
sub-function identifier. |
No |
COMMAND/ SUB-FUNCTION LENGTHS |
FIXED |
4 |
Length of the command name or sub-function identifier.
The value ranges from 1-255. |
No |
Usage notes
- Activity monitoring exits are the same for VIEW as for EDIT. From
within the VIEW function, the primary and line commands are monitored
exactly like they are from EDIT.
- A single exit routine is allowed for all monitoring PDF exit points.
The name of the module is placed into the ISPF configuration table
when the product is installed.
- 31-bit addressing must be supported by the exit routine as it
is given control in AMODE 31. ISPF/PDF does not restrict the RMODE
of the exit, but RMODE ANY is recommended.
- Standard OS linkage conventions are used to branch to the exit
routine that is defined.
- You can make PDF service calls from within the exit routine, with
the exception of those services that could cause recursion (for example,
calling the EDIT service for an EDIT primary command exit call).
- You cannot activate or deactivate the exit while an PDF session
is in progress. You can make changes to the exit routine load module
at any time, but because PDF loads the module only once at session
initialization, the changes are not recognized until the next ISPF
session.
- PDF does not provide data areas. You can use a predetermined ddname
as a work area. The ISPF initialization exit could allocate and open
a data set to this ddname. Each PDF exit could read and write to the
data set as needed. The ISPF termination exit could close and free
the data set.