On z/OS systems, the rapid purge utility for a DB2 event database
is implemented using the DB2 load utility.
Why and when to perform this task
To purge the inactive bucket:
Steps for this task
- Use the eventbucket.jacl command to identify the inactive
bucket (bucket 0 or bucket 1).
- Upload the appropriate utility control file. These files
are generated during database configuration and are located in the profile_path/event/dbscripts/db2zos
directory (profile_path is the path to the directory containing
the profile for the WebSphere ESB runtime environment. Upload one
of the following files:
- If bucket 0 is inactive, upload fastpurge00.ctl.
- If bucket 1 is inactive, upload fastpurge01.ctl.
Note: The control file must be uploaded with a fixed record format
and a logical record length of 80.
- On the z/OS host, go to the ISPF DB2I Primary Option Menu and select
the Utilities option.
- Specify the following information:
Field |
Value |
Function |
EDITJCL |
Utility |
LOAD |
Statement Data Set |
The name of the data set containing the uploaded control file |
LISTDEF |
NO |
Template |
NO |
- Press the Enter key to continue to the next panel.
- In the recdsn entry field, specify the name of the data set containing
the uploaded control file.
- Press the Enter key. The JCL script to purge the
inactive bucket is generated.
- Press the Enter key to clear the output messages.
- Edit the generated JCL script as needed.
- Submit the JCL script.