Capturing Transactions

When a transaction occurs that fits the criteria of a rule that is flagged to capture, a captured transaction is created. The captured transaction can be viewed and edited using the Work With Captured Transactions panel. Subsequent identical transactions are recorded in the incremental count within the captured transaction record. Captured transactions can be memorized and associated with rules specific to that transaction. (See Memorizing Transactions.)

Prerequisites to Capturing Transactions

You must do the following before you can begin capturing transactions:

Activate exit programs. See Activating Powertech Exit Point Manager, earlier in this User Guide for complete information on activation.
The job SUMCAPTRAN, in the PTWRKMGT subsystem, must be running before you can display captured transactions. The SUMCAPTRAN job starts automatically when you select option 10, Work with Captured Transactions, from the Exit Point Manager Main Menu. If it doesn't start automatically, which can occur if it previously ended abnormally, enter the command LENDCAPSUM to reset the job.

Capturing transactions

NOTE: We recommend that you capture the transactions at either the Server or Function level, rather than capturing all transactions for all servers. Capturing all transactions, for all servers, could produce a very large log file in a very short period of time. In addition, you should capture transactions only for the servers, server functions, or the particular user for which you want to enable transaction security.

To start capturing transactions, select option 1 from the Exit Point Manager Main Menu to display the Work with Security by Server panel.
On the Work with Security by Server panel, select the server for which you want to capture transactions. You can select to capture either user authorities by entering UA, Edit User Authority, or LA, Edit Location Authority, for the server.
When the Work with Security by User (or Location) panel displays, choose 2 for the *PUBLIC rule, set the Capture flag to Y (Yes), and press Enter. The confirmation message User Rule(s) successfully updated displays at the bottom of the panel.

When any transactions occur using the selected server/function, Exit Point Manager will capture them.

To memorize a captured transaction, see Memorizing Transactions.

About SUMCAPTRAN

You can verify that the SUMCAPTRAN job is running by issuing the WRKACTJOB command. SUMCAPTRAN should appear in the Subsystem/Job column on the Work with Active Jobs panel. The SUMCAPTRAN job runs in the PTWRKMGT subsystem.
If necessary, you can start the captured transaction subsystem manually by entering the LSTRCAPSUM command on a command line.
The default SUMCAPTRAN delay time is 120 seconds. You can use the LCHGCAPSUM command to reset the delay time, journal receiver delete handling, and change the last captured date/time.
When you display the Work with Captured Transactions panel, the summarization process starts automatically and runs every 5 minutes to check if there are new transactions to consolidate. It can take up to 5 minutes before a new captured transaction displays on the panel.
To end the summarization process, use the LENDCAPSUM command.